Projects / LILO / Comments

RSS Comments for LILO

09 Apr 2003 15:00 rheza

(another) [L 99 99 99 ... DISK BOOT FAILURE ... ] error
I'm having problems having LILO work. Basically, what I'm trying to do is load Slackware 9.0 using Windows NT's boot.ini

I've configured the boot.ini ok, and when I select Slackware from the choices, it'll go into LILO, but the L 99 99 99 ... DISK BOOT FAILURE INSERT.... shows up.

I have searched about this in google, tried out the solutions, including the one here, and having exhausted my options decided to also ask about it here.

My Linux installation resides at /dev/hda6 while my boot.ini file resides at /dev/hdc1

Anyway, here are the things you might want:

fdisk -l dev/hda
Device Boot Start End Blocks Id System
/dev/hda1 1 701 5630751 7 HPFS/NTFS
/dev/hda2 702 4997 34507620 f Win95 Ext'd (LBA)
/dev/hda5 702 1402 5630751 7 HPFS/NTFS
/dev/hda6 * 1403 1914 4112608+ 83 LInux
/dev/hda7 1915 2045 1052226 82 Linux Swap
/dev/hda8 2423 4997 20683656 b Win95 FAT32

fdisk -l dev/hdc
/dev/hdc1 * 1 702 5638783+ b Win95 FAT32
/dev/hdc2 703 4865 33439297+ f Win95 Ext'd (LBA)
/dev/hdc5 703 1212 4096543+ b Win95 FAT32
... (I don't think the rest are necessary)

Added SlackwareLinux*

# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hda6
#compact # faster, but won't work on all systems.
#timeout = 5
# 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 = /vmlinuz
root = /dev/hda6
label = SlackwareLinux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

/etc/lilo.conf (without most of the comments)
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hda6
vga = normal
image = /vmlinuz
root = /dev/hda6
label = SlackwareLinux

I've followed exactly what is written in
with regards to dual-booting
the dd ~~~, copying the bootsect.lnx, and editing boot.ini

Please help, thanks.

08 Apr 2003 19:25 murp

Can't boot on old machine
I've just installed Slackware 9.0 on an old AST P75 box, and LILO won't boot - I just get "L 40 40 40..." which I understand is a seek error.

The drive has 2099 cylinders, but the bios only lets me go up to 1023 - do I need to get a BIOS extender of some sort? Windows 95 used to be on this machine, and as far as I know it didn't need any other software to boot.



05 Apr 2003 16:15 johncoffman

Re: Report Bug
This is not a function of GCC, it is a function of the version of the C-library in use. Recently, "printf" was changed from a function to a macro. The syntax in question is legal for a function parameter list, but not for a macro parameter list. Quick fix: change "printf" to "fprint(stdout,". N.B. -- this has tripped me before. Sorry.

05 Apr 2003 11:38 yebo

Report Bug
1) Where do I report bugs?
2) Just upgraded to gcc 3.2.2 from 2.xsomthing
Now I get when building lilo 22.5.1 or 22.4.1
lilo.c:181:1: directives may not be used inside a macro argument
lilo.c:180:31: unterminated argument list invoking macro "printf"
lilo.c: In function `show_images':
lilo.c:182: parse error before "descrs"

I can compile lilo 22.0.2 w/o errors.

Do I need to patch gcc or lilo?

25 Mar 2003 10:26 johncoffman

Re: Where to report a bug?
Certain filesystems use the first sector of a partition as a superblock (just where a boot loader would be installed), among these are XFS, swap, NTFS, MSDOS. There may be others I don't know about. Since version 22.3, LILO checks for these "vulnerable" filesystems, and will not write a boot record there, unless "forced" (-F flag). Presumably, you are using a version of LILO that predates this check. With version 22, the "-x mbr-only" will avoid the superblock on RAID1 partitions. [Anyone knowing about other vulnerable filesystems, please alert the author -- as a community service. I'll be glad to add to the list of known problematic filesystems.]

25 Mar 2003 10:25 janfri

Versions, and more info 8D

Vanilla kernel 2.4.20 with xfs patch from SGI

lilo v22.2

Debian Woody 3.0r1

I hope it should be enough.


25 Mar 2003 10:07 janfri

Where to report a bug?
Hi all.
1st, now I am a happy user of lilo, and I've been using it since the slackware 2.0 to boot my linux boxes.
I write here to tell My very first problem: I was trying to set up a RAID1 boot device in /dev/md0, and, of course I've read the docs, so i've configurated lilo.conf as usual. But i've discovered that when I run lilo -v /mnt (where i've mounted my xfs filesystem which I want boot) xfs gets stuck and when the kernel tries to mount, panices saying that can't find /dev/md0. So (i think) lilo breaks the superblock of the xfs partition. I'd needed to xfs_repair the /dev/md0 partition before running lilo -v, and lilo has been able to boot the system... ¿is this a lilo bug or a xfs bug?
Comments and solutions, pleeeze ;)




17 Mar 2003 04:47 stuka1945

Re: "LI" error

> Hello Family,
> The issue is the system will boot FINE
> with the floppy but not from the
> standard startup UNLESS you softboot
> right after using the floppy..., then
> the computers LILO will work.
> Booting cold without the floppy gives
> you the "LI" error unless you
> reboot after using the floppy.
> This leads me to want to pipe the
> contents of the floppies data to the
> desktops MBR if that is possible, maybe
> a restore from the floppy to the mbr?
> Thanks

Hi Bill
Sometimes I have this problem ....
Boot from diskette an run the installed system as superuser, then run LILO. If u see the system don't have problems, reboot without diskette.


09 Mar 2003 08:36 johncoffman

Re: Odd booting problem.
A sensitivity of 22.5 to the video BIOS unexpectedly trashing the DX register has been tracked down on one system. The DX register contains the boot device code, so this is a fatal error. Symptoms were very similar to the two reports described here. It would be of great help if you contact the author directly, to see if you have the same or different problem. The e-mail address is easily generated from the project listing.

08 Mar 2003 18:53 remark

Re: Odd booting problem.
I have the same problem here. LILO 22.5 displays L 40 40 40
40 40 40 40 ..., but 22.4.1 works perfectly (the same for
older versions).

I have tried the Slackware current package and also have
compiled the sources, with the same result.

My BIOS supports LBA and has it enabled.

Here's my lilo.conf:

boot = /dev/hda

delay = 50

timeout = 50

vga = 0x0123



root = /dev/hda3


image = /boot/vmlinuz-2.4.21-pre5
label = 2421pre5
image = /boot/vmlinuz-2.4.21-pre4
label = 2421pre4
image = /boot/vmlinuz-2.4.21-pre3
label = 2421pre3
image = /boot/vmlinuz-2.4.21-pre2
label = 2421pre2
image = /boot/vmlinuz-2.4.21-pre1
label = 2421pre1
image = /boot/vmlinuz-2.4.20
label = 2420
image = /boot/vmlinuz-2.4.19
label = 2419
other = /dev/hda1
label = dos
table = /dev/hda




Project Spotlight


A Java XML editor.


Project Spotlight


A framework for secure peer-to-peer networking.