grub-mkconfig picks the wrong kernel.

[rew]

Binary package hint: grub-common

I have separate root-partitions for trying out if I really want to upgrade or not. But I have a shared /boot partition to allow me to tell grub to boot the old or the new install.

Currently "old" is jaunty, ia32. "new" is natty x86_64.

Somehow I managed to get a 32-bit vmlinuz-2.6.38-8-pae kernel in there. Anyway, according to the config-making utility (which seems to be grub-mkconfig) overrides the x86_64 kernel vmlinuz-2.6.38-8 . So I wasn't able to boot my fancy new x86_64 kernel, and using the 32-bit kernel results in a messy hang (the kernel will use a 64-bit insmod executable to try to load the binfmt handler for the first 64-bit binary (I'm guessing /sbin/init ?)

Workaround: I renamed the vmlinuz...-pae kernel to one version less, and then it lists the 64-bit kernel at the top.

[Marcus Tomlinson (marcustomlinson)]

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

[rew (r-e-wolff)]

I don't remember writing this 9 years ago. If I run into this again I'll probably open a new request. Go ahead and close it...

[Marcus Tomlinson (marcustomlinson)]

Thanks for the update rew. Sorry you were left hanging for so long.

[rew (r-e-wolff)]

Ah, Marcus. I maintain a package myself. Somtimes you hear "that bug has been present for years and hasn't been fixed" while it is an easy fix, but you didn't know about it. Nobody reported it.

So I try to report things and thereby make things better for everybody. And hopefully I won't run into it "years later" myself. So, something I've wanted in tcsh, I've reported that and now the maintainer has included my suggestions. So maybe buntu 2022 will have the new version of tcsh and FINALLY I can easily include my tcsh startup files in my systems!