Article Title: about lilo-IDE and SCSI. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.
There is also a very famous problem with LILO: Linux root file system cannot exceed 1024 cylinders, otherwise LILO may not be correct
Reading boot. B or the kernel has similar problems in many operating systems. The solution is to use loadlin when both dead and dead
. Exe/load95 to replace LILO, or make a boot floppy disk, or assign the Linux root file system to the top. once LILO
After reading the kernel, the kernel does not use the BIOS to operate the hard disk, and there will no longer be 1024 problems. The professional practice is: Dedicated to allocating to the root file system
A 64M or so partition (of course all before 1024), and then allocate partitions (independent file systems) for/usr,/var,/home (depending on the situation ).
When I sorted out this FAQ, I also encountered issues that I did not mention before. first, I would like to describe the background:
My computer uses Asus dual cpu bx motherboard P2B-DS, integrated with Adaptec AIC-7890 scsicard, then Linux
If this card is not yet supported, you have to find an IDE hard disk to install Redhat 5.1. after a while, find a patch on the suse homepage,
When the kernel is upgraded to 2.0.35 and this patch is installed, I recognize this card. so I began to think about replacing the RH kernel with my own compiled kernel.
The kernel on the drive, but how can I streamline the kernel configuration? the compiled kernel (using make bzImage) is always larger than the boot disk. later
A netizen told me that at runtime (9.1 GB), I carefully set the Linux root file system to be within 1024 cylinders during installation, and chose the Linear mode to restart, after "L" appears, you will not be moved. so I want to get rid of the linear parameter and see: Enter the BIOS to set the IDE device before the SCSI device, start Linux on the IDE hard disk, and copy the compiled kernel to the Linux partition on the SCSI hard disk, in/etc/lilo. add the Linux startup item on SCSI in conf:
Image =/boot/bzImage
Root =/dev/sda4
Label = newlinux
Run lilo again, and then you can start Linux on SCSI from LILO on the IDE. modify/etc/lilo. conf. remove the linear parameter and run lilo. the display is normal. restart and set the SCSI device to the IDE device.
L 04 04 04 04 ...... 04 loop repeatedly. haha, many netizens have encountered problems! No way. check/usr/doc/lilo-0.2/README first. 04 indicates that LILO cannot correctly understand the physical parameters of the hard disk (CHS). What is the problem? Is LILO working properly from IDE? Read it carefully!
It turns out that LILO has another problem: when there are both IDE hard disks and SCSI hard disks in the system, LILO does not know whether the BIOS is set to IDE first or SCSI first, as a result, the CHS' parameters on the hard disk will be garbled. in/etc/lilo. add the following in conf:
Disk =/dev/sda
Bios = 0x80 <= remember, 0x80 indicates the first hard disk. tell LILO that the SCSI hard disk is the first hard disk.
Sectors = 63
Heads = 255
Cylinders = 1110
Disk =/dev/hda
Bios = 0x81 <== 0x81 indicates the second hard disk
Sectors = 63
Heads = 128
Cylinders = 621
The problem is solved in this way (I was going to see the original code). we can use the p command of hdparm-g or fdisk to view the CHS parameter.
By the way, another problem has been solved:
The LILO on the IDE cannot start all the errors on SCSI, such as 98 and NT, or the drive letter is incorrect after startup. first copy boot1_804 and modify/etc/lilo. conf:
Other =/dev/sda1
Label = win98
Table =/dev/sda
Map-drive = 0x80
To = 0x81
Map-drive = 0x81
To = 0x80
The last four lines actually play the role of "soft" switching the hard disk order, which is especially useful for those machines in the BIOS that do not set the sequence of IDE or SCSI. even if there is, manual switching is much more troublesome!
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.