I would like to request a whitelisting.

1.) I'm trying to solve a problem with mining with Raspberry Pi and BFL Singles with Cgminer. All I get for replies in the newbie thread is how I shouldn't mine with a raspberry pi. I want to post in the appropriate external threads to get a concrete solution.

2.) If there is no solution, then I'll post the cgMonitor code I wrote to keep the mining combination alive without having to manually restart the damn cgminer when comm errors happen.

Thanks for consideration.

I'll repeat.

I'm not mining with a Raspberry PI. I'm using it as a 3watt solution to being the brains for mining connected to two BFL Singles.

This works great but drops periodically with a Comms error. Cgminer just needs a kick in the pants (restart) and it resumes work.

Nvidia cards do squat for mining.

Can you explain to me why anyone would sell you a BFL Single at a LOSS when you can trade in a BFL Single for no cost for a BFL Little Single ASIC? Seems silly.

As Largo said, I'm trying to find a solution to my PI as a controller. I wrote my own solution but I'd prefer if there was a real solution.

As I'm still restricted to the newbie board I thought I would start a post here.

I have 2 Raspberry Pis running 4 BFL singles. These were previously run on the same computer that's GPUs ran on. However, I've moved over to two Pis with the impending lack of value in GPU mining(I still net 1.00$ per day and heat so I'll keep them alive for the winter)....

So, the question I have is: does anyone else experience periodic drops of your BFL/FPGA units where CGMiner or other miners start stating "Comms error"? I can restart the miner and it works fine again, but I haven't found a good solution.

PS in the meantime, I wrote a simple RPC monitor that checks the "notify" status of reason for not well. If the reason isn't none for more than 3 attempts it restarts the miner remotely. This works, but feels dirty.