Mon, 23 Jul 2007 17:31:01 -0400, Jim Cornette wrote: > Antti J. Huhtala wrote: > > Jim Cornette wrote: > > > >> You might try uninstalling the kernel that fails to boot and then > >> re-installing it. On rare occasions I have had kernels install poorly > >> but would install correctly on the second install. I believe my problem > >> was due to mkinitrd being updated after the kernel in the past. When I > >> erased the failed kernel and then installed it again, everything was n > >> place for the kernel to install correctly. > >> > > Thank you, Jim > > > > I tried that but unfortunately it didn't help. I only removed the kernel > > proper (using pirut), not kernel-devel nor kernel-headers packages > > (assuming they have little relevance to the problem at hand), and dl'd > > the 2.6.22.1-27 kernel again. When installed and rebooted, the problems > > persist just like before. > > Maybe it's my hardware but it has worked with every kernel since FC4 as > > I told earlier. Guess I'll stick to 2.6.21-1.3228.fc7 kernel for now. > > I think the main packages for kernel are nash, mkinitrd and the grub > related packages. I have no idea if the kernel-headers could cause the > problem. The devel package would not matter for a booting kernel. > Well, my nash and mkinitrd are the same versions (6.0.9-7.1) used in booting the 2.6.21.1-3228.fc7 kernel and with it they work just fine. grub hasn't changed either, obviously there was no need to update it for the new kernel. Listing all the packages with pirut shows only one kernel-headers package, and that is the 2.6.22.1-27.fc7.x86_64 (new kernel) version. I have it installed but it doesn't seem to mess up the booting of the 'old' 2.6.21.1-3228 kernel. *If* there was an earlier version of kernel-headers replaced by the update, booting the older kernel (3228) doesn't seem to suffer any ill effects. Therefore I doubt my problem has anything to do with kernel-headers. > There i another posting on the list where a kernel panic was > encountered. I believe he posted messages containing uncompressing the > initrd and calls to nash which is a kernel environment shell if I understand correctly. > Yes, I read his post and replies to it but to me it looks like his problem is slightly different and it appears later in the booting process. There is something in common, though: how volumes or Volume Groups are handled (by nash or kernel? I'm not sure but nash *just works* with the older kernel). > Oh well, it was worth a try. > Thank you for putting some effort into this, Jim. I appreciate it. > Jim > Antti
