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

[nwoolls]

https://www.dropbox.com/s/ho5lf1vqj57f5a2/bfgminer_gridseed_pr1.7z

I give this my I Haven't Tried It And It May Take A Custom INF stamp.

So these do need a custom INF file for Windows. This one works for the devices I have:

https://www.dropbox.com/s/w06b7nj1f07lv29/Windows_ASIC_CDC_Drivers.zip

Check the GridSeed folder. If this doesn't work for you let me know.

Edit: And here's a second pre-release. This includes support for both the 1-chip and 5-chip devices:

https://www.dropbox.com/s/i8cai8x79b79gzo/bfgminer_gridseed_pr2.7z

[Blackbird0]

nwoolls: after a couple days running your DualMiner build, here's my experiences:

First: the DualMiner chip seems to shut off a lot. As you know, the plural of anecdotes isn't data, but it seems to be happing more frequently on this build. The most I've gotten is 13 hours running without a problem. Sometimes it runs for only a couple hours before it shuts off. I've tried moving to a somewhat larger/more stable pool. Don't know if that helps. I'm mining Dogecoin if that matters.

Second: the OV function isn'tworking as expected. After 13 hours on my current run, it's averaging 71.1 KH/s. I'd be expecting it be higher with the 850 OC argument added.

Any thoughts on this? Otherwise, the build is perfectly stable, and all my other devices in my SHA-256 instance is working fine.

[nwoolls]

First: the DualMiner chip seems to shut off a lot. As you know, the plural of anecdotes isn't data, but it seems to be happing more frequently on this build. The most I've gotten is 13 hours running without a problem. Sometimes it runs for only a couple hours before it shuts off. I've tried moving to a somewhat larger/more stable pool. Don't know if that helps. I'm mining Dogecoin if that matters.

Second: the OV function isn'tworking as expected. After 13 hours on my current run, it's averaging 71.1 KH/s. I'd be expecting it be higher with the 850 OC argument added.

I haven't had a unit "shut off" with either build on any OS, but I'll keep an eye out for it.

And 850 is the default frequency for U1s - you aren't OCing it so you aren't going to see a change in speed.

[sunjar2013]

Recently I use BFGMiner to drive my ASICMiner's USB deivce(333MH), it works very well, but I still have a problem that is when I trying to use a command like as bfgminer.exe 2>log.txt syntax to logging the output message, I found the log file is very verbose, just like:

[2014-03-10 17:56:29] 5s:397.3 avg:331.8 u:180.1 Mh/s | A:0 R:0+0(none) HW:0/none
[2014-03-10 17:56:34] 5s:372.7 avg:332.4 u:442.0 Mh/s | A:0 R:0+0(none) HW:0/none
[2014-03-10 17:56:41] 5s:213.4 avg:269.1 u:357.8 Mh/s | A:0 R:0+0(none) HW:0/none
[2014-03-10 17:56:47] 5s:355.6 avg:310.5 u:306.7 Mh/s | A:0 R:0+0(none) HW:0/none
...... etc

I remember the CGMiner only log the main message like as new block found or share accepted, and CGMiner not use time interval mode to log to file, it just write file when new message arrived. But BFGMiner not like this, it seems like write message every 5 second (can adjust by paramter or modify configuration file). My point is I don't like this record mode, if we use time interval mode we maybe miss something if interval value is to big, otherwise if this value too small, my hard driver is working hard beacause frequency read and write. So, is BFGMiner have a way to log data like CGMiner? Just execute write operate when output message appear?

By the way, BFGMiner is also a great program, many thanks for dev's work of this software.  

[alandsidel]

I have a (hopefully simple) question about the displayed difficulty in BFGMiner and other cpuminer derivatives like cgminer.

I'm working on some bitcoin related web stuff and am using both testnet and testnet-in-a-box.  On the 'real' testnet, the difficulty is always shown as 2.73k even when I would expect it to be showing difficulty 1.  Obviously I'm just not understanding something about testnet3 and the 20 minute difficulty 'reset' thing.  If anyone can explain just what's going on there, I'd appreciate it.

Bitcoind and bitcoin-qt seem to always show the 'correct' difficulty (1 after 20 minutes of inactivity, real difficulty otherwise).

[hurricandave]

I've gotten my hands on some AntMiner U2s but bfgminer is not seeing them.

This is on a Raspi.

Code:

./bfgminer-3.10.0/bfgminer -S antminer:all -o stratum.myfuckingpool.com:3333 -u demonmaestro_usb -p 1

   I got my Antminer U2 today also, no luck so far. I'm using Windows 7 Pro 32-bit.  SiLab drivers installed. Windows sees the device in corect port. The miner has a steady Red LED but BFGMiner has No New Device Found. I can't find any info from Bitmain for these either. Well, except for pricing.

[demonmaestro]

Until Luke gives us some goodies to work with I am using cgminer.

[hurricandave]

Until Luke gives us some goodies to work with I am using cgminer.

   Was your U2 showing a steady red led? This is my first ASIC and I feel like I talked myself into jumping in a foul moat.

[marcocoin]

I've gotten my hands on some AntMiner U2s but bfgminer is not seeing them.

This is on a Raspi.

Code:

./bfgminer-3.10.0/bfgminer -S antminer:all -o stratum.myfuckingpool.com:3333 -u demonmaestro_usb -p 1

  I got my Antminer U2 today also, no luck so far. I'm using Windows 7 Pro 32-bit.  SiLab drivers installed. Windows sees the device in corect port. The miner has a steady Red LED but BFGMiner has No New Device Found. I can't find any info from Bitmain for these either. Well, except for pricing.

Have you tried giving the COM port numbers in the command line?

Something like this...  -S \\.\COM1 or the COM port of your U2 antminer.

For example .. my run command bat file is:

bfgminer.exe -o ppc.fixx.ru:8437 -u xxxx.ppc01 -p xx1 -S \\.\COM3 -S \\.\COM4 -S \\.\COM8 -S \\.\COM9 -S antminer:all --set-device antminer:clock=x0981 --icarus-options 115200:2:2

I have a vista laptop and BFGminer 3.10...

BFGminer works fantastic with my Antminer U1 units and should be same for the U2 units.

By the way be very careful to not add extra spaces in between commands as that will create an error.

best regards

[marcocoin]

Until Luke gives us some goodies to work with I am using cgminer.

  Was your U2 showing a steady red led? This is my first ASIC and I feel like I talked myself into jumping in a foul moat.

Red led is always on.

When the miner is working there is a small green light flashing (on the U1 anyway).

[nwoolls]

I got my Antminer U2 today also, no luck so far. I'm using Windows 7 Pro 32-bit.  SiLab drivers installed. Windows sees the device in corect port. The miner has a steady Red LED but BFGMiner has No New Device Found. I can't find any info from Bitmain for these either. Well, except for pricing.

I've contacted both Bitmain and resellers about getting a sample so we can upgrade the driver. No responses yet. I'd heard these were compatible with the U1 but apparently not.

[Aurum]

I got my Antminer U2 today also, no luck so far. I'm using Windows 7 Pro 32-bit.  SiLab drivers installed. Windows sees the device in corect port. The miner has a steady Red LED but BFGMiner has No New Device Found. I can't find any info from Bitmain for these either. Well, except for pricing.

I've contacted both Bitmain and resellers about getting a sample so we can upgrade the driver. No responses yet. I'd heard these were compatible with the U1 but apparently not.

Please add the AntMiner S1 to the MuM armory  

[Isuearl]

Can't speak the praises enough of BFGminer.... I am a relative NOOB when it comes to mining, but I have been Using BFG miner for the most part...Its relatively simple....Just started using the Proxy yesterday....I had some consternation while setting it up...but it turned out it was my Antivirus program causing me the headache...turned off AV started the proxy and turned AV back on and now everything is hashing like a champ....
  I want to thank Luke Jr for the hard work not to mention nwools and everyone else I missed for an overall decent piece of software.......(not to mention this thread which contains a boatload of info for the NOOBs).
To the NOOBs out there, just page through the thread...most of your questions will be answered somewhere....

[Pistachio]

This looks great. Anyone tried this with 40+ miners (off 4 USB hubs)?

The previous driver I linked is for the GridSeed 1-chip device, so far resold by DualMiner.

For support for the GridSeed 5-chip devices, if you are feeling crazy you can try this out (Scrypt-only currently):

https://github.com/nwoolls/bfgminer/commits/feature/gridseed-support

I give it the It Works For Me(tm) stamp of approval. Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600).



For OS X users, these should be loaded automatically but in case they aren't:

Code:

sudo kextload -b com.apple.driver.AppleUSBCDC
sudo kextload -b com.apple.driver.AppleUSBCDCACMData

SHA2 support will be next followed by dual-algorithm support. If you have some of these and are feeling froggy, feedback is welcome.

[darkfriend77]

This looks great. Anyone tried this with 40+ miners (off 4 USB hubs)?

...

I tryed out yesterday with 20 on 2 hubs ... it was working ... but haven't tested more then 30 minutes.

As I wanted to have them hash on seperate workers ... to check some stuff ...

[chanberg]

Code:

root@raspberrypi:/home/pi/bfgminer-feature-gridseed-support# make
make  all-recursive
make[1]: Entering directory `/home/pi/bfgminer-feature-gridseed-support'
Making all in lib
make[2]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make  all-recursive
make[3]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make[4]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make[3]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make[2]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/lib'
Making all in ccan.bfg
make[2]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/ccan.bfg'
make[2]: *** No rule to make target `../ccan-upstream/ccan/opt/helpers.c', needed by `../ccan-upstream/ccan/opt/libccan_a-helpers.o'.  Stop.
make[2]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/ccan.bfg'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support'
make: *** [all] Error 2
root@raspberrypi:/home/pi/bfgminer-feature-gridseed-support# 

[nwoolls]

Code:

make[2]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/ccan.bfg'
make[2]: *** No rule to make target `../ccan-upstream/ccan/opt/helpers.c', needed by `../ccan-upstream/ccan/opt/libccan_a-helpers.o'.  Stop.
make[2]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/ccan.bfg'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support'
make: *** [all] Error 2
root@raspberrypi:/home/pi/bfgminer-feature-gridseed-support# 

Make sure you ran autogen.sh - that should clone requirements into the ccan directory. If that doesn't work copy over the contents from a working clone of the master repo.

[TrollboxChamp]

This looks great. Anyone tried this with 40+ miners (off 4 USB hubs)?

The previous driver I linked is for the GridSeed 1-chip device, so far resold by DualMiner.

For support for the GridSeed 5-chip devices, if you are feeling crazy you can try this out (Scrypt-only currently):

https://github.com/nwoolls/bfgminer/commits/feature/gridseed-support

I give it the It Works For Me(tm) stamp of approval. Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600).



For OS X users, these should be loaded automatically but in case they aren't:

Code:

sudo kextload -b com.apple.driver.AppleUSBCDC
sudo kextload -b com.apple.driver.AppleUSBCDCACMData

SHA2 support will be next followed by dual-algorithm support. If you have some of these and are feeling froggy, feedback is welcome.

I have 80 gridseeds. Gonna give this a go in the morning on windows 8.1

[hurricandave]

   I am at my wits end with this Antminer U2+.
I have tried all kinds of combinations of -S antminer: all, auto, \\COM4, capitol letters, small case letters, with --set device; without it.
I've uninstalled drivers, rebooted, made sure to check the remove all drivers box, reboot after reboot.
Installed the VCP drivers from Silicon Labs, ran the .exe as admin yada yada.
Deleted my .conf, several times.
Deleted BFG Miner 3.10.0 win 32, then un7zip to C\ a fresh copy as admin, etc,etc,etc.
I've run as administrator, installed as administrator.
Opened BFG Miner with CMD Prompt as admin, launched from command line.
All of these steps have been repeated on  two separate Windows computers, XP Pro and 7 Pro.
Even CG Miner refuses to work with this Antminer U2. But with a different message "USB init, open device failed, err -3, you don't have privilege to access -AMU device 2:1"
Now I only mention that because its the only line of any output that has reflected AMU.
And yes,I have properly removed Zadig from that computer( XP Pro) and left CG at that.

With VCP driver installed, Windows usually will give some thing like the following thru Device Manager (as admin)-
nit picking the parts that have Silicon Labs  or USB to UART type info.

   Location Path
PCIROOT(0)#PCI(ID01)#USBROOT(0)#USB(1)
   Device Instance Path
USB\VID_10C4&PID_EA60\0001
   Bus Reported Device Description
CP2102 USB to UART Bridge Controller
   manuf- Silicon Laboratories
   Location- Port_#0001.Hub_#0005
   USB Root Hub Location- Intel ICH8 Family USB Universal Host Controller-2831 (10%- resources)

   Launching Bfg Miner from the cmd line with-   bfgminer -d? -D -S antminer:all
I can pick out relevant lines with -

  lowlevel_scan: Found vcom device at com:4 (path=\\.\COM4, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null)

  lowlevel_scan: Found usb device at usb:005:e002 (path=(null), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null)

  Failed to ioctlin lowl_vcom.c windows_usb_get_string():389: A device attached to the system is not functioning.
  FTD2XX.DLL failed to load, not using FTDI auto detect

  Icarus Detect: Test Failed at \\.\COM4:get00000000, should:000187a2

   Devices detected:
0devices listed


 Windows sees that a device is there and lets Silicon Labs drivers install for it and BFG Miner sees that something is in the usb port but I'm not seeing things that I expected like manuf=(siliconlabs) prod=(USBtoUART)or(CP2102) serial=(??)



 What's relevant?   What's missing?  


[ Update-  One confirmed defective Antminer U2+, after receiving a replacement, the Antminer U 2+ starts in the command line just like the Antminer U1.]

[Mudbankkeith]

   I am at my wits end with this Antminer U2+.
I have tried all kinds of combinations of -S antminer: all, auto, \\COM4, capitol letters, small case letters, with --set device; without it.
I've uninstalled drivers, rebooted, made sure to check the remove all drivers box, reboot after reboot.
Installed the VCP drivers from Silicon Labs, ran the .exe as admin yada yada.
Deleted my .conf, several times.
Deleted BFG Miner 3.10.0 win 32, then un7zip to C\ a fresh copy as admin, etc,etc,etc.
I've run as administrator, installed as administrator.
Opened BFG Miner with CMD Prompt as admin, launched from command line.
All of these steps have been repeated on  two separate Windows computers, XP Pro and 7 Pro.
Even CG Miner refuses to work with this Antminer U2. But with a different message "USB init, open device failed, err -3, you don't have privilege to access -AMU device 2:1"
Now I only mention that because its the only line of any output that has reflected AMU.
And yes,I have properly removed Zadig from that computer( XP Pro) and left CG at that.

With VCP driver installed, Windows usually will give some thing like the following thru Device Manager (as admin)-
nit picking the parts that have Silicon Labs  or USB to UART type info.

   Location Path
PCIROOT(0)#PCI(ID01)#USBROOT(0)#USB(1)
   Device Instance Path
USB\VID_10C4&PID_EA60\0001
   Bus Reported Device Description
CP2102 USB to UART Bridge Controller
   manuf- Silicon Laboratories
   Location- Port_#0001.Hub_#0005
   USB Root Hub Location- Intel ICH8 Family USB Universal Host Controller-2831 (10%- resources)

   Launching Bfg Miner from the cmd line with-   bfgminer -d? -D -S antminer:all
I can pick out relevant lines with -

  lowlevel_scan: Found vcom device at com:4 (path=\\.\COM4, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null)

  lowlevel_scan: Found usb device at usb:005:e002 (path=(null), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null)

  Failed to ioctlin lowl_vcom.c windows_usb_get_string():389: A device attached to the system is not functioning.
  FTD2XX.DLL failed to load, not using FTDI auto detect

  Icarus Detect: Test Failed at \\.\COM4:get00000000, should:000187a2

   Devices detected:
0devices listed


 Windows sees that a device is there and lets Silicon Labs drivers install for it and BFG Miner sees that something is in the usb port but I'm not seeing things that I expected like manuf=(siliconlabs) prod=(USBtoUART)or(CP2102) serial=(??)



 What's relevant?   What's missing?   

Maybe Luke-Jr needs a sample?