Mdthbs

What is "oversubscription" in Networking?

Can European countries bypass the EU and make their own individual trade deal with the U.S.?

Checkmate in 1 on a Tangled Board

How to get a character's limb regrown at 3rd level?

What game is this character in the Pixels movie from?

How receiver knows the exact frequency in the channel to "listen to"?

Does a Hand Crossbow with the Repeating Shot Infusion still require a Free Hand to use?

How did they film the Invisible Man being invisible, in 1933?

Different budgets within roommate group

Is there a legal way for US presidents to extend their terms beyond two terms of four years?

Most elegant way to write a one-shot 'if'

How do we separate rules of logic from non-logical constraints?

Solving a Fractional Equation Involving a Logarithm

Story where diplomats use codes for emotions

Is it okay to fade a human face just to create some space to place important content over it?

Should 私の be omitted?

I hit a pipe with a mower and now it won't turn

"save as image" no confirmation when overwriting

Is it okay to submit a paper from a master's thesis without informing the advisor?

What verb for taking advantage fits in "I don't want to ________ on the friendship"?

A* pathfinding algorithm too slow

What exactly did Ant-Man see that made him say that their plan worked?

Using “ser” without "un/una"?

Do the 26 richest billionaires own as much wealth as the poorest 3.8 billion people?

Kernel Modules loaded when boot

who loaded my kernel modules?Virtualbox kernel modules not loading at bootHow to show loaded kernel modules inside OpenVZ virtual serverModule marked (F) in /proc/moduleslsmod lists only one single module, no other modules available to load, how do I proceed?Verifying kernel modules using a list of hasheslinux kernel boot parameters, which are available?Suppressing auto loading of Linux kernel modulesTCP variants under lsmod/proc in Kenrel Modules

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

0

Would like to know if there is a specific list or location for the name of the kernel modules that are loaded when the system is booted.

Commands like lsmod or cat /proc/kallsyms only show those that have been loaded.

Want to determine which are the modules that have been loaded manually.

Thanks in advance!

boot kernel-modules

share|improve this question

asked 59 mins ago

user357066user357066

322 bronze badges

add a comment | 

0

Would like to know if there is a specific list or location for the name of the kernel modules that are loaded when the system is booted.

Commands like lsmod or cat /proc/kallsyms only show those that have been loaded.

Want to determine which are the modules that have been loaded manually.

Thanks in advance!

boot kernel-modules

share|improve this question

asked 59 mins ago

user357066user357066

322 bronze badges

add a comment | 

Would like to know if there is a specific list or location for the name of the kernel modules that are loaded when the system is booted.

Commands like lsmod or cat /proc/kallsyms only show those that have been loaded.

Want to determine which are the modules that have been loaded manually.

Thanks in advance!

boot kernel-modules

share|improve this question

asked 59 mins ago

user357066user357066

322 bronze badges

share|improve this question

asked 59 mins ago

user357066user357066

322 bronze badges

share|improve this question

asked 59 mins ago

user357066user357066

322 bronze badges

asked 59 mins ago

user357066user357066

322 bronze badges

asked 59 mins ago

user357066user357066

322 bronze badges

1 Answer
1

active

oldest

votes

0

There might be multiple lists: one for kernel modules loaded within initramfs (i.e. modules necessary for basic I/O and accessing the root filesystem) and another list loaded once the root filesystem has been mounted.

For Debian and related Linux distributions like Ubuntu, there's /etc/initramfs-tools/modules for modules to be loaded in initramfs (in the specific order listed), and /etc/modules-load.d/ drop-in directory for specifying modules to be loaded after the root filesystem is accessible.

For any distribution using the dracut initramfs creator, you might want to look into /etc/dracut.conf and/or /etc/dracut.conf.d/*.conf files for add_drivers, force_drivers and/or filesystems lines: these will cause the specified modules to be added into initramfs, and in case of force_drivers, explicitly loaded regardless of hardware detection.

Besides those, on modern systems, many modules are usually loaded by hardware auto-detection: the kernel will format the hardware IDs detected on any autodetection-capable bus into specific module alias names, and the modules themselves will contain wildcard strings matching the hardware they support. If a match is found, the matching module is loaded. Each driver module will usually have a more detailed hardware detection routine that can further verify the compatibility between the module and the hardware.

On architectures with no auto-detection-capable system buses (e.g. RasPi and various embedded devices), a "device tree", a .dtb file either appended to the kernel image or loaded separately by the bootloader, will describe the system hardware: it includes identifiers for compatible "programming models", which will be used by the kernel to form module alias strings for automatic loading of appropriate modules.

The aim of kernel developers is to make the loading of kernel modules as automatic as reasonably possible.

share

answered 4 mins ago

telcoMtelcoM

24.2k11 gold badge2929 silver badges6363 bronze badges

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f527168%2fkernel-modules-loaded-when-boot%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

There might be multiple lists: one for kernel modules loaded within initramfs (i.e. modules necessary for basic I/O and accessing the root filesystem) and another list loaded once the root filesystem has been mounted.

For Debian and related Linux distributions like Ubuntu, there's /etc/initramfs-tools/modules for modules to be loaded in initramfs (in the specific order listed), and /etc/modules-load.d/ drop-in directory for specifying modules to be loaded after the root filesystem is accessible.

For any distribution using the dracut initramfs creator, you might want to look into /etc/dracut.conf and/or /etc/dracut.conf.d/*.conf files for add_drivers, force_drivers and/or filesystems lines: these will cause the specified modules to be added into initramfs, and in case of force_drivers, explicitly loaded regardless of hardware detection.

Besides those, on modern systems, many modules are usually loaded by hardware auto-detection: the kernel will format the hardware IDs detected on any autodetection-capable bus into specific module alias names, and the modules themselves will contain wildcard strings matching the hardware they support. If a match is found, the matching module is loaded. Each driver module will usually have a more detailed hardware detection routine that can further verify the compatibility between the module and the hardware.

On architectures with no auto-detection-capable system buses (e.g. RasPi and various embedded devices), a "device tree", a .dtb file either appended to the kernel image or loaded separately by the bootloader, will describe the system hardware: it includes identifiers for compatible "programming models", which will be used by the kernel to form module alias strings for automatic loading of appropriate modules.

The aim of kernel developers is to make the loading of kernel modules as automatic as reasonably possible.

share

answered 4 mins ago

telcoMtelcoM

24.2k11 gold badge2929 silver badges6363 bronze badges

add a comment | 

0

There might be multiple lists: one for kernel modules loaded within initramfs (i.e. modules necessary for basic I/O and accessing the root filesystem) and another list loaded once the root filesystem has been mounted.

For Debian and related Linux distributions like Ubuntu, there's /etc/initramfs-tools/modules for modules to be loaded in initramfs (in the specific order listed), and /etc/modules-load.d/ drop-in directory for specifying modules to be loaded after the root filesystem is accessible.

For any distribution using the dracut initramfs creator, you might want to look into /etc/dracut.conf and/or /etc/dracut.conf.d/*.conf files for add_drivers, force_drivers and/or filesystems lines: these will cause the specified modules to be added into initramfs, and in case of force_drivers, explicitly loaded regardless of hardware detection.

Besides those, on modern systems, many modules are usually loaded by hardware auto-detection: the kernel will format the hardware IDs detected on any autodetection-capable bus into specific module alias names, and the modules themselves will contain wildcard strings matching the hardware they support. If a match is found, the matching module is loaded. Each driver module will usually have a more detailed hardware detection routine that can further verify the compatibility between the module and the hardware.

On architectures with no auto-detection-capable system buses (e.g. RasPi and various embedded devices), a "device tree", a .dtb file either appended to the kernel image or loaded separately by the bootloader, will describe the system hardware: it includes identifiers for compatible "programming models", which will be used by the kernel to form module alias strings for automatic loading of appropriate modules.

The aim of kernel developers is to make the loading of kernel modules as automatic as reasonably possible.

share

answered 4 mins ago

telcoMtelcoM

24.2k11 gold badge2929 silver badges6363 bronze badges

add a comment | 

There might be multiple lists: one for kernel modules loaded within initramfs (i.e. modules necessary for basic I/O and accessing the root filesystem) and another list loaded once the root filesystem has been mounted.

For Debian and related Linux distributions like Ubuntu, there's /etc/initramfs-tools/modules for modules to be loaded in initramfs (in the specific order listed), and /etc/modules-load.d/ drop-in directory for specifying modules to be loaded after the root filesystem is accessible.

For any distribution using the dracut initramfs creator, you might want to look into /etc/dracut.conf and/or /etc/dracut.conf.d/*.conf files for add_drivers, force_drivers and/or filesystems lines: these will cause the specified modules to be added into initramfs, and in case of force_drivers, explicitly loaded regardless of hardware detection.

Besides those, on modern systems, many modules are usually loaded by hardware auto-detection: the kernel will format the hardware IDs detected on any autodetection-capable bus into specific module alias names, and the modules themselves will contain wildcard strings matching the hardware they support. If a match is found, the matching module is loaded. Each driver module will usually have a more detailed hardware detection routine that can further verify the compatibility between the module and the hardware.

On architectures with no auto-detection-capable system buses (e.g. RasPi and various embedded devices), a "device tree", a .dtb file either appended to the kernel image or loaded separately by the bootloader, will describe the system hardware: it includes identifiers for compatible "programming models", which will be used by the kernel to form module alias strings for automatic loading of appropriate modules.

The aim of kernel developers is to make the loading of kernel modules as automatic as reasonably possible.

share

answered 4 mins ago

telcoMtelcoM

24.2k11 gold badge2929 silver badges6363 bronze badges

share

answered 4 mins ago

telcoMtelcoM

24.2k11 gold badge2929 silver badges6363 bronze badges

answered 4 mins ago

telcoMtelcoM

24.2k11 gold badge2929 silver badges6363 bronze badges

answered 4 mins ago

telcoMtelcoM

24.2k11 gold badge2929 silver badges6363 bronze badges