I'll stop both announcements/comments and donation period to you.
If that is what you need to do to satiate your sense of entitlement to nag I am good with that.
Neil
Rui
Topic: Linux mining distro for the Raspberry PI - MinePeon - page 45. (Read 684985 times)
If that is what you need to do to satiate your sense of entitlement to nag I am good with that.
Neil
Rui
I'll stop both announcements/comments and donation period to you.
If that is what you need to do to satiate your sense of entitlement to nag I am good with that.
Neil
Please stop, your constant nagging tires me.
I am aware of miner releases, and I take my time to thoroughly test them before I release them.
Neil
I rest my case.
Well you can ignore that one above - for that one, he copied my klondike USB code into his miner ... without our usbutils ... heh I can see problems happening there ... 
Please stop, your constant nagging tires me.
I am aware of miner releases, and I take my time to thoroughly test them before I release them.
Neil
If the releases can be git-pulled in the miner and updated accordingly, it's kind of pointless having those announcements.
Bit of funny behaviour that I noticed recently. I noticed that MinePeon was reporting ~20% hardware errors, after briefly freaking out I figured out that it's based on (hardware errors / accepted shares), since all my miners are setup to submit on relatively high difficulties (64 on bitminter, 256 on p2pool backups. Higher variance, lower overhead) an accepted share is much less common than my diff1 shares and it tends to inflate the relative frequency of hardware errors by a factor of the difficulty I'm running at, any way to deal with this or is it coming from cgminer itself?
Depends on what version you are using.
Up until 0.2.4 I was calculating the percentages myself and I never seemed to be able to get it right. 0.2.4 onwards the miner API started to actually give percentages so MinePeon now uses them.
Neil
Please stop, your constant nagging tires me.
I am aware of miner releases, and I take my time to thoroughly test them before I release them.
Neil
Bit of funny behaviour that I noticed recently. I noticed that MinePeon was reporting ~20% hardware errors, after briefly freaking out I figured out that it's based on (hardware errors / accepted shares), since all my miners are setup to submit on relatively high difficulties (64 on bitminter, 256 on p2pool backups. Higher variance, lower overhead) an accepted share is much less common than my diff1 shares and it tends to inflate the relative frequency of hardware errors by a factor of the difficulty I'm running at, any way to deal with this or is it coming from cgminer itself?
Depends on what version you are using.
Up until 0.2.4 I was calculating the percentages myself and I never seemed to be able to get it right. 0.2.4 onwards the miner API started to actually give percentages so MinePeon now uses them.
Neil
Bit of funny behaviour that I noticed recently. I noticed that MinePeon was reporting ~20% hardware errors, after briefly freaking out I figured out that it's based on (hardware errors / accepted shares), since all my miners are setup to submit on relatively high difficulties (64 on bitminter, 256 on p2pool backups. Higher variance, lower overhead) an accepted share is much less common than my diff1 shares and it tends to inflate the relative frequency of hardware errors by a factor of the difficulty I'm running at, any way to deal with this or is it coming from cgminer itself?
Does the version of bfgminer on MinePeon have the getwork proxy?
It should if you git pull the latest Minepeon. I see BFGMiner 3.5.1 on mine which definitely has the proxy.
Excellent, thanks.
Does the version of bfgminer on MinePeon have the getwork proxy?
I'm looking to replace my OpenWRT system with a RPi/MinePeon system, and I need to use getwork proxy for my ASICMiner Blades.
I'm looking to replace my OpenWRT system with a RPi/MinePeon system, and I need to use getwork proxy for my ASICMiner Blades.
It should if you git pull the latest Minepeon. I see BFGMiner 3.5.1 on mine which definitely has the proxy.
All that said... there are ways to get a seamless and easy Wireless solution without going under the hood with Minepeon and BAMT or other headless Mining OS/box setups.
For example, I have a mining setup in my detached garage in a dedicated room since its very cold out there and my garage has a separate commercial electricity bill (long story).
So, I setup a network switch that connects to my house's wifi via a relatively powerful wifi client bridge (you can use a game/media wifi to ethernet adapter, same thing really). Now I just have to connect any and all miners through ethernet to the switch and it's as if I'm on the house network. Pings and bandwidth are pretty good and stable, not that mining uses all that much bandwidth. Latency is key with mining though, so as long as you have good line of sight or powerful Wifi antennae pointing at each other, you should be good to go. Be sure to test your ping to your boxes from the main wired network to make sure latency is minimal.
Yes, this is a great solution too. I used to do this with some old BAMT rigs back in the day. (Had to move them around the house to distribute the power load.) For example, I have a mining setup in my detached garage in a dedicated room since its very cold out there and my garage has a separate commercial electricity bill (long story).
So, I setup a network switch that connects to my house's wifi via a relatively powerful wifi client bridge (you can use a game/media wifi to ethernet adapter, same thing really). Now I just have to connect any and all miners through ethernet to the switch and it's as if I'm on the house network. Pings and bandwidth are pretty good and stable, not that mining uses all that much bandwidth. Latency is key with mining though, so as long as you have good line of sight or powerful Wifi antennae pointing at each other, you should be good to go. Be sure to test your ping to your boxes from the main wired network to make sure latency is minimal.
Does the version of bfgminer on MinePeon have the getwork proxy?
I'm looking to replace my OpenWRT system with a RPi/MinePeon system, and I need to use getwork proxy for my ASICMiner Blades.
I'm looking to replace my OpenWRT system with a RPi/MinePeon system, and I need to use getwork proxy for my ASICMiner Blades.
All that said... there are ways to get a seamless and easy Wireless solution without going under the hood with Minepeon and BAMT or other headless Mining OS/box setups.
For example, I have a mining setup in my detached garage in a dedicated room since its very cold out there and my garage has a separate commercial electricity bill (long story).
So, I setup a network switch that connects to my house's wifi via a relatively powerful wifi client bridge (you can use a game/media wifi to ethernet adapter, same thing really). Now I just have to connect any and all miners through ethernet to the switch and it's as if I'm on the house network. Pings and bandwidth are pretty good and stable, not that mining uses all that much bandwidth. Latency is key with mining though, so as long as you have good line of sight or powerful Wifi antennae pointing at each other, you should be good to go. Be sure to test your ping to your boxes from the main wired network to make sure latency is minimal.
For example, I have a mining setup in my detached garage in a dedicated room since its very cold out there and my garage has a separate commercial electricity bill (long story).
So, I setup a network switch that connects to my house's wifi via a relatively powerful wifi client bridge (you can use a game/media wifi to ethernet adapter, same thing really). Now I just have to connect any and all miners through ethernet to the switch and it's as if I'm on the house network. Pings and bandwidth are pretty good and stable, not that mining uses all that much bandwidth. Latency is key with mining though, so as long as you have good line of sight or powerful Wifi antennae pointing at each other, you should be good to go. Be sure to test your ping to your boxes from the main wired network to make sure latency is minimal.
Should I do a wired or wireless connection??? Technically am I drawing more power if I use the wireless USB card versus wired connection? What are the benefits of wired vs wireless for a mining rasberry pi??
Wireless is the source of all evil and should never be used unless you absolutely have to.
Neil
Uhhh can you be a bit for specific? Why not? Does it draw more power than wired?
Should I do a wired or wireless connection??? Technically am I drawing more power if I use the wireless USB card versus wired connection? What are the benefits of wired vs wireless for a mining rasberry pi??
Wireless is the source of all evil and should never be used unless you absolutely have to.
Neil
Uhhh can you be a bit for specific? Why not? Does it draw more power than wired?
Should I do a wired or wireless connection??? Technically am I drawing more power if I use the wireless USB card versus wired connection? What are the benefits of wired vs wireless for a mining rasberry pi??
Wireless is the source of all evil and should never be used unless you absolutely have to.
Neil
Should I do a wired or wireless connection??? Technically am I drawing more power if I use the wireless USB card versus wired connection? What are the benefits of wired vs wireless for a mining rasberry pi??
Thanks! Will try that later when at home.
Question: How do I change minepeon to cgminer? By choosing the "Default Cgminer" config in the "Settings" Tab?
Question: How do I change minepeon to cgminer? By choosing the "Default Cgminer" config in the "Settings" Tab?
Yup and reboot
Still no luck with the cgminer default config in minepeon. Only the 10 Block Erupters show up as running devices. 
Should I specify the two furies in the cgminer config? Help
Edit: Even "git pull" 'ing to the latest version made no difference.
Back to having to use two raspberries instead of one...
Should I specify the two furies in the cgminer config? Help
Edit: Even "git pull" 'ing to the latest version made no difference.
Back to having to use two raspberries instead of one...
Jump to: