Topic: a problem with Blade (10.7GH) (Read 1359 times)
Check the voltages of each bank since they are adjustable?
The only part I ever had trouble with these is the fuse, I burnt it out before. I don't that is your problem here but you might look at the fuse to be sure.
I had a a few of these long ago and 2 had fuse problems, I had to pug a bigger one in.
I had a a few of these long ago and 2 had fuse problems, I had to pug a bigger one in.
It is not worth it to run the blade anymore. W/GHs is too high.
it should work if you can ping the device externally.
it should work if you can ping the device externally.
Yes, I can ping it:
alicja@alicja-desktop ~/bfgminer $ ping 192.168.1.7
PING 192.168.1.7 (192.168.1.7) 56(84) bytes of data.
64 bytes from 192.168.1.7: icmp_req=6 ttl=100 time=1.95 ms
64 bytes from 192.168.1.7: icmp_req=7 ttl=100 time=1.67 ms
64 bytes from 192.168.1.7: icmp_req=8 ttl=100 time=1.44 ms
64 bytes from 192.168.1.7: icmp_req=9 ttl=100 time=1.50 ms
64 bytes from 192.168.1.7: icmp_req=10 ttl=100 time=1.49 ms
64 bytes from 192.168.1.7: icmp_req=11 ttl=100 time=1.99 ms
64 bytes from 192.168.1.7: icmp_req=12 ttl=100 time=1.70 ms
64 bytes from 192.168.1.7: icmp_req=13 ttl=100 time=1.40 ms
64 bytes from 192.168.1.7: icmp_req=14 ttl=100 time=1.78 ms
^C
--- 192.168.1.7 ping statistics ---
14 packets transmitted, 9 received, 35% packet loss, time 13048ms
35% packet loss ?/??? with small packet
It will not mine dude...
try ping 192.168.1.7 -s 1472 --you will see 70-80% packet loss
It is not worth it to run the blade anymore. W/GHs is too high.
it should work if you can ping the device externally.
it should work if you can ping the device externally.
Yes, I can ping it:
alicja@alicja-desktop ~/bfgminer $ ping 192.168.1.7
PING 192.168.1.7 (192.168.1.7) 56(84) bytes of data.
64 bytes from 192.168.1.7: icmp_req=6 ttl=100 time=1.95 ms
64 bytes from 192.168.1.7: icmp_req=7 ttl=100 time=1.67 ms
64 bytes from 192.168.1.7: icmp_req=8 ttl=100 time=1.44 ms
64 bytes from 192.168.1.7: icmp_req=9 ttl=100 time=1.50 ms
64 bytes from 192.168.1.7: icmp_req=10 ttl=100 time=1.49 ms
64 bytes from 192.168.1.7: icmp_req=11 ttl=100 time=1.99 ms
64 bytes from 192.168.1.7: icmp_req=12 ttl=100 time=1.70 ms
64 bytes from 192.168.1.7: icmp_req=13 ttl=100 time=1.40 ms
64 bytes from 192.168.1.7: icmp_req=14 ttl=100 time=1.78 ms
^C
--- 192.168.1.7 ping statistics ---
14 packets transmitted, 9 received, 35% packet loss, time 13048ms
It is not worth it to run the blade anymore. W/GHs is too high.
it should work if you can ping the device externally.
it should work if you can ping the device externally.
Hello
one of my Blade Erupters got its RJ 45 (internet) socket broken, so I've changed it to new one. Now after having it repaired I can see its interface (192.168.1.7:8000) but it doesn't mine (the interface shows 0GH and the blade is not seen in bfgminer). Restarting (by restart button) works, but doesn't help. Restarting bfgminer doesn't help neither. Other Blades are seen by bfgminer and work great.
Is it broken or what? What could I try or check?
one of my Blade Erupters got its RJ 45 (internet) socket broken, so I've changed it to new one. Now after having it repaired I can see its interface (192.168.1.7:8000) but it doesn't mine (the interface shows 0GH and the blade is not seen in bfgminer). Restarting (by restart button) works, but doesn't help. Restarting bfgminer doesn't help neither. Other Blades are seen by bfgminer and work great.
Is it broken or what? What could I try or check?
Jump to: