OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB

[drukoz]

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

[nwoolls]

The overclocking in V3 fails for me.

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.

[nwoolls]

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.

[drukoz]

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

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

[nwoolls]

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

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.

[drukoz]

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

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 ?

[Mudbankkeith]

The overclocking in V3 fails for me.

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.

Hi nwoolls

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.

[drukoz]

The overclocking in V3 fails for me.

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.

Hi nwoolls

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

[Mudbankkeith]

The overclocking in V3 fails for me.

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.

Hi nwoolls

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.

[twib2]

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?

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.

[Luke-Jr]

Still no Drillbit support...it's only been about 2 months now...

The code is in git, it'll be in 3.10.

[Laxe]

The overclocking in V3 fails for me.

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.

Hi nwoolls

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?

[Mudbankkeith]

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.

[Laxe]

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... 

[chiefstank]

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.

[nwoolls]

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.

[chiefstank]

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.

OIC... the last run i did of v3 earlier today my nfy did not appear. will check again.

Thanks!

[chiefstank]

Ran v3 again and got quite a few "Error trying to wake notifier" messages and NanoFury was not detected. All U1's and BE's working just fine.

Doing the device detection command detects 27/28 devices. Sticking with v2 for now.

[drukoz]

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... 

idk if u noticed but ur running them at 0881 for 1.8 ghs when u should be running them at 0981 for 2.0 ghs just a tip

[Fuglie]

Hey guys and gals,

I'm trying to get my miner running where it will do a a pool and then do a little bit (10%) solo mining based off a .conf script.  Right now though I can't even get it to solo mine normally.  Trying to use the wallet on my Windows machine. The Raspberry Pi is .2.38 and the Windows machine ip is .2.13.  New to Linux environment so might be something easy I'm missing.

Code:

Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers
Pool: 0 URL: http:://192.168.2.13:8332 User: blah Password: blah

the bitcoin-qt conf file:

Code:

daemon=1
listen=1
server=1
rpcuser=blah
rpcpassword=blah
rpcallowip=192.168.2.38
rpcport=8832

Here is how I'm executing.  Without sudo it kicks back to my .conf script and won't try to solo mine.

Code:

sudo ./bfgminer -o http://192.168.2.13:8832 -u blah -p blah --coinbase-addr 4098uq049uqawlkjadlkfjadlksfjasdfkjasdjlfk

Thanks again! trying to figure this stuff out.