12:04 a.m.
--- On Wed, 4/14/10, Mikus Grinbergs <mikus(a)bga.com> wrote:
From: Mikus Grinbergs <mikus(a)bga.com>
Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released
To: "Bernie Innocenti" <bernie(a)codewiz.org>
Cc: "OLPC Devel" <devel(a)lists.laptop.org>, "Fedora OLPC List"
<fedora-olpc-list(a)redhat.com>
Date: Wednesday, April 14, 2010, 6:08 PM
Was unable to boot XO-1 with
build140py installed on jffs2, unless
develop.sig was present.
If not present, OFW (q2e42e) gave the message "No signature
for our key
list"
My XO-1 has security disabled and boots fine. With the exception of the first boot that
something on olpc.fth blocks it (with no OFW messages) and never goes to console.
Regarding the freeze at the camera-check boot point, I had it with os129py (not with
os140py yet) but I considered it a consequence of my broken camera. Maybe not then.
mikus
_______________________________________________
olpc mailing list
olpc(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/olpc
7:12 a.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
yioryos wrote:
--- On Wed, 4/14/10, Mikus Grinbergs <mikus(a)bga.com> wrote:
>
> If not present, OFW (q2e42e) gave the message "No signature
> for our key list"
My XO-1 has security disabled and boots fine. With the
exception of the first boot that something on olpc.fth blocks
it (with no OFW messages) and never goes to console.
what changed between the first and second boots that might have
made the second successful after the first failed?
paul
Regarding the freeze at the camera-check boot point, I had it with os129py (not
with os140py yet) but I considered it a consequence of my broken camera. Maybe
not then.
=---------------------
paul fox, pgf(a)laptop.org
7:48 a.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Thu, 4/15/10, Paul Fox <pgf(a)laptop.org> wrote:
From: Paul Fox <pgf(a)laptop.org>
Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: "OLPC Devel" <devel(a)lists.laptop.org>, "Fedora OLPC List"
<fedora-olpc-list(a)redhat.com>
Date: Thursday, April 15, 2010, 8:12 AM
yioryos wrote:
>
> --- On Wed, 4/14/10, Mikus Grinbergs <mikus(a)bga.com>
wrote:
>
> >
> > If not present, OFW (q2e42e) gave the message
"No signature
> > for our key list"
>
> My XO-1 has security disabled and boots fine.
With the
> exception of the first boot that something on
olpc.fth blocks
> it (with no OFW messages) and never goes to console.
what changed between the first and second boots that might
have
made the second successful after the first failed?
See http://lists.laptop.org/pipermail/devel/2010-April/028172.html above
:-)
To repeat, I loaded the olpc.fth from my SDcard instead the internal NAND.
It looked like that:
\ Boot script
" root=/dev/mtdblock0 rootfstype=jffs2 console=ttyS0,115200 console=tty0
fbcon=font:SUN12x22 selinux=0" to boot-file
" nand:\boot\vmlinuz" to boot-device
" nand:\boot\initrd.img" to ramdisk
setup-smbios
unfreeze
dcon-unfreeze
visible
boot
Set up os140py. Removed the SDcard and rebooted.
paul
>
> Regarding the freeze at the camera-check boot point,
I had it with os129py (not
> with os140py yet) but I considered it a consequence
of my broken camera. Maybe
> not then.
>
>
=---------------------
paul fox, pgf(a)laptop.org
8:01 a.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
yioryos wrote:
--- On Thu, 4/15/10, Paul Fox <pgf(a)laptop.org> wrote:
> From: Paul Fox <pgf(a)laptop.org>
> Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released
> To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> Cc: "OLPC Devel" <devel(a)lists.laptop.org>, "Fedora OLPC
List"
<fedora-olpc-list(a)redhat.com>
> Date: Thursday, April 15, 2010, 8:12 AM
> yioryos wrote:
> >
> > --- On Wed, 4/14/10, Mikus Grinbergs <mikus(a)bga.com>
> wrote:
> >
> > >
> > > If not present, OFW (q2e42e) gave the message
> "No signature
> > > for our key list"
> >
> > My XO-1 has security disabled and boots fine.
> With the
> > exception of the first boot that something on
> olpc.fth blocks
> > it (with no OFW messages) and never goes to console.
>
> what changed between the first and second boots that might
> have
> made the second successful after the first failed?
See http://lists.laptop.org/pipermail/devel/2010-April/028172.html above
:-)
To repeat, I loaded the olpc.fth from my SDcard instead the internal NAND.
It looked like that:
\ Boot script
" root=/dev/mtdblock0 rootfstype=jffs2 console=ttyS0,115200 console=tty0
fbcon=font:SUN12x22 selinux=0" to boot-file
" nand:\boot\vmlinuz" to boot-device
" nand:\boot\initrd.img" to ramdisk
setup-smbios
unfreeze
dcon-unfreeze
visible
boot
Set up os140py. Removed the SDcard and rebooted.
so one possibility is that os140py isn't successfully enabling
smbios, or not recognizing the results correctly.
what firmware is installed on our XO-1?
and -- question for bernie -- does os140py include a new firmware?
paul
=---------------------
paul fox, pgf(a)laptop.org
8:14 a.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
On 15 April 2010 10:01, Paul Fox <pgf(a)laptop.org> wrote:
so one possibility is that os140py isn't successfully enabling
smbios, or not recognizing the results correctly.
(assuming this bug is indeed an instance of #9100...)
SMBIOS should not be required for not-crashing during early boot.
Daniel
8:44 a.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Thu, 4/15/10, Paul Fox <pgf(a)laptop.org> wrote:
From: Paul Fox <pgf(a)laptop.org>
Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: "OLPC Devel" <devel(a)lists.laptop.org>, "Fedora OLPC List"
<fedora-olpc-list(a)redhat.com>
Date: Thursday, April 15, 2010, 9:01 AM
yioryos wrote:
>
>
> --- On Thu, 4/15/10, Paul Fox <pgf(a)laptop.org>
wrote:
>
> > From: Paul Fox <pgf(a)laptop.org>
> > Subject: Re: ANNOUNCE: F11 for the XO-1 build
140py released
> > To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
> > Cc: "OLPC Devel" <devel(a)lists.laptop.org>,
"Fedora OLPC List"
> <fedora-olpc-list(a)redhat.com>
> > Date: Thursday, April 15, 2010, 8:12 AM
> > yioryos wrote:
> > >
> > > --- On Wed, 4/14/10, Mikus Grinbergs
<mikus(a)bga.com>
> > wrote:
> > >
> > > >
> > > > If not present, OFW (q2e42e)
gave the message
> > "No signature
> > > > for our key list"
> > >
> > > My XO-1 has security disabled and
boots fine.
> > With the
> > > exception of the first boot that
something on
> > olpc.fth blocks
> > > it (with no OFW messages) and never
goes to console.
> >
> > what changed between the first and second boots
that might
> > have
> > made the second successful after the first
failed?
>
> See http://lists.laptop.org/pipermail/devel/2010-April/028172.html
above
> :-)
>
> To repeat, I loaded the olpc.fth from my SDcard
instead the internal NAND.
> It looked like that:
>
> \ Boot script
> " root=/dev/mtdblock0 rootfstype=jffs2
console=ttyS0,115200 console=tty0
> fbcon=font:SUN12x22 selinux=0" to boot-file
> " nand:\boot\vmlinuz" to boot-device
> " nand:\boot\initrd.img" to ramdisk
> setup-smbios
> unfreeze
> dcon-unfreeze
> visible
> boot
>
> Set up os140py. Removed the SDcard and rebooted.
so one possibility is that os140py isn't successfully
enabling
smbios, or not recognizing the results correctly.
I'm not sure. It should not work in subsequent boots also then. No?
Looks like that needs something that is provided by the OS/initrd (/ofw?) but is generated
after the first successful run.
what firmware is installed on our XO-1?
as said (:-) q2e42d
and -- question for bernie -- does os140py include a new
firmware?
Did not offer to upgrade the FW at any point (initial or later boots) though it was
plugged for that exact reason.
paul
=---------------------
paul fox, pgf(a)laptop.org
7:33 p.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
On Thu, 2010-04-15 at 09:01 -0400, Paul Fox wrote:
and -- question for bernie -- does os140py include a new firmware?
Yes, it includes q2e42d. It works on all our laptops, and smbios is
enabled.
Yioryos, did you have AC plugged in when you flashed your laptop?
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
12:32 a.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Thu, 4/15/10, Bernie Innocenti <bernie(a)codewiz.org> wrote:
From: Bernie Innocenti <bernie(a)codewiz.org>
Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released
To: "Paul Fox" <pgf(a)laptop.org>
Cc: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>, "OLPC Devel"
<devel(a)lists.laptop.org>, "Fedora OLPC List"
<fedora-olpc-list(a)redhat.com>
Date: Thursday, April 15, 2010, 8:33 PM
On Thu, 2010-04-15 at 09:01 -0400,
Paul Fox wrote:
> and -- question for bernie -- does os140py include a
new firmware?
Yes, it includes q2e42d. It works on all our laptops, and
smbios is
enabled.
Yioryos, did you have AC plugged in when you flashed your
laptop?
Yes.
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
8:06 a.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
On 15 April 2010 09:48, Yioryos Asprobounitis <mavrothal(a)yahoo.com> wrote:
> what changed between the first and second boots that might
> have
> made the second successful after the first failed?
See http://lists.laptop.org/pipermail/devel/2010-April/028172.html above
This sounds like http://dev.laptop.org/ticket/9100
Your workaround is interesting.
For me, this bug isn't specific to first boot, it's a
from-time-to-time type thing.
Daniel
8:54 a.m.
New subject: ANNOUNCE: F11 for the XO-1 build 140py released
--- On Thu, 4/15/10, Daniel Drake <dsd(a)laptop.org> wrote:
From: Daniel Drake <dsd(a)laptop.org>
Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released
To: "Yioryos Asprobounitis" <mavrothal(a)yahoo.com>
Cc: "Paul Fox" <pgf(a)laptop.org>, "OLPC Devel"
<devel(a)lists.laptop.org>, "Fedora OLPC List"
<fedora-olpc-list(a)redhat.com>
Date: Thursday, April 15, 2010, 9:06 AM
On 15 April 2010 09:48, Yioryos
Asprobounitis <mavrothal(a)yahoo.com>
wrote:
>> what changed between the first and second boots
that might
>> have
>> made the second successful after the first
failed?
>
> See http://lists.laptop.org/pipermail/devel/2010-April/028172.html
above
This sounds like http://dev.laptop.org/ticket/9100
Your workaround is interesting.
For me, this bug isn't specific to first boot, it's a
from-time-to-time type thing.
os140py only has half a dozen reboots so far but the problem did not reappear.
Also it _might_ be different than #9100 since pressing the power button turns the XO off
almost immediately. When in kernel land I have the feeling it takes a bit longer (from my
mess-ups with different distros, kernels and initrds :-).
Daniel
5149
days inactive
5150
days old
9 comments
4 participants
participants (4)
-
Bernie Innocenti -
Daniel Drake -
Paul Fox -
Yioryos Asprobounitis