Total Comments 5
Comments
-
Well, I think I've tried every "solution" I could find by websearching. It's ****ed. Just to summarize what's happened:
1: It was OK when I got it, could boot into the pre-installed Ubuntu.
2: Successfully installed ARMedslack on USB to use on it.
3: Successfully installed ARMedslack on SDHC to use on it.
4: Booted OK into ARMedslack a couple of times, at intervals, with no problems.
5: Problems started. No obvious cause.Posted 02-22-2012 at 05:59 AM by brianL 
-
Seems like broken hardware now.
Posted 02-22-2012 at 08:56 PM by Web31337
-
No, don't think so. The problem happens when it starts loading the kernel. Instead of the usual messages, all that gibberish shown in the screenshot appears. Every time I plug it in, both LED's come on, so I think the hardware's OK. I'll probably have another go at it in a month or so, possibly try building a new kernel for it. That will mean installing a cross-compiler, etc.
Posted 02-23-2012 at 07:25 AM by brianL
-
Oh that's why. I thought building own kernel was supposed to be the first step for debugging embedded devices.
Posted 02-26-2012 at 04:27 AM by Web31337
-
I don't really know. I usually dive into doing things without having a clue what I'm doing.Quote:Originally Posted by Web31337
I thought building own kernel was supposed to be the first step for debugging embedded devices.
Anyway, I don't think the kernel is the problem, since I get more or less the same results on my desktop and laptop (dual-booting Slack and Debian "squeeze"). That's three sheevaplug-installers.
This is the only other reference to a similar problem I found:
http://www.newit.co.uk/forum/index.php/topic,541.0.htmlPosted 02-26-2012 at 04:59 AM by brianL
