Redhat is upgraded to 2.6.0! VMware Success Story - How to Configure SCSI Drivers in VMware

xiaoxiao2021-03-19  211

First, let's talk about my environment Win2kpro VMware (virtual SCSI's RedHat9)

Then talk about the needs of the files and elements:

1.Linux-2.6.0.tar.gz

2.Module-init-Tools-3.2-pre9.tar.gz

3.Mkinitrd-3.5.14-1-i386.rpm

4. Not afraid of failure

Let's talk about the detailed steps and practices:

[ljjk @ ljjk ljjk] #wget

http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/module-init-tools-3.2.tar.gz

[ljjk @ ljjk ljjk] #wget

http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.0.tar.gz

[ljjk @ ljjk ljjk] # wget

FTP: //ftp.mbl.is/pub/Fedora/1/i386/OS/Fedora/rpms/mkinitrd-3.5.14-1.i386.rpm

Now the software has it, the next step is to start specific do:

[ljjk @ ljjk ljjk] #CP module-init-tools-3.2.tar.gz / usr / src

[ljjk @ ljjk ljjk] #CP Linux-2.6.0.tar.gz / usr / src

[ljjk @ ljjk ljjk] #CP mkinitrd-3.5.14-1.i386.rpm / usr / src

[ljjk @ ljjk ljjk] #CD / USR / SRC

[LJJK @ LJJK SRC] #tar zxvf module-init-tools-3.2.tar.gz

[ljjk @ ljjk src] #tar zxvf linux-2.6.0.tar.gz

[ljjk @ LJJK SRC] # rpm -uvh mkinitrd-3.5.14-1.i386.rpm

[ljjk @ ljjk src] #rpm -qa | grep initrd

Mkinitrd-3.5.14-1-i386

[ljjk @ LJJK SRC] #CD Module-Init-Tools-3.2

[ljjk @ ljjk module-init-tools-3.2] #. / configure --prefix = /

[LJJK @ ljjk module-init-tools-3.2] #make moveold

[ljjk @ ljjk module-init-Tools-3.2] #make

[Ljjk @ ljjk module-init-tools-3.2] #make install

[ljjk @ ljjk module-init-tools-3.2] #cd ..

[ljjk @ ljjk src] #tar zxvf linux-2.6.0.tar.gz

[ljjk @ LJJK SRC] #CD Linux-2.6.0

[ljjk @ ljjk linux-2.6.0] #make mrproperty

[ljjk @ ljjk linux-2.6.0] #make menuconfig

In fact, you can choose according to your needs! I am a SCSI virtual hard disk.

Here, a few important configurations are summarized: * About "loadable module support" option, you must select two options "module unloading" and "automatic kernel module loading". * About "Processor Type and Features" option, must The "preemptible kernel" option is selected, this is one of the important reasons for the 2.4.x core than the 2.4.x kernel. * About "Block Devices" configuration, be sure to select support for loopback and ramdisk. * About "Multi -Device support (RAID AND LVM ", you want to select" Input Device Support ", remember to select" Keyboards "and" mice "support. * About" Graphics Support ", choose Support for Frame Buffer. * About ALSA, you want to select the "OSS API Emulation" option. OSS can not be used. * About USB, you can choose the * file system, please select the EXT3 file system, File Systems ---> [*] ext3 journalding file system support [*] ext3 security labels [*] jbd (ext3) debugging support The above three must be selected, and to build (ie, *). This is very important, Be sure to check the .config file has "config_ext3_fs = y". If it is not "config_ext3_fs = y" but "config_ext3_fs = m", you will meet the following error when you run the kernel: pivotroot: Pivot_Root (/ sysroot, / sysroot / initrd) Failed * NIC driver Be sure to compile the drive into the kernel, more popular network cards are Realtek 8139, here is the configuration of this network card for reference device drivers --- > Networking support ---> Ethernet (10 or 100Mbit) ---> <*> Realtek RTL-8139 C PCI Fast Ethernet Adapter Support Erimental <*> realtek RTL-8139 PCI Fast Ethernet Adapter Support

* Sound card driver also chooses the driver compiling of his own sound card into the kernel. The common sound card is I810_AUDIO. Here is the configuration of this sound card for reference for the device drivers ---> Sound ---> <*> Sound Card Support Advanced Linux Sound Architecture ---> <*> Advanced Linux Sound Architecture <*> Sequencer support <> Sequencer dummy client <*> OSS Mixer API <*> OSS PCM (digital audio) API [*] OSS Sequencer API <*> RTC Timer Support PCI Devices ---> <*> Intel i8X0 / MX440, SIS 7012; ALI 5455; NFORCE AUDIO; AMD768 / 8111 Open Sound System ---> <> Open Sound System (Deprecated) Note that if you use VMware Compile, then you need to pay attention to some places: If you recompile the kernel under VMware, the hard disk is used by SCSI. ---> SCSI Device Support ---> SCSI Low-Level Drivers ---> <*> BusLogic SCSI Support

can

[ljjk @ ljjk linux-2.6.0] #make bzimage

can

[ljjk @ ljjk linux-2.6.0] #make modules

[ljjk @ ljjk linux-2.6.0] #make modules_install

At last

[ljjk @ ljjk linux-2.6.0] #make install

At last:

I use the GRUB startup system, then the RO root = label = / this parameter behind the kernel /Vmlinux-2.6.14.2 in the Linux2.6 domain in /boot/grub/grub.conf, and then you can use it.

[ljjk @ ljjk linux-2.6.0] #CD / boor / grub

[ljjk @ ljjk linux-2.6.0] #vi grub.conf

Then make the corresponding modification.

[ljjk @ ljjk linux-2.6.0] #reboot

Then select the start of the 2.6 core after the upgrade.

Then succeed!

Successful picture:

Add a few words to:

When upgrading to 2.6.15.6, the steps are almost the same, but Mkinitrd is

Mkinitrd-4.1.18-2.i386.rpm

Of course, there is also a need for LVM2-2.00.25-1.01.i386.rpm

If you don't believe, you can install Mkinitrd, you will not succeed, you will prompt you

LVM2-2.00.25-1.01.i386.25-1.01.i386.25-1.01.i386.25-1.01.i386.rpm is available at www.pbone.NET.

The installation command is as follows:

# rpm -UVH --Nodeps lvm2-2.00.25-1.01.i386.rpm

Otherwise, you will be prompted to require 2.6 core, this is the redhat9 kernel is 2.4.20-8! Here, the installation is complete. If there is anything wrong, you can modify it yourself. I said that some services, such as iptables, these can solve themselves, but the system is absolutely able to go in.

Also, in general, after the compilation kernel is successful, write it in the grub.conf file, make install will change when make INSTALL! I am like this! Let's send a picture below:

转载请注明原文地址:https://www.9cbs.com/read-130225.html

New Post(0)