Ok Bill, thanks for that, but.... I'm getting the memory error message when running lilo -v, so can I assume that it checks to see how much memory is/will be used by the new kernel.. Also I installed via and RPM if that makes any difference..
I am considering just going straight for the 2.4 kernel, maybe that would be a bit less painful?
Simon ----- Original Message ----- From: wbh W.B.Hill@uea.ac.uk To: Simon Parkes simon.parkes@ukonline.co.uk Sent: Monday, January 29, 2001 2:09 PM Subject: Re: [Alug] RH Kernel Upgrade problems...
OK, my guesses. When an x86 PC boots, the BIOS doesn't leave it in protected mode (in order for DOS to work, don'tcha love it!) So only the first Meg of memory is available. The linux kernel's gotta fit into this, before it can switch from real mode. So, the kernel image is too big.
Added linux > Boot image: /boot/vmlinux-2.2.16-3 Kernel /boot/vmlinux-2.2.16-3 is too big <----- what have I done
wrong
##### Here's my lilo.conf ######
<SNIP>
image=/boot/vmlinuz-2.2.14-5.0
This is a compressed image, so seems to have worked.
label=linux initrd=/boot/initrd-2.2.14-5.0.img read-only root=/dev/sda7image=/boot/vmlinux-2.2.16-3
This isn't, and is apparently too big.
label=linux16 initrd=/boot/initrd-2.2.16-3.img read-only root=/dev/sda7So, recompile that kernel image with less in/more as modules/ using "make bzImage" to get better compression.
TTFN, Bill
-
Simon Parkes