pea510@xxxxxx wrote: > Check the size of your "inird" file. I you hadn't updated "mkinitrd" to > the current version before installing the new "2.1.19" kernel, chances > are high that it is corrupted. It's size then is much smaller than of > that created for the older kernel. > You might try to boot with the old kernel, update "mkinitrd" and > reinstall the new kernel package. In my case this procedure was successful. Hi, I had the same problem. When I first booted the 2.6.19-1.2877.fc7 kernel I got a kernel panic it couldn't start init. I booted back to the previous kernel and my initrd was only 336k, I updated it and now it's 3.6M. I checked my logs to see how yum updated my kernel and mkinitrd: Dec 12 17:01:00 localhost Updated: mkinitrd.i386 6.0.3-1 Dec 16 11:45:43 localhost Updated: mkinitrd.i386 6.0.5-1 Dec 16 11:48:03 localhost Installed: kernel.i686 2.6.19-1.2877.fc7 So I had the new mkinitrd before my kernel was updated. If necessary I can upload the initrd created at the updated and the one I created. What will happen the next time grub needs to be installed? Will the grup device map be updated to the new device naming? gr, Bart -- Bart Vanbrabant <bart.vanbrabant@xxxxxxxxxxxx> PGP fingerprint: 093C BB84 17F6 3AA6 6D5E FC4F 84E1 FED1 E426 64D1
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
