linux device driver There are two ways to load insmod and modprobe, here to talk about their differences on the use of
1, insmod can only load a specific device driver, and the need to address the specific driver. Written as:
insmod drv.ko
2. modprobe may once have driven all the dependencies loaded into the kernel. Driving without a specific address, but requires the installation file system is mounted according to the make modues_install drive module. The drive is installed in / lib / modules / $ (uname -r) / .... Written as:
modprob drv
1, insmod can only load a specific device driver, and the need to address the specific driver. Written as:
insmod drv.ko
2. modprobe may once have driven all the dependencies loaded into the kernel. Driving without a specific address, but requires the installation file system is mounted according to the make modues_install drive module. The drive is installed in / lib / modules / $ (uname -r) / .... Written as:
modprob drv
modprobe and insmod to load the kernel module, like all of
but modprobe relatively intelligent, it can be automatically loaded for you based on the dependence module;
and insmod can not do this.
------------- ------------------ dividing line
such as ipmitool use this tool requires the presence of the device ipmi0 dev / if if not, you need to load
modprobe ipmi_si
modprobe ipmi_devintf
read data from the local KCS interface using -I open such as
ipmitool -I open sensor
you want to uninstall module. Use rmmod
but modprobe relatively intelligent, it can be automatically loaded for you based on the dependence module;
and insmod can not do this.
------------- ------------------ dividing line
such as ipmitool use this tool requires the presence of the device ipmi0 dev / if if not, you need to load
modprobe ipmi_si
modprobe ipmi_devintf
read data from the local KCS interface using -I open such as
ipmitool -I open sensor
you want to uninstall module. Use rmmod
linux device driver There are two ways to load insmod and modprobe, here to talk about their differences on the use of
1, insmod can only load a specific device driver, and the need to address the specific driver. Written as:
insmod drv.ko
2. modprobe may once have driven all the dependencies loaded into the kernel. Driving without a specific address, but requires the installation file system is mounted according to the make modues_install drive module. The drive is installed in / lib / modules / $ (uname -r) / .... Written as:
modprob drv
1, insmod can only load a specific device driver, and the need to address the specific driver. Written as:
insmod drv.ko
2. modprobe may once have driven all the dependencies loaded into the kernel. Driving without a specific address, but requires the installation file system is mounted according to the make modues_install drive module. The drive is installed in / lib / modules / $ (uname -r) / .... Written as:
modprob drv
modprobe and insmod to load the kernel module, like all of
but modprobe relatively intelligent, it can be automatically loaded for you based on the dependence module;
and insmod can not do this.
------------- ------------------ dividing line
such as ipmitool use this tool requires the presence of the device ipmi0 dev / if if not, you need to load
modprobe ipmi_si
modprobe ipmi_devintf
read data from the local KCS interface using -I open such as
ipmitool -I open sensor
you want to uninstall module. Use rmmod
but modprobe relatively intelligent, it can be automatically loaded for you based on the dependence module;
and insmod can not do this.
------------- ------------------ dividing line
such as ipmitool use this tool requires the presence of the device ipmi0 dev / if if not, you need to load
modprobe ipmi_si
modprobe ipmi_devintf
read data from the local KCS interface using -I open such as
ipmitool -I open sensor
you want to uninstall module. Use rmmod