12:30 p.m.
Could someone post some instruction here or at the download page on howto run the new
soasXO builds from a USB stick (assuming this is feasible)?
thx
2:37 p.m.
On Sun, Nov 01, 2009 at 10:30:15AM -0800, Yioryos Asprobounitis wrote:
Could someone post some instruction here or at the download page on
howto run the new soasXO builds from a USB stick (assuming this is
feasible)?
From http://cgit.sugarlabs.org/soas/mainline/tree/README.txt :
Instructions for experts:
------------
either:
copy-nand u:\soas??xo.img
or: (2g or larger removable)
cat soas??xo.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX
or: (4g or larger removable)
cat soas??xo.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX
Quick Start for normal people:
-------------
Create a removable drive with Sugar for use on your XO.
You need to have an unlocked XO first. See instructions here for
unlocking:
http://wiki.laptop.org/go/Activation_and_Developer_Keys#Disable_the_secur...
1) Download the right sized-image: 2g if you have a 2g removable
drive, 4g if you have a 4 or larger gigabyte removable drive.
2) "burn" it onto your removable media (USB stick / SD card).
**** THIS WILL ERASE EVERYTHING ON YOUR REMOVABLE DRIVE ****
Either:
cat soasxo??.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX
or:
cat soasxo??.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX
Replace the "??" with the right filename, and replace the "/dev/sdX"
with the name of your removable device (the _whole device_, NOT a
partition like /dev/sda1)
3) When this is done, eject the device and be sure all data were
written:
eject /dev/sdX ; sync ; sync
4) Plug the stick/card into your XO-1 and power it on.
Improvements to these instructions are very welcome.
thx
Martin
3:06 p.m.
On Sun, 2009-11-01 at 20:37 +0000, Martin Dengler wrote:
On Sun, Nov 01, 2009 at 10:30:15AM -0800, Yioryos Asprobounitis
wrote:
> Could someone post some instruction here or at the download page on
> howto run the new soasXO builds from a USB stick (assuming this is
> feasible)?
From http://cgit.sugarlabs.org/soas/mainline/tree/README.txt :
Instructions for experts:
------------
either:
copy-nand u:\soas??xo.img
or: (2g or larger removable)
cat soas??xo.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX
or: (4g or larger removable)
cat soas??xo.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX
Quick Start for normal people:
-------------
Create a removable drive with Sugar for use on your XO.
You need to have an unlocked XO first. See instructions here for
unlocking:
http://wiki.laptop.org/go/Activation_and_Developer_Keys#Disable_the_secur...
1) Download the right sized-image: 2g if you have a 2g removable
drive, 4g if you have a 4 or larger gigabyte removable drive.
2) "burn" it onto your removable media (USB stick / SD card).
**** THIS WILL ERASE EVERYTHING ON YOUR REMOVABLE DRIVE ****
Either:
cat soasxo??.4gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX
or:
cat soasxo??.2gremovable.tar.lzma | lzma -dc - | tar xf - -O > /dev/sdX
Replace the "??" with the right filename, and replace the "/dev/sdX"
with the name of your removable device (the _whole device_, NOT a
partition like /dev/sda1)
3) When this is done, eject the device and be sure all data were
written:
eject /dev/sdX ; sync ; sync
4) Plug the stick/card into your XO-1 and power it on.
Improvements to these instructions are very welcome.
Might have to tweek the /boot/olpc.fth file, have a look at:
http://wiki.laptop.org/go/Custom_bootloader
http://wiki.laptop.org/go/USB_Boot_olpc.fth
Jerry
3:15 p.m.
On Sun, Nov 01, 2009 at 03:06:21PM -0600, Jerry Vonau wrote:
On Sun, 2009-11-01 at 20:37 +0000, Martin Dengler wrote:
> On Sun, Nov 01, 2009 at 10:30:15AM -0800, Yioryos Asprobounitis wrote:
> > Could someone post some instruction here or at the download page on
> > howto run the new soasXO builds from a USB stick (assuming this is
> > feasible)?
>
> From http://cgit.sugarlabs.org/soas/mainline/tree/README.txt :
[...]
> Improvements very welcome.
Might have to tweek the /boot/olpc.fth file
SoaS has a tweaked /boot/olpc.fth[1] already that asks OFW to boot the
kernel from whatever device OFW loaded the /boot/olpc.fth file.
Improvements to it very welcome, too!
Jerry
Martin
1. http://cgit.sugarlabs.org/soas/mainline/tree/soas-base.ks#n145
11:27 p.m.
Thank you.
However I was referring to the http://download.sugarlabs.org/soas/snapshots/2/ builds
specifically where you have only tree.tar.lzma versions. Trying these with the
instructions mentioned bellow failed miserably (tried soas01xo and soas02xo). Expanding
their content in an ext3 formatted stick also failed boot.
I could try the newer soas04xo.tree.tar.lzma but pls specify
a) Is this a device images? If yes what size?
b) If not device images but indeed trees, are devices build with their content know to
boot the XO-1?. If yes do they need anything "special"?
Thanks
--- On Sun, 11/1/09, Martin Dengler <martin(a)martindengler.com> wrote:
From: Martin Dengler <martin(a)martindengler.com>
Subject: Re: soasXO builds for USB?
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: fedora-olpc-list(a)redhat.com
Date: Sunday, November 1, 2009, 3:37 PM
On Sun, Nov 01, 2009 at 10:30:15AM
-0800, Yioryos Asprobounitis wrote:
> Could someone post some instruction here or at the
download page on
> howto run the new soasXO builds from a USB stick
(assuming this is
> feasible)?
From http://cgit.sugarlabs.org/soas/mainline/tree/README.txt
:
Instructions for experts:
------------
either:
copy-nand u:\soas??xo.img
or: (2g or larger removable)
cat soas??xo.4gremovable.tar.lzma | lzma -dc - | tar
xf - -O > /dev/sdX
or: (4g or larger removable)
cat soas??xo.2gremovable.tar.lzma | lzma -dc - | tar
xf - -O > /dev/sdX
Quick Start for normal people:
-------------
Create a removable drive with Sugar for use on your XO.
You need to have an unlocked XO first. See
instructions here for
unlocking:
http://wiki.laptop.org/go/Activation_and_Developer_Keys#Disable_the_secur...
1) Download the right sized-image: 2g if you have a 2g
removable
drive, 4g if you have a 4 or larger gigabyte removable
drive.
2) "burn" it onto your removable media (USB stick / SD
card).
**** THIS WILL ERASE EVERYTHING ON YOUR REMOVABLE DRIVE
****
Either:
cat soasxo??.4gremovable.tar.lzma | lzma -dc - | tar xf -
-O > /dev/sdX
or:
cat soasxo??.2gremovable.tar.lzma | lzma -dc - | tar xf -
-O > /dev/sdX
Replace the "??" with the right filename, and replace the
"/dev/sdX"
with the name of your removable device (the _whole device_,
NOT a
partition like /dev/sda1)
3) When this is done, eject the device and be sure all data
were
written:
eject /dev/sdX ; sync ; sync
4) Plug the stick/card into your XO-1 and power it on.
Improvements to these instructions are very welcome.
> thx
Martin
11:34 p.m.
On Sun, Nov 01, 2009 at 09:27:10PM -0800, Yioryos Asprobounitis wrote:
However I was referring to the
http://download.sugarlabs.org/soas/snapshots/2/ builds specifically
where you have only tree.tar.lzma versions. Trying these with the
instructions mentioned bellow failed miserably (tried soas01xo and
soas02xo). Expanding their content in an ext3 formatted stick also
failed boot.
Yes, that would fail.
I could try the newer soas04xo.tree.tar.lzma but pls specify
a) Is this a device images? If yes what size?
No, they are not device images. "tree.tar" tells me that.
b) If not device images but indeed trees, are devices build with
their
content know to boot the XO-1?. If yes do they need anything
"special"?
The tree should contain that, in the /boot/olpc.fth file. I've not
checked if it does. You are welcome to check.
--
James Cameron
http://quozl.linux.org.au/
2:27 a.m.
On Sun, Nov 01, 2009 at 09:27:10PM -0800, Yioryos Asprobounitis wrote:
Thank you.
However I was referring to the
http://download.sugarlabs.org/soas/snapshots/2/ builds specifically
where you have only tree.tar.lzma versions.
Ah yes.
Sebastian, can you copy the 2/4g removable images from the buildslave
as well?
How about I add a "dist" target to the makefile that does this?
Trying these with the instructions mentioned bellow failed miserably
(tried soas01xo and soas02xo)
As you pointed out, the instructions are for the *removable*.tar.lzma.
Other files won't work with the verbatim instructions.
Expanding their content in an ext3 formatted stick also failed boot.
Actually that should work, since OFW doesn't need anything but
/boot/olpc.fth to exist in the first partition (as long as that
partition is readable by OFW, like ext3). So I'm not sure what went
wrong for you.
I could try the newer soas04xo.tree.tar.lzma but pls specify
a) Is this a device images? If yes what size?
No. It should work if you untar it into the root of a ext3 USB stick,
though, like:
cd /media/myusbstick
lzma -dc /path/to/soas04xo.tree.tar.lzma - | tar xf -
b) If not device images but indeed tree [...] do they need anything
"special"?
See above.
are devices build with their content know to boot the XO-1?.
I haven't tried that build itself on any sticks. But I don't know of
any reason why it shouldn't work. I'm happy to fix any problems
anyone finds.
Thanks
Martin
3:15 a.m.
On Mon, Nov 02, 2009 at 08:27:20AM +0000, Martin Dengler wrote:
On Sun, Nov 01, 2009 at 09:27:10PM -0800, Yioryos Asprobounitis
wrote:
> Expanding their content in an ext3 formatted stick also failed boot.
Actually that should work, since OFW doesn't need anything but
/boot/olpc.fth to exist in the first partition (as long as that
partition is readable by OFW, like ext3). So I'm not sure what went
wrong for you.
I've seen OFW fail to read an ext3 partition if the partition table is
unusual. The failure is repeatable using "dir u:".
In my experience, a partition table created by Debian or Ubuntu cfdisk,
sfdisk or certain versions of fdisk may not work, but a table created by
parted "mklabel msdos" works every time. I've never had problems with
partition tables from the USB device manufacturers.
I presume it is a flaw in cfdisk, sfdisk, or fdisk.
--
James Cameron
http://quozl.linux.org.au/
7:19 a.m.
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com> wrote:
From: Martin Dengler <martin(a)martindengler.com>
Subject: Re: soasXO builds for USB?
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: fedora-olpc-list(a)redhat.com
Date: Monday, November 2, 2009, 3:27 AM
On Sun, Nov 01, 2009 at 09:27:10PM
-0800, Yioryos Asprobounitis wrote:
> Thank you.
> However I was referring to the
> http://download.sugarlabs.org/soas/snapshots/2/ builds
specifically
> where you have only tree.tar.lzma versions.
Ah yes.
Sebastian, can you copy the 2/4g removable images from the
buildslave
as well?
How about I add a "dist" target to the makefile that does
this?
> Trying these with the instructions mentioned bellow
failed miserably
> (tried soas01xo and soas02xo)
As you pointed out, the instructions are for the
*removable*.tar.lzma.
Other files won't work with the verbatim instructions.
> Expanding their content in an ext3 formatted stick
also failed boot.
Actually that should work, since OFW doesn't need anything
but
/boot/olpc.fth to exist in the first partition (as long as
that
partition is readable by OFW, like ext3). So I'm not
sure what went
wrong for you.
> I could try the newer soas04xo.tree.tar.lzma but pls
specify
> a) Is this a device images? If yes what size?
No. It should work if you untar it into the root of a
ext3 USB stick,
though, like:
cd /media/myusbstick
lzma -dc /path/to/soas04xo.tree.tar.lzma - | tar xf -
This command actually will generate the ¨soas04xo.tree¨ folder at the root of the USB
stick.
cd /media/stickname/soas04xo.tree
mv * ../
sync
will give you a stick with the right folders and files but on boot I get:
No filesystem available yet, can detect types: ext3 ext2 ext4
which repeats for ever.
Any ideas?
> b) If not device images but indeed tree [...] do they
need anything
> "special"?
See above.
> are devices build with their content know to boot the
XO-1?.
I haven't tried that build itself on any sticks. But
I don't know of
any reason why it shouldn't work. I'm happy to fix
any problems
anyone finds.
> Thanks
Martin
7:37 a.m.
On Mon, Nov 02, 2009 at 05:19:21AM -0800, Yioryos Asprobounitis wrote:
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com>
wrote:
> > a) Is this a device images? If yes what size?
>
> No. It should work if you untar it into the root of a
> ext3 USB stick,
> though, like:
>
> cd /media/myusbstick
> lzma -dc /path/to/soas04xo.tree.tar.lzma - | tar xf -
This command actually will generate the ¨soas04xo.tree¨ folder at
the root of the USB stick.
cd /media/stickname/soas04xo.tree
mv * ../
sync
will give you a stick with the right folders and files but on boot I get:
No filesystem available yet, can detect types: ext3 ext2 ext4
which repeats for ever.
Any ideas?
You're seeing custom kernel patch to the "rootwait" option that prints
out the filesystems it sees every five seconds until it finds the one
specified by the "root=" kernel option.
It probably can't mount your USB device to get at the root file
system. It could also be the "root=OLPCRoot" argument - could you try
with "root=/dev/sda1" or something?
It could also be that the initrd doesn't have the usb modules, or that
the initrd isn't being used. Do you see OFW loading an initrd?
Thanks for testing this. I wish I had more time to do it myself and
save you the trouble.
Martin
8:16 a.m.
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com> wrote:
From: Martin Dengler <martin(a)martindengler.com>
Subject: Re: soasXO builds for USB?
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: fedora-olpc-list(a)redhat.com
Date: Monday, November 2, 2009, 8:37 AM
On Mon, Nov 02, 2009 at 05:19:21AM
-0800, Yioryos Asprobounitis wrote:
> --- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com>
wrote:
> > > a) Is this a device images? If yes what
size?
> >
> > No. It should work if you untar it into the
root of a
> > ext3 USB stick,
> > though, like:
> >
> > cd /media/myusbstick
> > lzma -dc /path/to/soas04xo.tree.tar.lzma - | tar
xf -
>
> This command actually will generate the
¨soas04xo.tree¨ folder at
> the root of the USB stick.
>
> cd /media/stickname/soas04xo.tree
> mv * ../
> sync
>
> will give you a stick with the right folders and files
but on boot I get:
>
> No filesystem available yet, can detect types: ext3
ext2 ext4
>
> which repeats for ever.
> Any ideas?
You're seeing custom kernel patch to the "rootwait" option
that prints
out the filesystems it sees every five seconds until it
finds the one
specified by the "root=" kernel option.
It probably can't mount your USB device to get at the root
file
system. It could also be the "root=OLPCRoot" argument
- could you try
with "root=/dev/sda1" or something?
I think that can not mount the USB. When I forced /dev/dsa1 as root= option in the
olpc.fth I get:
can not open root device sda1[...]
available partitions: mtdblock0 driver cafe NAND [...]
Kernel panic -not syncing [...]
I also changed fstab from ext4 to ext3. No improvement.
Finally adding the initrd path to olpc.fth I got all the way to the ¨enter your name
screen¨ !!
however both interal and external mouse/keyboards were non functional.
I guess this is related to the _HAL-daemon initialization failure_ that appeared during
the boot sequence.
So to get up to here I have the following olpc.fth/fstab
/boot/olpc.fth:
\ olpc.fth
" root=/dev/sda1 rootfstype=ext3 console=tty0 fbcon=font:SUN12x22 video=fb:1200x900
selinux=0" to boot-file
" u:\boot\initrd.img" to ramdisk
" u:\boot\vmlinuz" to boot-device
setup-smbios
unfreeze
dcon-unfreeze
visible
boot
/etc/fstab:
LABEL=OLPCRoot / ext3 defaults,noatime,errors=remount-ro 0 1
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/tmp /tmp tmpfs rw 0 0
none /ofw promfs defaults 0 0
(my stick IS named OLPCRoot)
Is further than before but not quite there yet.
Any further ideas?
Is HAL failure related to any of these or is a different issue?
It could also be that the initrd doesn't have the usb
modules, or that
the initrd isn't being used. Do you see OFW loading
an initrd?
Thanks for testing this. I wish I had more time to do
it myself and
save you the trouble.
Martin
1:32 p.m.
On Mon, Nov 02, 2009 at 06:16:02AM -0800, Yioryos Asprobounitis wrote:
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com>
wrote:
So to get up to here I have the following olpc.fth/fstab
So do you need _just_ the initrd definition or also the modified
"root=/dev/sda1" to get soas04xo to boot?
If it's just the initrd definition, perhaps there's something wrong
with the initrd selection in soas04xo's /boot/olpc.fth...can you try
commenting out the line:
" root=mtd0" " \${DN}" expand$ sindex -1 <> if
with a backslash at the beginning, please?
Is HAL failure related to any of these or is a different issue?
The HAL failure is not obviously related. Do you get it if you
copy-nand soas05xo.img?
Martin
3:04 p.m.
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com> wrote:
From: Martin Dengler <martin(a)martindengler.com>
Subject: Re: soasXO builds for USB?
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: fedora-olpc-list(a)redhat.com
Date: Monday, November 2, 2009, 2:32 PM
On Mon, Nov 02, 2009 at 06:16:02AM
-0800, Yioryos Asprobounitis wrote:
> --- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com>
wrote:
> So to get up to here I have the following
olpc.fth/fstab
So do you need _just_ the initrd definition or also the
modified
"root=/dev/sda1" to get soas04xo to boot?
Not really. Just defining the variable works fine, eg
" ro root=LABEL=OLPCRoot console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22
rootwait selinux=0" to boot-file
However, the keyboad/mouse/HAL problem remains.
It must be an independent problem/missing kernel mapper because if I also have in an
SDcard with the same label that has Ubuntu, with this olpc.fth goes all the way to the
Ubuntu gdm screen and then again no keyboad/mouse input
If it's just the initrd definition, perhaps there's
something wrong
with the initrd selection in soas04xo's
/boot/olpc.fth...can you try
commenting out the line:
" root=mtd0" " \${DN}" expand$ sindex -1
<> if
with a backslash at the beginning, please?
This just fails boot totally. Never gets to load initrd. OFW complains that there is a
problem in line 40 (the last)
I also corrected the intention of the inirtd.img line. No difference.
> Is HAL failure related to any of these or is a
different issue?
The HAL failure is not obviously related.
Not to the olpc.fth, but to the no keyboard/mouse issue. Actually if this is solved then
the modified olpc.fth should be OK.
Do you get
it if you
copy-nand soas05xo.img?
soas05xo ???
Martin
3:11 p.m.
On Mon, Nov 02, 2009 at 01:04:23PM -0800, Yioryos Asprobounitis wrote:
It must be an independent problem/missing kernel mapper because if I
also have in an SDcard with the same label that has Ubuntu, with this
olpc.fth goes all the way to the Ubuntu gdm screen and then again no
keyboad/mouse input
Just confirming ... keyboard and mouse works in OFW?
ok test keyboard
ok test mouse
If not, try removing all power and battery, wait ten seconds, restore.
--
James Cameron
http://quozl.linux.org.au/
3:22 p.m.
--- On Mon, 11/2/09, James Cameron <quozl(a)laptop.org> wrote:
From: James Cameron <quozl(a)laptop.org>
Subject: Re: soasXO builds for USB?
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: "Martin Dengler" <martin(a)martindengler.com>,
fedora-olpc-list(a)redhat.com
Date: Monday, November 2, 2009, 4:11 PM
On Mon, Nov 02, 2009 at 01:04:23PM
-0800, Yioryos Asprobounitis wrote:
> It must be an independent problem/missing kernel
mapper because if I
> also have in an SDcard with the same label that has
Ubuntu, with this
> olpc.fth goes all the way to the Ubuntu gdm screen and
then again no
> keyboad/mouse input
Just confirming ... keyboard and mouse works in OFW?
I'm posting from this XO and is still using the same firmware, so I guess it works!
ok test keyboard
ok test mouse
If not, try removing all power and battery, wait ten
seconds, restore.
--
James Cameron
http://quozl.linux.org.au/
9:45 p.m.
On Mon, 2009-11-02 at 13:04 -0800, Yioryos Asprobounitis wrote:
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com> wrote:
> From: Martin Dengler <martin(a)martindengler.com>
> Subject: Re: soasXO builds for USB?
> To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> Cc: fedora-olpc-list(a)redhat.com
> Date: Monday, November 2, 2009, 2:32 PM
> On Mon, Nov 02, 2009 at 06:16:02AM
> -0800, Yioryos Asprobounitis wrote:
> > --- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com>
> wrote:
> > So to get up to here I have the following
> olpc.fth/fstab
>
> So do you need _just_ the initrd definition or also the
> modified
> "root=/dev/sda1" to get soas04xo to boot?
Not really. Just defining the variable works fine, eg
" ro root=LABEL=OLPCRoot console=ttyS0,115200 console=tty0 fbcon=font:SUN12x22
rootwait selinux=0" to boot-file
However, the keyboad/mouse/HAL problem remains.
It must be an independent problem/missing kernel mapper because if I also have in an
SDcard with the same label that has Ubuntu, with this olpc.fth goes all the way to the
Ubuntu gdm screen and then again no keyboad/mouse input
>
> If it's just the initrd definition, perhaps there's
> something wrong
> with the initrd selection in soas04xo's
> /boot/olpc.fth...can you try
> commenting out the line:
>
> " root=mtd0" " \${DN}" expand$ sindex -1
> <> if
>
> with a backslash at the beginning, please?
This just fails boot totally. Never gets to load initrd. OFW complains that there is a
problem in line 40 (the last)
Think you need to \ the "then" two lines below also.
Jerry
3:19 p.m.
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com> wrote:
From: Martin Dengler <martin(a)martindengler.com>
Subject: Re: soasXO builds for USB?
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: fedora-olpc-list(a)redhat.com
Date: Monday, November 2, 2009, 2:32 PM
On Mon, Nov 02, 2009 at 06:16:02AM
-0800, Yioryos Asprobounitis wrote:
> --- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com>
wrote:
> So to get up to here I have the following
olpc.fth/fstab
So do you need _just_ the initrd definition or also the
modified
"root=/dev/sda1" to get soas04xo to boot?
If it's just the initrd definition, perhaps there's
something wrong
with the initrd selection in soas04xo's
/boot/olpc.fth...can you try
commenting out the line:
" root=mtd0" " \${DN}" expand$ sindex -1
<> if
with a backslash at the beginning, please?
Just to specify. After commenting out the ofw says
set-path-macros not unique
<number@hex>:40: stack change
ok
> Is HAL failure related to any of these or is a
different issue?
The HAL failure is not obviously related. Do you get
it if you
copy-nand soas05xo.img?
Martin
3:36 p.m.
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com> wrote:
From: Martin Dengler <martin(a)martindengler.com>
Subject: Re: soasXO builds for USB?
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: fedora-olpc-list(a)redhat.com
Date: Monday, November 2, 2009, 2:32 PM
On Mon, Nov 02, 2009 at 06:16:02AM
-0800, Yioryos Asprobounitis wrote:
> --- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com>
wrote:
> So to get up to here I have the following
olpc.fth/fstab
So do you need _just_ the initrd definition or also the
modified
"root=/dev/sda1" to get soas04xo to boot?
If it's just the initrd definition, perhaps there's
something wrong
with the initrd selection in soas04xo's
/boot/olpc.fth...can you try
commenting out the line:
" root=mtd0" " \${DN}" expand$ sindex -1
<> if
with a backslash at the beginning, please?
Part 3... (sorry)
The ¨not unique¨ complain is only when I also have in the SDcard with the same label. When
the card is not in, it fails at the OFW with:
<buffer@ffb69628>:40: Stack Changed
> Is HAL failure related to any of these or is a
different issue?
The HAL failure is not obviously related. Do you get
it if you
copy-nand soas05xo.img?
Martin
8:58 a.m.
PS:
Regarding the hardware recognition, HAL etc I also get during boot:
/proc/misc: No entry for device-mapper found
Is device-mapper missing from kernel?
Both /ver/log/dmesg and /var/log/messages are available if anyone wants to take a look
--- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com> wrote:
From: Martin Dengler <martin(a)martindengler.com>
Subject: Re: soasXO builds for USB?
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: fedora-olpc-list(a)redhat.com
Date: Monday, November 2, 2009, 8:37 AM
On Mon, Nov 02, 2009 at 05:19:21AM
-0800, Yioryos Asprobounitis wrote:
> --- On Mon, 11/2/09, Martin Dengler <martin(a)martindengler.com>
wrote:
> > > a) Is this a device images? If yes what
size?
> >
> > No. It should work if you untar it into the
root of a
> > ext3 USB stick,
> > though, like:
> >
> > cd /media/myusbstick
> > lzma -dc /path/to/soas04xo.tree.tar.lzma - | tar
xf -
>
> This command actually will generate the
¨soas04xo.tree¨ folder at
> the root of the USB stick.
>
> cd /media/stickname/soas04xo.tree
> mv * ../
> sync
>
> will give you a stick with the right folders and files
but on boot I get:
>
> No filesystem available yet, can detect types: ext3
ext2 ext4
>
> which repeats for ever.
> Any ideas?
You're seeing custom kernel patch to the "rootwait" option
that prints
out the filesystems it sees every five seconds until it
finds the one
specified by the "root=" kernel option.
It probably can't mount your USB device to get at the root
file
system. It could also be the "root=OLPCRoot" argument
- could you try
with "root=/dev/sda1" or something?
It could also be that the initrd doesn't have the usb
modules, or that
the initrd isn't being used. Do you see OFW loading
an initrd?
Thanks for testing this. I wish I had more time to do
it myself and
save you the trouble.
Martin
3:42 p.m.
Martin Dengler wrote:
On Sun, Nov 01, 2009 at 09:27:10PM -0800, Yioryos Asprobounitis
wrote:
> Thank you.
> However I was referring to the
> http://download.sugarlabs.org/soas/snapshots/2/ builds specifically
> where you have only tree.tar.lzma versions.
Ah yes.
Sebastian, can you copy the 2/4g removable images from the buildslave
as well?
Yeah, sorry. I didn't keep those on the buildslave to save some space,
while doing new builds. I'll just sync them over with the next snapshot,
if that's fine for everybody.
We'll also get more detailed instructions for the Blueberry launch, to
make sure everything is covered.
How about I add a "dist" target to the makefile that does
this?
Sure, go for it! :)
--Sebastian
[...]
> Thanks
Martin
5311
days inactive
5314
days old
19 comments
5 participants
participants (5)
-
James Cameron -
Jerry Vonau -
Martin Dengler -
Sebastian Dziallas -
Yioryos Asprobounitis