Fury/Blizzard tuning and mods

[J4bberwock]

I do agree on the fact that the devices are a little disappointing:
Power draw is higher than expected
hard limit on overclock that isn't easily removable even if there is still plenty of room for extra hashes on the board.
Extremely fast price drop in the first weeks.

But the good thing is that Gridseed isn't alone anymore and prices are going down.

For those not happy with Zeus, the G-Blades are a good alternative, and the upcoming G-Black, even if it's simply 5 G-Blades in a box, still have a fair price compared to Zeus. It can also overclock "easily" to 35MH/s, probably 37-40MH since they revised the PCB.

Return on investment in crypto is always the same story.
It will depend on which coin you mine, when you mine it, and its value in a few monthes if you hold it.

If you hold the LTC you are making at the moment, and LTC goes up to the point it was in december 2013, you will make profit.
Of course, sometimes, you can make more profit simply buying the coins and waiting, but it's really less fun.

And I like to mod/improve things, so all the new miners that should be available in Q3 will have some room reserved in my collection if I can afford to buy one.

Next one on its way home for tomorrow is a Rockminer, and after it, probably a hurricaneX3 (cooling can be greatly improved on this one and I'd like to see it at 18MH/s)
A2 miners are still too expensive for me to play with them.

[1713244786]

1713244786

[1713244786]

1713244786

[1713244786]

1713244786

[1713244786]

1713244786

[Riley600]

Somewhere ind the Litecoin-Zeus thread Terry stated that WU has to be multiplied by 1.09 to get the pool side speed. But nevertheless it is really under performing. I also have such a dives...same config but is constantly performing 150kH behind the others

I am guessing that you're using the diff. of 2048 as you said same config.

350 might be too high.  Try 340 or try a different build.
Your rejects are high:
A: 593920 R: 26624

Mine look this after approx 12 hrs.
A:1067162 R:7752 WU:1507.6  Beta 1
A:1134848 R:1536 WU:1489.2  Beta 2

That's two different pools.  Beta 1 or 2 will work on one pool.  The other pool get a lot of rejects with beta 2 so I use beta 1.
Are you getting what people are calling a wall of rejects once in a while?  That's what I got on one pool with beta 2.  But beta 1 works on that pool.

Beta 3 was released last night: - Dmaxl's CGminer-4.3.5 Beta 3

What diff. are you using, and thanks for the link, I'll try it out.

Instant rejects with 440/2048, 440/1024 333/1024. Now trying 333/512.

Is there a version of this that also works with Gridseeds?  This one doesn't seem to accept GS flags.

[LongAndShort]

Hey guys/gals i'm hosting a wiki for all of our Zeus miner chips. And would just like to let the modders here know that you are more then welcome to make pages and document all of your findings. We just made it so its fresh. Thanks
wiki.zeusminer.info

[wolf_miner]

Hi, someone has tried to use the TP-LINK 703N as controller, with the firmware from zeusminer https://mega.co.nz/#!4xhWxaaB!Gi1BohY0Pj7SQKoM1n8ZJ58CBdoAAUeYznkGNTb4xVA , is possible to upgrade a WiiBox with firmware V3 to Zeus firmware?

Thanks in advance W_M

[nwoolls]

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

[Kokok]

Ok. New results. Good news.

Tested only for a few hours but it is holding up.

354Mhz. 2048 Difficulty. cgminer-4.3.5.beta3-zeus-win32. 0 rejects! HW 12.

The WU: Falls but increases, stays stable and steady. 2 1/2 Hours running. Gonna do full 24 hour run test.

https://i.imgur.com/ylgDSul.jpg

Glad you were able to get it working...

[djkyno]

Anyone doing anymore physical mod to the machine ? like on cooling aspect or something ?

[djkyno]

Kinda noob here, but what is the purpose of putting the heatsink at that location ?

[kingscrown]

is there any cgminer that doesntn eed COM things? for gridseed there is one which just finds all your machines.

[J4bberwock]

Here are probqbly the best heatsinks for the chips I could find.
http://www.moddiy.com/products/Micro-Thermal-Heatsink-for-Motherboard%27s-MOS-%286.5mm-x-12mm%29.html
They are 6.5x6.5x12mm and we have 12.8mm available between the chip and the top of the case/heatsink.
They are also perfect for most of the power MOSFETs used in gridseeds or Zeus.
http://www.moddiy.com/products/Passive-Heatsink-MOSFET-Chipsink-9mm-%252d-Blue.html
These ones are slightly larger than the 8mm chips but should do the job even better.

I ordered some and hope to receive them soon. They are cheaper when buying more.
If you are interested in buying some, I found the following coupon that gives 10% discount.
WHATSWITHJEFF10

[kingscrown]

is there any cgminer that doesntn eed COM things? for gridseed there is one which just finds all your machines.

Talking about cpuminer? CPUMiner does not support blizzard or fury.

cgminer man. i mean i have 4 furys, id prefer to have tchem in 1 cgminer instance of bfgminer instance not for.
how to accomplish that?

[forzendiablo]

hey on windows what mhz you use for FUrys? 328 or more ?

[icekohl]

Here are probqbly the best heatsinks for the chips I could find.
http://www.moddiy.com/products/Micro-Thermal-Heatsink-for-Motherboard%27s-MOS-%286.5mm-x-12mm%29.html
They are 6.5x6.5x12mm and we have 12.8mm available between the chip and the top of the case/heatsink.
They are also perfect for most of the power MOSFETs used in gridseeds or Zeus.
http://www.moddiy.com/products/Passive-Heatsink-MOSFET-Chipsink-9mm-%252d-Blue.html
These ones are slightly larger than the 8mm chips but should do the job even better.

I ordered some and hope to receive them soon. They are cheaper when buying more.
If you are interested in buying some, I found the following coupon that gives 10% discount.
WHATSWITHJEFF10

Personally I went with http://www.amazon.com/gp/product/B007XACV8O/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1 . They arrived in 2 days and are just a smidge larger than the chips, self adhesive thermal pads made for super simple install on chips and mosfets.

[nwoolls]

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 --scrypt -S zus:all -o host:port -u username -p password

If you have more than 6 chips, use:

Code:

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

To set the clock, use:

Code:

bfgminer --scrypt -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 --scrypt -S zus:all -o host:port -u username -p password --set zus:ignore_golden_nonce=1

[forzendiablo]

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?

[nwoolls]

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.

[forzendiablo]

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?

[forzendiablo]

ok here is my log, which one is bad and giving me none errors?

Code:

[2014-07-01 17:20:23] setrlimit: Not supported by platform
[2014-07-01 17:20:23] Started bfgminer 4.2.2-ZeusMiner
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:003:255
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:255
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:001:255
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 1 (iMan
r) from usb:001:001: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 2 (iPro
om usb:001:001: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 3 (iSer
r) from usb:001:001: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 1 (iMan
r) from usb:002:002: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 2 (iPro
om usb:002:002: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:004
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:005
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:003
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:006
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:008
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:007
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:009
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:001
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:003:001
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] Failed to get PortName registry key value in lowl-
vcom_devinfo_scan_windows__hubport():447:


[2014-07-01 17:20:24] FTDI reports 0 devices
[2014-07-01 17:20:24] FTDI device list failed, not using FTDI autodetect

[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 200
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 400
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 800
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 1000
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 2000
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 4000
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:003:001 (pa
), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:001 (pa
), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:009 (pa
), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:007 (pa
), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:008 (pa
), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:006 (pa
), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:003 (pa
), vid=1058, pid=1003, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:005 (pa
), vid=05e3, pid=0610, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:004 (pa
), vid=05e3, pid=0610, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:002 (pa
), vid=0518, pid=0001, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:001:001 (pa
), vid=046d, pid=c24e, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:001:255 (pa
), vid=1b21, pid=1042, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:255 (pa
), vid=8086, pid=1c26, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:003:255 (pa
), vid=8086, pid=1c2d, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:8 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:7 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:6 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:1 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:9 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] Timers: Using QueryPerformanceCounter

[2014-07-01 17:20:24] Recalibrating timeofday offset (delta 1403822711.4

[2014-07-01 17:20:29] Found ZUS 0 at \\.\COM1
[2014-07-01 17:20:29] Found ZUS 0 at \\.\COM1,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Zeus 0 on \\.\COM1 detected.
[2014-07-01 17:20:29] Found ZUS 1 at \\.\COM9
[2014-07-01 17:20:29] Found ZUS 2 at \\.\COM7
[2014-07-01 17:20:29] Found ZUS 3 at \\.\COM6
[2014-07-01 17:20:29] Found ZUS 1 at \\.\COM9,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] Found ZUS 4 at \\.\COM8
[2014-07-01 17:20:29] Found ZUS 2 at \\.\COM7,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] Found ZUS 3 at \\.\COM6,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Found ZUS 4 at \\.\COM8,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Zeus 1 on \\.\COM9 detected.
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Zeus 2 on \\.\COM7 detected.
[2014-07-01 17:20:29] Zeus 3 on \\.\COM6 detected.
[2014-07-01 17:20:29] Zeus 4 on \\.\COM8 detected.
[2014-07-01 17:20:29] Devices detected:
[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM1)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM9)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM7)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM6)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM8)

 devices listed

[ZiG]

ok here is my log, which one is bad and giving me none errors?

Code:

[2014-07-01 17:20:23] setrlimit: Not supported by platform
[2014-07-01 17:20:23] Started bfgminer 4.2.2-ZeusMiner
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:003:255
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:255
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:001:255
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 1 (iMan
r) from usb:001:001: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 2 (iPro
om usb:001:001: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 3 (iSer
r) from usb:001:001: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 1 (iMan
r) from usb:002:002: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error getting USB string 2 (iPro
om usb:002:002: LIBUSB_ERROR_NOT_FOUND
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:004
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:005
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:003
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:006
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:008
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:007
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:009
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:002:001
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] usb_devinfo_scan: Error opening device usb:003:001
_ERROR_NOT_SUPPORTED
[2014-07-01 17:20:24] Failed to get PortName registry key value in lowl-
vcom_devinfo_scan_windows__hubport():447:


[2014-07-01 17:20:24] FTDI reports 0 devices
[2014-07-01 17:20:24] FTDI device list failed, not using FTDI autodetect

[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 200
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 400
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 800
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 1000
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 2000
[2014-07-01 17:20:24] QueryDosDevice returned insufficent buffer error;
g to 4000
[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:003:001 (pa
), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:001 (pa
), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:009 (pa
), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:007 (pa
), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:008 (pa
), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:006 (pa
), vid=10c4, pid=ea60, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:003 (pa
), vid=1058, pid=1003, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:005 (pa
), vid=05e3, pid=0610, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:004 (pa
), vid=05e3, pid=0610, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:002 (pa
), vid=0518, pid=0001, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:001:001 (pa
), vid=046d, pid=c24e, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:001:255 (pa
), vid=1b21, pid=1042, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:002:255 (pa
), vid=8086, pid=1c26, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found usb device at usb:003:255 (pa
), vid=8086, pid=1c2d, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:8 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:7 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:6 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:1 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] lowlevel_scan: Found vcom device at com:9 (path=\\
vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

[2014-07-01 17:20:24] Timers: Using QueryPerformanceCounter

[2014-07-01 17:20:24] Recalibrating timeofday offset (delta 1403822711.4

[2014-07-01 17:20:29] Found ZUS 0 at \\.\COM1
[2014-07-01 17:20:29] Found ZUS 0 at \\.\COM1,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Zeus 0 on \\.\COM1 detected.
[2014-07-01 17:20:29] Found ZUS 1 at \\.\COM9
[2014-07-01 17:20:29] Found ZUS 2 at \\.\COM7
[2014-07-01 17:20:29] Found ZUS 3 at \\.\COM6
[2014-07-01 17:20:29] Found ZUS 1 at \\.\COM9,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] Found ZUS 4 at \\.\COM8
[2014-07-01 17:20:29] Found ZUS 2 at \\.\COM7,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] Found ZUS 3 at \\.\COM6,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Found ZUS 4 at \\.\COM8,  Init: baud=115200 with t
wing parameters:
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Zeus 1 on \\.\COM9 detected.
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Zeus 2 on \\.\COM7 detected.
[2014-07-01 17:20:29] Zeus 3 on \\.\COM6 detected.
[2014-07-01 17:20:29] Zeus 4 on \\.\COM8 detected.
[2014-07-01 17:20:29] Devices detected:
[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM1)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM9)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM7)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM6)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM8)

 devices listed

"...
[2014-07-01 17:20:29] Zeus 1 on \\.\COM9 detected.
[2014-07-01 17:20:29] [Speed] 328Mhz core|chip|board: [30kH/s], [245kH/s
kH/s], readcount:300, bitnum:3
[2014-07-01 17:20:29] Zeus 2 on \\.\COM7 detected.
[2014-07-01 17:20:29] Zeus 3 on \\.\COM6 detected.
[2014-07-01 17:20:29] Zeus 4 on \\.\COM8 detected.
[2014-07-01 17:20:29] Devices detected:
[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM1)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM9)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM7)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM6)

[2014-07-01 17:20:29]  Device (driver=zeus; procs=1; path=\\.\COM8)

 devices listed"

...just READ IT, buddy...

ZiG

   

[nwoolls]

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.