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

[captplanet]

Is anyone else having a problem where one of their miners is accepting a share every couple of minutes? All of my other miners are running find, but this one has only accepted one share in the past 2 minutes.

[1713977330]

1713977330

[1713977330]

1713977330

[drukoz]

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.

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

rpcallowip=192.168.2.38
rpcport=8832

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

ports are different try to change the config file port to 8332 idk it might work i couldn't tell u if its a sure fix but it might i think its bfgminer config is stuck on port 8332 it happens sometimes when i overclock my K16 it stays stuck on 446mhz even tho i set it to 362

[k2_1971]

Hi Luke-Jr, just curious - will long poll support be added to your next version for asicminer blades/cubes?

[Luke-Jr]

Hi Luke-Jr, just curious - will long poll support be added to your next version for asicminer blades/cubes?

Not 3.10, no.

[Laxe]

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

Yes I know don't worry.   I may try 0981 again on v3 soon but using v2 at 0981 I got loads of HW errors so I'd like to avoid them for now.  Also I don't have any active cooling so I wouldn't want to run the U1's too hot right now.

[drukoz]

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

Yes I know don't worry.   I may try 0981 again on v3 soon but using v2 at 0981 I got loads of HW errors so I'd like to avoid them for now.  Also I don't have any active cooling so I wouldn't want to run the U1's too hot right now.

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

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

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

[k2_1971]

Hi Luke-Jr, just curious - will long poll support be added to your next version for asicminer blades/cubes?

Not 3.10, no.

Ok, thank you.

[iongchun]

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

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

Hi Luke, thanks for the driver, just tried the latest code with my Drillbits, I have 2 issues:

1. Stats is unavailable for thumbs, so bfgminer causes lots of "Short read in response to 'T'" error.
Just adding a "if (dev->procs == 1) return false;" in drillbit_get_stats fixes this for me;

2. The range for external clock should be wider, many people overclock Thumbs to higher than 230.
Currently cgminer driver do not limit it, just prints a warning when lower than 80 or higher than 230.
Angus of Drillbit Systems had suggested to try 250 for up to 3GH/s with active cooling and enough power (1000mA).

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

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

rpcallowip=192.168.2.38
rpcport=8832

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

ports are different try to change the config file port to 8332 idk it might work i couldn't tell u if its a sure fix but it might i think its bfgminer config is stuck on port 8332 it happens sometimes when i overclock my K16 it stays stuck on 446mhz even tho i set it to 362

Thanks! That worked. Not just gotta get a script up and going.  I'm sure I'll have another question in a day or two 

- Fuglie

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

Hi Luke, thanks for the driver, just tried the latest code with my Drillbits, I have 2 issues:

1. Stats is unavailable for thumbs, so bfgminer causes lots of "Short read in response to 'T'" error.
Just adding a "if (dev->procs == 1) return false;" in drillbit_get_stats fixes this for me;

2. The range for external clock should be wider, many people overclock Thumbs to higher than 230.
Currently cgminer driver do not limit it, just prints a warning when lower than 80 or higher than 230.
Angus of Drillbit Systems had suggested to try 250 for up to 3GH/s with active cooling and enough power (1000mA).

I believe I have addressed both of these issues in the latest git code, please test.
Thanks

[Blackbird0]

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

Yes I know don't worry.   I may try 0981 again on v3 soon but using v2 at 0981 I got loads of HW errors so I'd like to avoid them for now.  Also I don't have any active cooling so I wouldn't want to run the U1's too hot right now.

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

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

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

Can you explain the icarus timing issue exactly?

[Laxe]

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

Yes I know don't worry.   I may try 0981 again on v3 soon but using v2 at 0981 I got loads of HW errors so I'd like to avoid them for now.  Also I don't have any active cooling so I wouldn't want to run the U1's too hot right now.

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

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

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

Thanks for the extra commands.  I'm trying those now on v3 but I think 1.8 Gh/s per U1 is the max my hub can take right now - we'll see in a few hours time.  I am running 3 BE's on the same hub so that could be affecting the overall hash rate. 

Regarding HW errors, you're right, v3 is far more stable even at 0981 - gotten 1 HW error on one U1 so far.  Very happy still with the results.

[sikke]

This is how BFG Miner handles 73 USB sticks in Win7
Really hate those REDFury devices and their HW error rate 5% anything i am doing wrong. Anyone got latest drivers for REDFury?
Gotta love the Antminers 2GH/s solid to the pool with 0HW errors in most of the units. 2.2GH brings out the errors. I prefer mining without.

[Luke-Jr]

BTW, in case it wasn't obvious, I'm more than glad to add any GUIs (within reason - must be open source and have some reviews, etc) anyone has to the README under "Q: Is there a GUI version?" Just ping me with info/link.

[mudge]

Hi

Any idea when you might support HEX16A2 avalon gen 2 boards?

Thanks

[Luke-Jr]

Any idea when you might support HEX16A2 avalon gen 2 boards?

Unfortunately, the Technobit boards don't seem to play nicely (ie, work at all) with Linux's CDC driver, so progress on them is slow.

[atomicchaos]

Luke-

I just wanted to thank you for your support on the GPU side of things. I am well aware of your opinion on ALTs and GPU mining, and appreciate the recent work you've done to add/fix a couple things recently. Expect a small donation in the near future.

Thanks again.

[Kronkvist]

When is Bfg 3.10 downloadable from github ?

[HellDiverUK]

When is Bfg 3.10 downloadable from github ?

Probably a few seconds after it's released, at a guess.   

[lajz99]

When is Bfg 3.10 downloadable from github ?

Probably a few seconds after it's released, at a guess.   

Wow, such a helpful response...