Quote from: nwoolls on July 01, 2014, 06:19:44 PM

Quote from: forzendiablo on July 01, 2014, 03:20:09 PM

Quote from: nwoolls on July 01, 2014, 06:01:42 AM

Quote from: forzendiablo on July 01, 2014, 04:42:01 AM

Quote from: nwoolls on July 01, 2014, 04:27:04 AM

Quote from: jekv2 on June 30, 2014, 07:23:15 PM

Quote from: nwoolls on June 30, 2014, 06:59:46 PM

BFGMiner 4.3 (available now) supports ZeusMiner ASICs (and more) on platforms including the Raspberry Pi and 703n:

https://bitcointalk.org/index.php?topic=626361.msg7602542#msg7602542

Has anyone tested this vs the cgminer beta 3 on windows? I will if anyone would like me too.

Edit:

nvm, it doesnt work for me.

Thankfully an RPI will be here soon, use hashra.

Do you have any details? What doesn't work and what did you try?

The driver has been tested on Windows, OS X, Linux, Raspberry Pi, and OpenWrt with both GAW and ZeusMiner ASICs including Blizzards, Furies, and Black Widows.

To start mining, run:

Code:

bfgminer -S zus:all -o host:port -u username -p password

If you have more than 6 chips, use:

Code:

bfgminer -S zus:all -o host:port -u username -p password --set zus:chips=6

To set the clock, use:

Code:

bfgminer -S zus:all -o host:port -u username -p password --set zus:clock=340

Finally, there are a few ZeusMiners with buggy firmware that don't properly respond to detection. For those you may need to use:

Code:

bfgminer -S zus:all -o host:port -u username -p password --set zus:ignore_golden_nonce=1

so if i had 2 miners 1 works 1 doesnt and im on windows. whats proper command line?

First of all, those all should have included --scrypt in the arguments. My apologies there.

Add -D to the arguments to see the debug output. So to scan for devices and see which one is being flaky:

Code:

bfgminer --scrypt -S zus:all -d? -D

Once you have confirmed one isn't responding to probing, and what the path is, you can use something like:

Code:

bfgminer --scrypt -S zus:all --zus@\\.\COMX:ignore_golden_nonce=1 -d? -D

Where \\.\COMX is the path shown for the devices when listed with the -d? argument.

Code:

bfgminer --scrypt -S zus:all -d? -D

did that but it doesnt save to any file and goes too fast - cannot read it.
how to make it write debug file?

Run it at the command prompt (CMD.exe) rather than from a shortcut so you can view the output when it is completed.

can also add 'pause' on next line, so whe nti finishes it stops and wait for a butto nto be pressed - thats my lazy way