Title: *daemon is a no-go*, BAMT-0.5c, cgminer-3.3.1, new mother Post by: bl0odless1 on July 21, 2013, 06:06:13 PM Troubleshooting frustration here, kind readers:
I've thrown together a rig here for my roommate (bl0odless1), I'd like to get it going for him before I move out in a couple weeks. ASRock 970 Extreme4 with 3 5830's and a bunch of Eruptors. To make it as easy for him, I threw BAMT on a flashcard for a most-of-the-time miner, instead of mucking around with MS or dual-booting nightmares of multi-card vs xorg.conf... Anyways, BAMT is up. I've patched up cgminer via Git to bring stratum:3333 and USB into the mix. Mother was updated. bamt.conf, pools, cgminer.conf all configured ok. Manual execution of cgminer in terminal is good, running 12 hours now. I even magically got all 3 GPU's reporting hashrates and temps to monitors somehow today (at first only GPU 0 was getting reported. GPUMON?) The wall I've hit is in the daemon. From what I can see in the start, /etc/init.d/mine -start is ok, reporting "Starting mining processes...",calling up $DAEMON (symlink /usr/sbin/start_mining --> /opt/bamt/start_mining) So what I see is: Code: Starting mining processes...: minestart_mining: starting mining processes And then.... nothing. The term closes, background goes red as it should. Just, nothing. I've been digging though this OS 48 hours straight, hoping for error logs, a misconfig somewhere, I'm finding nothing. It's a miracle that I actually have all 3 GPUs mining via stratum at this point, but I just need that last step of automation for my less-than-technical roommate to not be calling me all the time. Anyone have any ideas? Thanks for reading. Title: Re: *daemon is a no-go*, BAMT-0.5c, cgminer-3.3.1, new mother Post by: bl0odless1 on July 21, 2013, 10:56:44 PM NVRMD I threw my hands in the air.... no USB in the kernel for the erupters. Meh.
|