I'm on 3.5.4-1-ARCH, then I upgrade to linux-3.5.6-1 and reboot. The result is a message that cant load "autofs4" module. And a "uname -r" says me: 3.5.4-1-ARCH instead of 3.5.6!!
I've tried to run depmod after the upgrade with de same result.
Last edited by siot (2012-10-09 20:11:23)
It sounds as if the new kernel did not find its way to your boot partition. This could have been because the boot partition was not mounted when you did the upgrade (in which case the file is in the /boot mount point of your root partition) or that you are not booting from the partition you are expecting (Do you, per chance, have two boot partitions?)
Regardless, boot from an install media and fix it from the command line. if the files are in /boot of the root partition rather then one the boot partition, mount both volumes and just move the files. If there are multiple boot partitions, move the files to the correct partition. Once you reboot, fix the /etc/fstab to point to the correct boot partition.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence. You must not work with the public much. -- Trilby
How to Ask Questions the Smart Way
You make me think, I don't have a /boot partition but I've discovered that my raid1 was degraded and one of the two devices removed. I don't know why.
Raid1 -> Lvm -> / & /home
Actually I'm resyncing...
The problem was on my raid1.