LinuxQuestions.org - lilo of slackware 12.1 problem

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - lilo of slackware 12.1 problem (https://www.linuxquestions.org/questions/slackware-14/lilo-of-slackware-12-1-problem-716117/)

lilo of slackware 12.1 problem

Recently I installed slackware 12.1 in my frnd's comp. Everything went fine except lilo. Although it was installed successfully it just displayed 0s n 1s after booting.
Then I loaded linux using slack dvd and tried all commands including startx which were fine. I reinstalled lilo manually using liloconfig first time in simple and second time in advanced mode but both din work. I got same 0s n 1s :(

I also copied lilo file from dvd and executed /sbin/lilo I got 4 warnings but lilo installed successfully msg came.

Then I installed mbr of windows and tried to change boot.ini file like this:
first I went to slackware /* using dvd */ and installed lilo to super block. Then took 512 bytes /* using command dd if=/dev/hda2 of=/tmp/boot.lnx bs=1 count=512 */ of linux partition and stored it in c: as boot.lnx file. Then added c:\boot.lnx="Slackware" to boot.ini I got an option in boot menu for slackware but when I selected it nothin really happend. /* screen was freezed with an _ */

I also tried LOADLIN but nothin happend. /* If u know exact procedure for LOADLIN please mention it becuase I think what I did with LOADLIN was suitable for DOS not NT */

Please help me in solving this mystery /* It never happend in my last 52 installations of slackware */

Even grub dint load when I installed kubuntu in same comp ! It has to do something with hard disk ?

Hi

Please do not use mobile phone text language as it makes it very hard to decipher what you actually mean. For example

Quote:

it just displayed 0s n 1s after booting.

I think translates as

Quote:

It shows the error code L 01 01 01 01 ...

If this is the case it means that the first stage boot loader has been unable to find the device in the BIOS. You should check that the hard drive has been properly detected in you BIOS.

In order to solve this problem you need to post your /etc/lilo.conf

Re-installing a Windows MBR will of course completely wipe out anything that you have done with lilo.

samac

Hi,

Be sure to not have a BIOS virus protection setup. Disable the BIOS virus protection to allow the 'MBR' write.

Code:

as root from the cli;

~#lilo -v -t -b /dev/your_device    #sda, hda this will only test 

~#lilo -v -b /dev/your_device        #this will write MBR to your_device

The above commands assume you are satisfied with the '/etc/lilo.conf' file.
You can 'man lilo' or 'man lilo.conf' to get more information.

Try posting /etc/lilo.conf and the output of "fdisk -l /dev/[HARD DRIVE DEVICE]" (run as root). I have installed LILO to a superblock and forgotten to mark the partition as bootable in the past. Perhaps you have done something similar.