New F11 for XO-1.5 build 32 [#9457]
pgf at laptop.org
Thu Oct 22 18:39:00 UTC 2009
> On Thu, 2009-10-22 at 13:26 +1100, James Cameron wrote:
> > This appears to be #9457, so I've adjusted the subject line slightly.
> > On Wed, Oct 21, 2009 at 08:53:53PM -0500, Jerry Vonau wrote:
> > > On Thu, 2009-10-22 at 12:20 +1100, James Cameron wrote:
> > > > On Wed, Oct 21, 2009 at 07:57:13PM -0500, Jerry Vonau wrote:
> > > > > On Mon, 2009-10-19 at 05:13 -0400, John Watlington wrote: [?]
> > > > > > The expected usage model for an XO is that if there is a bootable
> > > > > > image on the external SD card or USB, it will be booted. If you
> > > > > > want to boot from the internal SD card, either remove the external SD
> > > > > > card or the bootable image installed on it.
> > > > > >
> > > > > > I don't think we want to change this model.
> > > > > >
> > > > > > This is currently broken, due to the way that the kernel names
> > > > > > devices. I believe that the proposed solution was to use udev
> > > > > > in the initramfs image to provide stable names.
> > > > >
> > > > > Think the key here is to use something like set-bootpath-dev in livecd's
> > > > > olpc.fth to auto detect where the olpc.fth was picked up (booted?) from.
> > > > > This is reflected in /ofw/chosen/bootpath, can some one short-cut me to
> > > > > the source in ofw?
> > > >
> > > > Not *quite* sure what you are after, but bootpath is in
> > > > ofw/core/bootparm.fth
> > >
> > > I've been playing around booting my XO with and without an external SD
> > > card. If I boot the external card, the internal on get mounted as /
> > > based on root=/dev/mmcblk0p2. While /ofw/chosen/bootpath recalls which
> > > device used as the source for the olpc.fth file.
> > Could you have a read of #9457 in case what you have discovered is fully
> > covered by that bug? http://dev.laptop.org/ticket/9457
> Yea, think that about covers it... The only thing I have not tried is to
> disable the internal mmc card. I thought there are udev rules in place
> to keep the slot naming consistent.
no, not yet.
> > > I was thinking that if we could parse bootpath, kind of like
> > > livecd-to-disk does with this...
> > >
> > > just with a different strings to tell the difference between the
> > > internal and external SD cards.
> > I'm not sure how that would work, sorry. It seems the issue is also
> > that the kernel chooses a name unpredictably. Have a look at the
> > discussion on #9457.
> I've updated http://members.shaw.ca/jvonau/pub/olpc.fth
> I have this running here, installed on both the internal and external
> mmc cards, both work as expected. Now the question is, are production XO
> going to have an internal mmc card when shipped?
certainly. it's the only internal storage.
> I have not tested this
> with the internal mmc card disabled, I really don't want to open up the
> XO. If someone else is brave enough to test that for me that would be
it may attempt to boot without an internal card, but i don't
think it will be successful because of the naming issue.
paul fox, pgf at laptop.org
More information about the olpc