Am Freitag, den 19.02.2010, 12:19 +0100 schrieb Michael Prokop: > What's inside your initramfs? Extract it running: > > cd /tmp ; mkdir init ; cd init > gunzip -c /boot/initrd.img-2.6.30-2-686 | \ > cpio -i -d -H newc --no-absolute-filenames > > Does lib/modules/2.6.30-2-686/modules.dep exist then? > Are you sure you're booting into the right root filesystem? > What's inside your /proc/cmdline? >
In the meantime I updated my kernel to 2.6.32-trunk but still have the same problem. Here are the answers to your questions: No, the file does not exist in the current initrd. I just had to boot twice with the same kernel/initrd, the first time I got that error, the second time it worked fine. I am sure that I boot the right root filesystem, as I only have one linux root filesystem and only one /boot filesystem on that machine. My /proc/cmdline: BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686 root=UUID=20dcd9c8-46aa-423e-9e1a-0ac010d2e7af ro quiet As I have a /boot filesystem, I don't see anything unusual in that line. What else can I do to help to get rid of that problem? -- Mit freundlichen Grüßen Felix Koop
