Are kernel-modules always built from kernel-generic?

average_user · 08-14-2016, 07:12 PM

For example, when trying to load `st' with modprobe I got this in /var/log/syslog:

Code:

kobject_add_internal failed for scsi_tape with -EEXIST, don't try to register things with the same name in the same directory.

I run kernel-huge and to make sure that st.ko is statically loaded into the kernel I looked into /lib/modules/4.4.14/modules.builtin but I didn't find 'st.ko' entry. I re-run modules.builtin Makefile from kernel source on config-generic-4.4.14.x64 from slackware64-14.2/source/k/config-x86/ and got the same modules.builtin output without st.ko entry I already had on my system. Of course st.ko was there in output modules.builtin after I had run modules.builtin Makefile on config-huge-4.4.14.x64 from slackware64-14.2/source/k/config-x86. Is it how it's supposed to be? It's not a big deal, just a bit misleading.

Richard Cranium · 08-14-2016, 09:11 PM

Not helpful at all to the OP: I gain knowledge in why Patrick wants to deep-six the huge kernel.

Ztcoracat · 08-14-2016, 11:14 PM

I'm not sure if kernel modules are built from the generic kernel or not.

However most of the articles I read online that teach how to build kernel modules the generic kernel was presented as being used just about every tutorial.

Maybe a kernel developer will chime in and tell you.

Otherwise members with this experience would most likely know.

I'd be interested in finding out if in fact the generic kernel is used for most of the modules that are built today.

suppy · 08-15-2016, 02:50 AM

Yes, the generic kernel is the one where the modules come from. The huge one already has most of them included, for better or worse.

The huge one is not really meant for general use, though if it works for you, there's no reason to stop. But you seem to have problems with the st module, so perhaps you ought to switch to a generic one with an initrd.