Will they ever ROI ?
No. It is -$42.00 USD "win" (lost). 
Topic: [SOLD OUT] NEW USB MINER - 5 Gh/s NANO FURY II USB MINER, **$39.00** - page 2. (Read 21262 times)
May 05, 2014, 06:25:54 AM
5 GH/s at $49.00 USD? This is very expensive. Maybe $8.00 USD and I buy it, if delivery is instant.
May 05, 2014, 06:17:23 AM
is it even worth to buy these ? Will they ever ROI ?
May 05, 2014, 02:50:52 AM
Any indications of when CGMiner will support full speed for NF2's?
In case you've missed it:
I've added support for NF2 and NF6 into cgminer git master branch. (...)
The NF2s are behaving very nicely. This is at --nfu-bits 54:
The NF2s are behaving very nicely. This is at --nfu-bits 54:
Code:
14: NF2 00001099: | 4.670G / 4.655Gh/s WU: 65.2/m
23: NF2 00000753: | 4.447G / 4.509Gh/s WU: 63.6/m
23: NF2 00000753: | 4.447G / 4.509Gh/s WU: 63.6/m
May 04, 2014, 12:32:08 PM
- cgminer uses its own version of the HID driver (Zadig). So in order to use cgminer you have to trick Windows to replace the driver for a particular device with Zadig's.
I hate to be pedantic but this is not quite true. The device talks USB while HID is a driver designed for user interface devices like keyboards and mice, so when using software that uses this driver, it goes device -> usb -> hid driver -> software. Zadig is not actually a driver; it's a utility to tell windows to remove the driver and use the microsoft direct usb communication protocol (effectively a Microsoft driver called WinUSB). So while WinUSB appears to be a "driver" it's actually telling windows to just give the raw usb data to the software. So software that uses WinUSB (like cgminer which uses it for every single USB device) is talking directly to the usb device, bypassing the need for any driver, so it is going device -> usb -> cgminer.
Having said that, we don't have support for 2+ chip nanofury based devices, but VS3 is kindly sending me some devices to add support to cgminer, thanks!
I just tried 4.3.3, still running at half speed.
Any indications of when CGMiner will support full speed for NF2's?
May 03, 2014, 06:16:45 PM
MAY SPECIAL - BUY 3 GET 1 FREE AT WWW.MOONLIGHTMINER.COM
April 25, 2014, 12:51:15 AM
Major price reduction. See OP. 
April 23, 2014, 07:52:47 PM
Bump
April 18, 2014, 10:27:09 PM
Also - if you are interested in the NF6 (11-12 Gh/s)you can order them via our Assembly thread at
https://bitcointalksearch.org/topic/closed-assembly-service-for-bitfury-r2-chips-into-nano-fury-6-usb-miner-545507
This is the only way to get a Nano Fury 6 until some in our group start selling them after our assembly service is complete.
We will be closing the group and starting PCB production next week. Minimum order of 8 required.
Please add any questions to the Assembly thread (not this one) or PM me.
Thanks!!
https://bitcointalksearch.org/topic/closed-assembly-service-for-bitfury-r2-chips-into-nano-fury-6-usb-miner-545507
This is the only way to get a Nano Fury 6 until some in our group start selling them after our assembly service is complete.
We will be closing the group and starting PCB production next week. Minimum order of 8 required.
Please add any questions to the Assembly thread (not this one) or PM me.
Thanks!!
April 18, 2014, 10:12:22 PM
Reminder to all to make sure you are only using the OP link for Bfgminer. Other versions do not work (yet).
April 17, 2014, 05:47:03 PM
Con - thanks for the clarification! That's actually much better than mine! (which was rather simplified when it shouldn't have been as much)
April 17, 2014, 10:39:48 AM
- cgminer uses its own version of the HID driver (Zadig). So in order to use cgminer you have to trick Windows to replace the driver for a particular device with Zadig's.
I hate to be pedantic but this is not quite true. The device talks USB while HID is a driver designed for user interface devices like keyboards and mice, so when using software that uses this driver, it goes device -> usb -> hid driver -> software. Zadig is not actually a driver; it's a utility to tell windows to remove the driver and use the microsoft direct usb communication protocol (effectively a Microsoft driver called WinUSB). So while WinUSB appears to be a "driver" it's actually telling windows to just give the raw usb data to the software. So software that uses WinUSB (like cgminer which uses it for every single USB device) is talking directly to the usb device, bypassing the need for any driver, so it is going device -> usb -> cgminer.
Having said that, we don't have support for 2+ chip nanofury based devices, but VS3 is kindly sending me some devices to add support to cgminer, thanks!
April 17, 2014, 10:34:30 AM
FYI, I created self-signed drivers for bf1 and bifury drivers, now works with bfgminer on win8.1 x64.
http://blog.insanegenius.com/2014/04/16/self-signed-bitfury-drivers/
http://blog.insanegenius.com/2014/04/16/self-signed-bitfury-drivers/
interesting post!
A few clarifications though -
- most of the other devices (such as c-scape's bf1/bifury/etc) communicate via a virtual COM (serial) port. Those usually require drivers.
- NanoFury via bfgminer uses Windows' built-in HID drivers (hidusb.sys) - and since those come from Microsoft all is good with them and they are properly signed.
- cgminer uses its own version of the HID driver (Zadig). So in order to use cgminer you have to trick Windows to replace the driver for a particular device with Zadig's. If you want to reverse that you need to "roll back driver". Sometimes uninstalling the device will not work as Windows already "knows better" and if it sees the same device will assign again the "last known good" driver - e.g. Zadig's.
Understood, I just meant that in my order of preference:
1) Devices identifies itself a standard HID device and Windows (and Linux and Mac) has built-in drivers. (Nano Fury II Thumbs Up)
2) Hardware vendor provides WHQL signed drivers for device for all platforms.
3) Zadig can be used to automatically install WinUSB/LibUSB drivers for device.
4) I have to sign the driver myself.
P.
April 17, 2014, 03:33:14 AM
FYI, I created self-signed drivers for bf1 and bifury drivers, now works with bfgminer on win8.1 x64.
http://blog.insanegenius.com/2014/04/16/self-signed-bitfury-drivers/
http://blog.insanegenius.com/2014/04/16/self-signed-bitfury-drivers/
interesting post!
A few clarifications though -
- most of the other devices (such as c-scape's bf1/bifury/etc) communicate via a virtual COM (serial) port. Those usually require drivers.
- NanoFury via bfgminer uses Windows' built-in HID drivers (hidusb.sys) - and since those come from Microsoft all is good with them and they are properly signed.
- cgminer uses its own version of the HID driver (Zadig). So in order to use cgminer you have to trick Windows to replace the driver for a particular device with Zadig's. If you want to reverse that you need to "roll back driver". Sometimes uninstalling the device will not work as Windows already "knows better" and if it sees the same device will assign again the "last known good" driver - e.g. Zadig's.
April 16, 2014, 10:48:27 PM
FYI, I created self-signed drivers for bf1 and bifury drivers, now works with bfgminer on win8.1 x64.
http://blog.insanegenius.com/2014/04/16/self-signed-bitfury-drivers/
http://blog.insanegenius.com/2014/04/16/self-signed-bitfury-drivers/
April 16, 2014, 08:40:52 PM
yeah, I saw it 
I wanted to stress on the importance of drivers' conflicts and incompatibility
I wanted to stress on the importance of drivers' conflicts and incompatibility
April 16, 2014, 03:10:43 PM
Thank you.
No need to guess, I did write that I used Zadig in my initial post
I reverted to the Windows drivers and BFGMiner can now find the nf2.
But now none of my red fury or hex fury's work (no signed drivers for win8x64), I ended up running bfgminer and cgminer at the same time.
CGMiner support would be awesome, so much easier to get devices working with cgminer than bfgminer.
P.
No need to guess, I did write that I used Zadig in my initial post
I reverted to the Windows drivers and BFGMiner can now find the nf2.
But now none of my red fury or hex fury's work (no signed drivers for win8x64), I ended up running bfgminer and cgminer at the same time.
CGMiner support would be awesome, so much easier to get devices working with cgminer than bfgminer.
P.
April 16, 2014, 02:11:14 AM
bfgminer.exe -d? results in 0 devices found.
cgminer finds and uses them all.
cgminer finds and uses them all.
Let me guess - did you install the Zadig drivers?
Quote
Q: I ran cgminer, and now BFGMiner doesn't work!
A: cgminer has its own non-standard implementations of the drivers for most USB
devices, and requires you to replace the official drivers with WinUSB on Windows
(usually using Zadig). Before you can use BFGMiner, you will need to restore the
original driver. Uninstalling the device (and WinUSB driver) from Device Manager
and re-plugging it will usually trigger driver re-installation to the default
drivers.
(source: BFGMINER Read-Me : https://github.com/luke-jr/bfgminer) A: cgminer has its own non-standard implementations of the drivers for most USB
devices, and requires you to replace the official drivers with WinUSB on Windows
(usually using Zadig). Before you can use BFGMiner, you will need to restore the
original driver. Uninstalling the device (and WinUSB driver) from Device Manager
and re-plugging it will usually trigger driver re-installation to the default
drivers.
April 16, 2014, 01:14:49 AM
Ahhh, that dreaded search option ... :-)
that's why - cgminer does not (yet) support multi-chip NanoFury devices (as mentioned on the previous page). This likely to be resolved in the coming month - some hardware will be sent towards Con within the next few days...
In case you've missed the instructions in the opening post here is the important bit again:
which is not perfectly accurate - the link above will get you the most latest version, and support was added about a month ago, so if you have a build since then you might be good. Or if in doubt - better get the one from the link.
Hi, have two NF2's, using cgminer, I get less than 2GH/s.
Any ideas how to get closer to 4GH/s?
Any ideas how to get closer to 4GH/s?
that's why - cgminer does not (yet) support multi-chip NanoFury devices (as mentioned on the previous page). This likely to be resolved in the coming month - some hardware will be sent towards Con within the next few days...
In case you've missed the instructions in the opening post here is the important bit again:
- Requires this version of BfgMiner: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer
which is not perfectly accurate - the link above will get you the most latest version, and support was added about a month ago, so if you have a build since then you might be good. Or if in doubt - better get the one from the link.
If only I knew what terms to search for
Unfortunately bfgminer does not work, as in it does not detect any devices, while cgminer has been working for a long time.
bfgminer.exe -d? results in 0 devices found.
cgminer finds and uses them all.
Any advice on getting bfgminer working?
bfgminer -D -d?:
Code:
[2014-04-15 22:32:49] setrlimit: Not supported by platform
[2014-04-15 22:32:49] Started bfgminer 3.99.0
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:001:001: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:002:002: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:001:007: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:001:006: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:002:012: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:002:007: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:001:002: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:002:001: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:001:003: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] usb_devinfo_scan: Error opening device usb:002:003: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:49] hidapi_try_lib: Couldn't load libhidapi.dll: unknown
[2014-04-15 22:32:49] hidapi_try_lib: Loaded libhidapi-0.dll, but no devices enumerated; trying other libraries
[2014-04-15 22:32:49] hidapi_try_lib: Couldn't load libhidapi-hidraw.dll: unknown
[2014-04-15 22:32:49] hidapi_try_lib: Couldn't load libhidapi-libusb.dll: unknown
[2014-04-15 22:32:49] hid_devinfo_scan: Failed to load any hidapi library
[2014-04-15 22:32:49] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:49] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:49] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:49] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:49] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:49] FTD2XX.DLL failed to load, not using FTDI autodetect
[2014-04-15 22:32:49] QueryDosDevice returned insufficent buffer error; enlarging to 200
[2014-04-15 22:32:49] QueryDosDevice returned insufficent buffer error; enlarging to 400
[2014-04-15 22:32:49] QueryDosDevice returned insufficent buffer error; enlarging to 800
[2014-04-15 22:32:49] QueryDosDevice returned insufficent buffer error; enlarging to 1000
[2014-04-15 22:32:49] QueryDosDevice returned insufficent buffer error; enlarging to 2000
[2014-04-15 22:32:49] QueryDosDevice returned insufficent buffer error; enlarging to 4000
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:010 (path=(null), vid=198c, pid=b1f1, manuf=c-scape, prod=bi?fury, serial=0606f02a02af266)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:003 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:003 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:011 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:010 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:009 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:008 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:008 (path=(null), vid=03eb, pid=204b, manuf=BPMC, prod=Bitfury BF1, serial=A49363533323517170B1)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=8086, pid=1c26, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:002 (path=(null), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:009 (path=(null), vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF2 v0.5 by MLM, serial=0000146469)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:014 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:013 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:006 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:007 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:012 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:006 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:007 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:002 (path=(null), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:004 (path=(null), vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF2 v0.5 by MLM, serial=0000144002)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=8086, pid=1c2d, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:001:005 (path=(null), vid=03eb, pid=204b, manuf=BPMC, prod=Bitfury BF1, serial=A49363533323516141F0)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:005 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found usb device at usb:002:004 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] lowlevel_scan: Found vcom device at com:3 (path=\\.\COM3, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found vcom device at com:1 (path=\\.\COM1, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:49] lowlevel_scan: Found vcom device at com:4 (path=\\.\COM4, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:49] Device rescan requested
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:001:001: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:002:002: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:001:007: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:001:006: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:002:012: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:002:007: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:001:002: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:002:001: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:001:003: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] usb_devinfo_scan: Error opening device usb:002:003: LIBUSB_ERROR_NOT_SUPPORTED
[2014-04-15 22:32:50] hidapi_try_lib: Couldn't load libhidapi.dll: unknown
[2014-04-15 22:32:50] hidapi_try_lib: Loaded libhidapi-0.dll, but no devices enumerated; trying other libraries
[2014-04-15 22:32:50] hidapi_try_lib: Couldn't load libhidapi-hidraw.dll: unknown
[2014-04-15 22:32:50] hidapi_try_lib: Couldn't load libhidapi-libusb.dll: unknown
[2014-04-15 22:32:50] hid_devinfo_scan: Failed to load any hidapi library
[2014-04-15 22:32:50] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:50] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:50] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:50] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:50] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
[2014-04-15 22:32:50] FTD2XX.DLL failed to load, not using FTDI autodetect
[2014-04-15 22:32:50] QueryDosDevice returned insufficent buffer error; enlarging to 200
[2014-04-15 22:32:50] QueryDosDevice returned insufficent buffer error; enlarging to 400
[2014-04-15 22:32:50] QueryDosDevice returned insufficent buffer error; enlarging to 800
[2014-04-15 22:32:50] QueryDosDevice returned insufficent buffer error; enlarging to 1000
[2014-04-15 22:32:50] QueryDosDevice returned insufficent buffer error; enlarging to 2000
[2014-04-15 22:32:50] QueryDosDevice returned insufficent buffer error; enlarging to 4000
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:010 (path=(null), vid=198c, pid=b1f1, manuf=c-scape, prod=bi?fury, serial=0606f02a02af266)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:003 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:003 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:011 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:010 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:009 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:008 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:008 (path=(null), vid=03eb, pid=204b, manuf=BPMC, prod=Bitfury BF1, serial=A49363533323517170B1)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=8086, pid=1c26, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:002 (path=(null), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:009 (path=(null), vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF2 v0.5 by MLM, serial=0000146469)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:014 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:013 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:006 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:007 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:012 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:006 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:007 (path=(null), vid=2109, pid=2812, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:002 (path=(null), vid=8087, pid=0024, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:004 (path=(null), vid=04d8, pid=00de, manuf=Microchip Technology Inc., prod=NanoFury NF2 v0.5 by MLM, serial=0000144002)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=8086, pid=1c2d, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:001:005 (path=(null), vid=03eb, pid=204b, manuf=BPMC, prod=Bitfury BF1, serial=A49363533323516141F0)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:005 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found usb device at usb:002:004 (path=(null), vid=10c4, pid=ea60, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] lowlevel_scan: Found vcom device at com:3 (path=\\.\COM3, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found vcom device at com:1 (path=\\.\COM1, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
[2014-04-15 22:32:50] lowlevel_scan: Found vcom device at com:4 (path=\\.\COM4, vid=0000, pid=0000, manuf=Silicon Labs, prod=CP2102 USB to UART Bridge Controller, serial=0001)
[2014-04-15 22:32:50] Device rescan requested a second time, delaying
[2014-04-15 22:32:50] Timers: Using QueryPerformanceCounter
[2014-04-15 22:32:50] Recalibrating timeofday offset (delta 1396381875.1084103s)
[2014-04-15 22:32:50] schedule_rescan: Scheduling rescan (no rescans currently pending)
[2014-04-15 22:32:50] Devices detected:
April 16, 2014, 12:00:40 AM
Ahhh, that dreaded search option ... :-)
that's why - cgminer does not (yet) support multi-chip NanoFury devices (as mentioned on the previous page). This likely to be resolved in the coming month - some hardware will be sent towards Con within the next few days...
In case you've missed the instructions in the opening post here is the important bit again:
which is not perfectly accurate - the link above will get you the most latest version, and support was added about a month ago, so if you have a build since then you might be good. Or if in doubt - better get the one from the link.
Hi, have two NF2's, using cgminer, I get less than 2GH/s.
Any ideas how to get closer to 4GH/s?
Any ideas how to get closer to 4GH/s?
that's why - cgminer does not (yet) support multi-chip NanoFury devices (as mentioned on the previous page). This likely to be resolved in the coming month - some hardware will be sent towards Con within the next few days...
In case you've missed the instructions in the opening post here is the important bit again:
- Requires this version of BfgMiner: http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer
which is not perfectly accurate - the link above will get you the most latest version, and support was added about a month ago, so if you have a build since then you might be good. Or if in doubt - better get the one from the link.
April 15, 2014, 10:38:43 PM
Hi, have two NF2's, using cgminer, I get less than 2GH/s.
Running on Windows Server 2012 R2.
Used zadig to set all USB devices to WinUSB.
Using CGMiner 4.2.2
Using two "Aitech USB 3.0 10 Ports HUB with 12V4A Power Adapter and Power Switch"
2 ports running fans
2 ports running NF2's
2 ports running red fury's
1 port running hex fury
rest of ports running old block erupters
Any ideas how to get closer to 4GH/s?
P.
Running on Windows Server 2012 R2.
Used zadig to set all USB devices to WinUSB.
Using CGMiner 4.2.2
Using two "Aitech USB 3.0 10 Ports HUB with 12V4A Power Adapter and Power Switch"
2 ports running fans
2 ports running NF2's
2 ports running red fury's
1 port running hex fury
rest of ports running old block erupters
Code:
cgminer version 4.2.2 - Started: [2014-04-15 19:27:52]
--------------------------------------------------------------------------------
(5s):23.07G (1m):23.57G (5m):17.84G (15m):8.886G (avg):23.50Gh/s
A:2349 R:14 HW:47 WU:336.9/m
Connected to stratum.bitcoin.cz diff 14 with stratum as user XXX
Block: 391a31cc... Diff:6.12G Started: [19:29:24] Best share: 1.38K
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
0: AMU 0 : | 306.9M / 327.6Mh/s
1: AMU 1 : | 335.8M / 329.9Mh/s
2: AMU 2 : | 335.8M / 334.0Mh/s
3: AMU 3 : | 335.5M / 331.4Mh/s
4: AMU 4 : | 335.3M / 332.3Mh/s
5: AMU 5 : | 335.2M / 332.5Mh/s
6: AMU 6 : | 335.9M / 333.6Mh/s
7: AMU 7 : | 335.7M / 330.7Mh/s
8: BF1 0f141615: | 2.297G / 2.200Gh/s
9: NF1 0 : | 1.876G / 1.852Gh/s
10: NF1 1 : | 1.777G / 1.539Gh/s
11: BF1 1b071715: | 1.919G / 2.320Gh/s
12: BXF 0 : 57.2C | 11.54G / 11.39Gh/s
13: AMU 8 : | 335.7M / 333.5Mh/s
14: AMU 9 : | 335.9M / 328.2Mh/s
15: AMU 10 : | 335.9M / 335.3Mh/s
16: AMU 11 : | 332.6M / 327.3Mh/s
17: AMU 12 : | 335.2M / 331.7Mh/s
--------------------------------------------------------------------------------
Any ideas how to get closer to 4GH/s?
P.
Jump to: