You are not logged in.
Hello all,
I've upgraded my machine from 2.6.31 to 2.6.32, making sure that kernel26-headers was installed as well.
After rebooting into either the stock or fallback kernel images, 2.6.31 is what boots. The quandary here is that all the 2.6.31 kernel modules have (rightly) been deleted in the upgrading process, leaving my machine without network or LVM support.
I tried manually running mkinitcpio in various modes as described in the Wiki. It reports building a 2.6.32 image, yet 2.6.31 is what always boots up. The mkinitcpio config files all appear to be normal.
For reference, here's the output of "uname -a" on the Fallback image:
Linux trantor 2.6.31-ARCH #1 SMP PREEMPT Tue Oct 13 11:33:39 CEST 2009 x86_64 Pentium(R) Dual-Core CPU E5300 @ 2.60GHz GenuineIntel GNU/Linux
This is quite a quandary, and I've pretty much run out of ideas.
pacman -Q kernel26:
kernel26 2.6.32.3-1
pacman -Q kernel26-headers:
kernel26-headers 2.6.32.3-1
I would greatly appreciate any help offered. Thanks!
Last edited by alingo (2010-01-12 06:20:10)
Offline
Check the configuration of your bootloader (probably /boot/grub/menu.lst). It should point to vmlinuz26, as installed by the kernel26 package.
Offline
Check the configuration of your bootloader (probably /boot/grub/menu.lst). It should point to vmlinuz26, as installed by the kernel26 package.
I looked and GRUB points to vmlinuz26 as it should.
Offline
Another possibility which comes to mind is the kernel image is not being written to the expected partition. If you have used / or are using a separate boot partition, ensure that everything is mounted correctly, reinstall kernel26 if required, and re-run grub-install.
If you don't have any luck, please post /boot/grub/menu.lst and the output of 'mount'.
Offline
Another possibility which comes to mind is the kernel image is not being written to the expected partition. If you have used / or are using a separate boot partition, ensure that everything is mounted correctly, reinstall kernel26 if required, and re-run grub-install.
Thanks for the help, but you were a few seconds too late! I just realized the correct solution and fixed it.
Turns out when I installed the machine, I created - and used - a separate /boot partition. I had forgotten about this. Somehow, I either neglected to add it to mount at /boot in /etc/fstab, or I deleted it. While it was not mounted, GRUB was set to use it. This "broken" setup managed to work fine until the minor version number changed and the kernel modules were no longer compatible.
The first hint that there was a mysterious /boot partition was that I, on a whim, deleted the contents of /boot -- and the machine still booted! Once I found the "lost" /boot partition, it was an easy enough fix: Add it to fstab, mount it, and reinstall the kernel packages.
Thanks for helping me! If not for me posting this and awaiting replies, I would not have keep digging away at the mystery with such fervor.
Offline