I should also add it takes.like 10 minutes to boot. It copies the images over then it boots them from.
I remembered why I was having issues building uboot. The new uboot binary was like 436k and wad writing over the space allocated for the uboot env storage which I think started at 380k. Then writing the env vars back you were overwriting uboot itself. It can be changed in the uboot code. The uboot partition is 1meg so there is space for it...
----- Reply message -----
From: "Robert Moskowitz" <rgm@htt-consult.com>
To: "Paul Whalen" <pwhalen@redhat.com>
Cc: <arm@lists.fedoraproject.org>
Subject: [fedora-arm] Bad image/instructions? - Re: Problems with a pogoplug v02
Date: Thu, Apr 18, 2013 4:19 pm
On 04/18/2013 03:11 PM, Paul Whalen wrote:
>
> ----- Original Message -----
>> Per:
>>
>> fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
>>
>> I just downloaded the image again from:
>>
>> http://dl.fedoraproject.org/pub/fedora-secondary/releases/18/Images/arm/Fedora-18-kirkwood-arm.img.xz
>>
>> This time I took a 4Gb usb drive I got from MicroCenter that still had a
>> FAT partition. On my F18 notebook as root, I ran:
>>
>> xzcat Fedora-18-kirkwood-arm.img.xz > /dev/sdc1
> Hi Rob,
>
> In your above example your writing to the first partition. Try changing that to:
>
> xzcat Fedora-18-kirkwood-arm.img.xz > /dev/sdc
>
> Hope that works,
OK. I kind of figured out part of this. That is, I had more to do
after the 1st boot, per:
fedoraproject.org/wiki/Architectures/ARM/F18/GuruPlug
Problem is with the instructions:
# NOTE: substitute "usb 1:1" with "usb 0:1" on non-Plus model devices,
or try:
usb start
ext2ls usb x:1
#where x can be any integer but usually 0-3, the right number will show
a directory listing including the files uInitrd and uImage
Well no usb or ext2ls commands. I searched all over the image. I ran
updatedb, the tried locate. Nothing. Now what?
_______________________________________________
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm