Summary: | Linux-2.6 uses /etc/modules.autoload.d/kernel-2.4 on startup | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lesley van Zijl <zyl> |
Component: | Current packages | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 1.4_rc4 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
The file that has to be added to resolve the bug.
The file that has to be added to resolve the bug. The file that has to be added to resolve the bug. patch fixing logic in /etc/init.d/modules |
Description
Lesley van Zijl
2003-07-16 15:48:11 UTC
Created attachment 14592 [details]
The file that has to be added to resolve the bug.
It seems you just have to create a kernel-2.6 file in /etc/modules.autoload.d.
Created attachment 14593 [details]
The file that has to be added to resolve the bug.
It seems you just have to create a kernel-2.6 file in /etc/modules.autoload.d.
Created attachment 14594 [details]
The file that has to be added to resolve the bug.
It seems you just have to create a kernel-2.6 file in /etc/modules.autoload.d.
I just ran into this and it seems to be a logic problem in /etc/init.d/modules. It's current logic is like so: 1) does /etc/modules.autoload exist, if so, use that 2) is the kernel > 2.5 and /etc/modules.autoload/kernel-MAJOR.MINOR exist, if so use that 3) otherwise use /etc/modules.autoload/kernel-2.4 The logic is flawed because in step 2 it requires you to be running a >2.5 kernel AND to have the /etc/modules.autoload/kernel-MAJOR.MINOR file to use it. I am attaching a patch that fixes this logic, by removing the check to see if /etc/modules/kernel-MAJOR.MINOR does exist (it's already checked to be readable in load_modules, if it doesn't exist it's obviously not readable, so this check is unnecessary--load_modules fails silently if it's not readable) Created attachment 15568 [details, diff]
patch fixing logic in /etc/init.d/modules
the patch I spoke of above
wrong category Just found this bug, my possible solution was just to rm the symlink /etc/modules.autoload -> modules.autoload.d/kernel-2.4 and just recreate it as /etc/modules.autoload -> modules.autoload.d/kernel-2.6 and re-add your modules into /etc/modules.autoload. The symlink have nothing to do with it, just add the file for 2.6. As for comment #5, the check is there to warn in the next if segment so that the use can add a new file for whatever kernel, and then try the 2.4 config file that might have a better chance of working than no one at all. This is correct. |