Linux mining distro for the Raspberry PI - MinePeon - page 61.

lajz99

hero member

Activity: 756

Merit: 500

Apologies if I missed it but is there a way to simply reorder the pools or switch pools easily?

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: Nighthawkxx on September 23, 2013, 02:47:54 PM

The correct start command seems to be '/opt/minepeon/bin/bfgminer'

Tried to start bfgminer manually with parameter '-S all' & '-S erupter:all' but i always receive 'All devices disabled, cannot mine'
With cgminer minpeon 0.2.3a works perfectly.

Quote

minepeon@minepeon ~ $ /opt/minepeon/bin/bfgminer -S all -c /opt/minepeon/etc/miner.conf
All devices disabled, cannot mine!
minepeon@minepeon ~ Sad

$ /opt/minepeon/bin/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf
All devices disabled, cannot mine!

miner.conf

Icarus settings manually added.

Quote

{
   "algo": "c",
   "api-listen": true,
   "api-port": "4028",
   "expiry": "120",
   "icarus-options": "115200:1:1",
   "icarus-timing": "3.0=100",
   "hotplug": "5",
   "log": "5",
   "no-pool-disable": true,
   "queue": "1",
   "scan-time": "60",
   "shares": "0",
   "kernel-path": "\/opt\/minepeon\/bin",
   "api-allow": "W:0\/0",
   "pools": [
   {
   "url": "asc.coinmine.pl:6110",
   "user": "xxxxxxxxx",
   "pass": "yyyyyyyyy"
   }
   ]
}

Pretty sure you shouldn't have the icarus-options & icarus-timing in there for CGMiner 3.4.0 or above (someone correct me on that if I'm wrong) also you definitely didn't need them in there for BFGMiner. Also, both my Pi's running BFG have the double slash, they've been stable for about a week now.

Code:

minepeon@stablePi ~ $ cat /usr/lib/systemd/system/bfgminer.service 
[Unit]
Description=bfgminer
After=network.target openntpd.service

[Service]
Type=forking
User=minepeon
ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf
ExecStop=/usr/bin/screen -S bfgminer -X quit
Restart=always

[Install]
WantedBy=multi-user.target

Edit:
I have recompiled BFGMiner with the latest + libmicrohttpd on both these miners as well as completing a full system update (sudo pacman -Syu).

Nighthawkxx

member

Activity: 90

Merit: 10

The correct start command seems to be '/opt/minepeon/bin/bfgminer'

Tried to start bfgminer manually with parameter '-S all' & '-S erupter:all' but i always receive 'All devices disabled, cannot mine'
With cgminer minpeon 0.2.3a works perfectly.

Quote

minepeon@minepeon ~ $ /opt/minepeon/bin/bfgminer -S all -c /opt/minepeon/etc/miner.conf
All devices disabled, cannot mine!
minepeon@minepeon ~ Sad

$ /opt/minepeon/bin/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf
All devices disabled, cannot mine!

miner.conf

Icarus settings manually added.

Quote

{
"algo": "c",
"api-listen": true,
"api-port": "4028",
"expiry": "120",
"icarus-options": "115200:1:1",
"icarus-timing": "3.0=100",
"hotplug": "5",
"log": "5",
"no-pool-disable": true,
"queue": "1",
"scan-time": "60",
"shares": "0",
"kernel-path": "\/opt\/minepeon\/bin",
"api-allow": "W:0\/0",
"pools": [
{
"url": "asc.coinmine.pl:6110",
"user": "xxxxxxxxx",
"pass": "yyyyyyyyy"
}
]
}

chanberg

hero member

Activity: 672

Merit: 500

PERFECT. Thanks so much TK!

Danny

KyrosKrane

sr. member

Activity: 295

Merit: 250

Quote from: tk1337 on September 23, 2013, 01:43:00 PM

At first I thought the same, however my bfgminer.service has it in there with both // and works fine.

Not double slashes - that does work fine. He was pointing out that bfgminer is listed twice in the path:

Quote

ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: Morblias on September 23, 2013, 01:03:59 PM

Shouldn't it be this?

Code:

ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf

instead of his original post:

Code:

ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf

At first I thought the same, however my bfgminer.service has it in there with both // and works fine.

Morblias

hero member

Activity: 576

Merit: 500

Shouldn't it be this?

Code:

ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf

instead of his original post:

Code:

ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: Nighthawkxx on September 23, 2013, 11:23:41 AM

Code:

[minepeon@minepeon ~]$ sudo cat /usr/lib/systemd/system/bfgminer.service

[Unit]
Description=bfgminer
After=network.target openntpd.service

[Service]
Type=forking
User=minepeon
ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf
ExecStop=/usr/bin/screen -S bfgminer -X quit
Restart=always

[Install]
WantedBy=multi-user.target

hmm, that all looks correct, did you try to trace the directory to make sure that's the location of the bfgminer executable?

Code:

cd /opt/minepeon/bin/bfgminer/
ls -la | grep bfgminer

I know I've recompiled BFGMiner and put it in /opt/bfgminer/ I doubt this is a cause (unless you recompiled it, then maybe), but never hurts to check.)

Nighthawkxx

member

Activity: 90

Merit: 10

Quote

[minepeon@minepeon ~]$ sudo cat /usr/lib/systemd/system/bfgminer.service

[Unit]
Description=bfgminer
After=network.target openntpd.service

[Service]
Type=forking
User=minepeon
ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf
ExecStop=/usr/bin/screen -S bfgminer -X quit
Restart=always

[Install]
WantedBy=multi-user.target

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: Nighthawkxx on September 23, 2013, 09:58:31 AM

I was testing Minepeon 0.2.2 and tried to change to bfgminer but for some reason it doesn't work, Also tried Minepeon 0.2.3a and got the same issue.

Currently i have no clue what might be wrong.

Quote

[minepeon@minepeon ~]$ sudo systemctl status bfgminer.service
bfgminer.service - bfgminer
Loaded: loaded (/usr/lib/systemd/system/bfgminer.service; enabled)
Active: failed (Result: start-limit) since Mon 2013-09-23 15:52:50 BST; 51s ago
Process: 473 ExecStop=/usr/bin/screen -S bfgminer -X quit (code=exited, status=1/FAILURE)
Process: 470 ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf (code=exited, status=0/SUCCESS)
Main PID: 471 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/bfgminer.service

Sep 23 15:52:50 minepeon systemd[1]: Unit bfgminer.service entered failed state.
Sep 23 15:52:50 minepeon systemd[1]: bfgminer.service holdoff time over, scheduling restart.
Sep 23 15:52:50 minepeon systemd[1]: Stopping bfgminer...
Sep 23 15:52:50 minepeon systemd[1]: Starting bfgminer...
Sep 23 15:52:50 minepeon systemd[1]: bfgminer.service start request repeated too quickly, refusing to start.
Sep 23 15:52:50 minepeon systemd[1]: Failed to start bfgminer.
Sep 23 15:52:50 minepeon systemd[1]: Unit bfgminer.service entered failed state.
[minepeon@minepeon ~]$

Can run & post the results of the below command:

Code:

sudo cat /usr/lib/systemd/system/bfgminer.service

Nighthawkxx

member

Activity: 90

Merit: 10

I was testing Minepeon 0.2.2 and tried to change to bfgminer but for some reason it doesn't work, Also tried Minepeon 0.2.3a and got the same issue.

Currently i have no clue what might be wrong.

Quote

[minepeon@minepeon ~]$ sudo systemctl status bfgminer.service
bfgminer.service - bfgminer
Loaded: loaded (/usr/lib/systemd/system/bfgminer.service; enabled)
Active: failed (Result: start-limit) since Mon 2013-09-23 15:52:50 BST; 51s ago
Process: 473 ExecStop=/usr/bin/screen -S bfgminer -X quit (code=exited, status=1/FAILURE)
Process: 470 ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf (code=exited, status=0/SUCCESS)
Main PID: 471 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/bfgminer.service

Sep 23 15:52:50 minepeon systemd[1]: Unit bfgminer.service entered failed state.
Sep 23 15:52:50 minepeon systemd[1]: bfgminer.service holdoff time over, scheduling restart.
Sep 23 15:52:50 minepeon systemd[1]: Stopping bfgminer...
Sep 23 15:52:50 minepeon systemd[1]: Starting bfgminer...
Sep 23 15:52:50 minepeon systemd[1]: bfgminer.service start request repeated too quickly, refusing to start.
Sep 23 15:52:50 minepeon systemd[1]: Failed to start bfgminer.
Sep 23 15:52:50 minepeon systemd[1]: Unit bfgminer.service entered failed state.
[minepeon@minepeon ~]$

Polyatomic

sr. member

Activity: 257

Merit: 250

Neil,would you consider a channel on freenode for discussion in real time about minepeon.

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: RicRock on September 21, 2013, 06:19:46 PM

Quote from: chanberg on September 21, 2013, 04:48:16 PM

Quote from: tk1337 on September 21, 2013, 03:59:54 PM

Quote from: chanberg on September 21, 2013, 03:48:15 PM

indeed it seems that cgminer does crash when using usb miners... BFG has been working solid for the past 10 hours

Since I switched to BFGMiner, 4d 8h 16m 36s uptime thus far.

Speaking of which i have sort of an issue. BFG mines fine with usb miners, but whenever it reboots it doesn't mine automatically like cgminer, i have to ssh into the Pi, and go into manage devices and type ALL for BFGminer to find the USB erupters...

So whenever my Pi crashes, i would have to physically log into Pi, and type in ALL just to get the Bfgminer going again... Anyway automated way for bfg to just recognize the devices from the get-go?

Do you start it with the switch -S 'erupter:all' ?

^ except without the single quotation marks.

Your bfgminer.service file should look something like:

Code: (/usr/lib/systemd/system/bfgminer.service)

[Unit]
Description=bfgminer
After=network.target openntpd.service

[Service]
Type=forking
User=minepeon
ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf
ExecStop=/usr/bin/screen -S bfgminer -X quit
Restart=always

[Install]
WantedBy=multi-user.target

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: chanberg on September 21, 2013, 04:48:16 PM

Quote from: tk1337 on September 21, 2013, 03:59:54 PM

Quote from: chanberg on September 21, 2013, 03:48:15 PM

indeed it seems that cgminer does crash when using usb miners... BFG has been working solid for the past 10 hours

Since I switched to BFGMiner, 4d 8h 16m 36s uptime thus far.

Speaking of which i have sort of an issue. BFG mines fine with usb miners, but whenever it reboots it doesn't mine automatically like cgminer, i have to ssh into the Pi, and go into manage devices and type ALL for BFGminer to find the USB erupters...

So whenever my Pi crashes, i would have to physically log into Pi, and type in ALL just to get the Bfgminer going again... Anyway automated way for bfg to just recognize the devices from the get-go?

Do you start it with the switch -S 'erupter:all' ?

chanberg

hero member

Activity: 672

Merit: 500

Quote from: tk1337 on September 21, 2013, 03:59:54 PM

Quote from: chanberg on September 21, 2013, 03:48:15 PM

indeed it seems that cgminer does crash when using usb miners... BFG has been working solid for the past 10 hours

Since I switched to BFGMiner, 4d 8h 16m 36s uptime thus far.

Speaking of which i have sort of an issue. BFG mines fine with usb miners, but whenever it reboots it doesn't mine automatically like cgminer, i have to ssh into the Pi, and go into manage devices and type ALL for BFGminer to find the USB erupters...

So whenever my Pi crashes, i would have to physically log into Pi, and type in ALL just to get the Bfgminer going again... Anyway automated way for bfg to just recognize the devices from the get-go?

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: chanberg on September 21, 2013, 03:48:15 PM

indeed it seems that cgminer does crash when using usb miners... BFG has been working solid for the past 10 hours

Since I switched to BFGMiner, 4d 8h 16m 36s uptime thus far.

chanberg

hero member

Activity: 672

Merit: 500

indeed it seems that cgminer does crash when using usb miners... BFG has been working solid for the past 10 hours

pluMmet

sr. member

Activity: 588

Merit: 251

Quote from: tk1337 on September 20, 2013, 03:24:04 PM

Quote from: pluMmet on September 20, 2013, 03:20:38 PM

*Does not matter pi still does not see my stuff on the usb 3.0 hubs Sad

to be honest, I didn't think it would... I have a Raspbian fully updated and it doesn't detect anything USB 3.0... if you want it to work with the Pi, best chances are sticking to USB 2.0

Well I'm chaining 4 usb 3.0 into a usb 2.0 then to my mining hardware... was hoping the 2.0 would work out as it's the host.

LogicalUnit

sr. member

Activity: 299

Merit: 250

I believe I have found the cause of a bug in the WebGui that distorts all of the statistics:

https://bitcointalksearch.org/topic/m.3201676

tk1337

sr. member

Activity: 266

Merit: 250

Quote from: pluMmet on September 20, 2013, 03:20:38 PM

*Does not matter pi still does not see my stuff on the usb 3.0 hubs Sad

to be honest, I didn't think it would... I have a Raspbian fully updated and it doesn't detect anything USB 3.0... if you want it to work with the Pi, best chances are sticking to USB 2.0

Topic: Linux mining distro for the Raspberry PI - MinePeon - page 61. (Read 685140 times)