user11884: I recently purchased a Nanofury ASIC unit. I tried running it on my Linux system, as I just let the computer sit and run. I couldn't get it to work on Linux, so I decided to give it a try on Windows = but I'm still getting the same problem. 
I installed Zadig, found the device, and installed WinUSB to the Nanofury NF1 0.6 device. I could then see it in the Device Manager listed as:
'NanoFury NF1 0.6'
So the device is recognized by Windows, but when I run BFGminer on the -S all option for finding devices, I get this message:
'NO DEVICES FOUND: Press 'M' and '+' to add'
How do I get the NanoFury device to operate properly with Windows? I'd really hate to be out like $150 on something I can't even get to work.
I'm currently running BFGminer 3.9.0 - if that helps at all.

user13698: I was able to get my Nanofury working on Linux (rPi raspbian) and bfgminer 3.10.0 with a few permissions changes.  You really have three options:

Run bfgminer as root (undesireable)
Add the user running bfgminer to the "root" group:
usermod -G root -a miner
Change group ownership of the usb device (you will need to determine which one is your Nanofury device):
chgrp dialout /dev/bus/usb/001/006

Option 1 is the easiest, 3 is the most secure.  I went with option 2 as a middle-ground.
I also reverted commit 8383e33 (git revert 8383e33) from the bfgminer git repository, which gets rid of the "reinitializing" warning, and gives me a better hashrate.  I don't know the long-term effect of reverting this commit, though...
To start the miner, I use:
/path/to/bfgminer -S NFY:ALL --set-device NFY:osc6_bits=54

Once you have everything set up, you can write your settings (S, W,  in bfgminer) and you can drop the -S NFY:ALL.  You still need the --set-device, as far as I can tell, though.
Hope this helps!

11884: <p>I recently purchased a Nanofury ASIC unit. I tried running it on my Linux system, as I just let the computer sit and run. I couldn't get it to work on Linux, so I decided to give it a try on Windows = but I'm still getting the same problem. </p>

<p>I installed Zadig, found the device, and installed WinUSB to the Nanofury NF1 0.6 device. I could then see it in the Device Manager listed as:</p>

<p>'NanoFury NF1 0.6'</p>

<p>So the device is recognized by Windows, but when I run BFGminer on the -S all option for finding devices, I get this message:</p>

<p>'<code>NO DEVICES FOUND: Press 'M' and '+' to add</code>'</p>

<p>How do I get the NanoFury device to operate properly with Windows? I'd really hate to be out like $150 on something I can't even get to work.</p>

<p>I'm currently running BFGminer 3.9.0 - if that helps at all.</p>
 13698: <p>I was able to get my Nanofury working on Linux (rPi raspbian) and bfgminer 3.10.0 with a few permissions changes.  You really have three options:</p>

<ol>
<li>Run bfgminer as root (undesireable)</li>
<li><p>Add the user running bfgminer to the "root" group:</p>

<p><code>usermod -G root -a miner</code></p></li>
<li><p>Change group ownership of the usb device (you will need to determine which one is your Nanofury device):</p>

<p><code>chgrp dialout /dev/bus/usb/001/006</code></p></li>
</ol>

<p>Option 1 is the easiest, 3 is the most secure.  I went with option 2 as a middle-ground.</p>

<p>I also reverted commit <code>8383e33</code> (<code>git revert 8383e33</code>) from the bfgminer git repository, which gets rid of the "reinitializing" warning, and gives me a better hashrate.  I don't know the long-term effect of reverting this commit, though...</p>

<p>To start the miner, I use:</p>

<pre><code>/path/to/bfgminer -S NFY:ALL --set-device NFY:osc6_bits=54
</code></pre>

<p>Once you have everything set up, you can write your settings (S, W,  in bfgminer) and you can drop the -S NFY:ALL.  You still need the --set-device, as far as I can tell, though.</p>

<p>Hope this helps!</p>
