When I boot my livecd with genkernel created init scripts, it looks for some depricated modules; :: scanning for uhci... module not found :: scanning for usb-ohci... module not found Reproducible: Always Steps to Reproduce: Just boot the genkernel kernel&initrd....... Actual Results: Nothing shocking, but it irritates me Expected Results: Detect that it is a 2.6.x kernel and not probe the modules
Created attachment 63088 [details] The .config I use
This is intentional as genkernel does not determine what is a 2.4 or a 2.6 kernel module. There would be too much work to do so and doesnt really gain anything. There are other items which show up as module no found as well. When things are compiled into the kernel and not modules.
*** Bug 98774 has been marked as a duplicate of this bug. ***
Actually... I did think of a solution for this that would work. Simply have genkernel verify the existence of the module before running a modprobe. This would keep users from seeing the "module not found" message, but would also keep us from having to maintain multiple modules_load lists for each arch. How does that sound?
(In reply to comment #4) > Simply have > genkernel verify the existence of the module before running a modprobe That's exactly what I recommended in bug 98774. Sorry I neglected to search for dups, though.
Reopening.
Created attachment 63244 [details, diff] Patch Patch to test.
Fixed in 3.2.2, thanks!
