I've just installed MD 8.2, formatting all partitions. When it boots up, at and the console it tells me kernel is 2.4.8-26. The kernel I have installed in /boot is 2.4.18-6, and the modules to be loaded from /lib/modules are in 2.4.18-6.
Due to the mismatch (I'm assuming) all modules that attempt to be loaded at boot time fail. I've edited lilo.conf and it all points to the newer kernel (the old one was from 8.1 install). I ran /sbin/lilo as root to make sure the effect of the editing worked, but when I boot, there are no changes and the old kernel is booted??
Can someone give me some help on this one?
Thanks.

Could you write what have you changed? It looks there's something left, because it's lilo.conf when you specify which kernels you can load.

I can make changes in here and they are just ignored when I reboot and see the lilo menu. For example, if I change the lable of linux to linux24186, it will still simply show up as linux.
vmlinuz and initrd are symbolic links to the 2.4.18-6 file.

boot=/dev/hda5
map=/boot/map
install=/boot/boot.b
vga=normal
default=linux
keytable=/boot/uk.klt
lba32
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label=linux
root=/dev/hda6
initrd=/boot/initrd.img
append="quiet devfs=mount hdc=ide-scsi"
vga=788
read-only
image=/boot/vmlinuz
label=linux-nonfb
root=/dev/hda6
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi"
read-only
image=/boot/vmlinuz
label=failsafe
root=/dev/hda6
initrd=/boot/initrd.img
append="failsafe devfs=nomount hdc=ide-scsi"
read-only
other=/dev/hda1
label=winXP
table=/dev/hda
other=/dev/fd0
label=floppy
unsafe

After making changes type
lilo
After reboot all changes will be visible.

Yes, I did all that, the entries are listed in the console window, but when I actually reboot, the changes aren't there.
It seems as though LILO is just not picking up any changes I make.

Looking at your lilo.conf, it appears that no matter which linux selection you choose on boot, you're loading the image /boot/vmlinuz. The question I have is who is vmlinuz symlinked to in /boot? -mk

The only kernel that existed was the 2.4.18-6. Still, it was not doing this.
Pretty much trashed my laptop, I now no longer have XP installed and won't unless I can buy a CD since they don't give out bootable CD's when you buy OEM. Spent the whole of today trying to get something back on here, so now it's 100% linux. I don't know if that's totally the best thing, but until I get my win2k cd from Australia, it will have to do.
Probably would be happy with this, if the sound would work without hassles and it was easy to play videos. I was able to watch videos using xine when logged in as root, no sound however. I can't imagine the sound problems will be fixed with a different version though. Pretty yanked, so will give it a rest for the moment, I'm sure I read something about AC97 being made workable, will see.