Yeah, I've tried that uboot (in my OP), but still no joy. It comes up with bad
block device. This makes me think it doesn't see the esata.
Before, using that uboot to my usb drive, results in the hang at uncompressing
linux which Ron is experiencing.
_B
Sent from my BlackBerry device on the Rog
This was my experience with the sheevaplug as well.
Sent from my BlackBerry device on the Rogers Wireless Network
-Original Message-
From: Stuart Winter
Sender: armedslack-boun...@lists.armedslack.org
Date: Mon, 29 Nov 2010 07:03:14
To: Slackware ARM port
Reply-To: Slackware ARM port
> This was my experience with the sheevaplug as well.
The SheevaPlug's USB was a bit flaky though, so I'm not *that* surprised;
but using the u-boot linked from the armedslack web site, my two boot
very quickly off USB, and the OpenRD is also fine.
I wouldn't recommend a FAT partition since ins
Sorry,
I meant to say that my experience was it booting no problem from the sheevaplug.
Nothing but problems with the guruplug... I'm starting to think its a lost
cause.
_B
Sent from my BlackBerry device on the Rogers Wireless Network
-Original Message-
From: Stuart Winter
Sender: ar
Oh my problems were only with the GuruPlug as far as ext booting is
concerned. Never with the Sheeva plug. And I do what Stuart says and
maintain the /boot manually since FAT doesn't handle sym-links.
** This message has been delivered via a Google Android **
On Nov 29, 2010 9:57 AM, wrote:
Sor
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
Sender: armedslack-boun...@lists.armedslack.org
Date: Thu, 6 Jan 2011 15:12:12
Reply-To: Slackware ARM port
Cc: Slackware ARM
I can test it out on my guruplugs
Sent from my BlackBerry device on the Rogers Wireless Network
-Original Message-
From: Jim Hawkins
Sender: armedslack-boun...@lists.armedslack.org
Date: Fri, 7 Jan 2011 15:36:00
To: Slackware ARM port
Reply-To: Slackware ARM port
Subject: Re: [ARMeds
