Linux mining distro for the Raspberry PI - MinePeon

[btharper]

Wondering about a new project for the pi; I've been looking for a way to setup a general "P2Pool" option for the pi as a backup pool (or primary for other folks if they like) but since many of them are only listed by IP address and aren't run on static IPs a dynamic tool to lookup addresses would be nice. I've done the basic digging into how, I'm just not sure the easiest way to get the functionality into minepeon, so any advice (or ambitious coders wanting to take it on) would be appreciated.

There are a few nodes I can find reliable domain names for, using these as seed nodes for a fresh install start iterating through http://<node>:9332/peer_addresses to find other peers and keep a running list of nodes with zero fee (0 or 0.0), then add them to the end (or beginning) of the pools list in the miner config (and reload the miner if needed). Repeat once every several days or when the number of alive nodes left goes below a certain threshold. Bonus if pool response time or other latency factors can be taken into account.

Any thoughts on where this would go in the codebase?

I have thought about it.

The major problem is that p2pool requires a running and up-to-date bitcoind and the raspberry pi just cannot do that.  It runs fine it cannot download and process the blockchain though.  Even if I give it a head start by using a "pre downloaded chain" it cannot even keep it up-to-date because of the CPU and IO requirements (not to mention it will kill any SD card).

I am playing around with some other hardware (cubieboard 2 & beaglebone black) and while they are better off for CPU they are still not enough (and they still use SD for IO's).

Neil

I was just looking for a way to add public p2pool nodes into the pool list by automatically finding them on the network and adding them to the list dynamically. Running p2pool or bitcoind is way beyond what I'd hope to do with the RasPi

[1713946765]

1713946765

[1713946765]

1713946765

[1713946765]

1713946765

[btharper]

I am playing around with some other hardware (cubieboard 2 & beaglebone black) and while they are better off for CPU they are still not enough (and they still use SD for IO's).

I thought the beagle-bone blacks had a 2GB flash/solid state storage on them with an optional SD slot for extra storage?

Yep it does.  I could also use a USB HDD for storage, but it still does not solve the CPU requirement problem.

Neil

very true on the CPU... wait, I know...

cluster 40 beagle-bone blacks! yeaaaa! lol (I had to)

I'd be interested to see if something like this is possible, more from the perspective of this being more common in the future. Lots of people hosting tiny chunks of the blockchain, bonus points if none of them have to trust each other and don't have to transmit whole blocks back and forth. Probably something for another thread though if anyone wanted to get serious about it.

[tk1337]

I am playing around with some other hardware (cubieboard 2 & beaglebone black) and while they are better off for CPU they are still not enough (and they still use SD for IO's).

I thought the beagle-bone blacks had a 2GB flash/solid state storage on them with an optional SD slot for extra storage?

Yep it does.  I could also use a USB HDD for storage, but it still does not solve the CPU requirement problem.

Neil

very true on the CPU... wait, I know...

cluster 40 beagle-bone blacks! yeaaaa! lol (I had to)

I'd be interested to see if something like this is possible, more from the perspective of this being more common in the future. Lots of people hosting tiny chunks of the blockchain, bonus points if none of them have to trust each other and don't have to transmit whole blocks back and forth. Probably something for another thread though if anyone wanted to get serious about it.

http://www.youtube.com/watch?v=i_r3z1jYHAc

[MineForeman.com]

http://www.youtube.com/watch?v=i_r3z1jYHAc

I actually built one of those using 5 Pi's!  Totally useless for what we are discussing but totally cool!

Neil

[tk1337]

http://www.youtube.com/watch?v=i_r3z1jYHAc

I actually built one of those using 5 Pi's!  Totally useless for what we are discussing but totally cool!

Neil

hehe, yea, it's a neat show piece though... need to make a life-size Cray-2 replica with nothing but RaspberryPi's filling it... haha

[arcticfox]

I have been running Minepeon 0.2.4 on two Raspeberries for about a week now, and I'm still having problems with it crashing. One raspeberry will run for about a day and then crash. The other one will go for about three days before the crash.

Is there a log on minepeon to identify what is causing the crashes? I have one monitor connected to one Raspberry and I can see the onscreen error log, but I can't really understand it (not a Linux guy!).

I'm getting ready to leave the Raspberries unsupervised for about three months. Was hoping to have them mining while I am gone, but since they keep crashing I won't be able to SSH them. So once they crash I have no way to reset them. I was thinking about attaching an electrical timer that will cycle the power off and then back on once every 24 hours. This way if one or both of the raspi's are crashed they will reboot. Since I won't be shutting minepoen off the proper way will this cause problems? Any other suggestions?

The setup is as follows:

Raspberry1

2 Rosewill RHB-500 hub, with 5 USB block erupters each, 3 Dlink DUB-H7 with 4 be's, connected through an unpowered 4 port hub to the raspi

Raspberry2

2 Rosewill RHB-500 hub, with 5 USB block erupters each, 1 Dlink DUB-H7 with 4 be's, connected through an unpowered 4 port hub to the raspi connected to the raspi on one USB port,

and 2 Dlink DUB-H7 with 4 be's connected through a powered 7 port USB hub to the second USB port on the raspi

Any idea's on why the above setup is crashing minepeon? I'm sure all the block erupters are getting enough power.

[jedimstr]

I have been running Minepeon 0.2.4 on two Raspeberries for about a week now, and I'm still having problems with it crashing. One raspeberry will run for about a day and then crash. The other one will go for about three days before the crash.

Is there a log on minepeon to identify what is causing the crashes? I have one monitor connected to one Raspberry and I can see the onscreen error log, but I can't really understand it (not a Linux guy!).

I'm getting ready to leave the Raspberries unsupervised for about three months. Was hoping to have them mining while I am gone, but since they keep crashing I won't be able to SSH them. So once they crash I have no way to reset them. I was thinking about attaching an electrical timer that will cycle the power off and then back on once every 24 hours. This way if one or both of the raspi's are crashed they will reboot. Since I won't be shutting minepoen off the proper way will this cause problems? Any other suggestions?

The setup is as follows:

Raspberry1

2 Rosewill RHB-500 hub, with 5 USB block erupters each, 3 Dlink DUB-H7 with 4 be's, connected through an unpowered 4 port hub to the raspi

Raspberry2

2 Rosewill RHB-500 hub, with 5 USB block erupters each, 1 Dlink DUB-H7 with 4 be's, connected through an unpowered 4 port hub to the raspi connected to the raspi on one USB port,

and 2 Dlink DUB-H7 with 4 be's connected through a powered 7 port USB hub to the second USB port on the raspi

Any idea's on why the above setup is crashing minepeon? I'm sure all the block erupters are getting enough power.

The BE's may be getting enough power, but what about the Pi's themselves.  How do you have them hooked up for power?

[arcticfox]

[/quote]

The BE's may be getting enough power, but what about the Pi's themselves.  How do you have them hooked up for power?
[/quote]

Both have 5V 1000mA power supplies

[Beastlymac]

The BE's may be getting enough power, but what about the Pi's themselves.  How do you have them hooked up for power?
[/quote]

Both have 5V 1000mA power supplies
[/quote]
You need 500mA per USB.

[arcticfox]

The BE's may be getting enough power, but what about the Pi's themselves.  How do you have them hooked up for power?

Both have 5V 1000mA power supplies
[/quote]
You need 500mA per USB.
[/quote]

All the Block Erupters are on powered hubs (Rosewill 5V 5A with 5 BE's and DLINK 5V 4A with 4 BE's), so they are all getting more than enough power). I see if I can find some 5V 2A power for the Raspberries.

[bomberb17]

Did you cut the red wire on the usb cable that connects the pi with the first hub to prevent backpower?

My pi with 5 erupters runs fine for about a week on average before crashing.  Maybe someone can help on how to find what's causing the crashing...

[ct1aic]

Bitcoin Difficulty:              510,929,738
Next difficulty (estimate): 517,595,126 (+1%)

[arcticfox]

Did you cut the red wire on the usb cable that connects the pi with the first hub to prevent backpower?

My pi with 5 erupters runs fine for about a week on average before crashing.  Maybe someone can help on how to find what's causing the crashing...

No I did not. The hub connected to the Pi is unpowered, should I still cut the red cable?

Would it be better to chain my powered hubs and then plugging them directly into the Pi?

[jedimstr]

Did you cut the red wire on the usb cable that connects the pi with the first hub to prevent backpower?

My pi with 5 erupters runs fine for about a week on average before crashing.  Maybe someone can help on how to find what's causing the crashing...

No I did not. The hub connected to the Pi is unpowered, should I still cut the red cable?

Would it be better to chain my powered hubs and then plugging them directly into the Pi?

The unpowered hub is leeching power from your Pi's.  That's why they are crashing.  Try connecting a good Powered USB Hub without backfeed between the Pi and other peripherals.  You should never use an unpowered hub directly with a Pi since it will always leech power.

You can check the reports on various powered Hubs with the Pi here: http://elinux.org/RPi_Powered_USB_Hubs

[madcratebuilder]

The BE's may be getting enough power, but what about the Pi's themselves.  How do you have them hooked up for power?

Both have 5V 1000mA power supplies

You need 500mA per USB.
[/quote]

All the Block Erupters are on powered hubs (Rosewill 5V 5A with 5 BE's and DLINK 5V 4A with 4 BE's), so they are all getting more than enough power). I see if I can find some 5V 2A power for the Raspberries.


[/quote]

Take another look at the Rosewill psu's, the RHB500 has a 4 amp psu and well run 8 sticks.  The D-link is 2.5 or 3amps, some early ones are the 2.5, I have one.  I have never had good luck with the D-link.  I have 4 of the rhb500 to a single PI, one hub to Pi and 3 hubs the the master hub.  3 with 8 sticks and the master has 6.  Two Pi's setup like this and they run for days.

[mikejones]

Okay so I have a USB Redfury, USB ASIC BlockErupter, and BFL Jalapeno. My minepeon is only detecting the blockerupter not the red-fury or the BFL jalapeno. How do I get it to detect them and start mining?

[Morblias]

i did git pull on /opt/minepeon/ to get cgminer 3.7.2, but it keeps trying to connect to a knc device (or driver? whatever this is) even though I don't have one. How do I stop this:

[MineForeman.com]

i did git pull on /opt/minepeon/ to get cgminer 3.7.2, but it keeps trying to connect to a knc device (or driver? whatever this is) even though I don't have one. How do I stop this:

Sorry, I have been playing around with the KnC driver and left it in there, it will be fixed soon.

Neil

[mikejones]

Why is my Hardware error so high with my Redfury:
 BPM 0:       |  2.34/ 2.34/ 2.25Gh/s | A: 754 R: 4+0(.51%) HW:3908/ 59%

[Beastlymac]

Why is my Hardware error so high with my Redfury:
 BPM 0:       |  2.34/ 2.34/ 2.25Gh/s | A: 754 R: 4+0(.51%) HW:3908/ 59%

It is because you are using a old version of bfgminer. It needs to be updated.