[SOLVED] Lilo not booting slackware correctly. Errors listed inside.

1349 · 03-01-2010, 02:41 PM

I am using 32-bit. If you can find a fix for Lilo I will be pleased to use it but so far it has done nothing but caused problems.

samac · 03-01-2010, 02:47 PM

Actually lilo hasn't actually caused any problems. The problem is that it cannot find the kernel on the specified hard drive. This can be for a variety of reasons including pointing to the wrong kernel, pointing to the wrong partition or not having the drivers for the file system available in the kernel modules.

If you have lilo installed you will have a lilo.conf file in /etc in order to fix the problem we need to be able to see that file.

Hope this clarifies.

samac

1349 · 03-01-2010, 03:10 PM

Alright, sorry about getting angry earlier, this can get frustrating at times. This is all I see in my lilo.conf

in the beginning its

#Append any additional kernel parameters:
append = "vt.default_utf 8=0"
boot = /dev/hda

then its just it talking about the slack.bmp and how its gonna display and here is the end.

#Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda

#Windows bootable partition config ends

#Linux bootable partition config begins
image = /boot/vmlinux
root = /dev/hda2
label = Linux
read-only

#Linux bootable partition config ends

samac · 03-01-2010, 03:21 PM

If you are running Slackware-13.0 the run lilo from the command line as root. If you are running Slackware-current Change hda1 and hda2 to sda1 and sda2 then re-run lilo.

Post the results.

samac

samac · 03-01-2010, 03:25 PM

Also the results of

Code:

ls -al /boot

would be useful.

samac

1349 · 03-01-2010, 03:31 PM

Quote:

Originally Posted by samac

If you are running Slackware-13.0 the run lilo from the command line as root. If you are running Slackware-current Change hda1 and hda2 to sda1 and sda2 then re-run lilo.

Post the results.

samac

You know... doing to sda could work since I'm using current. How do you delete the entries? I do backspace and it doesn't work but I can add words myself.

samac · 03-01-2010, 03:32 PM

Unless you know vi, it is easier to use nano /etc/lilo.conf

samac

1349 · 03-01-2010, 03:45 PM

Alright I changed hda1 and hda2 to sda1 and sda2 and reloaded lilo and didn't work. I will return next time with the ls -al /boot results.

1349 · 03-01-2010, 03:58 PM

ls -al /boot results

lrwxrwxrwx 1 root root 9 Aug 25 2009 /boot -> /mnt/boot

samac · 03-01-2010, 05:12 PM

OK ls -al /mnt/boot. It looks like you have somehow moved your /boot directory onto /mnt/boot and I don't think lilo will follow a symbolic link. We need to re-populate your /boot directory. It should be fairly easy but we need to find out if the files are in /mnt/boot first.

samac

ROXR · 03-01-2010, 05:14 PM

Quote:

Originally Posted by 1349

vi has shown me
image = /boot/vmlinuz
label = Linux
root = /dev/hda2

so it is pointing to the right direction. also to the people saying that i actually typed in mounting on device i didn't, i did it correct lol.

I think that the error is root= /dev/hda2
it must be root= /dev/sda2.

you can boot with installer cd or dvd, then mount /dev/sda2 /mnt/disk and chroot /mnt/disk, after edit etc/lilo.conf and change hda2 for sda2, and execute # lilo command.

1349 · 03-01-2010, 06:11 PM

ls -al /mnt/boot

/bin/ls: cannot access /mnt/boot: No such file or directory

mryuck · 03-01-2010, 07:41 PM

If your booting from the cd you should remount your /dev/hda2 on /mnt/slacktemp.

Code:

mkdir /slacktemp
mount /dev/hda2 /slacktemp
cd /slacktemp
mkdir -p dev proc sys
mount --bind /dev dev
mount --bind /proc proc
mount --bind /sys sys
chroot .

then check ls -al /boot.
just in case it wasn`t mounted.
Actually I think there is a menu style(ncurses) config utility for lilo you could run liloconfig

1349 · 03-01-2010, 08:12 PM

Okay I just reinstalled the A packages off my cd. It boots up fine. Now I just need to remember what my login and password was but that's a personal thing I could figured out. Problem solved for now... Thanks samac for helping me along this whole way. I actually learned a lot from this experience.