[opensuse] Cleaning up aged and grown systems from cruft and leftovers
Hi there, some system just recently displays via dmesg, that some realtek ethernet driver should be changed into some newer ethernet driver. I kind of only remember modprove and all this stuff from ancient days of linux only. Never cared much for this ever since Linux became nicer in plug and play and selecting drivers automatically or distros putty mainstream modules into the shipped kernels. Where does a leap 42.1 exactly get its modules from? Do modules become merged and integrated into the kernel boot image directly, or are they really loaded from /lib/modules/.... ? How does this work currently? Presently I have: /lib/modules/4.1.34-33-default/kernel/drivers/net/ethernet/realtek # ls -lart total 288 -rw-r--r-- 1 root root 135578 Oct 20 14:40 r8169.ko -rw-r--r-- 1 root root 22682 Oct 20 14:40 atp.ko -rw-r--r-- 1 root root 68890 Oct 20 14:40 8139too.ko -rw-r--r-- 1 root root 53034 Oct 20 14:40 8139cp.ko and dmesg complains briefly about: [ 0.441916] pci 0000:0x:0y.0: [10ec:8139] type 00 class 0x020000 [ 0.442093] pci 0000:0x:0y.0: [10ec:8139] type 00 class 0x020000 [ 12.714737] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [ 12.714746] 8139cp 0000:0x:0y.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too [ 12.714762] 8139cp 0000:0x:0y.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too [ 12.715466] 8139too: 8139too Fast Ethernet driver 0.9.28 [ 12.716356] 8139too 0000:0x:0y.0 eth0: RealTek RTL8139 at 0xffffc90001be2000, 00:00:00:00:00:00, IRQ 00 [ 12.717109] 8139too 0000:0x:0y.0 eth1: RealTek RTL8139 at 0xffffc90001be4000, 00:00:00:00:00:00, IRQ 00 Does mkinitrd or the newer dracut put modules somehow directly into the kernel images or secondary files grouping together or do those .ko get loaded by the kernel itself during boot-time from the real disk? /etc/modprobe.d/ doesnt have any 8139 or rtl named stuff anywhere inside. Thanks for all the help -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 24/10/2016 13:39, cagsm wrote:
Does mkinitrd or the newer dracut put modules somehow directly into the kernel images or secondary files grouping together or do those .ko get loaded by the kernel itself during boot-time from the real disk?
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. -- 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
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/24/2016 10:04 AM, cagsm wrote:
So how do I exactly list whats included in that generated-by dracut linux kernel image that gets booted?
Try 'lsinitrd'. Naturally, you should RTFM first :-)
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.
Part of the point of 'dracut' was to make the 'mkinitrd' process more controllable. Yes, there's a lot to understand, because there's a lot being done. But the algorithm is quite deterministic and comprehendable, its just deciding what to drill down on. I find it weasier to deal with/control than 'what went before' !! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
participants (3)
-
Anton Aylward -
cagsm -
Carlos E. R.