Multiple times to compile and start the 2.6.18 Kernel
Source: Internet
Author: User
Compile the 2.6.18 kernel multiple times and start it from the kernel-general Linux technology-Linux programming and kernel information. For details, see the following. Brother, I cannot install fedora6 under VM 4.0.
Downloading the new Virtual Machine 6.0, you can install dedora6. Unfortunately, the virtual machine has expired.
You have to compile 2.6.18 on your own under VM 4.0.
Rpm? E (old software name, here is software name, not software package, such as mkinitrd-4.1.18-2) -- nodeps
In the next two steps, delete the old lvm and device-mapper,
Remember, add ?? Nodeps parameters. Otherwise, they cannot be deleted. [* I browsed a lot of information and found that I did not mention this step. Do I use it ?? You can force install nodeps, but an error occurs when I install nodeps, so you can skip this step first. First, perform step 5, and then perform Step 2 if a problem occurs.]
# Cd/usr/src (go to the/usr/src directory. If it is already in the/usr/src directory, do not execute this command)
# Rm? Rf linux (delete the linux folder. It is worth mentioning that if the kernel has never been compiled before, there is no such folder, and this command line can be skipped)
# Tar jvxf linux-2.6.18.tar.bz2 (unzip new kernel)
# Ln-s linux-2.6.18 linux (regenerate linux folder)
6. Install the module-init-tools toolkit.
In the/usr/src directory, execute the following commands in sequence:
# Tar jvxf module-init-tools-3.2.tar.bz2 (extract module-init-tools)
# Cd module-init-tools-3.2 (by the/usr/src directory to enter the module-init-tools directory)
#./Configure -- prefix =/
# Make moveold
# Make all install
#./Generate-modprobe.conf/etc/modprobe. conf
7. install three other upgrade tools
Go back to the/usr/src directory and execute the following three commands to install the other three upgrade tools:
# Rpm-ivh -- nodeps mkinitrd-4.1.18-2.i386.rpm (note that -- nodeps parameters must be added here, the same below)
If you do not update the above upgrade packages, the following error will be prompted during kernel Compilation:
Mkinitrd failed
Make [1]: *** [install] Error 1
Make: *** [install] Error 2
(1) In the Loadable Module support option, you must select "Module unloading" and "Automatic kernel module loading;
(2) The Loopback Device support must be selected in device Drivers ---> Block Devices;
Choose Device Drivers ---> Multi-device support (RAID and LVM) to choose device mapper support ";
Device Drivers ---> Graphics support ", be sure to select" Support for frame buffer devices ";
Device Drivers --->; USB support ---> choose "USB Mass Storage support" (if you want more USB support in the real environment, select all. I am in a virtual machine. I don't need it anymore)
Device Drivers --->; Network device support --->; Ethernet (10 or 100 Mbit) --- >;< *>; AMD PCnet32 PCI support
(3) File system ---> (the following nine options are selected for the ext2 and ext3 File system configurations)
Second extended fs support
Ext2 extended attributes
Ext2 POSIX Access Control Lists
Ext2 Security Labels
Ext3 journalling file system support
Ext3 extended attributes
Ext3 POSIX Access Control Lists
Ext3 Security Labels
JBB (ext3) debugging support
File system ---> DOS/FAT/NT Filesystems ---> select "NTFS file system support ";
File Systems --> Miscellaneous filesystems ---> <*> Compressed ROM file system support (cramfs)
Note:
Ext2 and ext3 file system configurations are important and necessary. If the Ext3 and Ext2 file support is directly compiled into the kernel, the machine will be taken away during reboot and the following error message will appear:
Kernel panic: no init found, try passing init = option to kernel .....
Or:
VFS: Cannot open root device "hdxy" or unknow-block (0, 0)
Please append a correct "root =" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block (0, 0)
Kernel panic? Not syncing: No init found. Try passing init = option to kernel
Note: The following error message may appear during make install:
No module BusLogic found for kernel 2.4.12
Mkinitrd failed
This problem occurs only in the SCSI hard drive + VMWARE + REDHAT architecture, because BusLogic is compiled into the kernel rather than a module (even if the Buslogic module of the 2.4 kernel is statically compiled into the kernel ). The solution is to directly copy the BusLogic. o file:
But don't forget, run make install after the copy.
(If you select the BusLogic Module to M-Module mode when making menuconfig, this prompt will not appear .)
# Make bzImage (case sensitive. This step is used to compile the kernel)
After the kernel is compiled, an image file bzImage of the new kernel is generated in the/usr/src/linux/arch/i386/boot directory. If you use make zImage to compile a large kernel, the system will prompt you to use the make bzImage command to compile it. Therefore, I will use make bzImage to compile it directly.
# Make modules)
# Make modules_install (installable module)
After the installation is successful, the system will generate a 2.6.18 subdirectory under the/lib/modules Directory, which stores all the loaded modules of the new kernel.
# Make install (new kernel installation)
Note: The following error message may appear during make install:
No module BusLogic found for kernel 2.4.12
Mkinitrd failed
This problem occurs only in the SCSI hard drive + VMWARE + REDHAT architecture, because BusLogic is compiled into the kernel rather than a module (even if the Buslogic module of the 2.4 kernel is statically compiled into the kernel ). The solution is to directly copy the BusLogic. o file:
But don't forget, run make install after the copy.
(If you select the BusLogic Module to M-Module mode when making menuconfig, this prompt will not appear .)
At this point: you can find the option automatically added to the kernel in/boot/grub. con.
You can find 2 in the grub interface after the restart. 6. 18. This project
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
