did i miss the post that explains why miners aren't identified in v3 like they are in v2? for example NFY/ANY are now AMU.
Only AntMiner U1 naming was changed from ANT to AMU (AntMiner U1). This change has no affect on other devices.
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 63. (Read 1193208 times)
January 14, 2014, 07:15:14 PM
Only AntMiner U1 naming was changed from ANT to AMU (AntMiner U1). This change has no affect on other devices.
January 14, 2014, 07:10:23 PM
did i miss the post that explains why miners aren't identified in v3 like they are in v2? for example NFY/ANY are now AMU.
January 14, 2014, 05:56:09 PM
Well v3 doesn't do much better than v2 for me. Same as you I can't OC the U1's even with the new '--set-device antminer:clock=x0981' command. BFG Miner returns an ' unknown option' and cycles through different frequencies before defaulting to 0781.
Are you guys using a .bat file or a regular shortcut?
regular .bat for me. Saved as a desktop shortcut.
Ok after letting v3 run for a bit longer I'm getting no more HW errors compared to oc'ing with v2 which is a relief! Below is my four U1's running at 0881, the rate is slightly off but I'm happy with it now.
Block: ...5aae6b5d #280517 Diff:1.79G (12.81Ph/s) Started: [22:32:57]
ST:15 F:0 NB:5 AS:2 BW:[ 67/ 63 B/s] E:25.08 I:81.01uBTC/hr BS:1.27k
4 | 8.20/ 8.02/ 7.18Gh/s | A:1489 R:5+9(.92%) HW:0/none
--------------------------------------------------------------------------------
AMU 0 : | 2.07/ 2.01/ 1.78Gh/s | A: 353 R:2+2(1.1%) HW:0/none
AMU 1 : | 2.01/ 2.00/ 1.88Gh/s | A: 405 R:1+5(1.3%) HW:0/none
AMU 2 : | 1.99/ 2.01/ 1.82Gh/s | A: 378 R:1+1(.51%) HW:0/none
AMU 3 : | 2.03/ 2.01/ 1.70Gh/s | A: 353 R:1+1(.74%) HW:0/none
--------------------------------------------------------------------------------
I'm still confused with all the 'unknown freq' blurb when I use the new '--set-device antiminer:clock=xHEX' but so long as it works...
January 14, 2014, 02:11:48 PM
Well v3 doesn't do much better than v2 for me. Same as you I can't OC the U1's even with the new '--set-device antminer:clock=x0981' command. BFG Miner returns an ' unknown option' and cycles through different frequencies before defaulting to 0781.
Are you guys using a .bat file or a regular shortcut?
regular .bat for me. Saved as a desktop shortcut.
January 14, 2014, 12:02:18 PM
The overclocking in V3 fails for me.
V2 was the best
V2 was the best
Make sure you are using the correct format. Overclocking should work fine (and more reliably than the version you guys are referencing).
Code:
bfgminer --set-device antiminer:clock=xHEX
I would assume you are still trying to use --set-device antminer:freq instead.
Tried with :clock=0981 and :freq= 0981
I get the same result 2.05Gh at 5sec and 1.97Gh at the pool with HW 2%
when I use clock= there is an error message but everything still works
When I try the V3 files I still get 2.05Gh at 5sec but my pool speed drops to 1.5Gh with HW 2% the extra 0.5Gh just vanishes.
My erupters are on a separate session so the V2 files are reasonable for me.
bro its like this :clock=x0981 with an x infront idk if u messed that up or not but seems to be working fine for me as long as they say its the 3rd one that counts thats all i really need to hear lol
Its the 3rd number that pays.
If I use a higher clock speed It just creates more HW errors. After that you need to start changing resistors.
Well v3 doesn't do much better than v2 for me. Same as you I can't OC the U1's even with the new '--set-device antminer:clock=x0981' command. BFG Miner returns an ' unknown option' and cycles through different frequencies before defaulting to 0781.
Are you guys using a .bat file or a regular shortcut?
January 14, 2014, 11:32:16 AM
Still no Drillbit support...it's only been about 2 months now...
The code is in git, it'll be in 3.10. January 14, 2014, 10:41:20 AM
Hi nwoolls,
I've got the newest version of your 3.9.0 build for the antminers, and I do all the steps for linux - autogen.sh, configure, make, and antminer shows up on the -h switch.
However, even though my ants work with the bitmain cgminer 3.8.5, and with fractalbc's custom cgminer 3.9.0, I can't get your bfgminer to recognize them. bfgminer -d? -S antminer:all shows no devices, yet they're there just fine in lsusb, and of course for the two cgminers. I don't notice any errors during compilation, configure shows it as enabled for the antminer, and I'm using the correct newly-created binary - even called it by the full path just to be sure.
FWIW, this machine is Edubuntu 13.10, 64 bit version.
Any idea what could be going wrong?
I've got the newest version of your 3.9.0 build for the antminers, and I do all the steps for linux - autogen.sh, configure, make, and antminer shows up on the -h switch.
However, even though my ants work with the bitmain cgminer 3.8.5, and with fractalbc's custom cgminer 3.9.0, I can't get your bfgminer to recognize them. bfgminer -d? -S antminer:all shows no devices, yet they're there just fine in lsusb, and of course for the two cgminers. I don't notice any errors during compilation, configure shows it as enabled for the antminer, and I'm using the correct newly-created binary - even called it by the full path just to be sure.
FWIW, this machine is Edubuntu 13.10, 64 bit version.
Any idea what could be going wrong?
Bump.
Anyone else got any hints for me? I can't get nwoolls' bfgminer mods to compile. Been compiling cg/bfgminers for several versions now and this is the first time there's no joy. Is there a problem w/ 64-bit linux maybe? I'm still trying, but at this point not sure where to go next.
January 14, 2014, 10:07:31 AM
The overclocking in V3 fails for me.
V2 was the best
V2 was the best
Make sure you are using the correct format. Overclocking should work fine (and more reliably than the version you guys are referencing).
Code:
bfgminer --set-device antiminer:clock=xHEX
I would assume you are still trying to use --set-device antminer:freq instead.
Tried with :clock=0981 and :freq= 0981
I get the same result 2.05Gh at 5sec and 1.97Gh at the pool with HW 2%
when I use clock= there is an error message but everything still works
When I try the V3 files I still get 2.05Gh at 5sec but my pool speed drops to 1.5Gh with HW 2% the extra 0.5Gh just vanishes.
My erupters are on a separate session so the V2 files are reasonable for me.
bro its like this :clock=x0981 with an x infront idk if u messed that up or not but seems to be working fine for me as long as they say its the 3rd one that counts thats all i really need to hear lol
Its the 3rd number that pays.
If I use a higher clock speed It just creates more HW errors. After that you need to start changing resistors.
January 14, 2014, 09:57:45 AM
The overclocking in V3 fails for me.
V2 was the best
V2 was the best
Make sure you are using the correct format. Overclocking should work fine (and more reliably than the version you guys are referencing).
Code:
bfgminer --set-device antiminer:clock=xHEX
I would assume you are still trying to use --set-device antminer:freq instead.
Tried with :clock=0981 and :freq= 0981
I get the same result 2.05Gh at 5sec and 1.97Gh at the pool with HW 2%
when I use clock= there is an error message but everything still works
When I try the V3 files I still get 2.05Gh at 5sec but my pool speed drops to 1.5Gh with HW 2% the extra 0.5Gh just vanishes.
My erupters are on a separate session so the V2 files are reasonable for me.
bro its like this :clock=x0981 with an x infront idk if u messed that up or not but seems to be working fine for me as long as they say its the 3rd one that counts thats all i really need to hear lol
January 14, 2014, 09:52:21 AM
The overclocking in V3 fails for me.
V2 was the best
V2 was the best
Make sure you are using the correct format. Overclocking should work fine (and more reliably than the version you guys are referencing).
Code:
bfgminer --set-device antiminer:clock=xHEX
I would assume you are still trying to use --set-device antminer:freq instead.
Tried with :clock=0981 and :freq= 0981
I get the same result 2.05Gh at 5sec and 1.97Gh at the pool with HW 2%
when I use clock= there is an error message but everything still works
When I try the V3 files I still get 2.05Gh at 5sec but my pool speed drops to 1.5Gh with HW 2% the extra 0.5Gh just vanishes.
My erupters are on a separate session so the V2 files are reasonable for me.
January 14, 2014, 09:43:08 AM
i tried both still no quite good results i posted how my cgminer looks like
and alright i just dont really know if its all visual i rather just stay with my cgminer for a bit while everything gets fixed maybe?
http://imgur.com/a/786SJ
and alright i just dont really know if its all visual i rather just stay with my cgminer for a bit while everything gets fixed maybe?
http://imgur.com/a/786SJ
You are looking at the wrong numbers. Your picture clearly shows V3 running faster than V2 (look at the 3rd hashrate).
You are also taking pictures after mining has only been running for a few seconds. This is not nearly long enough.
Try the following:
- Run cgminer for 30 minutes - note the number of accepted shares (next to A)
- Run bfgminer with the --weighed-stats argument for 30 minutes and note the number of accepted shares
Compare them.
will do thank you for all your help
edit: ok i see what your saying btw what does the --weighed-stats argument do ?
January 14, 2014, 08:54:07 AM
i tried both still no quite good results i posted how my cgminer looks like
and alright i just dont really know if its all visual i rather just stay with my cgminer for a bit while everything gets fixed maybe?
http://imgur.com/a/786SJ
and alright i just dont really know if its all visual i rather just stay with my cgminer for a bit while everything gets fixed maybe?
http://imgur.com/a/786SJ
You are looking at the wrong numbers. Your picture clearly shows V3 running faster than V2 (look at the 3rd hashrate).
You are also taking pictures after mining has only been running for a few seconds. This is not nearly long enough.
Try the following:
- Run cgminer for 30 minutes - note the number of accepted shares (next to A)
- Run bfgminer with the --weighed-stats argument for 30 minutes and note the number of accepted shares
Compare them.
January 14, 2014, 08:45:34 AM
https://www.dropbox.com/s/nph1hhfqnqzeduf/bfgminer-npw-antminerV1.7z file dates 7th Jan
https://www.dropbox.com/s/s837jkiirzg5mvq/bfgminer-npw-antminerV2.7z file dates 9th Jan
https://www.dropbox.com/s/c7movpxohewides/bfgminer-npw-antminerV3.7z file dates 12thJan
Cheers!
I'll give the v3 a go and see what happens. The overclocking in V3 fails for me.
V2 was the best
thank you mate
i was on v1 lol ill go for v2 try v3 if anything and alright i just dont really know if its all visual i rather just stay with my cgminer for a bit while everything gets fixed maybe?
http://imgur.com/a/786SJ
January 14, 2014, 08:35:15 AM
does anyone else get a problem with their ant miner u1 i get 0.5/0.7/2.0 gh/s out of my ant miner with bfg with cgminer 3.8.5 i get a steady 1.9 - 2.3 gh/s
Yes, a couple of others have reported this issue. It is visual only. The first two numbers are estimates of hashrate for the device. The third is the "effective" hashrate based on shares accepted by the pool. You are getting 2.0+ Gh/s.
January 14, 2014, 08:32:29 AM
The overclocking in V3 fails for me.
V2 was the best
V2 was the best
Make sure you are using the correct format. Overclocking should work fine (and more reliably than the version you guys are referencing).
Code:
bfgminer --set-device antiminer:clock=xHEX
I would assume you are still trying to use --set-device antminer:freq instead.
January 14, 2014, 08:10:41 AM
https://www.dropbox.com/s/nph1hhfqnqzeduf/bfgminer-npw-antminerV1.7z file dates 7th Jan
https://www.dropbox.com/s/s837jkiirzg5mvq/bfgminer-npw-antminerV2.7z file dates 9th Jan
https://www.dropbox.com/s/c7movpxohewides/bfgminer-npw-antminerV3.7z file dates 12thJan
Cheers!
I'll give the v3 a go and see what happens. The overclocking in V3 fails for me.
V2 was the best
thank you mate
i was on v1 lol ill go for v2 try v3 if anything January 14, 2014, 08:04:18 AM
https://www.dropbox.com/s/nph1hhfqnqzeduf/bfgminer-npw-antminerV1.7z file dates 7th Jan
https://www.dropbox.com/s/s837jkiirzg5mvq/bfgminer-npw-antminerV2.7z file dates 9th Jan
https://www.dropbox.com/s/c7movpxohewides/bfgminer-npw-antminerV3.7z file dates 12thJan
Cheers!
I'll give the v3 a go and see what happens. The overclocking in V3 fails for me.
V2 was the best
January 14, 2014, 07:56:52 AM
https://www.dropbox.com/s/nph1hhfqnqzeduf/bfgminer-npw-antminerV1.7z file dates 7th Jan
https://www.dropbox.com/s/s837jkiirzg5mvq/bfgminer-npw-antminerV2.7z file dates 9th Jan
https://www.dropbox.com/s/c7movpxohewides/bfgminer-npw-antminerV3.7z file dates 12thJan
Cheers!
I'll give the v3 a go and see what happens. January 14, 2014, 07:51:50 AM
does anyone else get a problem with their ant miner u1 i get 0.5/0.7/2.0 gh/s out of my ant miner with bfg with cgminer 3.8.5 i get a steady 1.9 - 2.3 gh/s and i have the pool confirm that it seems like ant miners aren't working properly because if i use cgminer 3.100 (newest version) i get the same 700 or 800 mhs so it might be a problem with bfgminer and how it takes the miner if anyone has gotten it to work with BE's in same hub and same program (not 2 instances) with bfgminer then please pm me also i am using the bfgmienr-ant program please and thank you
You're not the only one, I too and getting slower speeds with BFG Miner. I've made some improvement but it's a hassle to do everytime. Check out my post here: https://bitcointalksearch.org/topic/m.4503625
The version 2 of BFGminer (files dated 9th Jan) seems to be the best
version 3 from the 11th? does not overclock properly.
https://www.dropbox.com/s/s837jkiirzg5mvq/bfgminer-npw-antminerV2.7z
I didn't know there was a version 3. I'm currently on version 2 of the BFG Miner that supports Antminer. Do you have a link to the version 3 because I must have missed that one?
Btw, currently at 15~11% HW right now when clocked to 0881 with BFG Miner. I think I need to move then U1's further apart on the hub.
https://www.dropbox.com/s/nph1hhfqnqzeduf/bfgminer-npw-antminerV1.7z file dates 7th Jan
https://www.dropbox.com/s/s837jkiirzg5mvq/bfgminer-npw-antminerV2.7z file dates 9th Jan
https://www.dropbox.com/s/c7movpxohewides/bfgminer-npw-antminerV3.7z file dates 12thJan
January 14, 2014, 07:39:03 AM
does anyone else get a problem with their ant miner u1 i get 0.5/0.7/2.0 gh/s out of my ant miner with bfg with cgminer 3.8.5 i get a steady 1.9 - 2.3 gh/s and i have the pool confirm that it seems like ant miners aren't working properly because if i use cgminer 3.100 (newest version) i get the same 700 or 800 mhs so it might be a problem with bfgminer and how it takes the miner if anyone has gotten it to work with BE's in same hub and same program (not 2 instances) with bfgminer then please pm me also i am using the bfgmienr-ant program please and thank you
You're not the only one, I too and getting slower speeds with BFG Miner. I've made some improvement but it's a hassle to do everytime. Check out my post here: https://bitcointalksearch.org/topic/m.4503625
The version 2 of BFGminer (files dated 9th Jan) seems to be the best
version 3 from the 11th? does not overclock properly.
https://www.dropbox.com/s/s837jkiirzg5mvq/bfgminer-npw-antminerV2.7z
I didn't know there was a version 3. I'm currently on version 2 of the BFG Miner that supports Antminer. Do you have a link to the version 3 because I must have missed that one?
Btw, currently at 13~11% HW right now when clocked to 0881 with BFG Miner. I think I need to move then U1's further apart on the hub.
Jump to: