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

[Mudbankkeith]

Any chance of a Windows binary with ANT support?  Screenshot is very nice and all, but I'm loathed to run cg (with all the zdiag and WinUSB bollocks fecking up the USB drivers) to get these things working.

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

If it breaks I didn't do it 

Code:

bfgminer -S antminer:all

Note that, like the Bitmaintech cgminer build, this won't play nice with Block Erupters for now (unless you manually specify the driver for each devices with -S antminer and -S erupter).

Hi nwoolls

11 antminers now happy on BFG

A 2nd instance of miner is easy with 10 port switchable hubs.   

Running at 18Gh on 5 sec        16.5Gh at the pool     power is 27.3w and steady 

I just need to look at the overclocking now   

[lucazane]

I just need to look at the overclocking now   

Let us now if you find anything

[kfactor]

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

If it breaks I didn't do it  

You, sir, are a legend.  Just spent hours messing around with my ant miner U1 that arrived this morning, with all the zadig hoo-ha and so on - couldn't get it to run reliably, it would detect the U1 maybe 1 time in 10 and wasn't consistent or predictable in that respect, plus is brain damaged in terms of remote access - I run a little setup with a php script that accesses the miners remotely so I can see if they're happy without having to check each machine, and while it's possible to get some remote info out of it, it's not much.

Downloaded and ran your version, once I'd removed the zadig-installed drivers, fired right up straight away!  Thanks.  

Edit:  I've just checked out MultiMiner, which looks great, so I guess that's this afternoon spoken for.  Thanks again.

How did you remove the stinkin' zadig drivers?

edit: never mind, got it

[HellDiverUK]

Any update on overclocking the Antminer U1? 

[nwoolls]

Any update on overclocking the Antminer U1? 

Just going to need time. It's not difficult, just a lot on my plate (I have a day job and another side job outside of all this Bitcoin bidness  )

I also want to try to figure out how to properly ID these buggers so I can tell them from BEs.

The good news is I got in touch with Bitmaintech and they are providing me with info to keep development going so that should be a great help.

[HellDiverUK]

Any update on overclocking the Antminer U1?  

Just going to need time. It's not difficult, just a lot on my plate (I have a day job and another side job outside of all this Bitcoin bidness  )

I also want to try to figure out how to properly ID these buggers so I can tell them from BEs.

The good news is I got in touch with Bitmaintech and they are providing me with info to keep development going so that should be a great help.

Cool.    Been running about 12 hours now solid with your Windows build.

Only thing I can note is that your build doesn't pick up my two IceFurys.  It works fine with the 10 Antminers, two Jalapenos and 3 proxies.  Doesn't even pick up the NFYs if I specify them in the command line.

[nwoolls]

Only thing I can note is that your build doesn't pick up my two IceFurys.  It works fine with the 10 Antminers, two Jalapenos and 3 proxies.  Doesn't even pick up the NFYs if I specify them in the command line.

Make sure you used Zadig to install the driver for the IceFurys. It is needed for those. I am using that exact same Windows build to run IceFurys and Antminers without issue.

[HellDiverUK]

Only thing I can note is that your build doesn't pick up my two IceFurys.  It works fine with the 10 Antminers, two Jalapenos and 3 proxies.  Doesn't even pick up the NFYs if I specify them in the command line.

Make sure you used Zadig to install the driver for the IceFurys. It is needed for those. I am using that exact same Windows build to run IceFurys and Antminers without issue.

Ah, OK.  I just moved the IceFurys to my BBB, so no big fuss.

[Luke-Jr]

Make sure you used Zadig to install the driver for the IceFurys. It is needed for those.

It shouldn't be... Icefury is just a nanofury, right? Those are HID...

[HellDiverUK]

Make sure you used Zadig to install the driver for the IceFurys. It is needed for those.

It shouldn't be... Icefury is just a nanofury, right? Those are HID...

Fair point.  They are coming up as HID devices in Windows, but Nate's bfg isn't picking them up.  I didn't remember having to do the zdiag dance before to get them going on Windows.

Yeah, they're just a Nanofury.

[nwoolls]

Make sure you used Zadig to install the driver for the IceFurys. It is needed for those.

It shouldn't be... Icefury is just a nanofury, right? Those are HID...

Too true - my bad. I just double-checked my IceFurys and they are using the HidUsb driver, not WinUSB.

[prehistoric]

That's interesting, somehow bfgminer 3.9.0 or btcguild pool switched from worker's diff 8 to diff 16 with olddifficulty rejection message

Code:

[2014-01-04 23:43:21] Accepted 194f432f NFY 3  pool 0 Diff 10/8
[2014-01-04 23:43:21] Stratum from pool 0 requested work update
[2014-01-04 23:43:21] Pool 0 stale share detected, submitting as user requested
[2014-01-04 23:43:21] Rejected 1795e873 NFY 5  pool 0 Diff 10/8 (olddifficulty)
[2014-01-04 23:43:21] Rejected 0cb8968a BPM 1  pool 0 Diff 20/8 (olddifficulty)
[2014-01-04 23:43:22] Pool 0 stale share detected, submitting as user requested
[2014-01-04 23:43:22] Rejected 1536fed3 BPM 0  pool 0 Diff 12/8 (olddifficulty)
[2014-01-04 23:43:25] Accepted 0491d025 NFY 2  pool 0 Diff 56/16

btw, 6NFY+2BPM around 20GH/s. Worker's diff is set to 8 instead 16 intentionally in btcguild worker's properties.
After restart it happened again without olddifficulty rejection message:

Code:

[2014-01-07 23:37:23] Accepted 07a5238f NFY 1  pool 0 Diff 33/8
[2014-01-07 23:37:23] Stratum from pool 0 requested work update
[2014-01-07 23:37:24] Accepted 00313cb6 NFY 2  pool 0 Diff 1.33k/16
[2014-01-07 23:37:27] Accepted 06385d7a BPM 0  pool 0 Diff 41/16

[Codemeister]

Running bfg with 5 Antminers U1 now. Waiting for the miners to reach the right speed
Awesome work so far.

[Mudbankkeith]

Running bfg with 5 Antminers U1 now. Waiting for the miners to reach the right speed
Awesome work so far.

They do take a while to come up to speed.

[Luke-Jr]

That's interesting, somehow bfgminer 3.9.0 or btcguild pool switched from worker's diff 8 to diff 16 with olddifficulty rejection message

Code:

[2014-01-04 23:43:21] Accepted 194f432f NFY 3  pool 0 Diff 10/8
[2014-01-04 23:43:21] Stratum from pool 0 requested work update
[2014-01-04 23:43:21] Pool 0 stale share detected, submitting as user requested
[2014-01-04 23:43:21] Rejected 1795e873 NFY 5  pool 0 Diff 10/8 (olddifficulty)
[2014-01-04 23:43:21] Rejected 0cb8968a BPM 1  pool 0 Diff 20/8 (olddifficulty)
[2014-01-04 23:43:22] Pool 0 stale share detected, submitting as user requested
[2014-01-04 23:43:22] Rejected 1536fed3 BPM 0  pool 0 Diff 12/8 (olddifficulty)
[2014-01-04 23:43:25] Accepted 0491d025 NFY 2  pool 0 Diff 56/16

btw, 6NFY+2BPM around 20GH/s. Worker's diff is set to 8 instead 16 intentionally in btcguild worker's properties.
After restart it happened again without olddifficulty rejection message:

Code:

[2014-01-07 23:37:23] Accepted 07a5238f NFY 1  pool 0 Diff 33/8
[2014-01-07 23:37:23] Stratum from pool 0 requested work update
[2014-01-07 23:37:24] Accepted 00313cb6 NFY 2  pool 0 Diff 1.33k/16
[2014-01-07 23:37:27] Accepted 06385d7a BPM 0  pool 0 Diff 41/16

Expected. There is a workaround for very old (no longer a problem?) pools that treated difficulty wrong. This results in invalid shares being submitted unnecessarily, but is otherwise harmless.

[rmolby]

Any chance of a Windows binary with ANT support?  Screenshot is very nice and all, but I'm loathed to run cg (with all the zdiag and WinUSB bollocks fecking up the USB drivers) to get these things working.

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

If it breaks I didn't do it  

Code:

bfgminer -S antminer:all

Note that, like the Bitmaintech cgminer build, this won't play nice with Block Erupters for now (unless you manually specify the driver for each devices with -S antminer and -S erupter).

Excellent.

I noticed my BEs are running at less than 50 Mhash, I assume that is due to the Antminer configuration being pushed down on them despite of me running the following?

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

Even though I only have two Antminers, I am mining at a slightly higher rate than with all the BEs (with 2 BEs removed to make room on one of the hubs)

OK, so I decided to use nwoolls Antminer version of BFG, and leave all the BEs unplugged, let AntBFG fire up and stabilize, then I plug in the hubs with the BEs and fire up BFG 3.2.8 (most stable with BEs on my system). Am now mining at full speed with all my mining gear

[prehistoric]

That's interesting, somehow bfgminer 3.9.0 or btcguild pool switched from worker's diff 8 to diff 16 with olddifficulty rejection message
...

Expected. There is a workaround for very old (no longer a problem?) pools that treated difficulty wrong. This results in invalid shares being submitted unnecessarily, but is otherwise harmless.

Seems strange, because bfgminer never lowers the diff, even if it is set to lower number in worker's property while mining. Can bfgminer only get worker difficulty correctly only at start?

[Luke-Jr]

That's interesting, somehow bfgminer 3.9.0 or btcguild pool switched from worker's diff 8 to diff 16 with olddifficulty rejection message
...

Expected. There is a workaround for very old (no longer a problem?) pools that treated difficulty wrong. This results in invalid shares being submitted unnecessarily, but is otherwise harmless.

Seems strange, because bfgminer never lowers the diff, even if it is set to lower number in worker's property while mining. Can bfgminer only get worker difficulty correctly only at start?

It does, just not right away.
Essentially it works as lowest-of(job-difficulty, current-difficulty)

[nwoolls]

I noticed my BEs are running at less than 50 Mhash, I assume that is due to the Antminer configuration being pushed down on them despite of me running the following?

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

Even though I only have two Antminers, I am mining at a slightly higher rate than with all the BEs (with 2 BEs removed to make room on one of the hubs)

OK, so I decided to use nwoolls Antminer version of BFG, and leave all the BEs unplugged, let AntBFG fire up and stabilize, then I plug in the hubs with the BEs and fire up BFG 3.2.8 (most stable with BEs on my system). Am now mining at full speed with all my mining gear

This is to be expected and I hope to find a way around it soon. Basically the AntMiner U1 design and implementation is very close to the Block Erupter. That is why there are issues in both cgminer and bfgminer when running both. Right now there is no way to determine the difference between the two in the code. I am glad you found a way to get it working. Another would be to use something like:

Code:

bfgminer -S antminer:/path/to/antminer -S erupter:/path/to/erupter

[Question_is]

BFGMiner : https://github.com/luke-jr/bfgminer
Where should I work to modify the sha256_nonce find code for CPU-64bit or GPU ?

I know that CPU and GPU mining is looked as: overcome by FPGA and Asics, but I want to
do that; in spite of all the odds.

I want to write my code for CPU-64bit or GPU mining, but I see that,
"sha256" and "nonce" are in all the following files below.
They are quite a lot. Probably there are files, with code for
different architectures.

Can someone suggest me the files that I have to work in ?

Thankyou anyway

------These files have "sha2" as text inside-------------
/driver-cpu.h
/sha2.c
/sha2.h
/libblkmaker/base58.c
/libblkmaker/private.h
/x86_32/Makefile.am
/x86_32/Makefile.in
/x86_32/sha256_xmm.asm
/x86_64/Makefile.am
/x86_64/Makefile.in
/x86_64/sha256_xmm_amd64.asm

-----These files have both "sha2" and "nonce" as text inside----------
/api.c
/diablo130302.cl
/driver-bitforce.c
/driver-cpu.c
/driver-ztex.c
/findnonce.c
/Makefile.am
/Makefile.in
/miner.c
/miner.h
/scrypt130511.cl
/scrypt.c
/sha256_4way.c
/sha256_altivec_4way.c
/sha256_cryptopp.c
/sha256_generic.c
/sha256_sse2_amd64.c
/sha256_sse2_i386.c
/sha256_sse4_amd64.c
/sha256_via.c
/util.c
/libblkmaker/blkmaker.c
/libblkmaker/blkmaker.h
/libblkmaker/example.c
/x86_64/sha256_sse4_amd64.asm

--------------------------------------------