|
October 01, 2013, 06:21:07 AM |
|
After building a simple case for my Raspberry Pi to live its life as a bitcoin miner, I hooked it up with 2 Eruptors and saw that one was being faulty, which I suspected was the case anyway. After ordering another, I swapped the bad one for the new one and was greeted with an unusual situation.
Now my pi, with a HUB attached mind you, will only utilize ONE of the miners. Both miners are detected properly and I had the settings set properly, yet only one appears to get the job done and the other idles indefinitely (green light remains on), even though it was working fine before. Confused, I removed the new miner and restarted CGMiner. Alas, it was working fine. Replaced it with the other, and behold, it had no complaints. But the moment both are in the same HUB, the newer one only works and the other takes the backseat.
Figuring maybe it was a bug with 3.1.1, I downloaded and recompiled 3.4.3 of CGMiner. I was actually impressed with the hotplug ability and this made testing easier. Upon running the newer version, it was the same story: Old one doesn't do a thing, but the newer one does. Removed the newer one, older one begins to work. Put the newer one back in and the older one idles again. The hash rates do show the correct numbers if both were working and if they are alone, and even plugging in the faulty miner shows the correct results; even the faulty one begins to actually mine (granted, this just gives HDW errors, but at least it is getting something to do).
So now I am at a loss. I am running simple Raspian and have the Pi and the 2 miners powered by a 2A USB 2.0 HUB. I am not using WiFi or any other devices on the Pi other than the HUB itself (which also powers the Pi). Does anyone have an idea what is going on?
|