1. If the kernel always compiles with the same error, as follows: The last few lines of the make modules_install pop up the error: if [ -r System.map -a -x /sbin/Depmod ]; then /sbin/depmod -ae -F System.map 2.6.12.2; fi /bin/sh: line 1: 3357 killed /sbin/depmod -ae -F System.map 2.6 .12.2 make: ** * [_modinst_post] Error 137 If you continue make install, restart, it is not able to enter the kernel that just compiled and installed, showing a kernel error. Analysis: If System.map is readable and /sbin/depmod is executable, then execute /sbin/depmod -ae -F System.map 2.6.20; end depmod(depend module) Function Description: Analyze the dependencies of loadable modules Sex. Syntax: depmod [-adeisvV][-m <file>][--help][module name] Note: depmod can detect module dependencies for modprobe to use when installing modules. Parameters: -a or --all Analyze all available modules. -d or debug Execute the debug mode. -e Outputs symbols that cannot be referenced. -i Does not check the version of the symbol table. -m<file> or system-map<file> Use the specified symbol table file. -s or --system-log logs errors in the system log. -v or --verbose Displays detailed information when executed. -V or --version displays version information. --help Displays help. Solution: Before you make module_install, do you close selinux? The problem is that selinux prevents writing /lib/modules/<version> directory 2. If you restart the system, it will display: Warning--SElinux relabel is required Disabling security enforcement Relabeling could take a Very long time depending on file system size You can change grub.conf to add selinux=0 to the following location kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/selinux=0 rhgb quiet or change /etc/selinux/config , SELINUX=Disabled, save the selinux can be closed 3, modify selinux in the new version of Red Hat and Fedora, modify the file /etc/sysconfig/selinux: # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX= Enforcing # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted Set SELINUX to disable, SElinux will be stopped the next time the system is booted Kernel Parameter can be added after the core parameter: selinux=0 (stop) or selinux=1 (on) parameter file /boot/grub/menu.lst title Fedora Core (2.6.18-1.2798. Fc6) root (hd0,0) kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=LABEL=/rhgb quiet selinux=0 initrd /initrd-2.6.18-1.2798.fc6.img Check the current state of SELinux Whether you are using SELinux now: # getenforce disabled 4. If Kernel panic appears after reboot: VFS: Unable to mount root fs on unknown-block(0,0) From the error message, the hard disk is not recognized. It seems that the SATA hard drive on my machine must be configured in the kernel to be recognized. Carefully read the help information in the kernel configuration, know that the kernel supports two SATA drivers: one is libata, the latest SATA controller is supported in the SCSI subsystem, and the other is SATA in the IDE driver. It is the first generation of SATA controllers. My machine should be relatively new, so try it first by libata. First look at what type of SATA controller is my? Run lspci, the output is as follows: 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Con troller (rev 01) is the type of SATA controller. Solution: Set the following options in make menuconfig: Device Driver |
---->SCSI device support |
---->SCSI disk support |
----->verbose SCSI error reporting (not required, but convenient for problem location) |
----->SCSI low-level drivers |
---->Serial ATA (SATA) support |
---->intel PIIX/ICH SATA support <*> RAM disk support In device drivers -> Block devices <*> Initial RAM disk (initrd) support in device drivers -> Block devices <*> Compressed ROM file system support (cramfs) in file systems -> Miscellaneous filesystems 5. If the network card does not recognize after restarting, it cannot be activated, and via-rhine device eth0 does not seem to be present, delaying initialization Missing VIA driver running make menuconfig Find <M>"VIA Rhine RevB support" in Networking support-->Networking device support --> Ethernet (10 or 100Mbit) 6. If restarted, the display is as follows: reading all physical Volumns, this may take a while… no volumns group found! unable to find volumns group "VolGroup00" ERROR: /bin/lvm exited abnormal with value 5 (pid 335) error 6 mounting ext3 ERROR OPENING /dev/console!!: 2 Error dup2ing fd of 0 to 0 error dup2ing fd of 1 to 1 error duping fd of 2 to 2 switchroot:mount failed:22 kernel panic - no syncing: attempted to kill init! When running make menuconfig in device drivers ->[* Multiple devices driver support (RAID and LVM) These should also be enabled if they have the following options: <*> Logical volume manager (LVM) support