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

[twib2]

antminer drivers are tied to the icarus drivers, so you don't need to enable the antminer drivers separately.

Just do ./configure  no need to add any enable options.

(If you manually disable icarus driver this would also disable antminer, so don't do that)

Thanks, that's what I would have thought, but it still didn't show with the "--help" switch.  *shrug*

[1714873516]

1714873516

[1714873516]

1714873516

[lajz99]

Are we ever going to get Drillbit support?

[nwoolls]

Thanks, that's what I would have thought, but it still didn't show with the "--help" switch.  *shrug*

Sorry that's my bad. It doesn't show in --help or ./configure unfortunately. If you see the .o file compiled though you are good to go.

[nwoolls]

If anyone feels like testing out the latest AntMiner U1 code, it now supports both over-clocking and running side-by-side with Block Erupters.

Code:

git clone -b feature\/antminer-u1-support https://github.com/nwoolls/bfgminer.git bfgminer-npw
cd bfgminer-npw
./autogen.sh
./configure
make

Make sure you see a driver-antminer.c before compiling and a driver-antminer.o after.

Probing is done similarly to the Block Erupter:

Code:

bfgminer -S antminer:all -S erupter:all

And you can overclock using --set-device:

Code:

bfgminer --set-device antminer:freq=4F02

Windows binaries:

https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7z

Tested on Windows, OS X, and Raspberry Pi (using MinePeon)

It Works For Me™

[stevenf]

And you can overclock using --set-device:

Code:

bfgminer --set-device antminer:freq=4F02

Sounds good!!

What value would I need to enter for the overclocking?

freq=4F02 is this stock speed? (1.6GH/s)

What value should I need to enter for 2.0GH/s

Thanks!

[nwoolls]

What value would I need to enter for the overclocking?

freq=4F02 is this stock speed? (1.6GH/s)

What value should I need to enter for 2.0GH/s

There's a table of values at the end of the current BITMAINtech documentation.

[stevenf]

There's a table of values at the end of the current BITMAINtech documentation.

+1 Thanks!

[drtek]

Nifty, thanks! So good you implemented proper U1 support so quick.

According to the AntMiner Spec Sheet - there is no 4F02 hex code?!

I will try the good old fashioned 0981 and hope it'll work.

[HellDiverUK]

Just picked up a Bitburner Fury - how is bfg's support for these things?

[dave111223]

@nwoolls  Thanks, excellent work.

I'm able to clock them up to 0981 and reach 2GH/s, but once I go to 0A81 it get funky results...ie hashrates all over the place from 400MH/s to 1.5GH/s

[nwoolls]

I'm able to clock them up to 0981 and reach 2GH/s, but once I go to 0A81 it get funky results...ie hashrates all over the place from 400MH/s to 1.5GH/s

I'll have to try it with the cgminer build. The thing is, the cgminer build from BITMAINtech doesn't calculate and estimate hashrate like other devices. It ignores the hashrate estimate and just uses a hard-coded value. This means you cannot compare the U1 hashrate shown in bfgminer with that shown in the cgminer build from BITMAINtech. How do the accepted shares compare?

[nwoolls]

Nifty, thanks! So good you implemented proper U1 support so quick.

According to the AntMiner Spec Sheet - there is no 4F02 hex code?!

I will try the good old fashioned 0981 and hope it'll work.

I got 4F02 from here. It is supposedly the default.

[Luke-Jr]

Are we ever going to get Drillbit support?

Yes, this is on my table. Just busy moving still, so not as much free time as usual

[Mudbankkeith]

Are we ever going to get Drillbit support?

Yes, this is on my table. Just busy moving still, so not as much free time as usual

I know the feeling 

Now, in which box, is the list of things, I put into boxes? 

[chiefstank]

If anyone feels like testing out the latest AntMiner U1 code, it now supports both over-clocking and running side-by-side with Block Erupters.

Code:

git clone -b feature\/antminer-u1-support https://github.com/nwoolls/bfgminer.git bfgminer-npw
cd bfgminer-npw
./autogen.sh
./configure
make

Make sure you see a driver-antminer.c before compiling and a driver-antminer.o after.

Probing is done similarly to the Block Erupter:

Code:

bfgminer -S antminer:all -S erupter:all

And you can overclock using --set-device:

Code:

bfgminer --set-device antminer:freq=4F02

Windows binaries:

https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7z

Tested on Windows, OS X, and Raspberry Pi (using MinePeon)

It Works For Me™

amazing! trying it now.
thank you!

EDIT:
all antminer, nanofury, and BE running on same instance. never thought i'd see the day. thank you! just have to wait and see if the BE get up to speed. this is great.

[stevenf]

On windows when bfgminer is started I get the message : NO DEVICES FOUND: Press 'M' and '+' to add

My commandline:

Code:

bfgminer.exe -S antminer:all -o stratum+tcp://stratum.bitcoin.cz:3333 -u stevenf.xxxxx -p xxxx --set-device antminer:freq=0881

I did install the CP210xVCP driver for windowsand I used the Zadig tool thingy, or is this not needed?

[chiefstank]

On windows when bfgminer is started I get the message : NO DEVICES FOUND: Press 'M' and '+' to add

My commandline:

Code:

bfgminer.exe -S antminer:all -o stratum+tcp://stratum.bitcoin.cz:3333 -u stevenf.xxxxx -p xxxx --set-device antminer:freq=0881

I did install the CP210xVCP driver for windowsand I used the Zadig tool thingy, or is this not needed?

The Zadig is not needed. just the VCP driver and you should be good to go.

[HellDiverUK]

I used the Zadig tool thingy, or is this not needed?

There's your problem.  You f**cked it by using that.  You'll have to remove all the drivers for the Antminers in Device Manager, then reinstall the VCP drivers.  Step away from zdiag.

[Juzz]

If anyone feels like testing out the latest AntMiner U1 code, it now supports both over-clocking and running side-by-side with Block Erupters.

Code:

git clone -b feature\/antminer-u1-support https://github.com/nwoolls/bfgminer.git bfgminer-npw
cd bfgminer-npw
./autogen.sh
./configure
make

Make sure you see a driver-antminer.c before compiling and a driver-antminer.o after.

Probing is done similarly to the Block Erupter:

Code:

bfgminer -S antminer:all -S erupter:all

And you can overclock using --set-device:

Code:

bfgminer --set-device antminer:freq=4F02

Windows binaries:

https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7z

Tested on Windows, OS X, and Raspberry Pi (using MinePeon)

It Works For Me™

http://www.nwoolls.com/othercontent/AntMiner-U1-bfgminer-MinePeon.png?1

I get segmentation fault when trying to launch that bfgminer - I am on an Ubuntu x86 latest version, I've compiled hidapi myself since there wasn't any in the repositories...

[rmolby]

If anyone feels like testing out the latest AntMiner U1 code, it now supports both over-clocking and running side-by-side with Block Erupters.

Probing is done similarly to the Block Erupter:

Code:

bfgminer -S antminer:all -S erupter:all

And you can overclock using --set-device:

Code:

bfgminer --set-device antminer:freq=4F02

Windows binaries:

https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7z

Tested on Windows, OS X, and Raspberry Pi (using MinePeon)

It Works For Me™

Awesome, so I started it up and had to do some fine tuning to get it running. I forgot to add the frequency because I ran with this command line option:

Code:

bfgminer.exe  -Q 8 -L log.txt -S antminer:all -S erupter:all

But when I added the default frequency of 193M like so:

Code:

 bfgminer.exe  -Q 8 -L log.txt -S antminer:all -S erupter:all --set-device antminer:freq=4F02

the ANTs spooled right up and started hashing at 1.5Ghashes and stabilized on 1.9x after about 10 minutes, however the BEs are fluctuating between 325 and 331 Mhashes, and my BFL Jalapeno that routinely got 7.47Ghashes is only mining at about 7.22 now... could be a hardware issues, I will have to try different USB hub connections to the laptop.