Arch Linux

darkangel

Member

Registered: 2009-10-27

Posts: 2

Kernel version persists

A few weeks ago, I upgraded from 2.6.29 to 2.6.30, and when I rebooted the machine, I got some errors saying some modules (including ext3! --luckily, only /boot was ext3) are not found. When it dropped to the shell, it says 2.6.29-ARCH, and uname -a says the same thing as well (yes, I checked the file under /boot, even grepped for 2.6.29 and 2.6.30. The version string is 2.6.30-ARCH in vmlinuz26. /etc/mkinitcpio.d/kernel26.kver says ALL_kver='2.6.30-ARCH' though.). It seems the kernel was looking for the modules undeer /lib/modules/2.6.29-ARCH and not /lib/modules/2.6.30-ARCH. I reverted to 2.6.29 using a live CD and got my system running again.

Yesterday, I tried a fresh install since this weird problem might be due to a filesystem corruption. This time, with the latest live CD. I had 2.6.30 coming along with the installation which worked fine out of the box. And now I try to upgrade to 2.6.31, and same things happen again!

So, in short. How can I upgrade my kernel???

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Kernel version persists

Are you sure /boot is mounted when you upgrade?

grey

Member

From: Europe

Registered: 2007-08-23

Posts: 679

Re: Kernel version persists

Are you getting any error messages when mkinitcpio is called by pacman during kernel upgrade?

---

Good ideas do not need lots of lies told about them in order to gain public acceptance.

darkangel

Member

Registered: 2009-10-27

Posts: 2

Re: Kernel version persists

Are you sure /boot is mounted when you upgrade?

Gee, didn't I mention I already grepped the files under /boot.
Before we get another pointless "are you an idiot?" question, I have migrated from Gentoo, and have been using GNU/Linux ~10 years. I don't I think I'm missing something obvious.

Are you getting any error messages when mkinitcpio is called by pacman during kernel upgrade?

mkinitcpio and whole kernel26 installation seemed to go smooth.

And BTW, the new kernel started doing crazy stuff, such as almost-ruining my XFS partition. I had my fair share of data loss. I'm beginning to suspect a hardware problem as well.