Help - Search - Members - Calendar
Full Version: Kernel Upgrade Kicking Newb's Ass
Linuxhelp > Support > Technical Support
Gersen
howdy all,

Situation: I'm trying to upgrade a RedHat 9 box's kernel from 2.4.20-8 to 2.6.11.7. Let me start out with a request that no one suggest I switch to a different distribution. Thanks!

I went through a few kernel upgrade articles, read the CHANGES document in the kernel source, and added/upgraded the modules suggested.

I followed the procedures to:

- extract my kernel source to /usr/src/linux-2.6.11.7

- make mrproper

- coped my config file to /usr/src/linux-2.6.11.7

- make oldconfig

- make menuconfig

- make dep (it responded that it wasn't necessary)

- make bzImage

- make modules

- make modules_install

- copied bzImage to /boot and renamed it to vmlinuz-2.6.11.7

- changed the symbolic link vmlinuz to point to vmlinuz-2.6.11.7

- copied System.map from my source directory to /boot/System.map-2.66.11.7

- changed the symbolic link System.map to point to System.map-2.66.11.7

- ran mkinitrd initrd-2.6.11.7 2.6.11.7

- edited /etc/lilo.conf and added a new section, copying the syntax from the existing section and changing the references to the kernel and initrd files.

- ran lilo which happily reported adding WinXP, RedHat9, and NewKernel

- REBOOT!

- chose "NewKernel" from my list of choices.

At which point my box booted straight into the old kernel. Merde!

Ran thru all my changes to double check for syntax and spellnig erorrss. Nope, everything's correct.

Look in /boot to discover my symlinks to System.map had been changed back to point at the old System.map. I changed it back to point to the 2.6.11.7 map and did ls -l to check that it was pointing to the new map file. Yep, it is! So once again it's time to...

REBOOT! and choose NewKernel.

Same result. Boots back into the old kernel... Checked in /boot again and, sure enough, my System.map symlink had again been hijacked.

I found one thing I think my be contributing to my problem: the module-info symlink, which is pointing to module-info.2.4.20-8 and I have no newer module-info file to replace it with. (yes, that sentence ends in a proposition!) If there should be a newer module-info file somewhere to which the symlink should point, please post that information!

hmm... Since it keeps going back to my old kernel, what would happen if I take the old kernel options out of lilo.conf and try again? My menu offered me NewKernel and WinXP. Upon choosing NewKernel, the boot process started and died quickly in a kernel panic with the message:

VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00

And it was this point that I turned to that most knowledgable of all sources, the Internet. Apparently the terms involved in my problems are generic and ubiquitous enough that I can't sort out a solution with Google, talented with it though I may be...

My current lilo.conf:

prompt
timeout=50
default=WinXP
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32

image=/boot/vmlinuz-2.4.20-8
label=RedHat9
initrd=/boot/initrd-2.4.20-8.img
read-only
append="hdd=ide-scsi root=LABEL=/"

image=/boot/vmlinuz-2.6.11.7
label=NewKernel
initrd=/boot/initrd-2.6.11.7.img
read-only
append="hdd=ide-scsi root=LABEL=/"

other=/dev/hda1
optional
label=WinXP


Lil help?


Gersen
indytech at att dot net
Termina
You're in luck, I've found some information regarding how to do this for RedHat.

http://www.linuxgazette.com/node/9060

A few things you might want to check there, it seems that you need to do some things diffrently in order for this to work. Very well written guide. smile.gif
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2017 Invision Power Services, Inc.