Arch Linux

paulfxh

Member

Registered: 2008-03-11

Posts: 33

[Solved]Big problem with version mismatch: 2.6.22-ARCH vs. 2.6.24-ARCH

I just started with Arch Linux yesterday but my introduction is a little troubled.
My main problem seems to arise from arch Modprobe being unable to load /lib/modules/2.6.22-ARCH/modules.dep

Now the reason it cannot be loaded is that it just isn't there. What IS there is /lib/modules 2.6.24-ARCH/modules.dep

This inconvenient state of affairs seems to have arisen after I did a pacman -Syu update as part of this guide http://wiki.archlinux.org/index.php/Beg … cessary.29 that I'm following very closely.
Nevertheless, despite the update, uname -r still gives 2.6.22-ARCH so I'm at a loss to understand why the /lib/modules directory has dumped its 2.6.22-ARCH folder.

Note that since I first noticed this problem yesterday, I have completely re-installed Arch Linux twice. Additionally, suspecting that the mirrors I chose may have varying package versions, I used very different mirrors than those I used yesterday.

But still getting the same problem.

One consequence of this is that ArchLinux is essentially unusable as when I boot I get a message complaining about the inability to load /lib/modules/2.6.22-ARCH/modprobe,dep which then prevents eth0 activating.

Please help me get out of this problem

Last edited by paulfxh (2008-03-13 00:07:44)

Misfit138

Misfit Emeritus

From: USA

Registered: 2006-11-27

Posts: 4,189

Re: [Solved]Big problem with version mismatch: 2.6.22-ARCH vs. 2.6.24-ARCH

So your lib/modules have upgraded to 2.6.24, but your kernel is still at 2.6.22..
Did you reboot immediately after the kernel upgrade from pacman -Syu?
Did the pacman output indicate it was upgrading the kernel and building the initrd after -Syu?

---

Amiga 1000 restomod
IBM PCjr restomod
C=64 restodmod
Sauengard

paulfxh

Member

Registered: 2008-03-11

Posts: 33

Re: [Solved]Big problem with version mismatch: 2.6.22-ARCH vs. 2.6.24-ARCH

So your lib/modules have upgraded to 2.6.24, but your kernel is still at 2.6.22..
Did you reboot immediately after the kernel upgrade from pacman -Syu?

I'm afraid not, But, I'll do it the next time (although the Beginners Guide doesn't say to reboot)
However, as I have no eth0, and things seem messed up, looks like I'm gona have to re-install ArchLinux (for the fourth time) just to get to the point where I can run pacman -Syu.
Is there anyway for me to recover my system without re-installing?

Did the pacman output indicate it was upgrading the kernel and building the initrd after -Syu?

To be honest, there were so many things happening (complete system upgrade) that I didn't note them all. Obviously, it must be logged somewhere but I'm not sure where to look.

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: [Solved]Big problem with version mismatch: 2.6.22-ARCH vs. 2.6.24-ARCH

What Misfit meant to say: REBOOT NOW

You upgraded the kernel package, so the files for the 2.6.24 kernel are now installed. However, the 2.6.22 kernel is still running, so all you need is a reboot to sync them up again. Reinstalling is definitely not necessary.

paulfxh

Member

Registered: 2008-03-11

Posts: 33

Re: [Solved]Big problem with version mismatch: 2.6.22-ARCH vs. 2.6.24-ARCH

What Misfit meant to say: REBOOT NOW

You upgraded the kernel package, so the files for the 2.6.24 kernel are now installed. However, the 2.6.22 kernel is still running, so all you need is a reboot to sync them up again. Reinstalling is definitely not necessary.

Yes, thank you. But I have rebooted three times now. Still, uname-r gives me 2.6.22-ARCH
So, I'm very puzzled.
If I could get an internet connection back without reinstalling, perhaps I could try the pacman -Syu again.
But, eth0 is not seen and the only interface I have is lo.

paulfxh

Member

Registered: 2008-03-11

Posts: 33

Re: [Solved]Big problem with version mismatch: 2.6.22-ARCH vs. 2.6.24-ARCH

Sorry, but I was making a silly error but everything is fine now.
My system is a bit complicated in that ArchLinux is installed on an external usb HDD. I'm booting it with Grub which is in the MBR of my internal HDD. To get this to work I must have both vmlinuz26 and kernel26.img stored in the /boot directory on my internal HDD.
So, when I did all of this updating, I had forgotten to manually update the kernel and vmlinux files in the internall HDD /boot directory.
But, things are looking good now apart from feeling silly:)
Thanks for your help