Mailinglist Archive: opensuse (1185 mails)

< Previous Next >
[opensuse] Help! - Can't boot kernel because no depmod -a --> can't depmod -a because I can't boot kernel (chicken or the egg??)
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
  • Date: Sat, 08 May 2010 17:20:07 -0500
  • Message-id: <4BE5E397.2070306@xxxxxxxxxxxxxxxxxx>
listmates,

I am having difficulty installing a couple of kernels on 11.0 i586. I
have
installed them on my x86_64 box without any problems. I've been fighting it for
a few hours and now need to cry for help... so... Help Please!

I have installed:

kernel-pae-2.6.32.11-1.1.i586.rpm
kernel-pae-base-2.6.32.11-1.1.i586.rpm
kernel-pae-devel-2.6.32.11-1.1.i586.rpm
kernel-source-2.6.32.11-1.1.noarch.rpm

From:

http://download.opensuse.org/repositories/home:/hennichodernich:/backport-stable-kernel-new/openSUSE_11.0/i586/

kernel-pae-2.6.31.12-2.1.i586.rpm is also available from

http://download.opensuse.org/repositories/home:/hennichodernich:/backport-stable-kernel/openSUSE_11.0/i586/

I did the same thing on my x86_64 box and the kernel booted just fine.
(FYI
both kernels work very well on 11.0, so you have a good upgrade path to 2.6.31
or 2.6.32 available)

On boot the i586 system goes through the grub menu and I select the
kernel to
boot, and everything looks normal until it goes to mount the root partition. It
then give the error similar to:

waiting on mandatory device:
/dev/disk/by-id/ata-Hitachi_HTS541616J9AT00_SB044DCJEJS1BH-part2...................

Then it asks to try the fallback device:

/dev/disk/by-id/scsi-SATA_Hitachi_HTS5416_SB044DCJEJS1BH-part2

(new kernel uses the 'ata-Hitachi-blahblah' 2.6.25.20-0.7 uses
'scsi-SATA_Hitachi-blahblah')

The problem is that apparently there are no modules compiled into the
initrd so
it can't mount the ext3 partitions. I know it is a modules issue, because it
couldn't even mount my usb-stick, giving the error: unknown filesystem type
'vfat'.

To me it seems like a 'chicken and the egg problem'. You need the
modules.dep
file from the /lib/modules/<newkernel>, but you can't create it with depmod -a
until you boot the kernel. (I know this is done all the time, but I can deduce
where in the process this takes place) If you wait until you are ready to try
and boot the kernel -> your hosed with this problem.

This should be a simple fix, but the light bulb upstairs hasn't blinked
on.
What's the trick and what do I need to do to fix it? I booted the installed OS
from the suse install DVD and reinstalled 2.6.25.20-0.7, so I now have all 3
kernels installed. After reinstall, 2.6.25.20-0.7 boot just fine so all the
disk/by-id information in grub/device.map and menu.lst and fstab is fine.

What say the experts?

--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups