Re: [gNewSense-users] I am unable to boot from vmlinuz-2.6.33.3-libre-lemote since upgrade

[Christophe Jarry]

> > When I boot from 2.6.33.3, after login, /dev does contain no "hd*" nor
> > "sd*"... But when "/dev/hda1" was being checked under 2.6.33.3 by "fsck from
> > util-linux-ng 2.17.2" (after "* Checking root file system..." message), it
> > was named "/lib/init/rw/rootdev" instead of "/dev/hda1".    
> 
> May it be just the name in some initrd ?

I don't know.

> If you just call mount, without arguments, after login, it should tell 
> you the name of each device and itsmountpoint in the filesystem.

    sudo mount /dev/hda2 /media/tmp

gives me:

    mount: you must specify the filesystem type

> > `dmesg | grep EXT3` after login under 2.6.33.3 gives me this:
> > 
> >     [   10.028000] EXT3-fs (hda1): mounted filesystem with writeback data
> > mode [  150.992000] EXT3-fs (hda1): using internal journal
> 
> And nothing about hda2 (/home) ? 

No...

> > > Might it be some module missing in one of the two kernels ?
> > 
> > How do I know if it is the case?
> 
> you could 
> 
> diff /boot/config-2.6.33.3-libre-lemote /boot/config-2.6.37-libre-lemote

The diff is just to big for me, and I don't think the problem comes from the
kernel itself, otherwise I would not be the only one with this problem I think.
Just in case, I attach the diff to this mail.

Christophe

boot-config-2.6.33.3-2.6.37.diff
Description: Text Data