upgraded to Slack Current a few days ago and everything was going
well. I haven't made any changes to my system files since then and
didn't install any new software yesterday. This morning I tried to
boot my machine and got the error message "LIL" when trying to load
LILO. I have LILO on my MBR and I don't run any other OS except linux.

The explanation for the LIL error is:

" LIL The second stage boot loader has been started, but it can't
load the descriptor table from the map file. This is typically caused
by a media failure or by a geometry mismatch."

I couldn't boot with the cd I made from "makerescue" but I was able
to boot with a Slax live cd. This morning I could get into the system
fine after booting (via root=/dev/hda3), but noticed that once I was
in, my hard drive was being recognized as
/dev/ide/host0/bus0/target0/lun0/ instead of hda3!! Other than that, I
could operate as "root" on /hd3. When I rebooted this evening, I
wasn't able to do that anymore. I can't access "root=/dev/hd3" at boot
time. The message I get back is that the kernel isn't available on
that partition. Nor is it available on
/dev/ide/host0/bus0/target0/lun0/part3.

I added a linear option to my lilo.conf file, but that didn't work. I
couldn't run /sbin/lilo from my position as "root" on the Slax live cd
because I didn't have proper permissions to the files on my hard drive
(how can I change this??)


This is from my lilo.conf file:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
linear
append = "hdc=ide-scsi"
boot = /dev/hda
#compact
install = /boot/boot.b
map = /boot/map
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# 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
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda3
label = Linux
read-only
# Linux bootable partition config ends



When I boot with the Slax live disk, my hda drive is no longer
recognized. Instead, it becomes /dev/ide/host0/bus0/target0/lun0/.
When I run /part3/sbin/lilo -v -v from that drive I get:

root@slax:/mnt/disc0part3# /sbin/lilo -v -v
LILO version 22.5.7.2, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2003 John Coffman
Released 20-Aug-2003 and compiled at 19:15:26 on Aug 25 2003.

Warning: LBA32 addressing assumed
raid_setup returns offset = 00000000 ndisk = 0
BIOS VolumeID Device
Reading boot sector from /dev/hda
pf_hard_disk_scan: ndevs=2
0300 3DB012B3 /dev/ide/host0/bus0/target0/lun0/disc
0800 2D6EE8C9 /dev/scsi/host1/bus0/target0/lun0/disc
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 0
device codes (canonical) = 3
Fatal: creat /boot/map~: Read-only file system

(The last "fatal" error is due to me running the program as "root" on
the Slax live cd and not as root on hda3).

The output I get from running fdisk -l as "root" on the Slax live cd
is :

Disk /dev/ide/host0/bus0/target0/lun0/disc: 40.0 GB, 40027029504
bytes
255 heads, 63 sectors/track, 4866 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/ide/host0/bus0/target0/lun0/part1 * 1 8 64259+ 83 Linux
/dev/ide/host0/bus0/target0/lun0/part2 9 138 1044225 82 Linux swap
/dev/ide/host0/bus0/target0/lun0/part3 139 4866 37977660 83 Linux

I tried to run /sbin/lilo -v -v -v >/boot/lilo.log
2>/boot/lilo.logerr from dev/ide/host0/bus0/target0/lun0/part3, but it
didn't work because I didn't have permission to write to the /boot
directory and I was unable to change this permission while logged on
as "root" on the Slax live cd. Is there some way that I can become
root on / on my hard drive so that I can change permissions to allow
me access to files and directories?

I entered the bios settings on my Dell Dimension 4500, but I didn't
see any information about the hard drive, so I can't tell if there is
a geometry mismatch or not.

I also have an external hard drive and CF card reader that the Slax
live cd also recognizes.

Any idea what I can try next? Fortunately, I have my system backed up
to my external hard drive. What else can try other than a complete
reinstall? What could suddenly be causing this error?

Thanks,
Lucinda

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is a highly unusual error. I've never personally encountered this
or heard of anyone else who did on any linux system, so please take the
below advice with that in mind. This is about half guess work.

In alt.os.linux.slackware, Lucinda dared to utter,
> The explanation for the LIL error is:
>
> " LIL The second stage boot loader has been started, but it can't
> load the descriptor table from the map file. This is typically caused
> by a media failure or by a geometry mismatch."

Pat yourself on the back for searching out that answer. Most people
just panic and come screaming here asking what's going wrong with LILO.
Typically when something like this suddenly crops up I expect hard ware
failure. You might want to try testing your hard drive to see if it
performs properly, or at least fsck those partitions.

> When I boot with the Slax live disk, my hda drive is no longer
> recognized. Instead, it becomes /dev/ide/host0/bus0/target0/lun0/.

Since Slax keeps recognizing it as that ide device instead of hda, why
don't you try booting off the slackware installation disk, or better
yet, then live disk (install disk 2) and see what it finds it as?

> When I run /part3/sbin/lilo -v -v from that drive I get:
> Fatal: creat /boot/map~: Read-only file system
> (The last "fatal" error is due to me running the program as "root" on
> the Slax live cd and not as root on hda3).

man lilo. Look for the -r option. Basically you need to run it as a
sort of chroot, so that it honors the hard drive root and not the ram
disk root.

> The output I get from running fdisk -l as "root" on the Slax live cd
> is :

Again, try this with either the slackware install disk or the slackware
live disk. See what you get back.

> Is there some way that I can become
> root on / on my hard drive so that I can change permissions to allow
> me access to files and directories?

man chroot

chroot /path/to/new/root /bin/bash

> I entered the bios settings on my Dell Dimension 4500, but I didn't
> see any information about the hard drive, so I can't tell if there is
> a geometry mismatch or not.

It's been my experience that the little tools Dell sends to test the
hardware are crap, but you might want to use one anyhow to test the
hard drive. If it returns a failure, you know where you problem lies.
Of course, I've had those utilities tell me everything was fine with a
SCSI hard drive that wasn't even spinning, so you're on your own there.

> Any idea what I can try next?

Yeah. Try recreating your device nodes by going into /dev on your hard
drive's root, and deletings all the hda entries, then running the
MAKEDEV script there. I can't gaurantee it'll work, but it's worth a
shot. (Might wanna backup those /dev files before you remove them.)

> Fortunately, I have my system backed up
> to my external hard drive.

There you go! Give yourself a sysadmin point. You should always have
good backups!

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAtUmoL3KiNGOqr6ERAu3uAKCVm/e5wqUeBSacYSrY6QmyaAuChACgvWCq
nAnWTgiyYHa7YJHJAbBV6Zw=
=vRRY
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Alan Hicks dared to utter,
> Yeah. Try recreating your device nodes by going into /dev on your hard
> drive's root, and deletings all the hda entries, then running the
> MAKEDEV script there.

Another thought, have you recompiled your kernel recently and included
devfs support? This looks like something that ugly shit would do. Look
here for pointers.

https://www.redhat.com/archives/linu.../msg00337.html

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAtUrPL3KiNGOqr6ERAh21AJ9JvGIUkjHY5stCVRSOto LidOiyMwCfRbDE
N2NLL2OleWgGIDOlCvYqu3k=
=38uQ
-----END PGP SIGNATURE-----

marketwatcher63@yahoo.com (Lucinda) wrote in message news:<b5dd2310.0405261533.78fd1d1d@posting.google. com>...
> upgraded to Slack Current a few days ago and everything was going
> well. I haven't made any changes to my system files since then and
> didn't install any new software yesterday. This morning I tried to
> boot my machine and got the error message "LIL" when trying to load
> LILO. I have LILO on my MBR and I don't run any other OS except linux.
>
> The explanation for the LIL error is:
>
> " LIL The second stage boot loader has been started, but it can't
> load the descriptor table from the map file. This is typically caused
> by a media failure or by a geometry mismatch."
>

I had problems with LILO and a new Giga-byte P4 MB. Tried
different settings in the BIOS and LILO didn't fix the problem.
Finally I tried 'nuni' and it boots no problem. nuni bypasses the
BIOS code and accesses the drives directly, I wish LILO would
incorporate it's code as an option. You can find nuni on freshmeat:

http://freshmeat.net/projects/nuni/

marketwatcher63@yahoo.com (Lucinda) wrote in message news:<b5dd2310.0405261533.78fd1d1d@posting.google. com>...
> upgraded to Slack Current a few days ago and everything was going
> well. I haven't made any changes to my system files since then and
> didn't install any new software yesterday. This morning I tried to
> boot my machine and got the error message "LIL" when trying to load
> LILO. I have LILO on my MBR and I don't run any other OS except linux.

> I couldn't boot with the cd I made from "makerescue" but I was able
> to boot with a Slax live cd. This morning I could get into the system
> fine after booting (via root=/dev/hda3), but noticed that once I was
> in, my hard drive was being recognized as
> /dev/ide/host0/bus0/target0/lun0/ instead of hda3!!

I noticed last week sometime that one of the slackware-current udev
upgrades came with an executable /etc/rc.d/rc.udev file. I have no
experience with udev whatsoever, but changing the device names you
are experiencing leads me to wonder if you are inadvertently running
(a possibly incompletely configured) udev since upgrading?

If so, then "chmod -x /etc/rc.d/rc.udev" might solve your problem.

Jeffrey

Lucinda wrote:

> upgraded to Slack Current a few days ago and everything was going
> well. I haven't made any changes to my system files since then and
> didn't install any new software yesterday. This morning I tried to
> boot my machine and got the error message "LIL" when trying to load
> LILO. I have LILO on my MBR and I don't run any other OS except linux.
>
> The explanation for the LIL error is:
>
> " LIL The second stage boot loader has been started, but it can't
> load the descriptor table from the map file. This is typically caused
> by a media failure or by a geometry mismatch."

IME it's typically caused by changing /boot/map without re-running lilo. Did
you by any chance try and install lilo on a floppy or something?
>
> I couldn't boot with the cd I made from "makerescue" but I was able
> to boot with a Slax live cd.

You're better off using the slackware install cd if you want to do real
system repair

> This morning I could get into the system
> fine after booting (via root=/dev/hda3), but noticed that once I was
> in, my hard drive was being recognized as
> /dev/ide/host0/bus0/target0/lun0/ instead of hda3!!

That's because slax uses devfs.

> Other than that, I
> could operate as "root" on /hd3. When I rebooted this evening, I
> wasn't able to do that anymore. I can't access "root=/dev/hd3" at boot
> time. The message I get back is that the kernel isn't available on
> that partition. Nor is it available on
> /dev/ide/host0/bus0/target0/lun0/part3.
>
> I added a linear option to my lilo.conf file, but that didn't work. I
> couldn't run /sbin/lilo from my position as "root" on the Slax live cd
> because I didn't have proper permissions to the files on my hard drive
> (how can I change this??)


Slax mounts hard disks read-only. umount /mnt/disc0part3, mount -o
rw /mnt/disc0part3 should do it. Remember to chroot into it when running
lilo
>
>
> This is from my lilo.conf file:
>
> # LILO configuration file
> # generated by 'liloconfig'
> #
> # Start LILO global section
> linear
> append = "hdc=ide-scsi"
> boot = /dev/hda
> #compact
> install = /boot/boot.b

That doesn't seem right. I thought slack didn't use boot.b

> map = /boot/map
> message = /boot/boot_message.txt
> prompt
> timeout = 1200
> # Override dangerous defaults that rewrite the partition table:
> change-rules
> reset
> # VESA framebuffer console @ 1024x768x256
> vga = 773
> # 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
> # End LILO global section
> # Linux bootable partition config begins
> image = /boot/vmlinuz
> root = /dev/hda3
> label = Linux
> read-only
> # Linux bootable partition config ends
>
>
>
> When I boot with the Slax live disk, my hda drive is no longer
> recognized. Instead, it becomes /dev/ide/host0/bus0/target0/lun0/.
> When I run /part3/sbin/lilo -v -v from that drive I get:
>
> root@slax:/mnt/disc0part3# /sbin/lilo -v -v
> LILO version 22.5.7.2, Copyright (C) 1992-1998 Werner Almesberger
> Development beyond version 21 Copyright (C) 1999-2003 John Coffman
> Released 20-Aug-2003 and compiled at 19:15:26 on Aug 25 2003.
>
> Warning: LBA32 addressing assumed
> raid_setup returns offset = 00000000 ndisk = 0
> BIOS VolumeID Device
> Reading boot sector from /dev/hda
> pf_hard_disk_scan: ndevs=2
> 0300 3DB012B3 /dev/ide/host0/bus0/target0/lun0/disc
> 0800 2D6EE8C9 /dev/scsi/host1/bus0/target0/lun0/disc
> device codes (user assigned pf) = 0
> device codes (user assigned) = 0
> device codes (BIOS assigned) = 0
> device codes (canonical) = 3
> Fatal: creat /boot/map~: Read-only file system
>
> (The last "fatal" error is due to me running the program as "root" on
> the Slax live cd and not as root on hda3).

Or it could be due to the hard disk being mounted read-only. Anyway, remount
it readwrite and then chroot into it to run /sbin/lilo
>
> The output I get from running fdisk -l as "root" on the Slax live cd
> is :
>
> Disk /dev/ide/host0/bus0/target0/lun0/disc: 40.0 GB, 40027029504
> bytes
> 255 heads, 63 sectors/track, 4866 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/ide/host0/bus0/target0/lun0/part1 * 1 8 64259+ 83 Linux
> /dev/ide/host0/bus0/target0/lun0/part2 9 138 1044225 82 Linux swap
> /dev/ide/host0/bus0/target0/lun0/part3 139 4866 37977660 83 Linux
>
> I tried to run /sbin/lilo -v -v -v >/boot/lilo.log
> 2>/boot/lilo.logerr from dev/ide/host0/bus0/target0/lun0/part3, but it
> didn't work because I didn't have permission to write to the /boot
> directory and I was unable to change this permission while logged on
> as "root" on the Slax live cd. Is there some way that I can become
> root on / on my hard drive so that I can change permissions to allow
> me access to files and directories?

The problem isn't the permissions, it's that the drive is mounted read-only.
>
> I entered the bios settings on my Dell Dimension 4500, but I didn't
> see any information about the hard drive, so I can't tell if there is
> a geometry mismatch or not.

I doubt it. If it's still failing after rebooting, come back.
>
> I also have an external hard drive and CF card reader that the Slax
> live cd also recognizes.
>
> Any idea what I can try next? Fortunately, I have my system backed up
> to my external hard drive. What else can try other than a complete
> reinstall? What could suddenly be causing this error?

First thing is to properly re-run lilo

Alan Hicks wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, Alan Hicks dared to utter,
>> Yeah. Try recreating your device nodes by going into /dev on your hard
>> drive's root, and deletings all the hda entries, then running the
>> MAKEDEV script there.
>
> Another thought, have you recompiled your kernel recently and included
> devfs support? This looks like something that ugly shit would do. Look
> here for pointers.
>
> https://www.redhat.com/archives/linu.../msg00337.html

The Slax kernel uses devfs, that's what it sounds like is causing it.

kevin360@yahoo.com (Kevin) wrote in message

> I had problems with LILO and a new Giga-byte P4 MB. Tried
> different settings in the BIOS and LILO didn't fix the problem.
> Finally I tried 'nuni' and it boots no problem. nuni bypasses the
> BIOS code and accesses the drives directly, I wish LILO would
> incorporate it's code as an option. You can find nuni on freshmeat:
>
> http://freshmeat.net/projects/nuni/

Thanks Kevin. I'm a real newbie...I've only been playing around with
Slack, Linux and OS's for about a month. I'm taking a look at the
program you suggested. Are the install instructions really as easy as
follows?

Installation instructions:

(1) put the nuni-0.08.tar.gz file in a convenient place
(2) tar zxf nuni-0.08.tar.gz
(3) cd nuni-0.08
(4) ./c (this is a script with a gcc command in it)

Configuration and installation instructions (for nuni):

(1) cd /path/nuni-0.08
(2) edit nuni to set the following items:
(a) path to kernel image <----------------So this would be
/boot/vmlinuz??
(b) target partition for installing the boot loader
<--------/dev/hda3??
(c) command line for kernel <---------Do I need one if I haven't
been passing any special paramters to the kernel??
(3) ./nuni


And I am assuming that I don't need to install nunimbr.asm since I
have only Linux on my system.

Are my assumptions correct? I just want to make sure before I try
this. If this doesn't work, can I just continue to boot with my
Syslink disk? Should I try GRUB as an alternate to LILO? This is
quite annoying. I can understand having problems if this were a new
installation, but I was fine up until yesterday. Strange.

Cheers,
Lucinda

Thanks, everyone, for your input. You've given me a lot of good ideas
to pursue. Here's where I'm at today, so please bear with me.

I haven't been able to get makebootdisk to make a proper LILO boot
disk for me (maybe the files are too big?), but I managed to find an
old Syslink boot disk that I could boot with. I used this to get into
my system and create a new Syslink boot disk with my new kernel. I
can boot up my system NO PROBLEM with the Syslink boot disk.
Everything looks and functions as it should. But I don't want to be
relegated to booting off a floppy for the rest of my life...

So it looks like my hard drive itself is fine.

I then tried this:
lilo -u /dev/hda

followed by lilo and rebooted, but I had no luck.

I then used "hdparm" to see how linux sees my hard drive and got these
results:
hdparm -g /dev/hda

/dev/hda:
geometry = 4866/255/63, sectors = 78177792, start = 0

So it is seeing 4866 cylinders, 255 heads and 63 sectors.

I then ran "/sbin/lilo -v -v -v >/boot/lilo.log 2>/boot/lilo.logerr"
and got nothing back in the .logerr file (good) and the .log file
produced this for lilo:

******************************************

raid_setup returns offset = 00000000 ndisk = 0
BIOS VolumeID Device
Reading boot sector from /dev/hda
pf_hard_disk_scan: ndevs=1
0300 3DB012B3 /dev/hda
Resolve invalid VolumeIDs
Resolve duplicate VolumeIDs
0300 3DB012B3 /dev/hda
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 0
Filling in '/dev/hda' = 0x80
device codes (canonical) = 1
Device 0x0300: BIOS drive 0x80, 255 heads, 4866 cylinders,
63 sectors. Partition offset: 0 sectors.
Using serial number 3DB012B3 on bios 80
Device 0x0303: BIOS drive 0x80, 255 heads, 4866 cylinders,
63 sectors. Partition offset: 2216970 sectors.
Using serial number 3DB012B3 on bios 80
Warning: Unable to determine video adapter in use in the present
system.
Using MENU secondary loader
Calling map_insert_data
Secondary loader: 17 sectors (0x3200 dataend).
bios_boot = 0x80 bios_map = 0x80 map==boot = 0 map S/N: 3DB012B3
Mapping message file /boot/boot_message.txt
Device 0x0303: BIOS drive 0x80, 255 heads, 4866 cylinders,
63 sectors. Partition offset: 2216970 sectors.
Using serial number 3DB012B3 on bios 80
Calling map_insert_file
Message: 1 sector.
BIOS data check will include auto-suppress check

Boot image: /boot/vmlinuz -> vmlinuz-ide-2.4.26
Device 0x0303: BIOS drive 0x80, 255 heads, 4866 cylinders,
63 sectors. Partition offset: 2216970 sectors.
Using serial number 3DB012B3 on bios 80
Setup length is 10 sectors.
Mapped 2457 sectors.
Added Linux *
<dev=0xc0,hd=54,cyl=122,sct=29>
"ro root=303 hdc=ide-scsi"

BIOS VolumeID Device
80 3DB012B3 0300
Writing boot sector.
/boot/boot.0300 exists - no boot sector backup copy made.
Map file size: 26624 bytes.
RAID device mask 0x0000
Failsafe check: boot_dev_nr = 0x0300 0xffc0

************************************************** ********

which seems to indicate that lilo is seeing the same hard drive
geometry as linux (i.e. 4866/255/63).

I didn't see any obvious errors in dmesg after booting with the
Syslink boot disk, and the part relevant to hda is shown as:

************************************************** ********

hda: MAXTOR 6L040J2, ATA DISK drive
blk: queue c03b73e0, I/O limit 4095Mb (mask 0xffffffff)
hdc: LITE-ON LTR-24102M, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 78177792 sectors (40027 MB) w/1819KiB Cache, CHS=4866/255/63,
UDMA(100)
hdc: attached ide-cdrom driver.
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Partition check:
hda: hda1 hda2 hda3
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 2288.400 MB/sec
32regs : 1466.800 MB/sec
pIII_sse : 2562.400 MB/sec
pII_mmx : 2286.000 MB/sec
p5_mmx : 2261.200 MB/sec
raid5: using function: pIII_sse (2562.400 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.8(17/11/2003)
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device ide0(3,3)) ...
for (ide0(3,3))
ide0(3,3):Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 120k freed
Adding Swap: 1044216k swap-space (priority -1)
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 690M
agpgart: Detected Intel i845 chipset
agpgart: AGP aperture is 64M @ 0xf8000000
scsi0 : SCSI host adapter emulation for IDE ATAPI devices

************************************************** *******

I have to admit, I don't know how to interpret the dmesg results. Any
obvious problems there?

And I did add LBA32 to my lilo.conf which is supposed to allow lilo to
bypass any cylinder limits on the hard drvie, but that didn't work
either.

I don't understand why lilo doesn't like the hard drive. Like I've
said, it's worked fine, I made no changes to lilo and then suddenly
the "LIL"... message popped up. Maybe I should consider using a new
loader (i.e. GRUB?). Or will doing something with "udev" help?

Thanks for your help,
Lucinda

> I have to admit, I don't know how to interpret the dmesg results. Any
> obvious problems there?

None that I saw
>
> And I did add LBA32 to my lilo.conf which is supposed to allow lilo to
> bypass any cylinder limits on the hard drvie, but that didn't work
> either.

Adding linear might be worth a shot.
>
> I don't understand why lilo doesn't like the hard drive. Like I've
> said, it's worked fine, I made no changes to lilo and then suddenly
> the "LIL"... message popped up. Maybe I should consider using a new
> loader (i.e. GRUB?). Or will doing something with "udev" help?
>
Udev won't make any difference, but you may find it easiest to install grub
rather than trying to get lilo working.