Comment 30 for bug 152820

I was able to modify my sources.list and test linux-image-2.6.24-5-386. I use the nvidia driver, so it could not load the kernel module, but it worked with the nv driver. The devices mounted fine without modification.

After booting to the gutsy kernel and removing the hardy kernel, apt gave me the following:

Log started: 2008-02-01 11:19:39
(Reading database ... 177899 files and directories currently installed.)
Removing linux-image-2.6.24-5-386 ...
Running postrm hook script /sbin/update-grub.
Your /etc/kernel-img.conf needs to be updated. Read grub's NEWS.Debian[1]
file and follow its instructions.

 1. /usr/share/doc/grub/NEWS.Debian.gz

Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... found: (hd0,1)/boot/grub/splashimages/36909-soft-tux.xpm.gz

Found kernel: /boot/vmlinuz-2.6.22-14-386
Found kernel: /boot/vmlinuz-2.6.20-16-386
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
 you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
 you may need to re-run your boot loader[grub]
Log ended: 2008-02-01 11:20:10

The machine booted fine though and the grub menu was intact. I'm going to research this now.

Thanks.