https://bugzilla.novell.com/show_bug.cgi?id=756085
https://bugzilla.novell.com/show_bug.cgi?id=756085#c15
--- Comment #15 from Raymond Wooninck 2012-05-10 12:43:55 UTC ---
Thomas,
Whatever solution you are coming up with, the fact remains that if the module
is not inside the initrd the kernel will never be able to load it. This is not
a kernel error, but clearly an error of mkinitrd.
The syntax seems to be a hack from mkinitrd as that it was indicated inside the
/lib/mkinitrd/scripts/setup-modules.sh. Checking the
/etc/modprobe.d/00-system.conf file then you can see a lot of these entries
where certain modules are requiring other modules. I agree with you that this
is a clear SUSE thing, but as indicated it is not a hack on top of another
hack, but a method to prevent all kernel modules to be copied to the initrd and
just take the ones that are required.
I would not see any possibility how you can solve this in the kernel unless you
build cpufreq inside the kernel. As long as this stays a module, then when the
kernel boots from the initrd, the required modules needs to be present there.
Unless you can find a way to instruct the kernel that once the system is fully
booted, it has to rescan all dependencies and load the required modules again.
--
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.