Topic: Avalon Nano 3 not working - Windows 8.1 BFGminer (Read 3486 times)

Do any of you have any luck getting this to work in Linux?

I have 3 nanos on a super-powered USB hub connected to my Raspberry Pi.  Nothing I can do gets BFGMiner to accept it... but CGMiner picks them up with Icarus.  Here is my command:

sudo ./cgminer --icarus-options 115200:1:1 --icarus-timing 0.22 –o stratum+tcp://stratum.bitcoin.cz:3333 –u **** -p ****

So this is what works; however, I have an error the MOMENT I start it:

Started cgminer 4.9.2
ICA 0 usb transfer err: (-9) LIBUSB_ERROR_PIPE
FAIL: USB get_lock not found (1:11)
ICA 0 usb transfer err: (-9) LIBUSB_ERROR_PIPE
FAIL: USB get_lock not found (1:9)
ICA 0 usb transfer err: (-9) LIBUSB_ERROR_PIPE
FAIL: USB get_lock not found (1:7)
Probing for an alive pool
Pool 0 difficulty changed to 256
Network diff set to 93.4G
Accepted blah blah blah
Accepted blah blah blah


It still works, though.  It just has a huge HW rate... here is almost a full day of mining:

 [2015-12-24 21:43:22] Runtime: 21 hrs : 3 mins : 57 secs                   
 [2015-12-24 21:43:22] Average hashrate: 14425.8 Mhash/s                   
 [2015-12-24 21:43:22] Solved blocks: 0                   
 [2015-12-24 21:43:22] Best share difficulty: 540M                   
 [2015-12-24 21:43:22] Share submissions: 24643                   
 [2015-12-24 21:43:22] Accepted shares: 24617                   
 [2015-12-24 21:43:22] Rejected shares: 26                   
 [2015-12-24 21:43:22] Accepted difficulty shares: 197217                   
 [2015-12-24 21:43:22] Rejected difficulty shares: 208                   
 [2015-12-24 21:43:22] Reject ratio: 0.1%                   
 [2015-12-24 21:43:22] Hardware errors: 15715                   
 [2015-12-24 21:43:22] Utility (accepted shares / min): 19.48/min                   
 [2015-12-24 21:43:22] Work Utility (diff1 shares solved / min): 157.57/min
                   
 [2015-12-24 21:43:22] Stale submissions discarded due to new blocks: 0                   
 [2015-12-24 21:43:22] Unable to get work from server occasions: 0                   
 [2015-12-24 21:43:22] Work items generated locally: 449216                   
 [2015-12-24 21:43:22] Submitting work remotely delay occasions: 0                   
 [2015-12-24 21:43:22] New blocks detected on network: 124
                   
 [2015-12-24 21:43:22] Summary of per device statistics:
                   
 [2015-12-24 21:43:22] ICA 0 (5s):4.721G (avg):4.808Gh/s | A:66148 R:64 HW:5223 WU:52.6/m                   
 [2015-12-24 21:43:22] ICA 1 (5s):4.973G (avg):4.806Gh/s | A:65235 R:88 HW:5260 WU:52.5/m                   
 [2015-12-24 21:43:22] ICA 2 (5s):4.591G (avg):4.810Gh/s | A:65834 R:56 HW:5232 WU:52.5/m





Any advice on these little monsters, or did I just pick a terrible USB Miner?

If anyone is having trouble this might help - https://bitcointalksearch.org/topic/avalon-nano-stick-mining-fun-1022764 .  It was a review a while back.  I used the GUI as it looked nice in the review.

But here is a place with parameters that might help some having problems - https://bitcointalksearch.org/topic/m.11351267

I was able to get the Avalon Nano 3 to work on my Windows 7 system with bfgminer.  The driver was the key and of course getting the correct commands to configure it.  It did quite well but I really wanted to do this on my Raspberry PI 2 since I did not really want to tie up my Windows box with these.

I had initially purchased some ASICMiner Block Erupter USB 330MH Saphire Miners.  I was able to get those running fine with bfgminer.

screen –S Mining ./bfgminer –o stratum+tcp://stratum.bitcoin.cz:3333 -S All –u UserName -p Password

But when I added the Avalon Nano 3's I can't seem get a config that works with both.  It runs for awhile but finally dies after a few hours.  The following was the config I tried that worked for awhile.  It shows the Safire Miners as BES and the Avalon Nano 3's as ICA.

screeen -S Mining ./bfgminer -o stratum+tcp://stratum.bitcoin.cz:3333 -S /dev/ttyUSB0,/dev/ttyUSB1,/dev/ttyUSB2,/dev/ttyUSB3,/dev/ttyACM0,/dev/ttyACM1 -u UserName -p Password --set-device ICA:baud111520 --set-device ICA:timing=0.22 --set-device ICA:reopen=timeout --set-device ICA:work_division=1 --set-device ICA:probe_timeout=100 --set-device ICA:fpga_count=1

The Raspberry PI 2 runs one or the other.  I am guessing that it might be power related but I am not sure.  I have a new USB hub arriving and will try that.

this sounds like you got it correct. enjoy it.

*** UPDATE *** (problem solved?)

I was troubled by some of the differences I saw in the device name (avalon vs ICA) and re-installed everything on another PC (running Windows 7 instead of 8.1).

Avalon Nano 3 worked fine.  But I realized the GUI looked different.  And I think I figured out the issue; There are multiple downloads at 'downloads.canaanon-creative.com' one is 'Avalon 3' and another is 'Avalon Nano'.  I believe that I downloaded the wrong version; Avalon 1, 2 and 3 are different systems - they are NOT the nano.

So I removed all the software (USB driver and Avalon service/UI) and downloaded the 'Avalon Nano Quickstart'.  Installed the USB driver from the download, modify the Avalon.ini (in the AvalonMiner.Qt4MSVC folder) - simply edited the COM port (mine is com3).  Launched gui, closed gui, plugged in Nano and launched GUI again.

Voila!  I've been running now for 10 minutes.  If anyone else is having an issue getting Avalon Nano running in windows, make sure you downloaded the 'NANO' version of the download files.

Good luck and thanks all!

Chronic

it is not the hub sorry you purchased the hub waste of money in this case.

I have really high end hubs  did not matter.
  No one explained it in a way I was able to understand.

And I mined with lots of sticks. I GAVE UP WITH IT.  Sorry some one talked you into buying a hub.

Try youtube maybe someone did a decent video last I looked no one did.

not English
https://www.youtube.com/watch?v=L2pyWw0-Wl8



https://www.youtube.com/watch?v=uu8u__F-Vv4

Thanks, my new powered hub just arrived.  I plugged it into my PC (and power) and the exact same outcome; AvalonGUI runs 5 min.  and BFGminer seems to see it, but never start.  I think the answer is to play with BFGminer settings (going back to bfgminer readme asic again) or USB driver (which is there, but someone mentioned a different driver to try).

I'm sure it's not broken, as others have had the same error and I think some of them got through this.

Some mainboard have overload protection on USB port, even though i never encounter it with nanofury & my gigabyte mainboard.
So maybe you can try using powered usb hub & see the behaviour.

I'm plugged directly into usb port on back of PC with a fan pointed directly at it.  I don't think it is a power issue, because it does run for 5 minutes using the AvalonGUI before that stops.  I believe it has to do with the device name or usb driver.  Thanks for your replies!  -Chronic

Are you using powered usb hub or not?
The miner need more power, so you need to use powered usb hub.

try moving it to  miner software


https://bitcointalk.org/index.php?board=42.0

or mining support

https://bitcointalk.org/index.php?board=40.0


I will ask mods to move it.

BTW :


I gave up trying to get mine to run I gave it away

I am new to Bitcoin mining and got an Avalon Nano 3 to start and learn.

I'm running Windows 8.1, and using the LPC USB VCom port (COM3).

AvalonGUI runs about 5 minutes at 3-4 GH/s - then it hangs.  No good info in the Avalon.log.  But according to my pool (slush's), my worker does work (albeit for 5 min).

So after reading the threads here, I stopped using AvalonGUI and have tried to get BFGminer (4.7.0) running.  I'm close, but the hash rate stays at 0 even though it sees the device.  The device shows up at AVA 0 (which is odd because I'm using the -S parameter with the 'Avalon://./COM3' name).

Here is my BFGminer command line (USER AND PASSWORD OMITTED):

"bfgminer -0 stratum+tcp://us-east.stratum.bitcoin.cz:3333 -S avalon:\\.\COM3 -u xxxxxxx -P ppppppp"

I am getting 'Avalon: Reset Failed! not an Avalon?' error.

Any help would be GREATLY appreciated!

Chronic