any ideas why BFGMiner won't pick up my antminer u1's and block erupters at the same time? I'm running Wheezy Debian and start it like this:
./bfgminer -S antminer:all --set-device antminer:clock=x0981 -S erupter:all --icarus-options 115200:1:1 --icarus-timing 3.0=100 -o pool -u user -p password
The two antminer U1's show up but only has at 500 mhs and the erutpers don't show up at all. I have to go into "M" "+" and type all to pick up the block erupters...are there other things besides bfgminer 3.10 I need installed on the linux machine?
Thanks!~
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 56. (Read 1193208 times)
January 21, 2014, 06:18:37 PM
January 21, 2014, 05:54:56 PM
it is not a susicious link whoever tampered with my text message it is a link to an online calculator to help pee ople work out how much they get based on the hash rates vs difficulty level.
and wots with this message i cant reply over 5 minte
i forgot wot i was going to say and type now...
and wots with this message i cant reply over 5 minte
i forgot wot i was going to say and type now...
January 21, 2014, 05:44:49 PM
ah f.uck it i wasted my moni 6g is dialup compared to the +30g range wots the point the difficulty increases so frequent wots the point in months to c.um 30gh will be new standard for dialup
i hath 3 erupters so 6gh = $42.10 a month and in 5 months from now ill hath 0.05 bitcoins woo hoo.
http://[Suspicious link removed]/8u3urad - calculator
i am addicted to this tempted to buy a huge 30-60gb but is it worth it i am so confused
i hath 3 erupters so 6gh = $42.10 a month and in 5 months from now ill hath 0.05 bitcoins woo hoo.
http://[Suspicious link removed]/8u3urad - calculator
i am addicted to this tempted to buy a huge 30-60gb but is it worth it i am so confused
January 21, 2014, 03:37:22 PM
antminer u1 wont overclock on bfgminer 3.10.0
--set-device antminer:clock=x0A81 2.2gh/s doesnt work only stays at 1.6gh/s
--set-device antminer:clock=x0982 2.0gh/s this works however i want to use 0a81
dose dose bfg miner not like letters in the code or something wot is going on im losing 10% hash rate because of it wot do i do
--set-device antminer:clock=x0A81 2.2gh/s doesnt work only stays at 1.6gh/s
--set-device antminer:clock=x0982 2.0gh/s this works however i want to use 0a81
dose dose bfg miner not like letters in the code or something wot is going on im losing 10% hash rate because of it wot do i do
Mine run rock steady at =x0981
I think to go higher reliably you have to change the resistors to give ASIC chips more power.
Just stick with 2.0ghash
January 21, 2014, 02:34:26 PM
antminer u1 wont overclock on bfgminer 3.10.0
--set-device antminer:clock=x0A81 2.2gh/s doesnt work only stays at 1.6gh/s
--set-device antminer:clock=x0982 2.0gh/s this works however i want to use 0a81
dose dose bfg miner not like letters in the code or something wot is going on im losing 10% hash rate because of it wot do i do
--set-device antminer:clock=x0A81 2.2gh/s doesnt work only stays at 1.6gh/s
--set-device antminer:clock=x0982 2.0gh/s this works however i want to use 0a81
dose dose bfg miner not like letters in the code or something wot is going on im losing 10% hash rate because of it wot do i do
I haven't found it successfully overclocks at 0A81; it has lots of HW errors. I just use 0981.
January 21, 2014, 11:43:26 AM
antminer u1 wont overclock on bfgminer 3.10.0
--set-device antminer:clock=x0A81 2.2gh/s doesnt work only stays at 1.6gh/s
--set-device antminer:clock=x0982 2.0gh/s this works however i want to use 0a81
dose dose bfg miner not like letters in the code or something wot is going on im losing 10% hash rate because of it wot do i do
--set-device antminer:clock=x0A81 2.2gh/s doesnt work only stays at 1.6gh/s
--set-device antminer:clock=x0982 2.0gh/s this works however i want to use 0a81
dose dose bfg miner not like letters in the code or something wot is going on im losing 10% hash rate because of it wot do i do
January 21, 2014, 02:12:31 AM
I am unable to get any hash rate:
I don't see any instructions on how to set CPU/GPU parameter.
I don't see any instructions on how to set CPU/GPU parameter.
I'm curious, are your trying to use scrypt or sha256?
January 21, 2014, 01:54:41 AM
I keep getting a thermal cut off REST on my 2 r9 290x they do run hot they run at 95c but thats normal for this card from what I see is there a way to adjust the cut off to say 98c ? to reduce the thermal cut off and rest times but still protect the system? Thanks!
January 20, 2014, 08:43:09 PM
I am unable to get any hash rate:
I don't see any instructions on how to set CPU/GPU parameter.
I don't see any instructions on how to set CPU/GPU parameter.
January 20, 2014, 08:03:39 PM
listen up wot is going on?
i have an antminer u1 and im using bfgminer 3.10.0
antminer is clocked to 2.2gh/s using code 0A81 however... it does not clock at that speed it just stays at the default 1.6gh/s
however... i can set it second best at 2gh/s using code 0981 and it stays at that speed.
WOT is going on?? doth the program not like letters in the freq code or?
clocking 2.2gh/s worked in cgminer however... i switched to bfg as i dont want to pull multiple erupters out of usb ports incase they get ted broken.
in any case... im losing 10% hash rate because of this WOT DO I DO should i continue with this ponzi scheme just wot do i do.
in any case wot is a hash error rate? if there is too much will the work be destroyed?
regarded
ipoomyself
i have an antminer u1 and im using bfgminer 3.10.0
antminer is clocked to 2.2gh/s using code 0A81 however... it does not clock at that speed it just stays at the default 1.6gh/s
however... i can set it second best at 2gh/s using code 0981 and it stays at that speed.
WOT is going on?? doth the program not like letters in the freq code or?
clocking 2.2gh/s worked in cgminer however... i switched to bfg as i dont want to pull multiple erupters out of usb ports incase they get ted broken.
in any case... im losing 10% hash rate because of this WOT DO I DO should i continue with this ponzi scheme just wot do i do.
in any case wot is a hash error rate? if there is too much will the work be destroyed?
regarded
ipoomyself
January 20, 2014, 06:26:04 PM
I see we are having the same issue with HW failures with the Block Erupters but the
ANTs are running fine. I barely had any issues with the previous version. Do we need
to add something to the command line to change the timing or something?
ANTs are running fine. I barely had any issues with the previous version. Do we need
to add something to the command line to change the timing or something?
January 20, 2014, 01:13:09 AM
ive been running in v3 for 8 hours at 0981 no HW errors what so ever 
getting 5 more antminers today ill post a update on them later
if u want my command line here it is
that whole switching timing of the icarus is just to make it run steadier i found that out couple days ago
https://i.imgur.com/VoyQG8R.jpg
getting 5 more antminers today ill post a update on them later
if u want my command line here it is Code:
bfgminer.exe -S erupter:all -S antminer:all -S all --set-device antminer:clock=x0981 --icarus-options 115200:2:2 --icarus-timing 2.5=90 --klondike-options 362:65 --weighed-stats
https://i.imgur.com/VoyQG8R.jpg
Hi =)
I've tried your command in windows with 3.10.0 but the hashrate of the ant-usb drop to 1Gh..
The problem seem to be the arguments
--icarus-options 115200:2:2 --icarus-timing 2.5=90
for my erupters: if I remove them the speed of ant miners is fine..
Any ideas?
thanks =)
I am running
Code:
bfgminer.exe -S antminer:all -S erupter:all -S all --set-device antminer:clock=x0981 --icarus-options 115200:2:2 --icarus-timing 2.5=90
in that order, but I have it saved to my .conf file. My two ANTs (AMUs) have been running at 1.99 and 2.01, and my 9 BEs are running steady in ranges from 330.2 to 336.2 with my stats being from a continious run of over two days:
Code:
bfgminer version 3.9.0 - Started: [2014-01-16 19:02:14] - [ 2 days 16:38:38]
[M]anage devices [P]ool management [S]ettings [D]isplay options [H]elp [Q]uit
Connected to stratum.mining.eligius.st diff 8 with stratum as user 1QEquFYkmCFu
Block: ...042333b5 #281355 Diff:1.79G (12.81Ph/s) Started: [11:40:41]
ST:23 F:3 NB:452 AS:5 BW:[ 69/ 60 B/s] E:51.06 I: 163uBTC/hr BS:376k
12/13 49.0C | 13.17/12.92/13.99Gh/s | A:91460 R:285+67(.37%) HW:11608/1.5%
--------------------------------------------------------------------------------
BFL 0: 47.0C | 7.32/ 7.20/ 6.99Gh/s | A:45661 R:204+34(.50%) HW:10616/2.7%
AMU 0: | 1.26/ 1.07/ 2.01Gh/s | A:13230 R: 25+ 9(.24%) HW: 0/none
AMU 1: | 1.10/ 1.07/ 1.99Gh/s | A:12938 R: 30+ 9(.31%) HW: 0/none
BES 0: | 359.4/398.4/334.8Mh/s | A: 2171 R: 2+ 2(.18%) HW: 104/.57%
BES 1: | 358.6/398.3/336.2Mh/s | A: 2167 R: 1+ 3(.18%) HW: 99/.54%
BES 2: | 359.9/398.5/332.4Mh/s | A: 2190 R: 1+ 3(.18%) HW: 101/.56%
BES 3: | 358.8/398.3/330.2Mh/s | A: 2184 R: 6+ 2(.36%) HW: 110/.61%
BES 4: | 358.6/398.5/335.8Mh/s | A: 2207 R: 2+ 2(.18%) HW: 108/.59%
BES 5: | 360.0/398.6/334.7Mh/s | A: 2172 R: 2+ 0(.09%) HW: 118/.65%
BES 6: | 360.6/398.4/335.1Mh/s | A: 2175 R: 2+ 0(.09%) HW: 127/.69%
BES 7: | 358.4/398.6/330.8Mh/s | A: 2208 R: 4+ 3(.19%) HW: 94/.52%
BES 8: | 358.8/398.5/333.2Mh/s | A: 2160 R: 6+ 0(.20%) HW: 131/.72%
Mind you, I am running on an 8 year old Dell Inspiron 6000 laptop, 20GB partition for Windows7_32bit with only 500MB free on drive, 2GB of RAM, and BFGminer 3.9.0 by nwools V3.
I have not had time to test 3.10.0
yea it should run fine ive been running at a steady 17ghs since 3.1.0 came out and hasnt stopped or dropped my hash rate im actually waiting to get a 5v 1amp transformer so i can add it to my little set up open up the wires and get a good 5v 5amps for my cheep-o-matic chinese usb hub because one of my miners doesn't have enought power to go past 1.6ghs
January 19, 2014, 07:54:19 PM
I have noticed with the latest BFGMiner on both Windows 32bit and 64bit that sometimes when the ice fury miners pickup no work available they get stuck in this place, its not until I restart bfgminer again that they finally start picking up work.
It happens for me mostly if I need to restart my P2Pool server, my avy's which connect directly to my server don't have this problem I have only noticed this with my ice fury's, so I am not sure if it's 100% related to bfgminer but it might be something worth checking out, or if you need something more from me let know I would be happy to help.
Thanks,
It happens for me mostly if I need to restart my P2Pool server, my avy's which connect directly to my server don't have this problem I have only noticed this with my ice fury's, so I am not sure if it's 100% related to bfgminer but it might be something worth checking out, or if you need something more from me let know I would be happy to help.
Thanks,
January 19, 2014, 01:46:19 PM
i may have found 2 oddities either with bfgminer, linux, or my choice of host system. idk but ill post and get thoughts.
i presently run my miners consisting of 2 NFY, 1 BPM, and 2 KLN K16 all off of 1 dlink dub-h7 connected to a Beaglebone black.
i presently run my miners consisting of 2 NFY, 1 BPM, and 2 KLN K16 all off of 1 dlink dub-h7 connected to a Beaglebone black.
All of your issues sound more like problems with the BBB than bfgminer. If you pop over to the MinePeon thread you'll see several of us all have the same issues:
https://bitcointalksearch.org/topic/m.4567911
From what others are saying it has more to do with the stability of USB on the BBB. It doesn't like the "probing" bfgminer does for USB devices. It may work ok once or twice, but after than you risk locking up the device.
Some folks are reported success by getting a successful run of bfgminer -d? out of the way and then launching it manually for each device thereafter, e.g.
Code:
bfgminer -S antminer:somepath -S antminer:somepath -S nanofury:somepath etc etc
This avoids constantly probing once you know the paths.
only issue is in debian the NFY doesnt have absolute unchanging path like the BF1 (/dev/ttyACMx). same with the klondikes.
anyway i let bfg just push through and Point 3 i made is just a timeout issue. itll appear to lockup while trying to ID and claim the second klondike. so it has to try again. second time it succeeds and all is fine and dandy.
January 19, 2014, 12:41:28 PM
ive been running in v3 for 8 hours at 0981 no HW errors what so ever
getting 5 more antminers today ill post a update on them later if u want my command line here it is
that whole switching timing of the icarus is just to make it run steadier i found that out couple days ago
https://i.imgur.com/VoyQG8R.jpg
getting 5 more antminers today ill post a update on them later
if u want my command line here it is Code:
bfgminer.exe -S erupter:all -S antminer:all -S all --set-device antminer:clock=x0981 --icarus-options 115200:2:2 --icarus-timing 2.5=90 --klondike-options 362:65 --weighed-stats
https://i.imgur.com/VoyQG8R.jpg
Hi =)
I've tried your command in windows with 3.10.0 but the hashrate of the ant-usb drop to 1Gh..
The problem seem to be the arguments
--icarus-options 115200:2:2 --icarus-timing 2.5=90
for my erupters: if I remove them the speed of ant miners is fine..
Any ideas?
thanks =)
I am running
Code:
bfgminer.exe -S antminer:all -S erupter:all -S all --set-device antminer:clock=x0981 --icarus-options 115200:2:2 --icarus-timing 2.5=90
in that order, but I have it saved to my .conf file. My two ANTs (AMUs) have been running at 1.99 and 2.01, and my 9 BEs are running steady in ranges from 330.2 to 336.2 with my stats being from a continious run of over two days:
Code:
bfgminer version 3.9.0 - Started: [2014-01-16 19:02:14] - [ 2 days 16:38:38]
[M]anage devices [P]ool management [S]ettings [D]isplay options [H]elp [Q]uit
Connected to stratum.mining.eligius.st diff 8 with stratum as user 1QEquFYkmCFu
Block: ...042333b5 #281355 Diff:1.79G (12.81Ph/s) Started: [11:40:41]
ST:23 F:3 NB:452 AS:5 BW:[ 69/ 60 B/s] E:51.06 I: 163uBTC/hr BS:376k
12/13 49.0C | 13.17/12.92/13.99Gh/s | A:91460 R:285+67(.37%) HW:11608/1.5%
--------------------------------------------------------------------------------
BFL 0: 47.0C | 7.32/ 7.20/ 6.99Gh/s | A:45661 R:204+34(.50%) HW:10616/2.7%
AMU 0: | 1.26/ 1.07/ 2.01Gh/s | A:13230 R: 25+ 9(.24%) HW: 0/none
AMU 1: | 1.10/ 1.07/ 1.99Gh/s | A:12938 R: 30+ 9(.31%) HW: 0/none
BES 0: | 359.4/398.4/334.8Mh/s | A: 2171 R: 2+ 2(.18%) HW: 104/.57%
BES 1: | 358.6/398.3/336.2Mh/s | A: 2167 R: 1+ 3(.18%) HW: 99/.54%
BES 2: | 359.9/398.5/332.4Mh/s | A: 2190 R: 1+ 3(.18%) HW: 101/.56%
BES 3: | 358.8/398.3/330.2Mh/s | A: 2184 R: 6+ 2(.36%) HW: 110/.61%
BES 4: | 358.6/398.5/335.8Mh/s | A: 2207 R: 2+ 2(.18%) HW: 108/.59%
BES 5: | 360.0/398.6/334.7Mh/s | A: 2172 R: 2+ 0(.09%) HW: 118/.65%
BES 6: | 360.6/398.4/335.1Mh/s | A: 2175 R: 2+ 0(.09%) HW: 127/.69%
BES 7: | 358.4/398.6/330.8Mh/s | A: 2208 R: 4+ 3(.19%) HW: 94/.52%
BES 8: | 358.8/398.5/333.2Mh/s | A: 2160 R: 6+ 0(.20%) HW: 131/.72%
Mind you, I am running on an 8 year old Dell Inspiron 6000 laptop, 20GB partition for Windows7_32bit with only 500MB free on drive, 2GB of RAM, and BFGminer 3.9.0 by nwools V3.
I have not had time to test 3.10.0
January 19, 2014, 12:17:16 PM
do you gain anything by using the icarus arguments? Erupters are fixed clock. if you use "-S erupter:all" then the extra arguments are not needed.
Little gain yes, I see the Mh goining up for 30/40 Mh.
I know with cgminer was some sort of timing bug... but with bfgminer isn't true Mh?
January 19, 2014, 12:13:52 PM
ive been running in v3 for 8 hours at 0981 no HW errors what so ever
getting 5 more antminers today ill post a update on them later if u want my command line here it is
that whole switching timing of the icarus is just to make it run steadier i found that out couple days ago
https://i.imgur.com/VoyQG8R.jpg
getting 5 more antminers today ill post a update on them later
if u want my command line here it is Code:
bfgminer.exe -S erupter:all -S antminer:all -S all --set-device antminer:clock=x0981 --icarus-options 115200:2:2 --icarus-timing 2.5=90 --klondike-options 362:65 --weighed-stats
https://i.imgur.com/VoyQG8R.jpg
Hi =)
I've tried your command in windows with 3.10.0 but the hashrate of the ant-usb drop to 1Gh..
The problem seem to be the arguments
--icarus-options 115200:2:2 --icarus-timing 2.5=90
for my erupters: if I remove them the speed of ant miners is fine..
Any ideas?
thanks =)
January 19, 2014, 11:58:28 AM
ive been running in v3 for 8 hours at 0981 no HW errors what so ever
getting 5 more antminers today ill post a update on them later if u want my command line here it is
that whole switching timing of the icarus is just to make it run steadier i found that out couple days ago
https://i.imgur.com/VoyQG8R.jpg
getting 5 more antminers today ill post a update on them later
if u want my command line here it is Code:
bfgminer.exe -S erupter:all -S antminer:all -S all --set-device antminer:clock=x0981 --icarus-options 115200:2:2 --icarus-timing 2.5=90 --klondike-options 362:65 --weighed-stats
https://i.imgur.com/VoyQG8R.jpg
Hi =)
I've tried your command in windows with 3.10.0 but the hashrate of the ant-usb drop to 1Gh..
The problem seem to be the arguments
--icarus-options 115200:2:2 --icarus-timing 2.5=90
for my erupters: if I remove them the speed of ant miners is fine..
Any ideas?
thanks =)
January 19, 2014, 10:14:03 AM
i may have found 2 oddities either with bfgminer, linux, or my choice of host system. idk but ill post and get thoughts.
i presently run my miners consisting of 2 NFY, 1 BPM, and 2 KLN K16 all off of 1 dlink dub-h7 connected to a Beaglebone black.
i presently run my miners consisting of 2 NFY, 1 BPM, and 2 KLN K16 all off of 1 dlink dub-h7 connected to a Beaglebone black.
All of your issues sound more like problems with the BBB than bfgminer. If you pop over to the MinePeon thread you'll see several of us all have the same issues:
https://bitcointalksearch.org/topic/m.4567911
From what others are saying it has more to do with the stability of USB on the BBB. It doesn't like the "probing" bfgminer does for USB devices. It may work ok once or twice, but after than you risk locking up the device.
Some folks are reported success by getting a successful run of bfgminer -d? out of the way and then launching it manually for each device thereafter, e.g.
Code:
bfgminer -S antminer:somepath -S antminer:somepath -S nanofury:somepath etc etc
This avoids constantly probing once you know the paths.
January 19, 2014, 05:44:49 AM
i may have found 2 oddities either with bfgminer, linux, or my choice of host system. idk but ill post and get thoughts.
i presently run my miners consisting of 2 NFY, 1 BPM, and 2 KLN K16 all off of 1 dlink dub-h7 connected to a Beaglebone black.
1)
Recently i have been running into an issue of one or both of the NFY devices locking up (have to kill bfgminer, and replug it to get the enabled LED to go off). i have a rising suspicion that one of the changes from tag 3.9.0 to 3.10.0 may be culprit, or the fact that the two downstream charging ports on the hub are enumerated in linux as HID devices(dafuz?)
but for now and the sake of mining (that is, until i get another NFY or two) it seems switching it all to "cheap" 7port hub from MCM.
2)
I am unable to use autodetect to start the BPM or else autodetect locks up klondike detection. i must add -S bigpic:noauto then M+ after startup
3)(*Bonus)
Idk if its bfgminer or the KLN FW but if i shutdown bfgminer, the restart it immediately the klondikes are picked up, initialized(i can watch the red Tx/Rx LEDS flash), and even report temperatures. But they donot report any hashes. only way to get them going again is to kill bfg and power cycle the klondikes.
i presently run my miners consisting of 2 NFY, 1 BPM, and 2 KLN K16 all off of 1 dlink dub-h7 connected to a Beaglebone black.
1)
Recently i have been running into an issue of one or both of the NFY devices locking up (have to kill bfgminer, and replug it to get the enabled LED to go off). i have a rising suspicion that one of the changes from tag 3.9.0 to 3.10.0 may be culprit, or the fact that the two downstream charging ports on the hub are enumerated in linux as HID devices(dafuz?)
but for now and the sake of mining (that is, until i get another NFY or two) it seems switching it all to "cheap" 7port hub from MCM.
2)
I am unable to use autodetect to start the BPM or else autodetect locks up klondike detection. i must add -S bigpic:noauto then M+ after startup
3)(*Bonus)
Idk if its bfgminer or the KLN FW but if i shutdown bfgminer, the restart it immediately the klondikes are picked up, initialized(i can watch the red Tx/Rx LEDS flash), and even report temperatures. But they donot report any hashes. only way to get them going again is to kill bfg and power cycle the klondikes.
Jump to: