Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 06-06-2004, 01:01 PM   #1
Registered: Feb 2004
Location: Phuket
Distribution: Slackware 14.2 and Slackware Arm
Posts: 479

Rep: Reputation: 43
new to slackware, lilo won't boot but bootdisk is fine

Sorry to post what I am sure is a common question.

My first experiences with linux were RH9 and FC1, but for reasons I decided I want Slackware.

Got the disks, did the install, and everything is fine when I boot from a floppy but I cannot for the life of me get Lilo to boot my system.

my lilo.conf is

# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS

boot = /dev/hda
#compact # faster, but won't work on all systems.
timeout = 600
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz-ide-2.4.22
root = /dev/hda1
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
If I boot without a floppy I get L (top left) and then about 10 screens of 99.

I have searched and searched but none of the solutions worked for so far,

During the install I set up /, home and swap, output from cfdisk is

Partition Table for /dev/hda
         ---Starting---      ----Ending----    Start     Number of
 # Flags Head Sect Cyl   ID  Head Sect Cyl     Sector    Sectors
-- ----- ---- ---- ---- ---- ---- ---- ---- ----------- -----------
 1  0x80    1    1    0 0x83  239   63 1023          63    39054897
 2  0x00  239   63 1023 0x83  239   63 1023    39054960    78125040
 3  0x00  239   63 1023 0x82  239   63 1023   153150480     3144960
 4  0x00    0    0    0 0x00    0    0    0           0           0
Please note that my Slackware installation (somehow) started working after making these changes.

I still am not sure what I am doing, so sorry for wasting your time

Last edited by slackist; 06-06-2004 at 01:35 PM.
Old 06-06-2004, 06:08 PM   #2
LQ Guru
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,865

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
"lba32 # Allow booting past 1024th cylinder with a recent BIOS"

If you have a large hard drive and an old BIOS then the BIOS may not be able to address the entire drive. Linux only uses the BIOS during boot so if you have /boot beyond the BIOS addressing limit then lilo cannot find the kernel. If this happens to be your problem then the solution is to set up /boot as a small partition at the very beginning of the hard drive to guarentee that /boot in within the BIOS addressing range.

Another possibility is that you may have minor hardware incompatibilities among your hard drive, hard drive controller chipset, and BIOS. If that is the problem then you should switch to grub since grub handles such minor glitches better than lilo.

Be prepared. Create a LifeBoat CD.

Steve Stites
Old 06-06-2004, 09:43 PM   #3
Registered: Oct 2003
Location: Tx,USA
Distribution: Slackware, Red Hat, CentOS
Posts: 495

Rep: Reputation: 30
I assume this is the original conf file and your / is on the #1 partition, that s/b within the 1024. But if by some chance you put / on #2, lilo could very well be the problem. Anyway, I agree with jailbait and use grubs. That's my choice. Just boot on of the diskette and download and setup grubs. At one time had a package for slack. It's a mess the first time, and isn't to bad the forth or fifth time. Get it and come back here. Maybe post to the slackware forum.

or maybe a lilo 'pert will show up.


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
Slackware 10.0 - Direct Boot Fails, Cannot Create Linux Bootdisk Ffi Slackware - Installation 9 07-20-2004 06:48 AM
Slackware bootdisk - boot failed NeuroTox Linux - Newbie 2 10-13-2003 09:09 PM
Slackware wont boot /w bootdisk fooforon Slackware 5 09-02-2003 03:17 PM
Slackware bootdisk/LILO problem bleach Linux - Software 6 12-03-2001 09:48 AM
Made a bootdisk with RedHat 7.1 to boot: Gave me SYSLINUX, not LILO:Want to use LILO Colonel Panic Linux - Software 0 08-17-2001 07:21 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 11:17 AM.

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