Bug 7648
Summary: | Default 6.1 install: no boot floppy, LILO hangs with "LI" | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | zenon |
Component: | lilo | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | zenon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-01-04 22:26:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
zenon
1999-12-07 05:16:14 UTC
A workaround (works if you have 6.0 system, or disk with it, at hand): The following trick worked OK: 1. I have two disks on my system. As reported, the basic "Server" 6.1 installation on one of the disks failed, because lilo hangs with LI and no bootable floppies were created. 2. I had another disk in the system with 6.0 system installed - the 6.0 procedure included creation of bootable floppy, which made the difference. 3. Used the bootable floppy from the 6.0 system to boot from the newly installed 6.1 system. It reported missing /lib/modules/2.2.5-* kernel modules, and as a result I could not use the "mkbootdisk" utility. 4. From another disk (you can do it from another system using floppies) I have copied /lib/modules/2.2.5-* to my newly installed system, which contained own /lib/modules/2.2.12-* modules. 5. Then the system was rebooted (using the same 6.0 bootable floppy). This time no missing modules were reported (obviously). 6. Noted the name of the new 6.1 kernel (ls /lib/modules had shown the full name of the 2.2.12-* kernel, say 2.2.12-22). Executed # mkbootdisk 2.2.12-22 The new created bootable floppy booted the 6.1 version of kernel, as intended. (One could remove now the /lib/modules/2.2.5-*) As explained above, I was able to create bootable LILO floppy, which boots the 2.2.12-* kernel. However, running lilo with the standard /etc/lilo.conf (which installed lilo on /dev/sda disk), and attemping to boot without bootable floppy, still resulted with handing at "LI" prompt. Now, I experimented with modifications to the /etc/lilo.conf and it happened, that for my HD (which is 9.1 GB SCSI disk) the "linear" option solved the problem. My current lilo.conf file looks like follows: boot=/dev/sda map=/boot/map install=/boot/boot.b prompt linear timeout=50 default=linux image=/boot/vmlinuz-2.2.12-20smp label=linux initrd=/boot/initrd-2.2.12-20smp.img read-only root=/dev/sda8 image=/boot/vmlinuz-2.2.12-20 label=linux-up initrd=/boot/initrd-2.2.12-20.img read-only root=/dev/sda8 Assigned to dledford In older releases, you were required to select the linear box during the install process to use linear mode, which is required for some scsi controllers and drives. In newer releases, we always use linear mode when installing lilo. |