If you insert the key after the machine boots, then it shouldn't have been a problem having a /boot directory. A possible explanation of the inconsistent behavior could be when in the boot process you insert the key.
-walter On Mon, Apr 28, 2008 at 3:07 PM, John Watlington <[EMAIL PROTECTED]> wrote: > > RTFM. > > It looks like most of the problem was not deleting the boot > directory on the key. Why this worked for 3 of five laptops, > but not these last two, I don't know... > > > > On Apr 28, 2008, at 3:02 PM, C. Scott Ananian wrote: > > > On Mon, Apr 28, 2008 at 2:53 PM, John Watlington <[EMAIL PROTECTED]> > > wrote: > >> When I reboot (after activating), it reports that the lease in > >> nand:\security\lease.sig is expired. > >> Then it finds valid signatures for the OS and proceeds. > > > > That's very interesting. Once you have a dev key, can you ask OFW > > what's actually in nand:\security\lease.sig? Does it look reasonable? > > It is writable? > > > > If you could also note the "mounting XYZ on /mnt options that are > > tried; the process should look like this: > > * try /dev/mmcblk0p1 (partitioned SD card) > > * /dev/mmcblk0 (unpartitioned SD card) > > * /dev/sdX for X in ['a1','a','b1','b','c1','c','b1','b','a1','a'] > > (we expect /dev/sda1 to work, so we try it again at the end in case > > the USB disk just took a while to be recognized) > > * wireless on channels 1, 6, 11, 1, 6, 11 > > > > If it doesn't make it all the way through this process, then what it > > likely happening is that it is successfully finding the lease and then > > failing to write it to NAND. So knowing how far it gets through this > > is useful. > > --scott > > > > -- > > ( http://cscott.net/ ) > > _______________________________________________ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
