Help - Search - Members - Calendar
Full Version: Kernel Update For Rh9
Linuxhelp > Support > Technical Support

So i've managed to get the src for the kernel , complied it...etc

and this is how my /boot looks like


the problem is that my old kernel is the one, that is still booting up... how to fix?

and just one more question, I'v customised the kernel, removed some features that I don't need [the ones I was really sure about],...and once i've finished compiling the kernel, only this error came out : Kernel to big for boot disk[I think it meant the floppy]

Robert B
please note : that I'm booting up from a bootdisk to RH9, the disk was created with the RH9 install , so I guess it's for the old kernel, so the next question would be : how do I create a boot floppy for the new kernel?

Robert B.
If you want to update your kernel to the latest RedHat compiled kernel ... and not have to compile it your self, do this:

Because you can install more than 1 kernel on your system
, apt doesn't install the latest kernel with the default commands:

However, you can use apt to get the new kernel ... like this:

always do:

apt-get update

before you install apt...then

apt-get install kernel

Your output will look something like this:
[root@localhost root]# apt-get install kernel
Reading Package Lists... Done
Building Dependency Tree... Done
Package kernel is a virtual package provided by:
 kernel-smp#2.4.20-30.9 2.4.20-30.9
 kernel-smp#2.4.20-28.9 2.4.20-28.9
 kernel-bigmem#2.4.20-30.9 2.4.20-30.9
 kernel-bigmem#2.4.20-28.9 2.4.20-28.9
 kernel-BOOT#2.4.20-30.9 2.4.20-30.9
 kernel-BOOT#2.4.20-28.9 2.4.20-28.9
 kernel#2.4.20-30.9 2.4.20-30.9
 kernel#2.4.20-30.9 2.4.20-30.9
 kernel#2.4.20-30.9 2.4.20-30.9
 kernel#2.4.20-28.9 2.4.20-28.9
 kernel#2.4.20-28.9 2.4.20-28.9
 kernel#2.4.20-28.9 2.4.20-28.9
 kernel-smp#2.4.20-8 2.4.20-8
 kernel-bigmem#2.4.20-8 2.4.20-8
 kernel-BOOT#2.4.20-8 2.4.20-8
 kernel#2.4.20-8 2.4.20-8
 kernel#2.4.20-8 2.4.20-8
 kernel#2.4.20-8 2.4.20-8
You should explicitly select one to install.
E: Package kernel has no installation candidate

Now you need to pick the kernel you want to install from that list ....

Some notes on when to pick other than the standard kernel...

1. BOOT - never ... it is the reference kernel for a 80386 chip

2. bigmem - a PC > 4gb RAM

3. smp - any PC with more than 1 processor {or a machine with hyperthreading enabled where you want to take advantage of hyperthreading ... right now hyperthreading is available on P4 > 3 Mhz and P4 Xeon processors. Hyperthreading must be enabled in the BIOS}

4. - Special kernels compiled by Alex Thimm's apt site .... If you go here (scrool down to the blue section) ... you will see the patches in this kernel. This kernel basically has more / different patches than the standard redhat kernel. I normally don't use the kernels.
So you would pick kernel#2.4.20-30.9 for a standard single processor intel / amd machine and then enter the command:

apt-get install kernel#2.4.20-30.9

I have done some research in the last couple days and that method will automatically pick the right arch (ie, i386, i586, i686, althon, etc.) for your install...
Before you reboot, go to /boot/grub and edit the file menu.lst (or boot.grub ... they should be the same file) and set the default line to:


(to boot to the first ... new ... kernel)

After you are satisfied that the new kernel is stable (normally I wait a couple days on a production machine), remove the old kernel like this:

rpm -q kernel


rpm -e kernel-xxxx
For any kernel upgrade ... any kernel modules you manually added (Like video drivers, SCSI drivers, motherboard drivers, NTFS drivers, etc. ) must be re-done for the new kernel.
BTW, I have never used a boot floppy for redhat ... what files are on the floppy.

If I were doing it, I probably would put grub there and a chainloader entry to /boot ... but I'm not sure.

If it is grub on the boot floppy ... what does the menu.lst file say?

You probably just need to add a new entry to point to the need kernel image and the new initrd image.

[Note: I've found this great tutorial Red Hat Tuning Tutorial, discuses Kernel updates, and network tweaking, etc...]

So about the floppy

the following files are on the floppy


in the syslinux.cfg

there is a line

kernel vmlinuz [hmmm? perhaps switch this whit the vmlinuzxxxxxcustom kernel?]

oh and by the way, I've succesfully installed and updated Whitebox Linux 3.0, and was very suprised, that yam
actualy downloaded and installed the latest kernel for me, now when grub start it default to the latest kernel and my older kernel is still there [good, I think ].

By the way, if I would use grub with red hat9 as the bootloader [since I've installed no boot loader on my test machine], it would ad a new entry into grub for the new kernel to...right?

And about those errors, kernel to big to fit to floppy , should I be concerned?, or some other warning, console bla-bla-bla says something about limit, and later on about unused variables, [I've learned a bit C 3.x about 4 yrs ago, so I guess these warning are no big deal right?].

Robert B

ps.: Whitebox updated the kernel with the athlon arch, and it says : 2.4.21-9.0.1.EL on an i686 this is good no? smile.gif
oh and almost completely forgot , in this haste smile.gif

thank you for those download/update sites for yum smile.gif)


Robert B
OK ... that boot disk contains the whole kernel and loads it from floppy ... and the new kernel won't fit on floppy, SO you must do something else to boot your new kernel.

What I would recommend is installing grub to the MBR (if it is installed in /boot/grub right now) of the hard drive to boot from.

(if grub isn't installed ... apt-get install grub will do it)

If this is a dual boot machine (with windows), make sure to add this at the bottom of the file /boot/grub/menu.lst (if the windows machine is on /dev/hda1 ... ie the first partition of the primary master drive)

title Windows
       rootnoverify (hd0,0)
       chainloader +1

then go into grub:


you are at the grub prompt ... now do this (you need to know what drive your /boot resides on ... if /boot is a seperate partition, use that partiton ... if /boot is not /dev/hda2, use the right value for (hd0,1) instead of what I typed below ... hda1 is (hd0,0) ... hda2 is (hd0,1) ... hda3 is (hd0,2) ... hdb1 is (hd1,0), hdb2 is (hd1,1), hdb3 is (hd1,2), etc. )

root (hd0,1)

Now to setup the MBR...

setup (hd0)


now edit the /boot/grub/menu.lst and point to the new kernel (and new initrd line, if applicable, looks like it is not on your compiled kernel ... one is required on the redhat pre-compiled kernels).

reboot and you should be good to should still also be able to boot to the floppy and get the old kernel
You are welcome for the Whitebox sites .... yes, yum also updates the kernel ... and the setup that you have (with 2 kernels and the newest one as default) is OK
If you don't have your current info in /boot/grub/menu.lst ... because of a new install ... here is mine for a redhat 9 machine:

title Red Hat Linux (2.4.20-30.9)
       root (hd1,4)
       kernel /boot/vmlinuz-2.4.20-30.9 ro root=/dev/hdb5

If you use up2date, yum, apt-get or rpm to install a precompiled kernel, it makes an entry in the /boot/grub/menu.lst file for you ... if you compile your own kernel, you would need to add it yourself (as another entry).... like this:

title Red Hat Linux (2.4.20-28.9custom)
       root (hd1,4)
       kernel /boot/vmlinuz-2.4.20-28.9custom ro root=/dev/hdb5

Some notes ... this is on a machine with NO boot seperate partition ... if the boot partition where seperate the kernel lines would look like this:

kernel /vmlinuz-2.4.20-28.9custom ro root=/dev/hdb5

AND the root(hd1,4) would point to the /boot partition and not the root partition ... but the root=/dev/hda5 would point to the root partition ... not the boot partiton.
As a side note:

I don't normally compile my own RedHat or Debian kernels on production machines (I do compile my own kernels in Gentoo ... and sometimes on test machines for debain/redhat) ... I usually download the latest kernel from redhat/debian that contains the latest security updates and then add modules as necessary for hardware.
Thank you smile.gif

Robert B
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-2018 Invision Power Services, Inc.