Author

Topic: Avalon Nano not being detected in bfgminer (Read 614 times)

newbie
Activity: 2
Merit: 0
January 06, 2016, 09:04:32 PM
#3
I am mining with the avalon nano, I dont understand what the different is then. I thought that the avalon's were a type of block eruptor.

I am trying to get the the avalon to work with bfgminer.
legendary
Activity: 1456
Merit: 1000
January 03, 2016, 02:24:26 PM
#2
I am new to the cryptocurrencies, for xmas I got two Avalon nano block erupters and using a raspberry pi that will run the block erupters, the pi is running rasbian with all the updates. I downloaded the bfgminer from github, and this is where I have come into issues, the Nano's are not being detected in the miner. I have tried activating each group of drivers that is build in bfgminer and nothing seems to be working. I am at a lost on what to do to get this erupters working. When use the command lsusb the erupters show up. So why cant bfgminer find the erupters? Has anyone else had this issue? If so can you help with this issue.
Thanks

You mention Avalon nano's in thread title and at start of post.  Then switch to block erupters, which usb stick are you mining with?

This could be your problem if your using Avalon nano's and using block erupter commands... they are not the same.  So would cause issues and probley not detect like you mention.
newbie
Activity: 2
Merit: 0
January 01, 2016, 08:10:26 PM
#1
I am new to the cryptocurrencies, for xmas I got two Avalon nano block erupters and using a raspberry pi that will run the block erupters, the pi is running rasbian with all the updates. I downloaded the bfgminer from github, and this is where I have come into issues, the Nano's are not being detected in the miner. I have tried activating each group of drivers that is build in bfgminer and nothing seems to be working. I am at a lost on what to do to get this erupters working. When use the command lsusb the erupters show up. So why cant bfgminer find the erupters? Has anyone else had this issue? If so can you help with this issue.
Thanks
Jump to: