Nanofury NF1 not working on Raspbian

[neoneos]

Hello.

I can't get Nanofury NF1 to work on Raspbian. I have been successfully using Block Erupters and Nanofury works excellent on Windows. I am using -S auto on Windows and -S all command on Raspbian, and it does detect Erupters, but not Nanofury. I am using bfgminer 3.4.0. Waiting for your advice.

Thanks.

[1715695503]

1715695503

[1715695503]

1715695503

[viriat0]

Try this:

bfgminer.exe -o stratum+tcp://pool -u user -p password -G -S all --set-device NFY:osc6_bits=52

[neoneos]

Not working. Raspbian still doesn't see Nanofury. The LED on Nanofury is not on. When I connect it to Windows, it comes on after bfgminer starts.

[Beastlymac]

Update to bfgminer 3.5.1

[neoneos]

Same. Not working.

[neoneos]

I now installed Minepeon and still Nanofury doesn't work.

[RicRock]

Same problem.

detecting them but not assigning a device (i.e. /dev/ttyUSB0 for erupters, /dev/ttyACM0 for blue fury)

What device should they appear as?

[Aggrophobia]

Same problem.

detecting them but not assigning a device (i.e. /dev/ttyUSB0 for erupters, /dev/ttyACM0 for blue fury)

What device should they appear as?

/dev/ttyNFY0

[neoneos]

I noticed that when I connect Nanofury to Raspberry running Minepeon I see Microchip Technology Inc. in a list by lsusb command. So I think Nanofury is detected, but it is not working. How do I specify options to make it work?

[RicRock]

Same problem.

detecting them but not assigning a device (i.e. /dev/ttyUSB0 for erupters, /dev/ttyACM0 for blue fury)

What device should they appear as?

/dev/ttyNFY0

do you really see that device in the /dev directory?

I'm thinking it's /dev/hidraw0 but I'm unclear.

Anyone else having luck?

Edit:

If it is hidraw* they are created upon boot with owners root:root instead of root:dialout and 600 permissions with no T sticky bit set.

Even manually changing those things makes no difference to bfgminer

[derjanb]

Working fine here after hours of trying...  At least I get ~2.3 GH/s out of the Nanofury.

I'm using bfgminer 3.8.0 (latest git version) and all you have to do (after compiling) is to enforce the USB 2.0 low speed mode to make the USB communication stable. Note: this will also limit the network speed of your Raspi!

The slowdown can be achieved by putting dwc_otg.speed=1 into /boot/cmdline.txt. Note: all statements need to be at one line.

See this page for more infomation: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=53832#sig411106 (the last section at the bottom.

Question: what does

NFY 0: Frequency drop over 50% detected, reinitialising

mean? I see a lot of these messages.

[RicRock]

Working fine here after hours of trying...  At least I get ~2.3 GH/s out of the Nanofury.

I'm using bfgminer 3.8.0 (latest git version) and all you have to do (after compiling) is to enforce the USB 2.0 low speed mode to make the USB communication stable. Note: this will also limit the network speed of your Raspi!

The slowdown can be achieved by putting dwc_otg.speed=1 into /boot/cmdline.txt. Note: all statements need to be at one line.

See this page for more infomation: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=53832#sig411106 (the last section at the bottom.

Question: what does

NFY 0: Frequency drop over 50% detected, reinitialising

mean? I see a lot of these messages.

Good job! never occurred to me to try setting low speed mode.

Unfortunately, I sold mine off so can't test it out

[Zich]

Working fine here after hours of trying...   At least I get ~2.3 GH/s out of the Nanofury.

I'm using bfgminer 3.8.0 (latest git version) and all you have to do (after compiling) is to enforce the USB 2.0 low speed mode to make the USB communication stable. Note: this will also limit the network speed of your Raspi!

The slowdown can be achieved by putting dwc_otg.speed=1 into /boot/cmdline.txt. Note: all statements need to be at one line.

See this page for more infomation: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=53832#sig411106 (the last section at the bottom.

Question: what does

NFY 0: Frequency drop over 50% detected, reinitialising

mean? I see a lot of these messages.

Thanks a lot derjanb. It work  

[thedue]

NFY 0: Frequency drop over 50% detected, reinitialising

---

I´m getting those too with my NF1... any idea of what this should tell us?!

[Haribo1980]

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

[Zich]

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  

[Haribo1980]

yeeeeehaaaw.... IT WORKS !!!! You're my daily HERO Zich !!!!!!  Thanks a lot... !!!!

[Zich]

yeeeeehaaaw.... IT WORKS !!!! You're my daily HERO Zich !!!!!!   Thanks a lot... !!!!

No problem dude, but i can't take all credit  . All credit go to derjanb who discover the usb speed problem  

[achib]

This looks great .. at least it works now !
But look at this:

 
--------------------------------------------------------------------------------
 NFY 0:       |  2.18/ 2.09/ 1.89Gh/s | A:11 R:0+0(none) HW: 5/4.5%
 BPM 0:       |  2.37/ 2.36/ 2.07Gh/s | A: 7 R:0+0(none) HW:51/ 30%
--------------------------------------------------------------------------------
 [2013-12-12 18:53:47] NFY 0: Frequency drop over 50% detected, reinitialising
 [2013-12-12 18:53:53] Accepted 07cf16ff NFY 0  Diff 32/16
 [2013-12-12 18:53:57] NFY 0: Frequency drop over 50% detected, reinitialising
 [2013-12-12 18:54:05] NFY 0: Frequency drop over 50% detected, reinitialising
 [2013-12-12 18:54:13] Accepted 04ae5508 BPM 0  Diff 54/16
 [2013-12-12 18:54:19] NFY 0: Frequency drop over 50% detected, reinitialising
 [2013-12-12 18:54:20] Stratum from pool 0 requested work update
 [2013-12-12 18:54:25] Accepted 0e87703f NFY 0  Diff 17/16
 [2013-12-12 18:54:29] Accepted 04844e77 NFY 0  Diff 56/16
 [2013-12-12 18:54:37] NFY 0: Frequency drop over 50% detected, reinitialising
 [2013-12-12 18:54:42] Accepted 0624290d NFY 0  Diff 41/16
 [2013-12-12 18:54:44] NFY 0: Frequency drop over 50% detected, reinitialising
 [2013-12-12 18:54:44] Accepted 0a8e4540 BPM 0  Diff 24/16
 [2013-12-12 18:54:52] NFY 0: Frequency drop over 50% detected, reinitialising

Any idea how to get them work correct ?  If i plug them to my windows machine it works without any errors  

[hammer]

Same by me. Many Reinitialising 
Have a man a solution for this?