--- On Wed, 9/30/09, Martin Dengler <martin(a)martindengler.com> wrote:
From: Martin Dengler <martin(a)martindengler.com>
Subject: Re: New SoaS [XO-1] build soas70
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: fedora-olpc-list(a)redhat.com
Date: Wednesday, September 30, 2009, 5:49 AM
On Wed, Sep 30, 2009 at 01:56:45AM
-0700, Yioryos Asprobounitis wrote:
>
>
> --- On Wed, 9/30/09, Martin Dengler <martin(a)martindengler.com>
wrote:
>
> > From: Martin Dengler <martin(a)martindengler.com>
> > Subject: Re: New SoaS [XO-1] build soas70
> > To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> > Cc: fedora-olpc-list(a)redhat.com
> > Date: Wednesday, September 30, 2009, 4:31 AM
> > On Wed, Sep 30, 2009 at 12:01:01AM
> > -0700, Yioryos Asprobounitis wrote:
> > > soas71xo.2gremovable: olpcrd.img symlink is
missing
> > from the /boot
> > > folder
> >
> > This is by design. The initrd olpc.fth asks for
is
> > /boot/initrd.img. olpcrd.img has not been used
for a long
> > time, and
> > initrd.img is not necessary to boot the included
kernel on
> > the XO-1.
>
> However, the olpc.fth points to \boot\initrd.img
Well, it points to something a bit different than that, but
that's not
really germane.
The lack of the initrd.img file in the specified location
will cause
OFW to print an error message, and then carry on giving
control to the
linux kernel. So unless the kernel needs the initrd
(in the case, it
doesn't), you don't have to worry about it.
I repeated the process form scratch.
The included olpc.fth in the vergin stick _does_ point to initrd.img and the OFW complains
that can not open the boot devise and stops there. (more below)
> Looks like a SoaS olpc.fth generated by liveCD-to-usb
and tries to
> generate an overlay I think.
There's no livecd-to-usb script involved. There is no
overlay
involved either.
> > > [...] resulting in kernel panic
> >
> > There should be no kernel panic due to a missing
> > initrd.img. Are you
> > really trying to boot from the removable image?
Its
> > olpc.fth looks
> > fine to me.
>
> I downloaded soas71xo.2gremovable.img.tar.lzma and
then
> cat soas71xo.2gremovable.tar.lzma | lzma -dc - | tar
xf - -O >
> /dev/sda to a _USB_ stick (not SD card)
Ok. So the instructions should be:
1) Power on the XO-1 with the USB stick in it
2) Press Esc to get to the OFW prompt
3) Check the USB stick looks ok with "dir u:\boot"
4) Boot from the USB stick with these OFW commands:
" ro root=LABEL=OLPCRoot rootwait" to boot-file
" u:\boot\vmlinuz" to boot-device
setup-smbios
boot
Then it'd be good to observe what happens. Do you see the
green and
blue "sugarlabs" logo when the kernel messages appear?
I made a new olpc.fth file with just these 4 lines after a "\ boot script" line
on the top.
It does go through the kernel loading with the SL logo on the top and then freezes at:
Waiting for root devise LABEL=OLPCRoot...
Changing to
" ro root=/dev/dsa1 rootwait" to boot-file
in case their is label conflict with the NAND which has F11-XO1/os7, results in a freeze
at: Waiting for root devise /dev/dsa1
Just to verify that the the stick shows up as "OLPCRoot" on any Linux OS
including Sugar and it is /dev/sda1 when booting the XO from the NAND or an SD card. It is
ext2 formatted and I did erase the stick just before 'cating' the soas71xo file
into it.
So certainly will not boot with just the kernel in this setting.
> so the console=... etc parameters are not needed in
the boot-file
> string?
They're good to have in normal operation but are not
required to get
to a basic runlevel 3 or 5.
Martin