Bitcoin Forum

Bitcoin => Mining support => Topic started by: Lexarus on November 05, 2015, 10:44:35 PM



Title: Looking for help getting Avalon Nano 3 USB working
Post by: Lexarus on November 05, 2015, 10:44:35 PM

For starters I thank you for taking the time to try and help me out here, it has been a struggle to even this far.

Hardware:
Raspberry Pi Model B 756-8308 Motherboard (RASPBRRYPCBA512)
3 of Avalon Nano 3 USB 3.6Gh/s Asic Bitcoin Miner
Powered USB 2.0 hub

Software:
Minepeon - Linux minepeon 3.12.35-1-ARCH armv6l
BFGminer - bfgminer version 3.990
PuTTY

Pool:
bitminter.com

After much surfing of forums and guides I have finally gotten everything installed and to the point where I am getting requests from my pool for work. However I am getting a No Devices Found issue. I have tried the auto and all options but nothing is found. I cannot figure out where I have gone wrong. I am completely new to using the Pi and all the software, but I feel I have learned a lot from the mistakes I've made. I have not been able to find a way to test if the Avalon Nano 3 even work, the green LED light comes on, but that is all I know. The Pi gets power from a USB 2.0 cable connected to the same hub as the Avalon Nano 3. I have not been able to find much directly related to the Avalon Nano 3, so I don't know if that is where my problem is. Advised and guidance would be a great help at this point.


I have found drivers for the bfgminer form Avalon Nano GUI. But I don't want to run it from the computer, that is why i got the Pi. Would it be possible to transfer the files from the computer?

I also found

Run under Linux
./bfgminer \
-S ICA:/dev/ttyACMx \
-o stratum+tcp://stratum.ozco.in:80 -O mikeqin.avalon:1234 \
--set-device ICA:baud=115200 \
--set-device ICA:reopen=timeout \
--set-device ICA:work_division=1 \
--set-device ICA:fpga_count=1 \
--set-device ICA:probe_timeout=100 \
--set-device ICA:timing=0.22 \
--api-listen \
2>log


but all I ever get in return in -bash: ./bfgminer: no such file or directory
I know it has to be somewhere in there or it won't be running, right?


Title: Re: Looking for help getting Avalon Nano 3 USB working
Post by: notlist3d on November 06, 2015, 06:49:11 PM
Here is a working BFG command line with a nano - https://bitcointalk.org/index.php?topic=1022764.msg11204285#msg11204285

It's been a while since I played with one.  But I remember he said he had sucess with that.  Here is entire thread: https://bitcointalk.org/index.php?topic=1022764.0


Title: Re: Looking for help getting Avalon Nano 3 USB working
Post by: deltalima on November 06, 2015, 06:53:25 PM
./bfgminer tells the shell to run the copy of bfgminer in the current directory so either cd into that location (maybe /usr/local/bin) or if it's in the path run bfgminer without the ./ prefix


Title: Re: Looking for help getting Avalon Nano 3 USB working
Post by: Lexarus on November 07, 2015, 03:11:40 AM
Here is a working BFG command line with a nano - https://bitcointalk.org/index.php?topic=1022764.msg11204285#msg11204285

It's been a while since I played with one.  But I remember he said he had sucess with that.  Here is entire thread: https://bitcointalk.org/index.php?topic=1022764.0
Looks like he was not using it from a raspberry pi, which is what I am currently working with. But there was a lot of good info in there. Still I was not able to get it to detect my devices. Looks like I have bfgminer v 3.99. I thought that upgrading that might do the trick. Following the guide from
http://minepeon.com/forums/viewtopic.php?f=19&t=1530
to install 4.2.0 seems to have left me still running 3.99.0 - This has left me totally confused.

./bfgminer tells the shell to run the copy of bfgminer in the current directory so either cd into that location (maybe /usr/local/bin) or if it's in the path run bfgminer without the ./ prefix

Removing the ./ was the trick. While I am still not getting my devices to be found, it has allowed me to work more with the commands I have found. So at least a step in the right direction.

Thank you both for helping out, still looking for more insight on this issue...