Ice Fury (nano fury) support thread.

[HellDiverUK]

Can you try a different OS? Running them on raspberry pi has issues with hidapi

Yes - I just got it running on a Windows laptop to rule out chip issues.

Is the issue with the Raspberry hardware? I'd like to move it back if possible.

The Pi's USB support is broken at best.  Don't bank on getting them working on the Pi, ever.

They run perfectly on a BeagleBone Black, which hasn't got broken USB.

[1713879329]

1713879329

[1713879329]

1713879329

[1713879329]

1713879329

[1713879329]

1713879329

[Mudbankkeith]

Can you try a different OS? Running them on raspberry pi has issues with hidapi

Yes - I just got it running on a Windows laptop to rule out chip issues.

Is the issue with the Raspberry hardware? I'd like to move it back if possible.

The Pi's USB support is broken at best.  Don't bank on getting them working on the Pi, ever.

They run perfectly on a BeagleBone Black, which hasn't got broken USB.

That's a shame, Blues,Reds,Bi.'s,Twins, they all live happily together on the Pi.

[vs3]

Can you try a different OS? Running them on raspberry pi has issues with hidapi

Yes - I just got it running on a Windows laptop to rule out chip issues.

Is the issue with the Raspberry hardware? I'd like to move it back if possible.

The Pi's USB support is broken at best.  Don't bank on getting them working on the Pi, ever.

They run perfectly on a BeagleBone Black, which hasn't got broken USB.

That's a shame, Blues,Reds,Bi.'s,Twins, they all live happily together on the Pi.

Hopefully this helps:

Hello,

could anyone sent me a kind of tutorial how to get the nanofury working on rasberry pi? I dont know much about linux.

Raspian ist still installed, and networkspeed ist reduced like in your messages. But which bfgminer version should I install (link?). What do you mean with "after comiling"

are there any other settings do do? ... I tryed lots of versions but nothing works... A small tutorial would save my next 5 evenings

Greetings from Germany

First you need to install needed library

Code:

1. sudo aptitude update
2. sudo aptitude install libudev-dev libusb-1.0-0-dev libfox-1.6-dev autotools-dev autoconf automake libtool libncurses-dev yasm curl libcurl4-openssl-dev libjansson-dev pkg-config uthash-dev make pkg-config yasm 

Second download HIDAPI from git

Code:

1. git clone git://github.com/signal11/hidapi.git hidapi
2. cd hidapi
3. ./bootstrap
4. ./configure --prefix=/usr
5. make
6. sudo make install 

Third download bfgminer to some directory(in this example is "miner")

Code:

1. mkdir miner
2. cd miner
3. wget http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.8.1/bfgminer-3.8.1.tbz2
4. tar xvf bfgminer-3.8.1.tbz2
5. cd bfgminer-3.8.1
6. ./configure 
7. make

You can enable or disable some miner while run ./configure bfgminer with this options
Example: ./configure --enable-bfsb --disable-bitforce

Code:

	--disable-avalon        Compile support for Avalon (default enabled)
	--enable-cpumining      Build with cpu mining support(default disabled)
	--enable-opencl         Compile support for OpenCL (default disabled)
	--disable-adl           Build without ADL monitoring (default enabled)
	--disable-bitfury       Compile support for Bitfury (default enabled)
	--enable-bfsb           Compile support for BFSB (default disabled)
	--disable-bigpic        Compile support for Big Picture Mining USB (default enabled)
	--disable-littlefury    Compile support for LittleFury (default enabled)
	--disable-nanofury      Compile support for NanoFury (default enabled)
	--disable-hashbuster    Compile support for HashBuster Nano (default enabled)
	--disable-hashbuster2   Compile support for HashBuster Micro (default if libusb)
	--enable-metabank       Compile support for Metabank (default disabled)
	--disable-bitforce      Compile support for BitForce (default enabled)
	--disable-icarus        Compile support for Icarus (default enabled)
	--disable-klondike      Compile support for Klondike (default enabled)
	--enable-knc            Compile support for KnC (default disabled)
	--disable-modminer      Compile support for ModMiner (default enabled)
	--disable-x6500         Compile support for X6500 (default enabled)
	--disable-ztex          Compile support for ZTEX (default if libusb)
	--enable-scrypt         Compile support for scrypt mining (default disabled)
	--with-system-libblkmaker  Use system libblkmaker rather than bundled one (default disabled)
	--without-sensors       Build with libsensors monitoring (default enabled)
	--without-curses        Compile support for curses TUI (default enabled)
	--without-libmicrohttpd Compile support for libmicrohttpd getwork server (default enabled)
	--without-libevent      Compile support for libevent stratum server (default enabled)
	--without-libusb        Compile using libusb (default enabled)
	--without-libudev       Autodetect FPGAs using libudev (default enabled)

Then change usb speed to usb 1 with text editor nano

Code:

1. sudo nano /boot/cmdline.txt
then add dwc_otg.speed=1 at the end of line

To run bfgminer just go to the directory

Code:

1. cd miner
2. cd bfgminer-3.8.1
3. sudo ./bfgminer

That was the summary i colected from other thread since i am also linux noob 

[HellDiverUK]

^^^

Adding dwc_otg.speed=1 brings the Pi's USB down to USB1.1 speed.  This is a kludge at best, especially considering the Pi's NIC runs off the same USB bus.  You're essentially totally nerfing the Pi's USB and NIC throughput to a total 12Mb (taking off protocol overhead you're less than 10Mb).

[vs3]

I agree. I'm not saying it's an ideal solution. I'm merely saying that there is a way.

There are also other ways - see https://bitcointalk.org/index.php?topic=137934.msg4315185#msg4315185

[nwoolls]

Hi there. I have a How-To up for mining with Ice Fury on Mac OS X:

http://nf1.xgminer.com

Great little devices! 

[-ck]

Posted the first version of cgminer (3.10.0) that supports these devices.

[vs3]

Posted the first version of cgminer (3.10.0) that supports these devices.

I read about a lot of magic in the release notes ... I like magic

Anyways - Nicely done! Thanks Con!

[snoopy_nzl]

Posted the first version of cgminer (3.10.0) that supports these devices.

I just tried this but I cant get passed this error, I enabled Bitfury devices in configure as I didnt see any specific ref to nano or ice fury..(was that ok?)

[2014-01-10 16:55:31] Started cgminer 3.10.0
 [2014-01-10 16:55:33] Failed to sem_timedwait errno=4 cgsem=0x0xbfbf7a4c in usb
utils.c callback_wait():2451

[-ck]

Posted the first version of cgminer (3.10.0) that supports these devices.

I just tried this but I cant get passed this error, I enabled Bitfury devices in configure as I didnt see any specific ref to nano or ice fury..(was that ok?)

[2014-01-10 16:55:31] Started cgminer 3.10.0
 [2014-01-10 16:55:33] Failed to sem_timedwait errno=4 cgsem=0x0xbfbf7a4c in usb
utils.c callback_wait():2451

What did you build it on? I've only tried it on pc linux/windows so far.

[snoopy_nzl]

Posted the first version of cgminer (3.10.0) that supports these devices.

I just tried this but I cant get passed this error, I enabled Bitfury devices in configure as I didnt see any specific ref to nano or ice fury..(was that ok?)

[2014-01-10 16:55:31] Started cgminer 3.10.0
 [2014-01-10 16:55:33] Failed to sem_timedwait errno=4 cgsem=0x0xbfbf7a4c in usb
utils.c callback_wait():2451

What did you build it on? I've only tried it on pc linux/windows so far.

Sorry this was on PC Ubuntu 12.04.

Seems to be ok now after a removal and reinsert of devices.

[tk1337]

Beastlymac, I just got the units in today, so far I'm pretty impressed!
Awesome smaller design, makes the Blue/Red Fury USB's look huge, hehe. It would seem as if they are already over clocked, hehe, one is running at a solid 2.9GH/s & the other at 3.2GH/s

I haven't really played with the much, what's them much yet and won't get a chance to for a little while as I'll be away on business next week, but so far it's looking awesome. What's the over-clocking magic for these, resistor change?

If anyone is curious, I'm running them on a Beaglebone Black w/Debian & CGMiner 3.10.0.

[Beastlymac]

Beastlymac, I just got the units in today, so far I'm pretty impressed!
Awesome smaller design, makes the Blue/Red Fury USB's look huge, hehe. It would seem as if they are already over clocked, hehe, one is running at a solid 2.9GH/s & the other at 3.2GH/s

I haven't really played with the much, what's them much yet and won't get a chance to for a little while as I'll be away on business next week, but so far it's looking awesome. What's the over-clocking magic for these, resistor change?

If anyone is curious, I'm running them on a Beaglebone Black w/Debian & CGMiner 3.10.0.

All that is required is usb 3.0 and osc bit 55 to max them.

[krazy_al]

I got in on the pre-order for the Ice Fury and took up the option to get a Red Fury at a slight discount.  They arrived today and so far I've not been able to get the Ice Fury to work.  The Red Fury is working and giving me what I expected as for a hash rate. 

So first I'd love help getting the Ice Fury to be seen.  I installed the driver which worked just fine for the Red Fury but when I go into bfgminer it shows one device which is Bitfury BF1 from BFMG.  If I do the + to add a device, bfgminer doesn't find the Ice Fury.  I'm running Windows 7 Pro and bfgminer 3.9 x64.  One odd thing is when I go into Device Manager the Ice Fury is showing up under Universal Serial Bus Devices and is listed as NanoFury NF1 v0.7.  The working Red Fury is showing up under Ports (COM & LPT) as Bitfury BF1 USB Miner (COM4).  I would expect both to show up in the same spot, I've tried reinstalling the driver for the Ice Fury but no luck from the bfgminer download.

The next part I'd love some help with is the batch file for bfgminer.  Once I get the Ice Fury working I'd like to have them as different workers so I can keep an eye on them.  Would this be a good config, I also have tried to disable GPU mining and neither the -G or --disable-gpu works.  Of course my actual batch file doesn't have me.worker1 or Password.

bfgminer.exe -o stratum.bitcoin.cz:3333 -u me.worker1 -p Password -o stratum.bitcoin.cz:3333 -u me.worker2 -p PASSWORD -S all

[snoopy_nzl]

I got in on the pre-order for the Ice Fury and took up the option to get a Red Fury at a slight discount.  They arrived today and so far I've not been able to get the Ice Fury to work.  The Red Fury is working and giving me what I expected as for a hash rate.  

So first I'd love help getting the Ice Fury to be seen.  I installed the driver which worked just fine for the Red Fury but when I go into bfgminer it shows one device which is Bitfury BF1 from BFMG.  If I do the + to add a device, bfgminer doesn't find the Ice Fury.  I'm running Windows 7 Pro and bfgminer 3.9 x64.  One odd thing is when I go into Device Manager the Ice Fury is showing up under Universal Serial Bus Devices and is listed as NanoFury NF1 v0.7.  The working Red Fury is showing up under Ports (COM & LPT) as Bitfury BF1 USB Miner (COM4).  I would expect both to show up in the same spot, I've tried reinstalling the driver for the Ice Fury but no luck from the bfgminer download.

The next part I'd love some help with is the batch file for bfgminer.  Once I get the Ice Fury working I'd like to have them as different workers so I can keep an eye on them.  Would this be a good config, I also have tried to disable GPU mining and neither the -G or --disable-gpu works.  Of course my actual batch file doesn't have me.worker1 or Password.

bfgminer.exe -o stratum.bitcoin.cz:3333 -u me.worker1 -p Password -o stratum.bitcoin.cz:3333 -u me.worker2 -p PASSWORD -S all

Hi Krazy, i have been running them on 3.8 windows 7 Pro my start string is
bfgminer.exe -S "NFY:all" --set-device NFY:osc6_bits=54 -o stratum+tcp://stratum.mining.eligius.st:3334 -O address, When you plug it in does windows see it as a USB device or a HID device? I installed zadig and it started identifying he devices as Libusb instead if HIDUSB and bfgminer then didnt see it until I removed that device driver from the system and it again appeared as  HID compliant device. (check device manager which group it shows up under may give a clue)

[krazy_al]

I got in on the pre-order for the Ice Fury and took up the option to get a Red Fury at a slight discount.  They arrived today and so far I've not been able to get the Ice Fury to work.  The Red Fury is working and giving me what I expected as for a hash rate.  

So first I'd love help getting the Ice Fury to be seen.  I installed the driver which worked just fine for the Red Fury but when I go into bfgminer it shows one device which is Bitfury BF1 from BFMG.  If I do the + to add a device, bfgminer doesn't find the Ice Fury.  I'm running Windows 7 Pro and bfgminer 3.9 x64.  One odd thing is when I go into Device Manager the Ice Fury is showing up under Universal Serial Bus Devices and is listed as NanoFury NF1 v0.7.  The working Red Fury is showing up under Ports (COM & LPT) as Bitfury BF1 USB Miner (COM4).  I would expect both to show up in the same spot, I've tried reinstalling the driver for the Ice Fury but no luck from the bfgminer download.

The next part I'd love some help with is the batch file for bfgminer.  Once I get the Ice Fury working I'd like to have them as different workers so I can keep an eye on them.  Would this be a good config, I also have tried to disable GPU mining and neither the -G or --disable-gpu works.  Of course my actual batch file doesn't have me.worker1 or Password.

bfgminer.exe -o stratum.bitcoin.cz:3333 -u me.worker1 -p Password -o stratum.bitcoin.cz:3333 -u me.worker2 -p PASSWORD -S all

Hi Krazy, i have been running them on 3.8 windows 7 Pro my start string is
bfgminer.exe -S "NFY:all" --set-device NFY:osc6_bits=54 -o stratum+tcp://stratum.mining.eligius.st:3334 -O address, When you plug it in does windows see it as a USB device or a HID device? I installed zadig and it started identifying he devices as Libusb instead if HIDUSB and bfgminer then didnt see it until I removed that device driver from the system and it again appeared as  HID compliant device. (check device manager which group it shows up under may give a clue)

Thank you!  It really was as simple as uninstall the driver and this time I clicked delete driver.  Windows did a rescan and it started working in bfgminer. 

[smoothrunnings]

I got in on the pre-order for the Ice Fury and took up the option to get a Red Fury at a slight discount.  They arrived today and so far I've not been able to get the Ice Fury to work.  The Red Fury is working and giving me what I expected as for a hash rate.  

So first I'd love help getting the Ice Fury to be seen.  I installed the driver which worked just fine for the Red Fury but when I go into bfgminer it shows one device which is Bitfury BF1 from BFMG.  If I do the + to add a device, bfgminer doesn't find the Ice Fury.  I'm running Windows 7 Pro and bfgminer 3.9 x64.  One odd thing is when I go into Device Manager the Ice Fury is showing up under Universal Serial Bus Devices and is listed as NanoFury NF1 v0.7.  The working Red Fury is showing up under Ports (COM & LPT) as Bitfury BF1 USB Miner (COM4).  I would expect both to show up in the same spot, I've tried reinstalling the driver for the Ice Fury but no luck from the bfgminer download.

The next part I'd love some help with is the batch file for bfgminer.  Once I get the Ice Fury working I'd like to have them as different workers so I can keep an eye on them.  Would this be a good config, I also have tried to disable GPU mining and neither the -G or --disable-gpu works.  Of course my actual batch file doesn't have me.worker1 or Password.

bfgminer.exe -o stratum.bitcoin.cz:3333 -u me.worker1 -p Password -o stratum.bitcoin.cz:3333 -u me.worker2 -p PASSWORD -S all

Hi Krazy, i have been running them on 3.8 windows 7 Pro my start string is
bfgminer.exe -S "NFY:all" --set-device NFY:osc6_bits=54 -o stratum+tcp://stratum.mining.eligius.st:3334 -O address, When you plug it in does windows see it as a USB device or a HID device? I installed zadig and it started identifying he devices as Libusb instead if HIDUSB and bfgminer then didnt see it until I removed that device driver from the system and it again appeared as  HID compliant device. (check device manager which group it shows up under may give a clue)

Thank you!  It really was as simple as uninstall the driver and this time I clicked delete driver.  Windows did a rescan and it started working in bfgminer. 

So are you saying you need to uninstall the driver that assigns COM ports to your USB keys?

Thanks,

[snoopy_nzl]

bfgminer.exe -o stratum.bitcoin.cz:3333 -u me.worker1 -p Password -o stratum.bitcoin.cz:3333 -u me.worker2 -p PASSWORD -S all
[/quote]
Hi Krazy, i have been running them on 3.8 windows 7 Pro my start string is
bfgminer.exe -S "NFY:all" --set-device NFY:osc6_bits=54 -o stratum+tcp://stratum.mining.eligius.st:3334 -O address, When you plug it in does windows see it as a USB device or a HID device? I installed zadig and it started identifying he devices as Libusb instead if HIDUSB and bfgminer then didnt see it until I removed that device driver from the system and it again appeared as  HID compliant device. (check device manager which group it shows up under may give a clue)
[/quote]Thank you!  It really was as simple as uninstall the driver and this time I clicked delete driver.  Windows did a rescan and it started working in bfgminer. 
[/quote]

So are you saying you need to uninstall the driver that assigns COM ports to your USB keys?

Thanks,
[/quote]
In the above case check in device manager which group your device shows under, (if using BFGMINER) if its under usb devices then you can go the miner properties and remove driver and delete from system, scan for changes, miner auto detected and driver auto installed and it appears under HID compoliant devices this time, bfgminer will then see it..

[tk1337]

All that is required is usb 3.0 and osc bit 55 to max them.

I'll be honest, I'm half afraid to overclock them... they're running at/above 3GH/s each, with an HW Error % BELOW 1%... I think I'll um... just not even bother with overclocking great job man!

[smoothrunnings]

All that is required is usb 3.0 and osc bit 55 to max them.

I'll be honest, I'm half afraid to overclock them... they're running at/above 3GH/s each, with an HW Error % BELOW 1%... I think I'll um... just not even bother with overclocking great job man!

Wow that's great, you must be storing them in a freezer so that they don't melt!