Linux kernel driver loading

Linux: How to load a kernel module automatically at boot time

🐧 Get the latest tutorials on Linux, Open Source & DevOps via

Category	List of Unix and Linux commands
Documentation	help • mandb • man • pinfo
Disk space analyzers	df • duf • ncdu • pydf
File Management	cat • cp • less • mkdir • more • tree
Firewall	Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04
Linux Desktop Apps	Skype • Spotify • VLC 3
Modern utilities	bat • exa
Network Utilities	NetHogs • dig • host • ip • nmap
OpenVPN	CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04
Package Manager	apk • apt
Processes Management	bg • chroot • cron • disown • fg • glances • gtop • jobs • killall • kill • pidof • pstree • pwdx • time • vtop
Searching	ag • grep • whereis • which
Shell builtins	compgen • echo • printf
Text processing	cut • rev
User Information	groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w
WireGuard VPN	Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04

Comments on this entry are closed.

Try this method to load module at boot time

#echo module_name >> /etc/rc.modules
#chmod +x /etc/rc.modules

Hello,
I use Ubuntu 11.4 (Linux 2.6.38)
I tried both the files modules.conf and rc.modules.
Unfortunately the modules is not loaded.
Do you have any idea?
Thanks,
Yacob.

/etc/modules is the file you’re looking for Yacob

Thank you.
I tried this file also but the modules are not loaded.
Do you have another idea?
Thanks,
Yacob.

Try this:
echo “modprobe module_name” >> /etc/modprobe.d/modeprobe.conf

My understanding is that modprobe.conf and modules.conf are only configuration files. They do not invoke modprobe. All they do is provide modprobe with information about what it should do when it is invoked.

Scripts that are run immediately after the boot (in the start up sequence) are called rc scripts. Many systems have a script called rc.local. This script is arranged in such a way (normally with symlinks) that it is executed as the last script in the start up sequence. This is a good place to put additional commands that are required and which have not been invoked already. The normal location of this script is /etc/rc.d/rc.local.

Therefore if the modprobe command is added to that script it will be executed at the end, and before a login shell prompt is provided. Determine the location of modprobe. If, for example, it is /sbin/modprobe, then the end of the rc.local file should look something like this:
# Put your required modprobe command here:
/sbin/modprobe name-of-module

Note that if the module in question requires options, then a place to put these is in /etc/modprobe.conf, because when modprobe runs it will read that configuration file and pick up any required options from there.

Your steps helped me. It works.
I wanted to bring 8021q after every reboot.
I added it in /etc/rc.local file.
For me /etc/rc.d/rc.local doesn’t exist, I have Ubuntu 14.04 platform.

I am glad that helped you.

I use “linux from scratch”. That is a system in which the operating system is built step by step, not simply installed from some disk or web site. It takes a long time but can give some improvements in understanding and control.

Different distributions tend to store files (including configuration files) in different places. It appears that with Ubuntu there is a configuration file called /etc/modules which lists the names of modules to be loaded at boot time. If so then that might be a better place to put the 8021q module name. rc.local tends to be used for “local” after thoughts – anything unusual that needs to be done for that one host. There is a web page that describes Ubuntu’s /etc/modules here:
https://help.ubuntu.com/community/Loadable_Modules

The use of the 8021q module for vlan’s in Ubuntu is described here:
https://wiki.ubuntu.com/vlan
The section “Making it permanent”, which comes at the end of the article, seems to be relevant in your case. If that’s right then it might be tidier to do it that way than to use rc.local (even though it does work).

Hi all,
i am new buddy to Linux module programming.I am facing same problem in loading a module at boot time in Ubuntu 11.04. Can any one tell me the perfect steps to load the module at the boot time.

same problem here. I did change /etc/modules, but where do I put the module object itself so moprob can find it?

To put the question in another way, what are the default lcoation that modprobe look for modules?

i i tried to put the .KO file with the all drivers .KO file.But that doesn’t worked.
The other way to do this is configuring the Kconfig file and recompile the kernel.
But i am not getting proper documentation.

I figured that out.

add a line to /etc/modules for your module (without .ko)
copy the module file to /lib/modules/
do

sudo depmod -a
reboot and it worked for me on Ubuntu 12.04

error. copy the module file to /lib/modules/

This solution worked for me too on 12.04 . Thanks redjupiter.

Thanks redjupiter. It worked with ubuntu 11.04.

Glad it worked. one correction for others:
copy the module file to /lib/modules/

there is no /etc/modules…rather /etc/modprobe.conf is there…
please suggest

quite often there is no need for a modprobe configuration file. As I said before (see previous remark from November, 2011), modprobe is not invoked by that configuration file. Its just that if you need to provide it with additional information, then that can be done from the configuration file. The name used for the configuration file has changed a bit between different versions, and sometimes it is given as a file in a directory, modprobe.d. On my workstation (built from scratch) there is no modprobe configuration file. Its not needed.

The critical thing usually is making the kernel aware of modules. To do this you have to put the module in the right place, and run depmod to update the module dependencies.

Perhaps if you explained what you were trying to do, then it would be possible to provide a more specific explanation.

I would like to add that some systems have the modules file in /etc/sysconfig/modules

To load a module by filename (i.e. one that is not installed in /lib/modules/$(uname -r)/):
# insmod filename [args]

To unload a module:
# modprobe -r module_name

Or, alternatively:
# rmmod module_name

Check this link for more info on how to work with modules:
https://wiki.archlinux.org/index.php/kernel_modules

You forgot to mention about unsupported modules file.

Источник

VirtualBox выдаёт ошибкуKernel driver not installed (rc=-1908)(linux ubuntu 20.04LTS)

В линукс честно говоря нуб. Вот что пишет программа:

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please reinstall virtualbox-dkms package and load the kernel module by executing

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system’s documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) — The support driver is not installed. On linux, open returned ENOENT.

Телепаты в отпуске. У тебя проблема с запуском Ubuntu внутри VirtualBox или проблема с запуском VirtualBox на Ubuntu?

Что в чем ты запускаешь?

Судя по всему, у тебя не подтягивается модуль коробки.

VirtualBox на Ubuntu

А, хорошо. Теперь покажи выводы

Linux ivan-X551CA 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal

ls -l /sys/firmware/efi

итого 0 -r–r–r– 1 root root 4096 авг 25 19:05 config_table drwxr-xr-x 2 root root 0 авг 25 16:51 efivars -r–r–r– 1 root root 4096 авг 25 19:05 fw_platform_size -r–r–r– 1 root root 4096 авг 25 19:05 fw_vendor -r–r–r– 1 root root 4096 авг 25 19:05 runtime drwxr-xr-x 32 root root 0 авг 25 19:05 runtime-map -r——– 1 root root 4096 авг 25 19:05 systab drwxr-xr-x 97 root root 0 авг 25 19:05 vars

apt list –installed | grep -i virtualbox

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ubuntu1.20.04.1 amd64 [установлен] virtualbox-qt/focal-updates,now 6.1.10-dfsg-1

ubuntu1.20.04.1 amd64 [установлен] virtualbox-source/focal-updates,now 6.1.10-dfsg-1

ubuntu1.20.04.1 amd64 [установлен, автоматически] virtualbox/focal-updates,now 6.1.10-dfsg-1

Источник

Linux: Find out what kernel drivers (modules) are loaded

lsmod command

You need to use lsmod command to show the status of modules in the Linux Kernel. Simply type the lsmod at a shell prompt to list all loaded modules:
$ lsmod
Sample outputs:

Get more information about the driver

To get more information about specific driver use modinfo command. The syntax is:
modinfo < driver-name >
To see information about a Linux Kernel module called e1000, enter:
$ modinfo e1000
Sample outputs:

• No ads and tracking
• In-depth guides for developers and sysadmins at Opensourceflare✨
• Join my Patreon to support independent content creators and start reading latest guides:
  • How to set up Redis sentinel cluster on Ubuntu or Debian Linux
  • How To Set Up SSH Keys With YubiKey as two-factor authentication (U2F/FIDO2)
  • How to set up Mariadb Galera cluster on Ubuntu or Debian Linux
  • A podman tutorial for beginners – part I (run Linux containers without Docker and in daemonless mode)
  • How to protect Linux against rogue USB devices using USBGuard

Join Patreon ➔

See modinfo and lsmod man pages for more info.

🐧 Get the latest tutorials on Linux, Open Source & DevOps via

Источник

Howto: Display List of Modules or Device Drivers In the Linux Kernel

H ow do I display the list of loaded Linux Kernel modules or device drivers on Linux operating systems?

You need to use lsmod program which show the status of loaded modules in the Linux Kernel. Linux kernel use a term modules for all hardware device drivers.

Tutorial details
Difficulty level	Easy
Root privileges	Yes
Requirements	lsmod
Est. reading time	Less than a one minute

Please note hat lsmod is a trivial program which nicely formats the contents of the /proc/modules , showing what kernel modules are currently loaded.

This is an important task. With lsmod you can verify that device driver is loaded for particular hardware. Any hardware device will only work if device driver is loaded.

Task: List or display loaded modules

Open a terminal or login over the ssh session and type the following command
$ less /proc/modules
Sample outputs:

To see nicely formatted output, type:
$ lsmod
Sample outputs:

First column is Module name and second column is the size of the modules i..e the output format is module name, size, use count, list of referring modules.

• No ads and tracking
• In-depth guides for developers and sysadmins at Opensourceflare✨
• Join my Patreon to support independent content creators and start reading latest guides:
  • How to set up Redis sentinel cluster on Ubuntu or Debian Linux
  • How To Set Up SSH Keys With YubiKey as two-factor authentication (U2F/FIDO2)
  • How to set up Mariadb Galera cluster on Ubuntu or Debian Linux
  • A podman tutorial for beginners – part I (run Linux containers without Docker and in daemonless mode)
  • How to protect Linux against rogue USB devices using USBGuard

Join Patreon ➔

Finding more info about any module or driver

Type the following command:
# modinfo driver-Name-Here
# modinfo thermal_sys
# modinfo e1000e
Sample outputs:

Источник