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.
Topic: PI Driven Miners (Read 787 times)
Don't bother trying to mine with your raspi...
Those ASICs look pretty neat though.
Those ASICs look pretty neat though.
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.
on the pi I'm getting about 0.6Mhash (when i was experimenting) lol, didn't spend too long on it though......
I've just started mining recently how fast do those PIs process hashes? My laptop gets around 19.5MH/s running on my nVidia GPU. I'm using RPCMiner and I haven't seen any issues with errors, it seems to run without intervention just fine.
The Raspberry PIs are just 'controllers' for the BFL singles, they dont process hashes.
I've just started mining recently how fast do those PIs process hashes? My laptop gets around 19.5MH/s running on my nVidia GPU. I'm using RPCMiner and I haven't seen any issues with errors, it seems to run without intervention just fine.
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.
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.
Jump to: