bye,
Giovanni.
The upgrade included kernel2.6.4, so modprobe should be looking for /lib/modules/2.6.4/modules.dep, correct? How do I make it do that? Does this mean that something's gone wrong with my sysupgrade?
The upgrade may have included kernel 2.6.4, but if you have not rebooted you are not currently running kernel 2.6.4 you are still at 2.6.3. Since modprobe uses your running kernel version (uname -r) it is going to continue looking in /lib/modules/2.6.3. If you really don't want to reboot you should be able to do this:
# depmod -v 2.6.4
# modprobe --set-version 2.6.4 [i]module[/i]
If I were you, I would just simply reboot. A new kernel is a pretty major change and it would just be easier to do that. My guess is even with the steps above you will get some symbol errors and the modules may not load.
]]>Bug or feature?
It occured to me as I was writing the OP that perhaps a reboot would take care of the problem, but I figured I'd post anyway because I'm curious about the very thing you mentioned. A reboot did fix the problem. Is it a bug? Is it a limitation in Arch's setup that hasn't been overcome? Is it simply a necessity always, whenever the kernel gets upgraded?
I was surprised, having been irritated half-to-death by the Linux zealots on USENET who claim they 'never need to reboot.' If it's an on-going requirement of any sysupgrade that brings along a kernel upgrade, then I hope some kind of notification scheme will be incorporated into pacman -- something like "you need to reboot" (ooo, echoes of Windows again ), akin to the way that pacman notifiies you that it should be upgraded first when there's a new version of it available. OTOH, if it's just a bug, no biggie. But I am curious about whether this is something that affects everyone, or just certain set-ups.
]]># modprobe snd-intel8x0
FATAL: Could not load /lib/modules/2.6.3/modules.dep: No such file or directory
The upgrade included kernel2.6.4, so modprobe should be looking for /lib/modules/2.6.4/modules.dep, correct? How do I make it do that? Does this mean that something's gone wrong with my sysupgrade?
]]>