Arch Linux

desertViking

Member

From: Arizona

Registered: 2005-10-30

Posts: 170

trouble upgrading to kernel 2.6.22 [SOLVED]

Hi,
It's been awhile since I updated my system.  Ran pacman -Syu today, and I'm now having difficulty booting to the new kernel.  On boot, at "loading Modules", the system is responding:

FATAL: Could not load /lib/modules/2.6.21-ARCH/modules.dep

Thereafter, several modules fail to load.
I've tried re-installing kernel26

pacman -Sf kernel26

and this seems to run successfully.  I've rebooted, and gone so far as doing a power cycle to make sure the disk cache was flushed.
I noticed a new

kconfig26.pacnew

file in the boot directory, so I renamed the old one, and moved ".pacnew" to kconfig26, then reran the installation of the kernel, and still no soap.
I'm sure that I've done something stupid here, but any advice you could offer would be most appreciated!

Last edited by desertViking (2007-08-15 22:37:11)

---

"In theory, there's no difference between theory and practice, but in practice there is."

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: trouble upgrading to kernel 2.6.22 [SOLVED]

Are you sure your bootloader is pointed at the correct kernel?  it should be /boot/vmlinuz26

desertViking

Member

From: Arizona

Registered: 2005-10-30

Posts: 170

Re: trouble upgrading to kernel 2.6.22 [SOLVED]

Thanks for replying.
I think my boot line is OK.  I haven't changed it for a long time.  It currently looks like this

title Arch Linux (2007)
root (hd0,2)
kernel /boot/vmlinuz26 root=/dev/sda3 ro vga=792
initrd /boot/kernel26.img

Was booting successfully with 2.6.21.
Looking at rc.sysinit, it appears "modprobe" fails, and I confirmed that from the command line.

Last edited by desertViking (2007-08-15 19:07:42)

---

"In theory, there's no difference between theory and practice, but in practice there is."

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: trouble upgrading to kernel 2.6.22 [SOLVED]

Well, I just found this message odd:

FATAL: Could not load /lib/modules/2.6.21-ARCH/modules.dep

That indicates to me it's still looking for modules in the 2.6.21 search path, which is why I thought you might be pointing at a custom 2.6.21 kernel or something of that sort.

Do you have /boot or /lib on a separate partitions?  Are you sure it's mounted and writable when you're updating your kernel?

desertViking

Member

From: Arizona

Registered: 2005-10-30

Posts: 170

Re: trouble upgrading to kernel 2.6.22 [SOLVED]

Again, thank you.  I understand your logic.
/lib and /boot are on the same volume.  mkinitcpio runs to successful completion, and I've checked time and date stamps to make sure it wasn't phantom.  Seems OK.
The system continues to boot successfully from the point of failure, with the exception of course that any modules being loaded (wireless adapter for example) fail to load.  The cannot be loaded by hand.  When I try, modprobe throws the same error message.  I've also tried rerunning mkinitcpio, but that doesn't seem to help. 
I'm certain that I am just not seeing the forest for the trees.  Just too close to spot my error.
Did I do the right thing by renaming kconfig26.pacnew to kconfig26?

---

"In theory, there's no difference between theory and practice, but in practice there is."

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: trouble upgrading to kernel 2.6.22 [SOLVED]

I'm 99% sure, actually, that the kconfig file is just there for your own reference; so you can see how the kernel was built.

Checking the following might help you figure out what's going on:

$ uname -a
$ ls -l /lib/modules
$ # This next one should update the modules.dep file
$ sudo depmod -ae

Last edited by Cerebral (2007-08-15 19:49:38)

desertViking

Member

From: Arizona

Registered: 2005-10-30

Posts: 170

Re: trouble upgrading to kernel 2.6.22 [SOLVED]

Hmm.  Definitely confusing.
uname -a indicates that I am booted to 2.6.21-ARCH kernel.  So, I reran mkinitcpio with, and without, the -k option, and it was definitely generating 2.6.22-ARCH.
So, in the /boot directory, I again checked the names.  Out of curiosity, I renamed kernel26.img to kernel26.img.sav, and vmlinuz to vmlinuz.sav, and, hmm, rebooted to 2.6.21.
Seems like 2.6.21 kernel is somewhere, but I'll be darned if I can figure out where it's pulling from.
The menu.lst

title Arch Linux (2007)
root (hd0,2)
kernel /boot/vmlinuz26 root=/dev/sda3 ro vga=792
initrd /boot/kernel26.img

should be referencing /sda3/boot, correct?
Edit:
Found it!  At some point long ago, I pointed /boot in fstab to the sda1.  This was where the kernels were being regenerated.
But I was booting to sda3.  This contained the old image.
I copied the images to sda3, and I was able to boot.  I've regenerated the kernel image just to make sure that everything is pointing to the proper places.
Thank you for the clues and advice.

Last edited by desertViking (2007-08-15 22:36:14)

---

"In theory, there's no difference between theory and practice, but in practice there is."

Cerebral

Forum Fellow

From: Waterloo, ON, CA

Registered: 2005-04-08

Posts: 3,108

Website

Re: trouble upgrading to kernel 2.6.22 [SOLVED]

aha, so you did have /boot mounted from a different partition.  Glad you got figured out! 

desertViking

Member

From: Arizona

Registered: 2005-10-30

Posts: 170

Re: trouble upgrading to kernel 2.6.22 [SOLVED]

aha, so you did have /boot mounted from a different partition.

Yes!  You were correct ,
Thx for sticking with me!

---

"In theory, there's no difference between theory and practice, but in practice there is."