tick boot shows: a couple of pages of modprobe:chdir/lib/modules/;no such file or directory then: no root device found boot has failed sleeping forever
ps successfully reflashed another xo1 it doesnt have any bad blocks in the blue area either pps would add a screen photo but the journal is mangling attachment file names, but thats another discussion ;) > On Sat, Jun 18, 2011 at 12:49:54PM +1000, [email protected] wrote: > > Successfully installed os22 onto another xo1 > > The first xo does have a lot of bad memory blocks but installs other os ok > > > > I hypothesise that this dual file system (.onu and .uim) build will > > not tolerate a bad block in the initial (blue) part of the os > > I agree, something like that. Most XO-1's work fine, some do not. I > think we need to see what the kernel says on the affected XO-1, so > please hold down the tick key and capture what you can. I don't think > we've caught what we need yet. > > -- > James Cameron > http://quozl.linux.org.au/ > _______________________________________________ > Testing mailing list > [email protected] > http://lists.laptop.org/listinfo/testing > > _____________________________________________________ > This mail has been virus scanned by Australia On Line > see http://www.australiaonline.net.au/mailscanning _______________________________________________ Testing mailing list [email protected] http://lists.laptop.org/listinfo/testing
