|
Thanks for the updates, the only worse than bad news is no news.
|
|
|
|
I guess we are down all my ants beeping. Thought it was my end this sucks  |
|
|
|
Most of the above are NTP related.
Have you tried disabling NTP?
Just to see where that gets you.
The damn thing has gone completely lame. both blades dead, the led's on the wrt board are lit but the one under the rj45 connector is dead. Reset has no affect. will try swapping PSU but I fear the WRT board is shit. Sounds like a connection problem to me. EDIT: Can you ping google.com from your miner? Tried a different PSU same problem, blades dead, rj45 jack wouldn't connect. For shits and giggles tried a new cable.. seems to be working but its worked for awhile and crapped out before. will update if it makes it through the nite. Thanks for all the suggestions. Bro if it powers up and you see lights coming on then it works. You just need to set it up properly. Just my opinion... [/quote] It's not my cherry, #21 it's just lame. Stuff happens. |
|
|
|
Most of the above are NTP related.
Have you tried disabling NTP?
Just to see where that gets you.
The damn thing has gone completely lame. both blades dead, the led's on the wrt board are lit but the one under the rj45 connector is dead. Reset has no affect. will try swapping PSU but I fear the WRT board is shit. Sounds like a connection problem to me. EDIT: Can you ping google.com from your miner? Tried a different PSU same problem, blades dead, rj45 jack wouldn't connect. For shits and giggles tried a new cable.. seems to be working but its worked for awhile and crapped out before. will update if it makes it through the nite. Thanks for all the suggestions. [/quote] Crapped out again both blades dead. Open wrt card? Anyone done an RMA with bitmain? |
|
|
|
Most of the above are NTP related.
Have you tried disabling NTP?
Just to see where that gets you.
The damn thing has gone completely lame. both blades dead, the led's on the wrt board are lit but the one under the rj45 connector is dead. Reset has no affect. will try swapping PSU but I fear the WRT board is shit. Sounds like a connection problem to me. EDIT: Can you ping google.com from your miner? [/quote] Tried a different PSU same problem, blades dead, rj45 jack wouldn't connect. For shits and giggles tried a new cable.. seems to be working but its worked for awhile and crapped out before. will update if it makes it through the nite. Thanks for all the suggestions. |
|
|
|
|
Most of the above are NTP related.
Have you tried disabling NTP?
Just to see where that gets you.
[/quote]
The damn thing has gone completely lame. both blades dead, the led's on the wrt board are lit but the one under the rj45 connector is dead. Reset has no affect. will try swapping PSU but I fear the WRT board is shit.
|
|
|
|
|
Fri Mar 7 10:22:12 2014 daemon.notice netifd: lan (631): Sending discover...
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 67.18.187.111
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 129.250.35.251
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 184.105.182.7
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 184.22.97.162
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x01 offset 420621.609588 delay 0.028075 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x01 offset 420621.612023 delay 0.053287 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x01 offset 420621.613557 delay 0.054871 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:13 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x01 offset 420621.613231 delay 0.105110 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x03 offset 420621.613637 delay 0.055955 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:14 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x03 offset 420621.612570 delay 0.104104 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x03 offset 420621.611508 delay 0.032669 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x07 offset 420621.613920 delay 0.057415 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:15 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x03 offset 420621.615444 delay 0.059030 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x07 offset 420621.614455 delay 0.057509 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:16 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x07 offset 420621.609121 delay 0.096621 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x07 offset 420621.611499 delay 0.032790 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x0f offset 420621.614046 delay 0.057432 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:17 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x0f offset 420621.615462 delay 0.059072 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x0f offset 420621.618661 delay 0.045978 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 67.18.187.111: reach 0x1f offset 420621.621467 delay 0.071996 status 0x24 strat 2 refid 0x808a8dac rootdelay 0.016556
Fri Mar 7 10:22:18 2014 daemon.info sysinit: ntpd: reply from 184.105.182.7: reach 0x0f offset 420621.620041 delay 0.118584 status 0x24 strat 2 refid 0xd8dafeca rootdelay 0.001190
Fri Mar 7 10:22:19 2014 daemon.info sysinit: ntpd: sent query to 184.22.97.162
Fri Mar 7 10:22:19 2014 daemon.info sysinit: ntpd: reply from 184.22.97.162: reach 0x1f offset 420621.610403 delay 0.049994 status 0x24 strat 2 refid 0x8076190c rootdelay 0.043366
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 67.18.187.111
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 129.250.35.251
Fri Mar 7 10:22:20 2014 daemon.info sysinit: ntpd: sent query to 184.105.182.7
Wed Mar 12 07:12:42 2014 daemon.info sysinit: ntpd: reply from 129.250.35.251: reach 0x1f offset 420621.610769 delay 0.032257 status 0x24 strat 2 refid 0xd133a1ee rootdelay 0.005890
Wed Mar 12 07:12:42 2014 daemon.info sysinit: ntpd: setting clock to Wed Mar 12 07:12:42 CST 2014 (offset 420621.610896s)
Wed Mar 12 07:12:42 2014 daemon.info sysinit: --bitmain-options 115200:32:8:36:393.75:5f05 -o Stratum.bitcoin.cz:3333 -O -o stratum.mining.eligius.st:3334 -O 17UhZWXLyiHmPmAb4VdFweGWRYY52qjxwp:123 --api-listen --api-network
Wed Mar 12 07:12:42 2014 daemon.info sysinit: - init complete -
Wed Mar 12 07:12:42 2014 kern.info kernel: [ 33.830000] bitmain 1-1.1:1.0: USB Bitmain asic #0 now disconnected
Wed Mar 12 07:13:23 2014 cron.err crond[575]: time disparity of 7011 minutes detected
Wed Mar 12 07:15:01 2014 cron.info crond[575]: crond: USER root pid 859 cmd /usr/bin/cgminer-monitor
|
|
|
|
Hi, have and Ant that just started to shut down on me. This morning I noticed the green led's on the outer blades were both off. The Wrt board lights were still on and the ethernet lights were flashing as normal. Tried to log into it but couldn't. Did a reboot and all was well, just got home and the same problem. Anyone else had this happen or have any ideas? I'll log in now and see if anything looks weird. Thanks
Sounds like a PSU problem to me. What PSU are you using? CX 600 393MHZ it started and was working fine compared the sys log to other ants and it was completely different. Tried logging back in and got the following /usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'. The called action terminated with an exception: /usr/lib/lua/luci/sauth.lua:87: Session data invalid! stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194> try 375Mhz and slowly bring it up. I think that your PSU cannot handle it. Maybe a more experienced member can verify this, but I have heard that other users had probs with the cx600. Personally I use one cx750 for each and they are not even overclocked. I'll give it a try will post the sys log after reboot I apologize in advance for the long post coming. Hopefully someone will see what it is, just got it Monday. |
|
|
|
Hi, have and Ant that just started to shut down on me. This morning I noticed the green led's on the outer blades were both off. The Wrt board lights were still on and the ethernet lights were flashing as normal. Tried to log into it but couldn't. Did a reboot and all was well, just got home and the same problem. Anyone else had this happen or have any ideas? I'll log in now and see if anything looks weird. Thanks
Sounds like a PSU problem to me. What PSU are you using? CX 600 393MHZ it started and was working fine compared the sys log to other ants and it was completely different. Tried logging back in and got the following /usr/lib/lua/luci/dispatcher.lua:448: Failed to execute function dispatcher target for entry '/'. The called action terminated with an exception: /usr/lib/lua/luci/sauth.lua:87: Session data invalid! stack traceback: [C]: in function 'assert' /usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch' /usr/lib/lua/luci/dispatcher.lua:195: in function </usr/lib/lua/luci/dispatcher.lua:194> |
|
|
|
|
Hi, have and Ant that just started to shut down on me. This morning I noticed the green led's on the outer blades were both off. The Wrt board lights were still on and the ethernet lights were flashing as normal. Tried to log into it but couldn't. Did a reboot and all was well, just got home and the same problem. Anyone else had this happen or have any ideas? I'll log in now and see if anything looks weird. Thanks
|
|
|
|
Thanks have a bunch of these i need to install and now I don't need to pull one out to size it. |
|
|
|
Worked out a secure way to do a manual payout.
Majority of queue was paid, minus some blocks that are not yet confirmed. Stats should reflect this shortly.
278.49192020 BTC in manual payments applied to balances from tx 8ff569995ff56632309fcf968d2a30beda1140ede49f4460783a35f1b2f791b3
50.12648701 BTC in manual payments applied to balances from tx 2b24410cc1dab9f3b4f1de9937e627a98b56838f563ff4827f01890731ea3200
125.06159973 BTC in manual payments applied to balances from tx 0bb57f6e38012c86d4c5a28c904f2675082859147921a707d48961015a3e5057
964.90392745 BTC in manual payments applied to balances from tx dbab1c84db23abc33c2c89a650b23e2996e14e5876334d083f7281b62e3ef898
I will do another when more coins mature to 120+ confirms.
Close to a $1 million in payouts. How many CEO's do we know that run a $250 million dollar business in his spare time on tips? You guys should charge and hire a profession staff. My hat is off to you though. There are very very few people in this world that would work 12 hour days handling that massive amount of money for almost zero pay, and NOT be tempted to skim some. Disclaimer: not a troll post Why bitcoin can go from $1000 to $1 in a day. LOL... wizkid digging through his couch cushions looking for millions of dollars  |
|
|
|
Bitmain always ships. Usually get tracking the day before it arrives, hell they ship quick faster than newegg. If your order is confirmed you'll get your Ant. And if your not happy with the product or service there's always BFL  |
|
|
|
AUTO-NOTICE: The CPPSRB reward system appears to be in fail-safe mode.
Some stats are likely not updating as they should right now (128/256 second hash rates, balances, balance graph, payout queue). These items will correct themselves soon when CPPSRB is out of fail safe mode. This can take several hours. No earnings are lost as long as your shares are accepted! Sorry for the inconvenience! 3 times in 3 days? https://i.imgur.com/KzEIRzT.jpg This is one of Eligius's greatest advantages "Low Variance"  |
|
|
|
I am not going to claim much technical knowledge about chips.. but from what I read, sha2 asic chips gives up error checking for speed, hence the HW errors...
as long as the pool is reporting a good hashrate, which is estimated by accepted shares.. then your good to go, the pool pays you for your shares!!
It's all about the balance. If it's too much HW, you're losing accepted shares but if your overall hashrate is much higher, it could be desirable anyway. Just have to find the sweet spot. 393.75mhz has worked best for me. Mine: 375Mhz - 195 or so GHs - almost no HW errors 393.75Mhz - 204 GHs - 0.06% HW 400Mhz - 206 GHs - 1.98% HW The HW seems miniscule in the example above, but 393.75 resulted in the best Accepted rate. Could you please post the the freq and time out numbers you're using for 393.75? I can't seem to find them in the thread. Thanks option 'freq_value' '5f05' #393.75M option 'chip_freq' '393.75' option 'timeout' '36' Thanks changed a cranky 400 to these and its much happier now. |
|
|
|
|
Gods, I pray it's not a 23,000,000,000 work block....
Eligius had one 23,652,645,952
|
|
|
|
Bitmain you are the best.  Thanks for the surprise on my account. |
|
|
|
I am not going to claim much technical knowledge about chips.. but from what I read, sha2 asic chips gives up error checking for speed, hence the HW errors...
as long as the pool is reporting a good hashrate, which is estimated by accepted shares.. then your good to go, the pool pays you for your shares!!
It's all about the balance. If it's too much HW, you're losing accepted shares but if your overall hashrate is much higher, it could be desirable anyway. Just have to find the sweet spot. 393.75mhz has worked best for me. Mine: 375Mhz - 195 or so GHs - almost no HW errors 393.75Mhz - 204 GHs - 0.06% HW 400Mhz - 206 GHs - 1.98% HW The HW seems miniscule in the example above, but 393.75 resulted in the best Accepted rate. Could you please post the the freq and time out numbers you're using for 393.75? I can't seem to find them in the thread. Thanks |
|
|
|
Hi
How would I set my difficulty on avalons and antminers?
Would I set my password as d=256?
Thanks
Yes, that's all you have to do. Thanks just to be sure which format? d=256 "d=256" Thanks |
|
|
|
|
Show Posts
