Pages:
Author

Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 68. (Read 1193208 times)

full member
Activity: 131
Merit: 100
Hobby Miner
Running the new build now. In short: awesome! Seven miners running 2,2 GH/s really stable now. Thanks again!
hero member
Activity: 1246
Merit: 501
Yes the zlib1 is missing and correct it does NOT work on the 64 bit

It works fine on 64-bit windows. It's just not a 64-bit application.
It failed on my win 8.1x64 but works first time on my win 7x86  (but then win8.1x64 is a bit low on drivers for other things )

Works on x64 7 and x64 8.1 for me, once the zlib.dll is copied over. Smiley
hero member
Activity: 868
Merit: 1000
Yes the zlib1 is missing and correct it does NOT work on the 64 bit

It works fine on 64-bit windows. It's just not a 64-bit application.
It failed on my win 8.1x64 but works first time on my win 7x86  (but then win8.1x64 is a bit low on drivers for other things )
hero member
Activity: 840
Merit: 1002
Yes the zlib1 is missing and correct it does NOT work on the 64 bit

It works fine on 64-bit windows. It's just not a 64-bit application.
hero member
Activity: 868
Merit: 1000
Thanks!!!
are the win binaries compiled in 32 or 64?  I should probably know the answer...
testing with 20 U1s and 1 Erupter. so far OK!
the windows binaries are missing at least the "zlib1.dll" which was easy to copy over from 32 bit 3.9.0 released version.

My pleasure and thanks for the notice on the missing DLL. I'll take care of that and update windows-build.txt as well.

The build is 32-bit as the 64-bit version has no getwork proxy support. At some point I'll try to work out the 64-bit build process for Windows.

Yes the zlib1 is missing and correct it does NOT work on the 64 bit

You are now "in charge" of the fork,  nwoolls, thankyou.
hero member
Activity: 840
Merit: 1002
Thanks!!!
are the win binaries compiled in 32 or 64?  I should probably know the answer...
testing with 20 U1s and 1 Erupter. so far OK!
the windows binaries are missing at least the "zlib1.dll" which was easy to copy over from 32 bit 3.9.0 released version.

My pleasure and thanks for the notice on the missing DLL. I'll take care of that and update windows-build.txt as well.

The build is 32-bit as the 64-bit version has no getwork proxy support. At some point I'll try to work out the 64-bit build process for Windows.
donator
Activity: 2352
Merit: 1060
between a rock and a block!


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

Thanks!!!
are the win binaries compiled in 32 or 64?  I should probably know the answer...
testing with 20 U1s and 1 Erupter. so far OK!
the windows binaries are missing at least the "zlib1.dll" which was easy to copy over from 32 bit 3.9.0 released version.
newbie
Activity: 11
Merit: 0
forgive my ignorance about this.

using the new build with antminer and overclocking support, i'm seeing a very high rate of hardware errors related to my nanofury. what steps would i need to take to reduce them?

 NFY 0:       |  2.38/ 2.37/ 2.32Gh/s | A: 326 R:0+2(.78%) HW:287/4.0%

you need more V on the nanofury then it goes stabler,

locks to pencil Mod on nanofurys in this forum,

    
Re: [CLOSED] NanoFury NF1 USB stick - Group Buy + Product Assembly
December 07, 2013, 06:27:15 PM
   
 #392
Quote from: prehistoric on December 07, 2013, 05:57:51 AM
Hi vs3,

I'm trying to pencil mod NF1 v0.6 and I've measured R2=100 Ohm and R3=115 Ohm in 3 NF1s by digital multimeter DT830B. R3 is different from R3=2.4 kOhm you've specified in https://bitcointalksearch.org/topic/m.3574768
What could be wrong here?

Taugeran also mentioned R15 and R16 in https://bitcointalksearch.org/topic/m.3574726 Could you please point them on the picture as well as measurement points just to be sure that the measurements will be correct?

Thank you.

i attempted a pencil mod by using a pencil across the right side of r3 (2.4kOhm). i could not get the graphite to stick to the side and was unsuccessful in lowering the resistance (increase the voltage). the performance of my unit decreased due to comms errors with bfgminer:(bitfury_init_oldbuf [4 tries]) caused posibly damaged r3 while penciling.

the unit i tried pencil mod on lost the ability to run higher than 51 or 52 osc6 bits while the untouched unit will run at 54 bits just fine( no comm errors)

if you want to mod the voltage i would recommend purchasing some smd resistors to fit the following calculation:

V = 0.8*(R2+R3)/R3
(and factory settings are R2=100 and R3=2.4k for about 0.833V)

find value of R3(marked 242) that increases voltage to ~0.865 or your preferred target.

resistance across the right side of r3 and left side of r2 at 2k measurement setting is ~0.95 if i rememeber correctly; at work atm :/

newbie
Activity: 6
Merit: 0
Worked for me, thanks a ton NWooll! http://minepeon.com/forums/viewtopic.php?f=4&t=1213&start=30 describes my process for getting it going in Minepeon 2.4.3.
member
Activity: 81
Merit: 10
forgive my ignorance about this.

using the new build with antminer and overclocking support, i'm seeing a very high rate of hardware errors related to my nanofury. what steps would i need to take to reduce them?

 NFY 0:       |  2.38/ 2.37/ 2.32Gh/s | A: 326 R:0+2(.78%) HW:287/4.0%

I wouldn't necessarily call HW of 4% "very high" especially for a Bitfury device.  Usually Bitfury devices are fine with HW errors in the 10% or less range.

ahh, ok. it was just higher than what i've seen before as i've been running it for a while.

thank you!
hero member
Activity: 798
Merit: 1000
forgive my ignorance about this.

using the new build with antminer and overclocking support, i'm seeing a very high rate of hardware errors related to my nanofury. what steps would i need to take to reduce them?

 NFY 0:       |  2.38/ 2.37/ 2.32Gh/s | A: 326 R:0+2(.78%) HW:287/4.0%

I wouldn't necessarily call HW of 4% "very high" especially for a Bitfury device.  Usually Bitfury devices are fine with HW errors in the 10% or less range.
member
Activity: 81
Merit: 10
forgive my ignorance about this.

using the new build with antminer and overclocking support, i'm seeing a very high rate of hardware errors related to my nanofury. what steps would i need to take to reduce them?

 NFY 0:       |  2.38/ 2.37/ 2.32Gh/s | A: 326 R:0+2(.78%) HW:287/4.0%
hero member
Activity: 798
Merit: 1000
...snip...

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...

Try running bfgminer under sudo permissions.
newbie
Activity: 11
Merit: 0
Hello with https://www.dropbox.com/s/z29x4n6ng510joi/bfgminer-npw-antminer.7z, and
bfgminer -S antminer:all -S erupter:all, it goes with my erupter an antminer but my nanofurys no more go why?

 with bfgminer3.9 and only -S erupter:all i see my nanofury and my erupters.

without zadig.

how my nanofury, erupters and antminers go on windows???


setup :

1* dlink 10 port usb hub  -> 2 erupters and 2 nanofurys   3.5A power
1* delock 7 port hub -> 3 antminer 3.5A power
and individual an two differnt usb ports on my pc
so i have enough power i think.
sr. member
Activity: 280
Merit: 250
Helperizer
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.

I had thought as much, and I did get the driver-antminer.o file made, BUT no joy on bfgminer recognizing my ants, using "-S antminer:all" or manually looking with M+ antminer:all during operation when it's telling me no devices found.  As far as I can tell, no errors during the compile.  I even tried with a fresh git clone and antminer feature, and of course did the autogen, configure, make steps.  I do use "strip" - could that be the problem (never has before, but you never know...)?
member
Activity: 75
Merit: 10

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

Thanks! That was the problem. Running nicely now.  Smiley
member
Activity: 75
Merit: 10
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.
newbie
Activity: 3
Merit: 0
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...
hero member
Activity: 1246
Merit: 501
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.
member
Activity: 81
Merit: 10
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.
Pages:
Jump to: