LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-01-2010, 03:41 PM   #16
1349
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 35

Original Poster
Rep: Reputation: 15

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.
 
Old 03-01-2010, 03:47 PM   #17
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
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
 
Old 03-01-2010, 04:10 PM   #18
1349
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 35

Original Poster
Rep: Reputation: 15
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
 
Old 03-01-2010, 04:21 PM   #19
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
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
 
Old 03-01-2010, 04:25 PM   #20
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
Also the results of
Code:
ls -al /boot
would be useful.

samac
 
Old 03-01-2010, 04:31 PM   #21
1349
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 35

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by samac View Post
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.
 
Old 03-01-2010, 04:32 PM   #22
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

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

samac
 
Old 03-01-2010, 04:45 PM   #23
1349
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 35

Original Poster
Rep: Reputation: 15
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.
 
Old 03-01-2010, 04:58 PM   #24
1349
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 35

Original Poster
Rep: Reputation: 15
ls -al /boot results

lrwxrwxrwx 1 root root 9 Aug 25 2009 /boot -> /mnt/boot
 
Old 03-01-2010, 06:12 PM   #25
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
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
 
Old 03-01-2010, 06:14 PM   #26
ROXR
Member
 
Registered: Jan 2009
Location: Spain
Posts: 111
Blog Entries: 1

Rep: Reputation: 20
Quote:
Originally Posted by 1349 View Post
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.
 
Old 03-01-2010, 07:11 PM   #27
1349
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 35

Original Poster
Rep: Reputation: 15
ls -al /mnt/boot

/bin/ls: cannot access /mnt/boot: No such file or directory
 
Old 03-01-2010, 08:41 PM   #28
mryuck
Member
 
Registered: Feb 2010
Posts: 107

Rep: Reputation: 23
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

Last edited by mryuck; 03-01-2010 at 09:07 PM.
 
Old 03-01-2010, 09:12 PM   #29
1349
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 35

Original Poster
Rep: Reputation: 15
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.

Last edited by 1349; 03-01-2010 at 09:14 PM.
 
  


Reply

Tags
boot, lilo, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Qemu kvm : No eth0 inside a Slackware-13.0 guest, although listed in lspci and lsmod Linux.tar.gz Slackware 9 02-08-2010 07:36 PM
Lilo NOT booting Slackware dmcbeing Linux - Newbie 3 09-25-2006 09:28 AM
Slackware install not booting correctly (I think) FatherDrew Slackware - Installation 10 08-01-2006 03:46 PM
Booting Slackware 9.1 errors PhuckFonix Slackware 1 03-28-2004 01:20 PM
Lilo not working correctly after installing slackware. jpierce09 Slackware 5 07-15-2003 02:04 PM


All times are GMT -5. The time now is 06:10 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration