modprobe failures after 8.2 install
I've just moved from a fully-functional 8.1 to 8.2 (clean install) and am now experiencing some module-related weirdness. At boot time, modprobe issues numerous errors of the form modprobe: Can't open dependencies file /lib/module/2.4.20-4GB/modules.dep (No such file or directory) leading to inaccessible soundcard, inability to start up PPP, failure to detect USB printer, etc. Looking in /lib/modules, I see a directory 2.4.20-4GB-athlon, rather than the 2.4.20-4GB that modprobe is clearly expecting. Anyone else experienced anything like this? Can anyone suggest a fix? I've tried reinstalling with acpi=off, in response to a suggestion from SuSE support, but the same problem occurs. Nick
On Fri, 2003-05-02 at 22:31, nick@runner.u-net.com wrote:
I've just moved from a fully-functional 8.1 to 8.2 (clean install) and am now experiencing some module-related weirdness. At boot time, modprobe issues numerous errors of the form
modprobe: Can't open dependencies file /lib/module/2.4.20-4GB/modules.dep (No such file or directory)
Once the system is booted, log in as root and run "depmod -a"
Anyone else experienced anything like this? Can anyone suggest a fix? I've tried reinstalling with acpi=off, in response to a suggestion from SuSE support,
hm
On Friday 02 May 2003 22:31, nick@runner.u-net.com wrote:
modprobe: Can't open dependencies file /lib/module/2.4.20-4GB/modules.dep (No such file or directory)
leading to inaccessible soundcard, inability to start up PPP, failure to detect USB printer, etc.
Looking in /lib/modules, I see a directory 2.4.20-4GB-athlon, rather than the 2.4.20-4GB that modprobe is clearly expecting.
try cp vmlinuz.version.h /usr/src/linux/include/linux/version.h
I've just moved from a fully-functional 8.1 to 8.2 (clean install) and am now experiencing some module-related weirdness. At boot time, modprobe issues numerous errors of the form
modprobe: Can't open dependencies file /lib/module/2.4.20-4GB/modules.dep (No such file or directory)
Once the system is booted, log in as root and run "depmod -a"
Tried this. Had to edit /etc/modules.conf so set paths to point to the actual directory, /lib/modules/2.4.20-4GB-athlon. Ended up with a different error (line breaks are my own): /lib/modules/2.4.20-4GB-athlon/kernel/drivers/scsi/ide-scsi.o: kernel-module version mismatch /lib/modules/2.4.20-4GB-athlon/kernel/drivers/scsi/ide-scsi.o was compiled for kernel version 2.4.20-4GB-athlon while this kernel is version 2.4.20-4GB. I can't work around this by renaming the modules dir to 2.4.20-4GB; the same error occurs. So it seems there's a clear discrepancy between the installed kernel and the installed modules. Incidentally, uname reports 2.4.20-4GB, and my system genuinely does have an Athlon CPU. Any suggestions for ways to proceed that don't involve recompiling kernel or modules? I'll do this if I have to, but surely shouldn't need to, given that there were no such problems when installing 8.1 on the same hardware. Nick
On Sunday 04 May 2003 13:06, nick@runner.u-net.com wrote:
Any suggestions for ways to proceed that don't involve recompiling kernel or modules?
The whole thing looks very strange. It looks like you have some sort of mixed installation of k_deflt and k_athlon mount CD1. Then check which one you actually have installed with rpm -q k_deflt rpm -q k_athlon do "rpm -e" on the package you actually have installed, and then install k_athlon with rpm -ivh /media/cdrom/suse/i586/k_athlon-2.4.20-38.i586.rpm That *should* do it
participants (3)
-
Anders Johansson -
growbynet＠hotpop.com -
nick＠runner.u-net.com