Search content
Sort by
Showing 20 of 32 results by arcticfox
How can I connect to Mutipool through a stratum proxy? I have 4 Blade Erupters that I can connect to Slush's Pool with, but when I try to connect to any of the Multipool ports I keep getting "not connected. I am running the stratum script from Slush's site and adding the -o and -p to try to point it to Multipool.
This is the command I'm running: ./mining_proxy.py -o pool1.us.multipool.us -p 8888. Any idea of why I can't connect?
This is the command I'm running: ./mining_proxy.py -o pool1.us.multipool.us -p 8888. Any idea of why I can't connect?
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...
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 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.
[/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
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.
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.
I was having issues running Minepeon 0.2.3a with CGminer and the USB Block Erupters. If I ran more than 12 Erupters (on three powered D-Link DUB-H7's), CGminer would crash my Raspi Pi. Tried to switch to BFGMiner, but could never get it working.
Decided to try Minepeon 0.2.4PR2 and loaded the BFGminer config file. This time Minepeon is running BFGminer with 23 USB Block Erupters on 4 D-Link hubs without a hicckup for almost 9 hrs. Only thing I lost is my LCD output to my AdaFruit LCD and LCD Systems Info screens
Decided to try Minepeon 0.2.4PR2 and loaded the BFGminer config file. This time Minepeon is running BFGminer with 23 USB Block Erupters on 4 D-Link hubs without a hicckup for almost 9 hrs. Only thing I lost is my LCD output to my AdaFruit LCD and LCD Systems Info screens
If you want, I have an image of 0.2.3a w/ BFG set as the default, along with OS packages updated (about two weeks old), http://tk1337.com/downloads/minepeon-0.2.3a-bfg-2gb-im1.img.zip - Made it awhile back for a few people on here
Thanks, I'll give it a try.
I was having issues running Minepeon 0.2.3a with CGminer and the USB Block Erupters. If I ran more than 12 Erupters (on three powered D-Link DUB-H7's), CGminer would crash my Raspi Pi. Tried to switch to BFGMiner, but could never get it working.
Decided to try Minepeon 0.2.4PR2 and loaded the BFGminer config file. This time Minepeon is running BFGminer with 23 USB Block Erupters on 4 D-Link hubs without a hicckup for almost 9 hrs. Only thing I lost is my LCD output to my AdaFruit LCD and LCD Systems Info screens
Decided to try Minepeon 0.2.4PR2 and loaded the BFGminer config file. This time Minepeon is running BFGminer with 23 USB Block Erupters on 4 D-Link hubs without a hicckup for almost 9 hrs. Only thing I lost is my LCD output to my AdaFruit LCD and LCD Systems Info screens
[/quote]
do you have it set in the web UI to restart if it has problems with the miners?
also i have found after constantly getting the "cgminer failed to load" that my Brand new SD Card was dead replaced it and she is just humming along now =D
[/quote]
Yep, it is set to restart in the Web UI.
Reinstalled minepeon on my Lexar Pro, and it is running as of now. Will see in a couple of hours.
[/quote]
For the issue about the rPi shutting down, are you powering the rPi off a USB hub or do you have a stand-alone 5v1a source for it?
If you are powering it off of a hub, I would suggest using a stand-alone power source. (Apple USB chargers work great, as they are 5v 1a.)
[/quote]
I'm using a standalone 5v1A powersource.
And this morning the Raspi has rebooted again and this time I'm getting a CGminer failed to load error.
was about to try this today and found another problem... my pi was frozen so i restarted it and it says PANIC: VFS: Unable to mount root fs on unknown-block(179,2)
Entering kdb (current=0xda82aca0, pid 1) due to keyboard entry
..................
this is what happened before to make me reinstall like 5 days ago... i am going to reinstall again and hope for a fix soon
Entering kdb (current=0xda82aca0, pid 1) due to keyboard entry
..................
this is what happened before to make me reinstall like 5 days ago... i am going to reinstall again and hope for a fix soon
Forget what it says about the keyboard, that is just the default that was passed to the kernel.
What it most likely means though is that your SD Card is going bad (the unknown-block(179,2) error message makes it plain).
Last time you re-installed did you use a new SD card? If not I would say the SD card was the problem then too.
Neil
I had the same problem as the poster above yesterday. Got the same error "Entering kdb (current=0xda82aca0, pid 1) due to keyboard entry". I was never able to reboot and I was never able to reinstall the image to the SD card (brand new SanDisk Class 10), so I think the SD is shot. Reinstalled Minepeon on a Lexar Pro card today and just got the same kdb error after a couple of hours. This time I was able to unplug the Raspi and get a reboot and it seems to running OK now.
My Raspi is constantly shutting itself down and rebooting (every 30 min to 1hr), I'm assuming it is not supposed to do this?
I have two Manhattan 2.0 USb hubs attached running 5 Block Erupters each.
Any suggestions as to what may be causing these problems?
Thanks for the replies guys. I am a complete Raspberry Pi and Linux novice. I just really followed the online tutorial to set the Pi up with MinePeon. Somewhere along the way I read about using ssh to remotely access the Pi and figured I would try it just for the learning experience. Right now I have both keyboard, mouse and screen hooked up.
Everyone was a noob at one time. I'm very new to the Pi and Linux, after a few months it well start to make sense. Learning the new "speak" is the hardest part. I always thought pacman was a game, only to learn it's a package manager.
If you have the Pi hooked up to a monitor and keyboard/mouse you don't really need to do ssh. Sooner or later you well want to use the second usb port on the Pi for something else, that's when ssh comes to play.
Google 'putty ssh" it's a windoze compatible program to ssh and offers some nice options.
I got ssh to work from terminal on my Mac
. It was actually pretty easy.Thanks for the replies guys. I am a complete Raspberry Pi and Linux novice. I just really followed the online tutorial to set the Pi up with MinePeon. Somewhere along the way I read about using ssh to remotely access the Pi and figured I would try it just for the learning experience. Right now I have both keyboard, mouse and screen hooked up.