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.
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 62. (Read 1193271 times)
January 15, 2014, 01:37:57 PM
January 15, 2014, 01:32:42 PM
Hi
Any idea when you might support HEX16A2 avalon gen 2 boards?
Thanks
Any idea when you might support HEX16A2 avalon gen 2 boards?
Thanks
January 15, 2014, 12:31:15 PM
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. 
January 15, 2014, 12:18:17 PM
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.
January 15, 2014, 12:10:22 PM
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 agohttps://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.
January 15, 2014, 11:17:58 AM
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 agohttps://i.imgur.com/VoyQG8R.jpg
Can you explain the icarus timing issue exactly?
January 15, 2014, 11:06:57 AM
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).
Thanks
January 15, 2014, 09:05:03 AM
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.
the bitcoin-qt conf file:
Here is how I'm executing. Without sudo it kicks back to my .conf script and won't try to solo mine.
Thanks again! trying to figure this stuff out.
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
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
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
January 15, 2014, 08:30:44 AM
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).
January 15, 2014, 08:11:49 AM
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.
January 15, 2014, 07:20:16 AM
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 agohttps://i.imgur.com/VoyQG8R.jpg
January 15, 2014, 06:34:30 AM
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. January 15, 2014, 01:23:01 AM
Hi Luke-Jr, just curious - will long poll support be added to your next version for asicminer blades/cubes?
Not 3.10, no. January 15, 2014, 12:39:39 AM
Hi Luke-Jr, just curious - will long poll support be added to your next version for asicminer blades/cubes?
January 15, 2014, 12:16:07 AM
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.
the bitcoin-qt conf file:
Here is how I'm executing. Without sudo it kicks back to my .conf script and won't try to solo mine.
Thanks again! trying to figure this stuff out.
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
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
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
January 14, 2014, 11:46:59 PM
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.
January 14, 2014, 11:02:30 PM
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.
the bitcoin-qt conf file:
Here is how I'm executing. Without sudo it kicks back to my .conf script and won't try to solo mine.
Thanks again! trying to figure this stuff out.
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
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
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.
January 14, 2014, 10:30:38 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...
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
January 14, 2014, 10:23:43 PM
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.
Doing the device detection command detects 27/28 devices. Sticking with v2 for now.
January 14, 2014, 07:16:36 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.
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!
Jump to: