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

[loshia]

Luke, just to bring this to your attention,
https://bitcointalk.org/index.php?topic=140539.msg4568041#msg4568041
Excuse my cross post
Pls comment it if you like
10X

[WhiteBeard]

But it's still not working...  I've been working on it for hours.  Any ideas?   

Need more info.  What OS are you running on?  What way is the BFL attached?  Hubs?  What sort of USB port?

OS is Ubuntu
1 BFL attached directly to motherboard USB
3 others by generic 10 port powered hub

[Sarticus]

I can get my AMU to mine at ~ 400Mh/s using cgminer. Zadig driver overwrite/installed.
I can't get BFGminer to recognize it. (Windows XP SP3 dual core Dell w 3GB ram)
Running bfgminer -D -d? -T from command prompt shows the device but does not recognize it:

"[2014-01-17 20:09:44] lowlevel_scan: Found vcom device at com:3 (path=\\.\COM3,
 vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
 [2014-01-17 20:09:44] Devices detected:
 [2014-01-17 20:09:44] Timers: Using QueryPerformanceCounter

 [2014-01-17 20:09:44] Recalibrating timeofday offset (delta 1389992602.308127s)

0 devices listed "

Also, how does one get the named configuration file used when starting bfgminer?
Thanks

[nwoolls]

I can get my AMU to mine at ~ 400Mh/s using cgminer. Zadig driver overwrite/installed.
I can't get BFGminer to recognize it.

Don't use the Zadig driver for bfgminer. For AntMiner U1s you want:

http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx

[Taugeran]

I can get my AMU to mine at ~ 400Mh/s using cgminer. Zadig driver overwrite/installed.
I can't get BFGminer to recognize it. (Windows XP SP3 dual core Dell w 3GB ram)
Running bfgminer -D -d? -T from command prompt shows the device but does not recognize it:

"[2014-01-17 20:09:44] lowlevel_scan: Found vcom device at com:3 (path=\\.\COM3,
 vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
 [2014-01-17 20:09:44] Devices detected:
 [2014-01-17 20:09:44] Timers: Using QueryPerformanceCounter

 [2014-01-17 20:09:44] Recalibrating timeofday offset (delta 1389992602.308127s)

0 devices listed "

Also, how does one get the named configuration file used when starting bfgminer?
Thanks

Bfgminer uses the silabs VCP DRIVERS. Not Zadig. To fix go to device manager with it plugged in right click choose driver settings make sure the checkbox for delete driver is ticked.

DL the island driver. Install it.

Reboot. Bfgminer -d -D? Should list it now

Named config is -c /path/to/file.conf

The asicminer USB sticks aren't software tunable. It uses a FIXED frequency and always yields the same hash rate rated at 12MHz*28 clock multiplier(in ASIC) = 336Mhash/sec. Any variation caused by altering timings with -- icarus-options and --icarus-timing are artefacts and do not represent an increase in realized hashrate

[Xer0]

antminer support is in openwrt release, too?

[Luke-Jr]

I can get my AMU to mine at ~ 400Mh/s using cgminer. Zadig driver overwrite/installed.
I can't get BFGminer to recognize it. (Windows XP SP3 dual core Dell w 3GB ram)
Running bfgminer -D -d? -T from command prompt shows the device but does not recognize it:

"[2014-01-17 20:09:44] lowlevel_scan: Found vcom device at com:3 (path=\\.\COM3,
 vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
 [2014-01-17 20:09:44] Devices detected:
 [2014-01-17 20:09:44] Timers: Using QueryPerformanceCounter

 [2014-01-17 20:09:44] Recalibrating timeofday offset (delta 1389992602.308127s)

0 devices listed "

AMUs do not support autodetection (no idea why not, it'd be trivial for them to add...), so you need -S antminer:\\.\COM3

antminer support is in openwrt release, too?

Yes

[voingiappone]

Run the following and report the output back here:

Code:

bfgminer -d? -D -S antminer:all

Code:

 [2014-01-18 12:51:19] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)                    
 [2014-01-18 12:51:19] Started bfgminer 3.10.0                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:001:020 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:001:019 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:001:017 (path=(null), vid=1a40, pid=0201, manuf=(null), prod=USB 2.0 Hub [MTT], serial=(null))                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:007:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 3.5.0-23-generic uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1d.2)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:006:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 3.5.0-23-generic uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1d.1)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:005:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 3.5.0-23-generic uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1d.0)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:004:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 3.5.0-23-generic uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1a.1)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:003:001 (path=(null), vid=1d6b, pid=0001, manuf=Linux 3.5.0-23-generic uhci_hcd, prod=UHCI Host Controller, serial=0000:00:1a.0)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=1d6b, pid=0002, manuf=Linux 3.5.0-23-generic ehci_hcd, prod=EHCI Host Controller, serial=0000:00:1d.7)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=1d6b, pid=0002, manuf=Linux 3.5.0-23-generic ehci_hcd, prod=EHCI Host Controller, serial=0000:00:1a.7)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:006:005 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:005:002 (path=(null), vid=0000, pid=0000, manuf=ServerEngines, prod=SE USB Device, serial=401A64E74826F2)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:003:009 (path=(null), vid=04b3, pid=3108, manuf=(null), prod=(null), serial=(null))                    
 [2014-01-18 12:51:19] lowlevel_scan: Found usb device at usb:001:015 (path=(null), vid=1a40, pid=0201, manuf=(null), prod=USB 2.0 Hub [MTT], serial=(null))                    
 [2014-01-18 12:51:19] lowlevel_scan: Found vcom device at dev_t:01bc000000000000 (path=/dev/ttyUSB1, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found vcom device at dev_t:02bc000000000000 (path=/dev/ttyUSB2, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)                    
 [2014-01-18 12:51:19] lowlevel_scan: Found vcom device at dev_t:00bc000000000000 (path=/dev/ttyUSB0, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)                    
 [2014-01-18 12:51:19] Icarus Detect: Attempting to open /dev/ttyUSB1                    
 [2014-01-18 12:51:19] Icarus Detect: Attempting to open /dev/ttyUSB2                    
 [2014-01-18 12:51:19] Icarus Detect: Attempting to open /dev/ttyUSB0                    
 [2014-01-18 12:51:19] Acquired exclusive advisory lock on /dev/ttyUSB1                    
 [2014-01-18 12:51:19] Timers: Using clock_gettime(CLOCK_MONOTONIC_RAW)                    
 [2014-01-18 12:51:19] Acquired exclusive advisory lock on /dev/ttyUSB0                    
 [2014-01-18 12:51:19] Acquired exclusive advisory lock on /dev/ttyUSB2                    
 [2014-01-18 12:51:19] Icarus Detect: Test succeeded at /dev/ttyUSB0: got 000187a2                    
 [2014-01-18 12:51:19] Found AMU 0 at /dev/ttyUSB0                    
 [2014-01-18 12:51:19] AMU 0: Init: baud=115200 work_division=0 fpga_count=0                    
 [2014-01-18 12:51:19] AMU 0: Init: mode=default read_count=19 limit=0ms Hs=4.761000e-10                    
 [2014-01-18 12:51:19] Icarus Detect: Test failed at /dev/ttyUSB1: expected 5 bytes, got 4                    
 [2014-01-18 12:51:19] Icarus Detect: Test failed at /dev/ttyUSB2: expected 5 bytes, got 4                    
 [2014-01-18 12:51:19] Devices detected:                    
 [2014-01-18 12:51:19]  CP2102 USB to UART Bridge Controller by Silicon Labs (driver=antminer; procs=1; serial=0001; path=/dev/ttyUSB0)                    
1 devices listed

* I moved only one Antminer for testing and there are also two Erupters on the same HUB I am using to mine for my sister.

Thank you nwoolls... it detects it! But only if I run your command beforehand.. otherwise it returns me the same error (No devices). I think I can just script it to run your command and then my bfgminer command line so the problem is solved but I still miss the point....
I feel like a dumb right now as I spent all the evening yesterday trying to get it running to no avail! Thought the problem was in the libs.
Can I ask you what kind of magic was in that command that made it recognized??

[wwwin]

I can get my AMU to mine at ~ 400Mh/s using

AMUs do not support autodetection (no idea why not, it'd be trivial for them to add...), so you need -S antminer:\\.\COM3

OK, so based on that I uninstalled Zadig driver again and ran it and now is working with 3.10.  

this is the command I used, just overclocked to 1.80 to test.

"bfgminer  -o stratum+tcp://us1.ghash.io:3333 -u XXXXXXXX -p 123 -S antminer:\\.\COM5  --set-device antiminer:clock=x0881"

and nothing else.  Do I need to add what I see other people adding such as "--icarus-options 115200:2:2 --icarus-timing 2.5=90 "  or is that just for the BEs...I am asking b/c with CG it has something like "bmsc-options 115200:20"  BFG does not like that bmsc...do I need to add something with this 115200:00 or am I done?

It seems to be doing good so far ZERO  HW errors where I was getting around .02 before...below is pic, the only thing is I see a lot of "Stratum from pool 0 requested work update" where with CG never got that there.




But seems to be working mighty fine now, will try OC to 2.00

at OC 1.8  hashing as below



I guess my only question is the "Stratum from pool 0 requested work update" and can I add something else to the command. I was  not getting that with CG but I guess BFG has different info?

[Xbits]

How long do you give it?  Try giving it a minute or two to load.  Are you running it in a command prompt or a shortcut/.bat file?  If it's the latter try using the command prompt directly since the window closes if the shortcut or .bat file runs into an error.  Using a command prompt lets you see what the error message is.

You could try to start BFG Miner with just the '--set-device antiminer:clock=x0981' command and see if that works or with no commands at all.

Also make sure the pool details are correct as it will auto close the window if it is not.

At the end of your .bat file start a new line and put:

pause

instead of closing out, this will keep the window open when there is a problem so you can see what the problem is.

Its easier to use windows explorer to go to you miners directory and click on the path to highlight it, then type in "CMD" and press enter.  This will open a command prompt, you can start your batch file in this window.  If the miner stops or if you stop the miner, the window will stay open.

If you put

Code:

pause

in the second line of your batch file then all you have to do is double click the batch file and it will open the CMD window for you, but will stay open and won't close if there is any error. I find this much easier since my batch file is a shortcut on my desktop.

[wwwin]

Ok, so tomorrow I will get delivered a second U1, I have been looking for the correct syntax to get that one to get recognized as well but cannot find it. So do I do  

   -S antminer:\\.\COM5     -S antminer:\\.\COMX       twice

   or is there a shortcut

like    -S antminer:\\.\COM5;\\.\COMX  

in other words how do I add the second antminer with a different COM, what is the syntax??? Thanks

[nwoolls]

Ok, so tomorrow I will get delivered a second U1, I have been looking for the correct syntax to get that one to get recognized as well but cannot find it. So do I do  

   -S antminer:\\.\COM5     -S antminer:\\.\COMX       twice

   or is there a shortcut

You should be able to do:

Code:

-S antminer:all

[wwwin]

Ok, so tomorrow I will get delivered a second U1, I have been looking for the correct syntax to get that one to get recognized as well but cannot find it. So do I do  

   -S antminer:\\.\COM5     -S antminer:\\.\COMX       twice

   or is there a shortcut

You should be able to do:

Code:

-S antminer:all

Hi, no if I do that won't recognize in Win 7 64bit...the only way to get it to work for me was doing the   -S antminer:\\.\COM5    

[kabopar]

If anyone wants to elaborate on the README FAQ covering un-Zadig'ing, I bet that would be well-appreciated by many.

What is the Com driver used for the Drillbit devices?

Standard USB CDC ACM.

Luke-Jr,
Thanks.  I still cannot find this driver (specifically for Win7/64).  I know how to remove the current Zadig installed one, but the only one that I can find for Drillbit is the Atmel driver used for firmware updates, which doesn't seem to work for me.  Any clues would be appreciated.

Thanks

Managed to solve my driver issue - using the Atmel driver provided by Drillbit for firmware updates.  Tried this so far on the Thumb.  Removing the WinUSB driver has to be 'complete' (not just uninstal, but tick the box to remove the driver).

Cheers

Tried the same approach using the Atmel driver for the Drillbit Eight Board, but it failed to accept the driver (Win7/64) and subsequently bfgminer3.10 could not find it either.  This was attempted on a separate PC with just the 8Board connected directly to one of the PC's USB ports.
Any idea where to find the drivers for the Drillbit Eight board for Windows 7/64?

(btw I'm running bfgminer 3.10 successfully on some BF/RF USB miners which used 3.9.0 previously)

[Sarticus]

Thanks for the help. Running stable as a rock @ default freq yielding 1.6Gh/S. 14 hours HW:0. 19.2 uBTC/hr.

[dave111223]

For some reason with version 3.10.0 i can only get 40 antminers to be detected.  I have 2 raspberries setup both with about 50 miners each, both only detected 40 each with 3.10.0

I had to rollback to using nwoolls version 3.9 in order to get all miners to be detected.

The weird thing is that with 3.10.0 it's showing 40 devices, but all physical miners are getting accepted share LED flashes (all 50).  But hashrate is only for 40, both in BFG and in pool stats.

[Taugeran]

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.

[nwoolls]

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.

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://bitcointalk.org/index.php?topic=137934.msg4567911#msg4567911

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.

[retek]

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

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 =)

[Mudbankkeith]

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

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 =)

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.