Analysis and summary of the problems of Linux kernel in "make install"

When you compile the kernel, make install may encounter problems with "ERROR:modinfo:could not find Module XXX", and the actions on the command line see the following:

The code is as follows

Copy Code

[Root@smilejay linux-3.12]# make Modules_install .......... INSTALL Sound/soundcore.ko INSTALL Sound/synth/emux/snd-emux-synth.ko INSTALL Sound/synth/snd-util-mem.ko INSTALL Sound/usb/snd-usb-audio.ko INSTALL Sound/usb/snd-usbmidi-lib.ko INSTALL Sound/usb/usx2y/snd-usb-usx2y.ko Depmod 3.12.0 [Root@smilejay linux-3.12]# make install sh/root/linux-3.12/arch/x86/boot/install.sh 3.12.0 Arch/x86/boot/bzimage System.map "/boot" ERROR:modinfo:could not find module Power_meter ERROR:modinfo:could not find module Nf_conntrack_ipv4 ERROR:modinfo:could not find module Nf_defrag_ipv4 ERROR:modinfo:could not find module Nf_conntrack_ipv6 ERROR:modinfo:could not find module Nf_defrag_ipv6 ERROR:modinfo:could not find module xt_state ERROR:modinfo:could not find module Nf_conntrack ERROR:modinfo:could not find module i2c_piix4 ERROR:modinfo:could not find module SG ERROR:modinfo:could not find module EXT4 ERROR:modinfo:could not find module Mbcache ERROR:modinfo:could not find module jbd2 ERROR:modinfo:could not find module Sr_mod ERROR:modinfo:could not find module cdrom ERROR:modinfo:could not find module PATA_ACPI ERROR:modinfo:could not find module ata_generic ERROR:modinfo:could not find module Ata_piix

Cause analysis: When making install, in order for the new kernel to not be missing the required module, the current system has already loaded the module (LSMOD command can be viewed), and then compare the newly installed kernel module, If some module is missing from the new kernel module (compared to the output of the current Lsmod command), an error message such as "ERROR:modinfo:could not find module Power_meter" is reported.

Specifically, the lack of corresponding module and error, can be divided into 3 kinds of situations:

1. It is true that a module is missing, and the solution is: If the reported module is useful to you, check the. config file when compiling kernel, and then recompile and install modules with the corresponding configuration (with =m) If you think this module is useless, you don't have to worry about it.

2. The newly compiled kernel has already compiled this option into kernel (select as =y in. config) so that the. ko file for this module does not need to be generated, the system cannot find the corresponding. ko file, but it is already in the new kernel, regardless of the error. For example, the above "ERROR:modinfo:could not find module Ext4" is because I compiled the EXT4 file system module to built-in, as follows:

The code is as follows	Copy Code
[Root@smilejay linux-3.12]# grep EXT4. config Config_ext4_fs=y # Config_ext4_fs_posix_acl is not set # config_ext4_fs_security is not set # Config_ext4_debug is not set

The name of the

3. module has changed, and the module name is not found in the newly compiled kernel, with the names of the modules found with the current system lsmod command. Just check for confirmation, as this type of "ERROR:modinfo:could not find module Power_meter" Here is the way to check, as follows:

The code is as follows

Copy Code

# The current system has loaded the Power_meter module [Root@smilejay ~]# Lsmod | grep meter Power_meter 9169 1 # but the module name in kernel 3.12 is called acpi_power_meter and is inconsistent with the power_meterb found in ' lsmod '. [Root@smilejay ~]# find/lib/-name "*power_meter.ko" /lib/modules/2.6.32-358.el6.x86_64/kernel/drivers/acpi/power_meter.ko /lib/modules/3.12.0/kernel/drivers/hwmon/acpi_power_meter.ko

Finally, if the faulty kernel modules you think are unimportant or have been resolved by the above analysis, you can ignore the error prompts, despite these "Error:modinfo:" error prompts, but kernel is properly installed, continue to operate.