Bug 132467

Summary: kernel module load path doesn't work
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Forgotten User XG9X5w8kVa <forgotten_XG9X5w8kVa>
Component: KernelAssignee: Andreas Gruenbacher <agruen>
Status: RESOLVED INVALID QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: x86   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User XG9X5w8kVa 2005-11-05 13:02:54 UTC 
Problem:
The module load paths don't work, so I can't put my modules in a directory and expect them to survive the next kernel update.
The kernel sources README.SUSE file still refers to the override directory.

The suse kernel in all 9.x previous releases uses the path /lib/modules/*-override-* to hold external modules and avoid having to reinstall the modules on each kernel minor update (depmod is patched for this to work)
This path doesn't exist on SuSE 10.0 kernel-default-2.6.13-15, and if created by hand, modules put there are not found.
After looking at module-init-tools sources, depmod now looks for /lib/modules/xx.xx.xx/updates and /lib/modules/xx.xx.xx/updates2 subdirectories, where updates2 should be a soft link to the xx.xx.xx-override-yy directory. But update and update2 don't exist too.

Workaround: 
Create by hand all the *-override-* directory and update2 softlink.
Comment 1 Olaf Kirch 2005-11-15 11:24:59 UTC 
Marian, can you look into this please?
Comment 2 Marian Jancar 2005-11-15 12:10:42 UTC 
the directory and the link should be in the kernel rpm
Comment 4 Andreas Gruenbacher 2005-11-15 15:33:29 UTC 
We have deprecated the override mechanism in favor of a more powerful mechanism: since SUSE Linux 10.0, the /usr/sbin/kernel-update-tool script is used for kernel updates. The kernel-update-tool.spm package contains a DriverUpdate.{sxw,pdf} document describing the process, mechanisms, and conventions. The documentation isn't perfect yet, and neither is the implementation, but this is the way we will be going.

Feel free to come back and ask me in case something is still unclear after reading the documentation.