Mine both, huh? Well I have been working on a expansion script that allows you to use an LCD screen (like those cheap 3.5" ones), which does work. I'll have to see if I can't make it work on reading and combining information from two or more sources. Should be simple enough. Adjusting my personal script should give me an idea on how to modify the other one (since mine uses the classes from that project).

I am just having a migraine getting the files due to an earlier experiment of running my mining enclosure in the garage. Funny to see it stay at 18C while also doing scrypt mining on the CPU. I'll post back once I have things working.

I can assure you it isn't that. It's taking my RPi Miner who is already using CGMiner and running CPUMiner for another currency. Yeah it would be better classified under the other crypto-currencies but since it's just about the software itself, which currency is mined doesn't really matter.

Oh well, thanks for the response.

I was wondering if CPUMiner has a remote API much like CGMiner and BFGMiner. I've been researching around, but have had no luck. In a project I am working on, I will be needing to use CPUMiner exclusively, so if I can re-purpose my API script for CGMiner to CPUMiner, that would save me a lot of headache.

I'm planning to upgrade my small rig with some AntMiner U1s and figured that I might give a gentle overclock a try. The problem I'm seeing is that my older setup, which consists of the classic Eruptors, will be running along side of the AntMiners and I'm not sure if CGminer will try to also overclock them (which would spell disaster). Is there a way to individually overclock the Antminers or just any device by itself?

Note: My rig is a humble Pi.

First, you should focus on getting the miners working period (says me compiling 3.8.4 on the raspberry pi  ). Anyhow, there will be two executables you can launch, one of which is cgminer-nogpu. This contains the extra goodies needed for ASIC related mining. The other one is for GPU related mining, which doesn't seem to be what you are wanting.

As for mining with overlock... that is out of my area of knowledge.

Okay, I have a bit more info now:

First, I unplugged the Pi from the Hub, which the Pi could STILL power on even when not connected due to the 5v rail. Even with that, I plugged the Pi into another charger which gives 2A solid. Taking a volt meter to the miners, when 1 miner is idling, I get 5.2v. When operating, it goes down to 5.0v. With two plugged in, both report 5v idling and 4.95v mining. With the third (faulty) one, the value goes down to 4.5v with all 'mining', though the one good one continues to idle. Upon checking the voltage on the two working ones (aka, not idling), they were reporting the same voltage and yet were working fine (no hw errors except from the one that is faulty for obvious reasons).

So I'm now at a loss: even with the Pi being powered separately (with the Pi in the Hub, all results are the same where the voltages were about 0.2-0.3v lower), the one miner continues to idle. In CGMiner, it is showing the speeds correctly (3: ~905Mh/s; 2: 666Mh/s; 1:320Mh/s), but on the pool's end, it only acts as though 1 is working (since one is faulty and results with errors and maybe 1 good result every 100 errors).

I'll have to give it a try, though what has me confused is if I have the 3 miners active, the 'good' one still idles yet the other two work fine. The power source is a PSP charger (5v, 2A). I'll give the Pi it's own source in a sec and try that to rule out power issues.

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?

I had to recently reinstall my system and before having to do so, I had no problem grabbing the blocks (took a day, but it got done). Now on my reinstall, same system, no changes, I will get every error you can think of. Download maybe 10k blocks, crash, have to reindex, requires 3 crashes to properly reindex, etc. What is going on here? I have already tried a clean reinstall of Bitcoin-qt (cleaning the app-data section, saving the wallet.dat first) and that isn't working.