Neil,
Is there any way that Minepeon could support mining both BTC and LTC at the same time? (like Multiminer).
I suspect that I can manually start a second instance of bfgminer with the --scrypt option, but it would be cool to be able to manage it all at once via Minepeon.
Again congratulations for your excellent work!
Topic: Linux mining distro for the Raspberry PI - MinePeon - page 5. (Read 685133 times)
The August version works just fine on the PI B+.
I keep getting conflicted reports about this... I have one now I just need the time to set it up with a miner.
From now on I am fully on MinePeon, so please let us know when donation will start work, so we all can turn it on. 
Will do... priories though
. The method used in 0.2.1 or so above works 100% but I have yet to even open it up in the test releases.Neil
Anyone here have any experience with cgminer 4.3.5 on MinePeon 0.2.4.6? I compiled it from git, and it works brilliantly with my 3 x Zeus Hurricane X3's... but I now want to add a 4th Zeus, but a different model. This means instead of specifying chip count and frequency globally, and having the driver detect my devices automatically, I now need to specify each device individually and use the --zeus-options switch to specify the correct chips and frequencys. What is working currently with my 3 Hurricanes X3's is:
I've been trying to manually specify each miner in preparation for adding a Lightning X6, but none of the following work. I've been following the guidance from the github page for this version here: https://github.com/dmaxl/cgminer
Adding in "zeus:" but shouldn't be necessary as I compile with ONLY zeus support:
Trying to use the Auto scan in conjunction with --zeus-options
Instead of using /dev/ttyUSBx I've also tried using the device ID in the form of bus:device from the output of "lsusb":
Using -S instead of --scan-serial:
I end up with a bizarre "screen" behaviour too.... basically I get 3 dead screens called "zeus"... so something bizarre is being triggered with this.
Sorry for the gratuitous use of the CODE tags... but I personally like the simplicity of being able to copy and paste in Notepad++ to analyse... little easier than a thread post sometimes.
Code:
/usr/bin/screen -dmS zeus /opt/minepeon/bin/cgminer-zeus --scrypt --failover-only --api-listen --api-port 4028 --api-allow 127.0.0.1 --zeus-chips 64 --zeus-clock 328 --scan-serial zeus:auto -o
I've been trying to manually specify each miner in preparation for adding a Lightning X6, but none of the following work. I've been following the guidance from the github page for this version here: https://github.com/dmaxl/cgminer
Code:
/usr/bin/screen -dmS zeus /opt/minepeon/bin/cgminer-zeus --scrypt --failover-only --api-listen --api-port 4028 --api-allow 127.0.0.1 --scan-serial /dev/ttyUSB0 --scan-serial /dev/ttyUSB1 --scan-serial /dev/ttyUSB2 --zeus-options /dev/ttyUSB0,64,328;/dev/ttyUSB1,64,328;/dev/ttyUSB2,64,328 -o
Adding in "zeus:" but shouldn't be necessary as I compile with ONLY zeus support:
Code:
/usr/bin/screen -dmS zeus /opt/minepeon/bin/cgminer-zeus --scrypt --failover-only --api-listen --api-port 4028 --api-allow 127.0.0.1 --scan-serial zeus:/dev/ttyUSB0 --scan-serial zeus:/dev/ttyUSB1 --scan-serial zeus:/dev/ttyUSB2 --zeus-options /dev/ttyUSB0,64,328;/dev/ttyUSB1,64,328;/dev/ttyUSB2,64,328 -o
Trying to use the Auto scan in conjunction with --zeus-options
Code:
/usr/bin/screen -dmS zeus /opt/minepeon/bin/cgminer-zeus --scrypt --failover-only --api-listen --api-port 4028 --api-allow 127.0.0.1 --scan-serial zeus:auto --zeus-options /dev/ttyUSB0,64,328;/dev/ttyUSB1,64,328;/dev/ttyUSB2,64,328 -o
Instead of using /dev/ttyUSBx I've also tried using the device ID in the form of bus:device from the output of "lsusb":
Code:
/usr/bin/screen -dmS zeus /opt/minepeon/bin/cgminer-zeus --scrypt --failover-only --api-listen --api-port 4028 --api-allow 127.0.0.1 --scan-serial zeus:auto --zeus-options --zeus-options 001:006,64,328;001:007,64,328;001:008,64,328 -o
Using -S instead of --scan-serial:
Code:
/usr/bin/screen -dmS zeus /opt/minepeon/bin/cgminer-zeus --scrypt --failover-only --api-listen --api-port 4028 --api-allow 127.0.0.1 -S /dev/ttyUSB0 -S /dev/ttyUSB1 -S /dev/ttyUSB2 --zeus-options /dev/ttyUSB0,64,328;/dev/ttyUSB1,64,328;/dev/ttyUSB2,64,328 -o
I end up with a bizarre "screen" behaviour too.... basically I get 3 dead screens called "zeus"... so something bizarre is being triggered with this.
Sorry for the gratuitous use of the CODE tags... but I personally like the simplicity of being able to copy and paste in Notepad++ to analyse... little easier than a thread post sometimes.
I run 4 R-Boxes from one Minepeon. They get testy from time to time, but for the most part it works fine. I place the blame more on the R-Boxes than the Minepeon since I never got them to work under Windows, Zadiq drivers and all.
Anyway, you will need to update bfgminer (or cgminer if you prefer it) to a more recent release as the ones included in Minepeon do not support the R-Box.
Edit: Forgot to add in the original post that I updated the bfgminer to 4.3. Minepeon includes 3.1 if I'm not mistaken and I believe that 3.1 doesn't support the R-Boxes.
Anyway, you will need to update bfgminer (or cgminer if you prefer it) to a more recent release as the ones included in Minepeon do not support the R-Box.
Edit: Forgot to add in the original post that I updated the bfgminer to 4.3. Minepeon includes 3.1 if I'm not mistaken and I believe that 3.1 doesn't support the R-Boxes.
Sorry if it's been asked before, but does MinePeon support the RockMiner R-Box?
I believe bfgminer supports it. I cannot say for sure because I don't actually have one.
Neil
I'll try it in a half a week or so and get back to you on compatibility then!
Just working on a new test image that should fix most of those issues... No donate as of yet but both the status and pools page are fully functional. The settings page is 90% complete and the plugins page loads (no test past that).
It will be called MPRPI20140804.img.gz and will be available in the test area (http://minepeon.com/img/testing/).
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though .
Neil
Downloaded MPRPI20140804.img, wrote to SD card, popped it into the RPI B+, started up, set pools, plugged in USB cable and it runs like a dream!It will be called MPRPI20140804.img.gz and will be available in the test area (http://minepeon.com/img/testing/).
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though
.Neil
Thanks Neil.
Im getting 'A start job is running for Quick and dirty date (4hr 20s / no limit))' on my Pi B+.
Any suggestions? I cant boot up.
Thanks!
I am intending to have a download for a VM that has it fully configured and ready to go so if someone wants to run a full fledged "miner farm" they can.
AWESOME.... I run a small vSphere lab at home... that's my day job... virtualisation specialist... vSphere, Citrix, Hyper-V etc etc. MinePeon just keeps getting better and better. I have to admit, I was a PiMP user for a long time... since they released it, but when I started having issues with it playing nice with my Zeusminers and their dev team started enforcing donations for updates, AND I wanted to use Raspberry Pi I switched over to MinePeon. I thought this might be temporary until PiMP got it's act together... but honestly... I think I'm here to stay now!
I really want to run the auto-donate feature... but I stopped it when I realised it wasn't switching back reliably. Is it now working fully? I need to be able to trust that it's going to do the 15 minutes then switch back to my own pool(s).
(Small) Bug Report on RPI20140804 version.
- "document.body.style.background = "#FFFFCF"" appears after the device table on the status page.
- Donation amount in the plea should be 0.00000027 BTC, not 0.00027, per GH/s/day,
- Timezone reset itself to Africa/Abidjan (first in the list) overnight (there may have been a power cut). Similarly Expected Devices and Expected Hashrate show blank.
- Settings backup creates an empty file, probably still on the TODO list?
The August version works just fine on the PI B+.
30% issue: it's turned out after some more testing that in fact all miners are working at full speed according to slush's pool. Only interface shows that they work on 30%. Perhaps that info will help a bit in fixing this cosmetic bug.
From now on I am fully on MinePeon, so please let us know when donation will start work, so we all can turn it on.
Great job. Thank you.
30% issue: it's turned out after some more testing that in fact all miners are working at full speed according to slush's pool. Only interface shows that they work on 30%. Perhaps that info will help a bit in fixing this cosmetic bug.
From now on I am fully on MinePeon, so please let us know when donation will start work, so we all can turn it on.
Great job. Thank you.
I believe bfgminer supports it.
bfgminer and cgminer support with the most recent versions
Sorry if it's been asked before, but does MinePeon support the RockMiner R-Box?
I believe bfgminer supports it. I cannot say for sure because I don't actually have one.
Neil
Hello Neil. Im a noob for linux, but installed Minepeon in my Raspberry Pi , and Im really AMAZED.... all my Block Erupters are working, All my Red Furys too ..... in 30 minutes!!!!
PLUS - Im getting 2,7 gh in every Red Fury ....... meanwhile in windows, I can not get 2,2 - 2,5...... so Im really Happy!!
"0.38 charge and about 48º" (tomorrow I will install pure copper heatshink in the main chips) with 6 fury, 7 block erupters and 3 Antmain U2.
I readed you a few post back, that you think "people is waiting much more from you (about the low donation people)". My 15 min daily donation with 230 GH is checked by fire and grabbed to stone. Your minepeon Version is wonderfull.
Thanks a lot for all your hard work.
Sorry about my English, is not my main language.
Sorry if it's been asked before, but does MinePeon support the RockMiner R-Box?
I believe bfgminer supports it. I cannot say for sure because I don't actually have one.
Neil
I suggest:
- Open source the server side, and have the client side require a server configured.
Done... absolutely even. My intention is so that anyone can run their own server either on the internet or on their local network. I am intending to have a download for a VM that has it fully configured and ready to go so if someone wants to run a full fledged "miner farm" they can.
- Ensure everything works if *pool commands are disabled (or at least addpool, if the user wants to actually change pools via the interface).
As I see it the device takes priority, server stuff always looses out to local configuration.
- Possibly accept direct access if the user wants to just forward a port.
Direct access always takes priority in my mind, nothing is ever "disabled" or anything on the local device, server access is an add on, not the other way around.
- Enforce secure passwords (using eg cracklib).
I will do what I can, from experience people can be rather dumb with what security features they choose to enable
. 2FA, Locked IP's, and brutal passwords are all going to be available (I would also like key-exchanges as well) but lets see what people actually activate .Neil
Sorry if it's been asked before, but does MinePeon support the RockMiner R-Box?
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though .
.Any reason you are going this route instead of improving your already existing MobileMiner support? There are many features MinePeon could be using (easily), but is not (such as switching pools, switching coins, etc).
What I am doing is just an alternative to MobileMiner. Having said that, I would love to have MobileMiner support for pool switching etc but the author of the MobileMiner plugin does not support it (yet).
I also still have a wired idea that one day MinePeon will become my full time job. At the moment, with the current feature set, the public have spoken and it seems I must do better
! (I will never make donations compulsory though)Neil
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though .
How do you plan to make this such that someone compromising your server cannot hijack every miner using it? .Good question. All of the normal security layers will be there, ssl certs, ssh private keys, fire walling, VPN, load balance front end's. I also have plenty of experience at running these things (my real life job is wrapping servers up in layers of security). Even the communication between the miner and the server will use key signatures (as well as ssl etc).
In the end though, as we well know from pools, exchanges and a myriad of other "things on the internet" if someone gets root, your stuffed, and I don't think anyone who runs servers on the internet is going to deny that or say that their systems are un-hack able.
It is also not going to be compulsory
. By default it is not going to be on.Neil
- Open source the server side, and have the client side require a server configured.
- Ensure everything works if *pool commands are disabled (or at least addpool, if the user wants to actually change pools via the interface).
- Possibly accept direct access if the user wants to just forward a port.
- Enforce secure passwords (using eg cracklib).
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though .
How do you plan to make this such that someone compromising your server cannot hijack every miner using it? .Good question. All of the normal security layers will be there, ssl certs, ssh private keys, fire walling, VPN, load balance front end's. I also have plenty of experience at running these things (my real life job is wrapping servers up in layers of security). Even the communication between the miner and the server will use key signatures (as well as ssl etc).
In the end though, as we well know from pools, exchanges and a myriad of other "things on the internet" if someone gets root, your stuffed, and I don't think anyone who runs servers on the internet is going to deny that or say that their systems are un-hack able.
It is also not going to be compulsory
. By default it is not going to be on.Neil
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though .
.Any reason you are going this route instead of improving your already existing MobileMiner support? There are many features MinePeon could be using (easily), but is not (such as switching pools, switching coins, etc).
Just a guess here, but sounds like he's taking the server functionality that Spondoolies grafted onto his original code for their miners and pulling it back down into the main Minepeon setup.
Just working on a new test image that should fix most of those issues... No donate as of yet but both the status and pools page are fully functional. The settings page is 90% complete and the plugins page loads (no test past that).
It will be called MPRPI20140804.img.gz and will be available in the test area (http://minepeon.com/img/testing/).
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though .
Neil
Downloaded MPRPI20140804.img, wrote to SD card, popped it into the RPI B+, started up, set pools, plugged in USB cable and it runs like a dream!It will be called MPRPI20140804.img.gz and will be available in the test area (http://minepeon.com/img/testing/).
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though
.Neil
Thanks Neil.
Just as a warning, the server code is starting to make it's appearance in this release. The eventual outcome of this is that you will be able to go to https://mineforeman.io/ to manage your mining... at present all it does is erroneously tell you your mining rig is out of date though .
.Any reason you are going this route instead of improving your already existing MobileMiner support? There are many features MinePeon could be using (easily), but is not (such as switching pools, switching coins, etc).
Jump to: