[ARMedslack] Booting Slack 13.1 from eSata on Guruplug ServerPlus

blair.hoddinott at gmail.com blair.hoddinott at gmail.com
Thu Jan 6 17:01:38 UTC 2011


Not for me, its just a straight no boot device error. :(


Sent from my BlackBerry device on the Rogers Wireless Network

-----Original Message-----
From: Stuart Winter <m-lists at biscuit.org.uk>
Sender: armedslack-bounces at lists.armedslack.org
Date: Thu, 6 Jan 2011 15:12:12 
Reply-To: Slackware ARM port  <armedslack at lists.armedslack.org>
Cc: Slackware ARM port<armedslack at lists.armedslack.org>
Subject: Re: [ARMedslack] Booting Slack 13.1 from eSata on Guruplug Server
 Plus


> I did have a look actually, but I think I've run into an initialisation
> issue. It works intermittently - if you run up a kernel, halt and then
> reset via JTAG, it will detect the drive, but fail when trying to access
> it. If you reset the plug after that happens the drive then becomes
> accessible to u-boot.

Is the symptom that when u-boot tries to find the drive, it stops with a
"T" and won't go further?  I see this on one of my sheevaplugs and afaict
it's because the drive spun down.  This is why I have a "reset" at the end
of the boot command -- if the timeout happens, the plug reboots, the drive
is still spinning and the boot works.
This happens every time I complete a reinstallation of the plug (I assume
because the spin down delay is just short enough that by the time the
installer has shut itself down, and the system's rebooted, the drive has
spun down).

_______________________________________________
ARMedslack mailing list
ARMedslack at lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack


More information about the ARMedslack mailing list