[Bug 345103] New: 3rd Party Kernel Modules - not loadable after installing Package
https://bugzilla.novell.com/show_bug.cgi?id=345103 Summary: 3rd Party Kernel Modules - not loadable after installing Package Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rob.opensuse.linux@googlemail.com QAContact: jsrain@novell.com Found By: --- Have reproduced a problem where a 3rd party binary kernel module is not found by modprobe, after installing with YaST. Without knowing how the /lib/modules/*/{weak-,}updates directories are meant to be filled, I cannot assign the Bug accurately, so chose YaST2 as it was the component that installed the rpm's. The up to date kernel 2.6.22.12-0.1-bigsmp does not have link in weak-updates directory. Previous NVidia 3D rpm install, my weak-updates directory was only made correct by a later kernel upgrade. RPM's known to be affected : virtualbox-kmp-bigsmp-1.5.0_2.6.22.5_31-11 nvidia-gfxG01-kmp-bigsmp-100.14.19_2.6.22.5_30-1.1 This is what I did. Have current 2.6.22.12-0.1-bigsmp kernel installed. With YaST Software Manager install VirtualBox, it correctly selects a bigsmp kernel module. After receiving Pop Up in Virtual Box. I read I should in /usr/share/doc/packages/virtualbox/README.SUSE to modprobe, but modprobe cannot find it. fir:/lib/modules # modprobe vboxdrv FATAL: Module vboxdrv not found. Now in /lib/modules fir:/lib/modules # ls 2.6.22.12-0.1-bigsmp 2.6.22.5-30-bigsmp 2.6.22.5-31-bigsmp fir:/lib/modules # find . -name updates | xargs ls -l /2.6.22.5-30-bigsmp/updates: total 6743 -rw-r--r-- 1 root root 6894152 Sep 25 02:28 nvidia.ko /2.6.22.5-31-bigsmp/updates: total 56 -rw-r--r-- 1 root root 57079 Sep 25 22:39 vboxdrv.ko fir:/lib/modules # fir:/lib/modules # find . -name nvidia.ko -o -name vboxdrv.ko /2.6.22.5-31-bigsmp/updates/vboxdrv.ko /2.6.22.5-30-bigsmp/updates/nvidia.ko /2.6.22.12-0.1-bigsmp/weak-updates/nvidia.ko I did not make a mistake here, a symlink is not automatically created, I saw the exact same with nvidia.ko in previous Bug report. First saw this with NVidia 3D driver, closed Bug https://bugzilla.novell.com/show_bug.cgi?id=339640. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345103#c1 --- Comment #1 from Robert Davies <rob.opensuse.linux@googlemail.com> 2007-12-02 13:39:12 MST --- Work round is to force Yast2 to update kernel unconditionally, inefficient but got weak updates done. So it must be some script that's not run but should be, rather than anything deep. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345103 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345103#c2 --- Comment #2 from Robert Davies <rob.opensuse.linux@googlemail.com> 2007-12-06 07:41:13 MST --- On a different machine similar with 2.6.22.13-0.3-default, and a seperate /boot partition, installing virtualbox package, did create a weak-updates directory. If there's something odd about the installation on the box with -bigsmp kernel, I'd at least expect things to fail in a way that attracts attention, from YaST it looks like all installation steps succeeded. So I use same 32bit OS on an AMD64 capable chip, as the box that "works" has Athlon MP 32bit SMP. Linux fir 2.6.22.13-0.3-bigsmp #1 SMP 2007/11/19 15:02:58 UTC i686 athlon i386 GNU/Linux cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 67 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ stepping : 3 cpu MHz : 2812.758 cache size : 1024 KB .. uname -a Linux oak 2.6.22.13-0.3-default #1 SMP 2007/11/19 15:02:58 UTC i686 athlon i386 GNU/Linux cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) MP 2000+ stepping : 1 cpu MHz : 1666.822 cache size : 256 KB ,,, processor : 1 vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) MP -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345103 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345103#c3 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkudlvasr@novell.com, chrubis@novell.com, | |sndirsch@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com --- Comment #3 from Cyril Hrubis <chrubis@novell.com> 2007-12-17 10:35:57 MST --- I don't know what's the mechanism to handle this problem IMHO yast can't create any symlinks and things like this should be done via scripts in rpm. Reassigning to kernel people to ask if there is any general rule. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345103 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345103#c4 --- Comment #4 from Robert Davies <rob.opensuse.linux@googlemail.com> 2007-12-17 11:46:06 MST --- There's a Kernel Module Packages concept http://en.opensuse.org/Kernel_Module_Packages The issue is integration of kernel + 3rd party stuff. The problem for me was that things could go badly wrong, but YaST would think everything was fine. I suspect that somewhere an error is occuring but is ignored, making isolation of fault difficult. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345103 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345103#c5 --- Comment #5 from Stefan Dirsch <sndirsch@novell.com> 2007-12-17 11:54:31 MST ---
./2.6.22.5-30-bigsmp/updates/nvidia.ko ./2.6.22.12-0.1-bigsmp/weak-updates/nvidia.ko So nothing is wrong here for nvidia. Only the symlink for vboxdrv is missing.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345103 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345103#c6 --- Comment #6 from Robert Davies <rob.opensuse.linux@googlemail.com> 2007-12-18 02:36:32 MST --- This problem previously occurred with the nvidia module. A subsequent update to the kernel created the nvidia weak-updates entry (actually forcibily installing same kernel version with YaST with "uncondiational upgrade" option has same effect). I have a fresh install, on the machine which is currently using the "nv" driver, where I could try to install, the nvidia module. As I now reproduced same but with a different kernel module package vboxdrv, it seemed to me, to be a more general problem, The problem did not occur on a different SMP box, set up very similarly (partition wise /, /boot, /usr, /opt, /var), but with -default kernel. Have not tried to reproduce on the fresh install yet, perhaps I could and someone can tell me how to make sure I preserve any logged information, that could explain it. The box with this issue installing KPM's has been sooooper solid, since 2.6.22-12.0-1 kernel came out, which solved various problems I'd seen before. The fresh install had to be done with the onboard netorking, not the 2nd network card, due to driver issue in ne2k-pci module for example. This seems like a slip in a script somewhere in the rpm's, rather than a big issue, the problem is isolating it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345103 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |agruen@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=345103 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=345103#c7 Robert Davies <rob.opensuse.linux@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #7 from Robert Davies <rob.opensuse.linux@googlemail.com> 2009-02-04 06:49:43 MST --- I noticed that vbox recently had a fix to use weak updates directory in a more recent release. Closing this one due to lack of interest, noone is installing 10.3 anymore. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com