From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) i installed redhat 7.0 a a Pentiunm II 400 MHz machine with 128 MB of memory. I have Windows NT on the same disk but on other partiitons. I had Red Hat 5.2 befor so I fdisk /MBRd it an dremoved completely. I chose a custom install for 7.0 and chose to install LILO in the first sector of /boot. After completing installation and creation of the boot disk the machine rebooted but went into NT directly. It booted fine with the boot disk. Tried the exact procedure on another machine [Pentium III, 400 MHz, 128 Mb memory] and it was the same. No LILO, only NT and boot disk works fine. Reproducible: Always Steps to Reproduce: 1.Fdisk /MBR the existing Linux verison [5.2 in my case], 2.Partition disks [/ 1.7gb, /boot 20 MB, swap 64 MB], 3.Install verison 7.0, choosing a custom install, 4.Install all components except the various servers. Actual Results: After the machine was rebooted LILO was not present i.e. Windows NT boot options were presented. Expected Results: LILO should have been installed and should have presented an option to boot either NT or Red Hat Linux 7.0.
I checked and the LILO program is PRESENT on the system in the correct directories. The RPM verification shows no problems. I tried uninstalling the RPM and installing it again but no change.
We have not seen this issue internally. Are you sure that you selected to install LILO to the MBR in the installer? After installation, can you run the lilo command and does it then write itself to the MBR?
Yes I can run the LILO program after and it saya "wrote linux, wrote nt". And yet nothing happens. I still have to boot using a floppy. The same for the second machine on whwich I installed. Thank you.
Can you attach your lilo.conf file? That would be helpful.
I solved the problem. It seems that during installation the lilo.conf file had been written as "boot=/dev/hda8" instead of just "boot=/dev/hda". Removing the "8" from the "boot=/dev/hda8" solves the problem. Although I still dont understand why this mistake happened during the installation. Anyways, thank you very much and sorry for the waste of time.