This is the weirdest thing...I just upgraded from R5A16 to R5A30.1, and when the system rebooted it dumped me to a command prompt. Finding the system badly broken, I set out to discover why. Wondering why NO modules loaded, I checked uname and its running kernel 2.6.11. However a 2.6.13 image is what appears to be in /boot. I also checked /etc/lilo.conf and it appears to be defaulting to the 2.6.13 image in /boot. There doesn't appear to be an entry in lilo.conf for 2.6.11. There are no 2.6.11 modules, which explains why the box is so broken. I'm surprised it works at all.

For the life of me I can't figure out where 2.6.11 is coming from unless the kernel image is screwed up. dpkg reports that kernel-image-2.6.13.2-chw-3 is installed. I checked the md5 of the R5A30.1 iso just now, and it checks out.

I would post output from the above commands, but I have no network connectivity to the box, so I have no way of getting the output.

Has anyone else had this problem?

Btw, I searched for "R5A30 kernel" in the forums and didn't turn up anything useful.

Bad burn?

_________________
cesman

When the source is open, the possibilities are endless!

haven't had that problem or heard of it, but sounds like maybe the boot sector didn't get upgraded. try running lilo -v and rebooting.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

I'll try both of those suggestions. For the time being I've restored R5A16 from an image (makes for quick egress in case of problems!). I'll burn the disc again and try reinstalling tomorrow.

I'm not that familiar with how lilo works, but doesn't it read lilo.conf out of /etc on hda1? So even if it didn't get updated in the mbr, lilo.conf got updated, and the kernel image got updated. Or are the settings in lilo.conf somehow cached in the mbr?

My only frame of reference is with grub, and changes to /boot/grub/menu.lst take effect with no further action.

And if lilo works that way, there isn't a 2.6.11 kernel image in /boot, so where could it be coming from?

Like I said, this is weird. I wish I could post command output and configs, because I would never believe had I not seen it with my own eyes.

The only other thing that I can think of that I didn't mention is that in addition to hda, I have an hdc with one fat32 partition, containing a couple of mbr images and a few partition images from various systems. The cd-rom is on hdd. I doubt this is relevant.

Anyway I'll post what happens next, as it happens.

Thanks for the advice.

lilo does not read the configuration file when it is booted. The configuration file tells the lilo command how to write the boot record. running "lilo -v" like suggested will update the boot record based of the configuration file in /etc. So, to answer your question: yes, the settings are cached in the mbr. every time you install a new kernel with a file path different than the last you will need to update the mbr and that is what the "lilo" command does (-v is for verbose so you can see what is happening).

_________________
1.3GHz Athlon XP 2200+ CPU, Elitegroup KT600-A Motherboard, Hitachi 300gig IDE HDD, 16x DVD-ROM, 512meg RAM, KnoppMyth R5E50, PVR-350, Plextor PX-740UF DVD�RW (DL) burner