-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-09-18 at 15:07 -0500, Moby wrote:
I verified that udev is indeed version 085-30.13.
After more investigation, it looks like the current mkinitrd (version 1.2-106.18) is the culprit. I opened the initrd the system is using for kernel 2.6.16.13-4 and also the initrd generated for kernel 2.6.16.21-0.21. I saw that the working initrd had all the lvm stuff in it, but the newer one had material for evms and not lvm. My thoughts are that the current mkinitrd (1.2-106.18) has a flaw and fails to include the appropriate lvm material. Going through the changelog of the current mkinitrd's RPM I see lots of changes mention evms and lvm. However, that still does not bring me closer to getting the latest kernel to work on this machine :(
Ufff.
Would it be possible to go with the current kernel but just back rev the mkinitrd RPM, or is that big no no?
It's a big I have no idea :-P Sorry. And... did you try running the new mkinird? Either that or keep using the old one, but running mkinird to recreate the correct ram disk image. And I think you should report this in bugzilla. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFDxQYtTMYHG2NR9URAgdGAJ9yjSuOYqewLtSTYk+UJn9vJldClQCgmLmJ sIDxQc3jjREpYpRbMot7fiM= =Pifb -----END PGP SIGNATURE-----