Quote from: crashoveride54902 on July 13, 2014, 12:21:06 AM

Quote from: Drystion on July 12, 2014, 10:43:15 PM

Quote from: crashoveride54902 on July 12, 2014, 04:43:57 PM

Quote from: Drystion on July 12, 2014, 04:11:28 PM

Quote from: iikun on July 12, 2014, 08:24:20 AM

Quote from: Drystion on July 12, 2014, 03:41:08 AM

I just got a launcher today, plugged it all up, turned it on... And it just shuts back down after about one minute. If I unplug the launcher then I can get the pi to run, and was able to update it. I haven't been able to add a pool however, the page seems to freeze when I try.

Any ideas what I did wrong? Could it be the power cable that shipped with the pi?

my pi didnt load up that far on my original cable. Im not sure the pi power cable is the issue in your case but that would be a good starting point to look at

Thanks, I picked up a 5v 1.5A micro usb cable to power the pi with. The launcher unit still shuts down after a minute ish. Have not had a single hash as of yet. Still cant even add a pool or delete the one it came with. I'm starting to get worried something is faulty. The pi lights up and keeps running now that its plugged into a socket instead of the PSU, could it be the PSU?

It was listing "socket connect(127.0.0.1,4001) failed returning null" in the log before shutting the launcher down.

if you have a spare psu i'd try that, the more you can narrow down the faulty part the faster you can get to a solution

The only other PSU I have is in my PC, and that could be a problem to unplug everything, however Its 750W so same as the PSU I have, but its not modular.

I'm worried about the pi mostly, I should be able to at least just load the pi interface and add/change pool info, and I cant do that. Unless I'm missing something... Maybe I shouldn't have updated it right away. Can anyone confirm that it is possible to add pool info to the pi without the launcher running?

I decided I might want to format the SD card and install the software on it fresh, I plugged the SD card into my pac and its showing 18.7MB used and 37.2MB free. What the heck, isn't it supposed to be a 8GB card? The imagine you put on it is multiple gigs, I'm either doing something wrong, totally lost, or maybe the problem is this card. Hmm, maybe I need to go buy a new card and try this.

pull out the card n see what it says on it...but ya sometimes running a sd card with something special on it only shows so much space on it whether its a 8gig card showing 37mb...my 16gig card did the same thing when i had to flash my jups and as soon as i reformated it went back to 16gig...

Your right, I got a new SD card, formatted ect, and using it (not updating firmware this time) I can now actually change my pool info at least, thought its still not connecting to the miner by the looks of it. Not sure why, but I've noticed the pi is 5 hours ahead of my time zone, both with the SD card they sent and the new one, not sure if that matters... I've restated a few times and I've got the launcher actually running for over a minute, but still not hashing, I think maybe the card was corrupted or damaged or something. Or maybe it was because I updated the firmware asap that was giving problems.

Now that the launcher and the pi are both running, its just giving this in the log file, over and over
Jul 13 01:19:27 single_ltc_monitor[2418]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:29 MinerClass log[1972]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:32 single_ltc_monitor[2418]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:34 MinerClass log[1972]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:37 single_ltc_monitor[2418]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:39 MinerClass log[1972]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:42 single_ltc_monitor[2418]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:44 MinerClass log[1972]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:47 single_ltc_monitor[2418]: socket connect(127.0.0.1,4001) failed returning null
Jul 13 01:19:49 MinerClass log[1972]: socket connect(127.0.0.1,4001) failed returning null

So I click reboot, it runs a bit, and then the launcher shuts down after a min again. But hey, at least it ran for a while this time, kinda think its not the PSU at all.

So yea, starting to kick myself for not doing full diligence before ordering one, I don't think there is a single company that makes any kind of ASICs that's taking it seriously. Ill mess more and keep restarting later, but I haven't found anything useful on these errors as of yet. Ty crashoveride and iikun for the help thus far.