--- On Thu, 4/15/10, Paul Fox pgf@laptop.org wrote:
From: Paul Fox pgf@laptop.org Subject: Re: ANNOUNCE: F11 for the XO-1 build 140py released To: "Yioryos Asprobounitis" mavrothal@yahoo.com Cc: "OLPC Devel" devel@lists.laptop.org, "Fedora OLPC List" fedora-olpc-list@redhat.com Date: Thursday, April 15, 2010, 9:01 AM yioryos wrote:
--- On Thu, 4/15/10, Paul Fox pgf@laptop.org
wrote:
From: Paul Fox pgf@laptop.org Subject: Re: ANNOUNCE: F11 for the XO-1 build
140py released
To: "Yioryos Asprobounitis" mavrothal@yahoo.com Cc: "OLPC Devel" devel@lists.laptop.org,
"Fedora OLPC List"
Date: Thursday, April 15, 2010, 8:12 AM yioryos wrote: > > --- On Wed, 4/14/10, Mikus Grinbergs
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@laptop.org