On 24/10/2016 16:04, cagsm wrote:
On Mon, Oct 24, 2016 at 2:17 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
The boot image may have kernel modules included, but that doesn't mean they are all loaded. They are loaded only if needed at boot time from the initrd image; if needed later they are loaded from disk.
So how do I exactly list whats included in that generated-by dracut linux kernel image that gets booted? as 8139 stuff is not listed in that other modprobe file and I didnt find recerences to 8139 in etc or etc/sysconfig or those places. Apparently it can load that cp and too driver, both of them, but it complains about cp first being unsuitable and then moving over to too. I want to clean up or make it not load cp first and immediately go for too module as it is asking for. Hard to understand all of this methinks. Lot of stuff building on top of each other. Thanks.
I think that you can say that you do not want a module loaded, and the boot process will respect that. Right now I'm on Windows, so I can't look up the file and the syntax for you. Maybe /etc/modules.conf or something like that. -- Saludos/Cheers, Carlos E.R. (Minas-Morgul - W10) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org