|
pluMmet
|
 |
September 20, 2013, 08:08:56 PM
Last edit: September 20, 2013, 08:21:11 PM by pluMmet |
|
I'm updating right now. I got this message: ___________________________________________________ Timestamp hook for mkinitcpio no longer exists. If you used this hook is must be removed. A systemd hook has been added which provides this functionality. ___________________________________________________ sshd.conf is now different too.. /etc/ssh/sshd.conf.pacnew ___________________________________________________ sysctl.conf is now removed change name to etc/sysctl.d/99-sysctl.conf if you modified all settings are kernel defaults ___________________________________________________ I hope MinePeon does need it the way it was.  |
|
|
|
|
|
|
|
If you want to be a moderator, report many posts with accuracy. You will be noticed.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
pluMmet
|
|
September 20, 2013, 08:20:38 PM |
|
*Does not matter pi still does not see my stuff on the usb 3.0 hubs  |
|
|
|
|
|
tk1337
|
|
September 20, 2013, 08:24:04 PM |
|
*Does not matter pi still does not see my stuff on the usb 3.0 hubs 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 |
|
|
|
|
|
|
|
pluMmet
|
|
September 21, 2013, 09:33:25 AM |
|
*Does not matter pi still does not see my stuff on the usb 3.0 hubs 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. |
|
|
|
|
|
chanberg
|
|
September 21, 2013, 08:48:15 PM |
|
indeed it seems that cgminer does crash when using usb miners... BFG has been working solid for the past 10 hours
|
|
|
|
|
|
tk1337
|
|
September 21, 2013, 08:59:54 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
|
|
September 21, 2013, 09:48:16 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? |
|
|
|
|
|
RicRock
|
|
September 21, 2013, 11:19:46 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' ? |
|
|
|
|
|
tk1337
|
|
September 22, 2013, 01:48:46 AM |
|
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: [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 |
|
|
|
|
|
Polyatomic
|
|
September 22, 2013, 01:49:02 AM |
|
Neil,would you consider a channel on freenode for discussion in real time about minepeon.
|
|
|
|
|
Nighthawkxx
Member
 Offline
Activity: 90
Merit: 10
|
|
September 23, 2013, 02:58:31 PM |
|
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. [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 ~]$
|
|
|
|
|
|
tk1337
|
|
September 23, 2013, 03:38:30 PM |
|
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. [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: sudo cat /usr/lib/systemd/system/bfgminer.service |
|
|
|
|
Nighthawkxx
Member
Offline
Activity: 90
Merit: 10
|
|
September 23, 2013, 04:23:41 PM |
|
[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
|
|
September 23, 2013, 05:14:50 PM |
|
[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? 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.) |
|
|
|
|
|
Morblias
|
|
September 23, 2013, 06:03:59 PM |
|
Shouldn't it be this? ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf instead of his original post: ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf |
Tips / Donations accepted: 1Morb18DsDHNEv6TeQXBdba872ZSpiK9fY
|
|
|
|
tk1337
|
|
September 23, 2013, 06:43:00 PM |
|
Shouldn't it be this? ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf instead of his original post: 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. |
|
|
|
|
|
KyrosKrane
|
|
September 23, 2013, 07:08:01 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: ExecStart=/usr/bin/screen -dmS bfgminer /opt/minepeon/bin//bfgminer/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf |
|
|
|
|
chanberg
|
|
September 23, 2013, 07:32:07 PM |
|
PERFECT. Thanks so much TK!
Danny
|
|
|
|
|
Nighthawkxx
Member
Offline
Activity: 90
Merit: 10
|
|
September 23, 2013, 07: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. minepeon@minepeon ~ $ /opt/minepeon/bin/bfgminer -S all -c /opt/minepeon/etc/miner.conf All devices disabled, cannot mine! minepeon@minepeon ~ $ /opt/minepeon/bin/bfgminer -S erupter:all -c /opt/minepeon/etc/miner.conf All devices disabled, cannot mine! miner.conf Icarus settings manually added. {
"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"
}
]
} |
|
|
|
|
|
