On Tue, 13 Sep 2005, Jens Radloff wrote:
So I did an upgrade from udev-030 to udev-58. I did that upgrade
according to the steps at
http://www.linuxfromscratch.org/lfs/view/development/chapter06/udev.html
I _hope_ 058 is a typo - we're on udev-068 now.
After I have done the udev-upgrade, when I try to load the 2.6.13
kernel, the kernel loading sequence does not stop anymore at the point
of populating the /dev directory, i.e. the whole kernel loading sequence
is done to its end. But some error messages are displayed:
(1) An error message which I am nearly unable to read because the kernel
boot is too fast when it is displayed. I think it is an message which
says that /dev cannnot be populated. It is displayed directly after
init is started ("Init: version 2.85 booting"). I could not find this
error message in dmesg, nor in the log files in /var/log.
If that's what it said, all subsequent errors are kind of irrelevant
(no device nodes to mount filesystems on).
(2) Some seconds later, this message is displayed: "Ext-fs: mounted file
system with ordered data mode: [Failed]"
(3) Some seconds later, this message is displayed: "RNTLINK answers:
Files exists [Failed]"
Actually, that's common and doesn't seem to cause any problems.
(4) Additionaly, Alsa cannot be loaded: "Starting ALSA ... [Failed]"
Again, perhaps a lack of device nodes.
When I then load the older kernel (2.6.11.7) again, I need to load this
older kernel twice to get the older kernel loaded without error
messages - the first time I boot into this kernel, I get the same error
message as (2), (3), (4) and possibly (1).
That makes me suspect problems with your udev upgrade. If 058 wasn't a
typo, try 068.
I am quite sure that all settings in the kernel config file of the newer
kernel 2.6.13. are correct. When the newer kernel has been loaded,
a) the following (pseudo) file systems are mounted: proc, sysfs, devpts,
shm, usbfs and ramfs,
From your error messages, I thought you hadn't been able to log in.
I was going to suggest init=/bin/bash then manually mounting /dev and
running udevstart. If you've got a usable system, you can work out
which filesystem(s) didn't get mounted (or, possibly, something was
mounted r/o, or as ext2 instead of ext3).
b) the /dev directory contains 659 files (which i found out using
ls /dev | wc -l )
That sounds reasonably full (653 on this box).
Let me add that I have compiled the real time modules (LSM) into the
newer, but also into the older kernel. The real time modules need a
kernel config file with Selinux enabled (which I enabled).
Any ideas to solve all this would be great.
Work out what is going on with the ext fs message, and check that you
have the expected device nodes for the disk partitions you expect to
see. If it makes no sense, tell us which disk devices you expect to
see, which actually exist, and what happened in the mount to give the
error message.
For alsa, try running the bootscript manually, and note the error
messages - I get messages with newer kernels, usually it means the sound
hasn't been restored and everything reverts to the default of muted.
This has been covered on blfs-support recently, I think it's just a
question of setting the volumes and unmuting, then running a command to
save the state.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
