LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   LILO 'Floating point Exception' error? (http://www.linuxquestions.org/questions/slackware-14/lilo-floating-point-exception-error-317481/)

fallout 04-26-2005 06:39 PM

LILO 'Floating point Exception' error?
 
I can not find any information on an error msg i am getting with lilo... If I try to run 'lilo' as root I get a floating point exception error. Does anyone know what would cause this? I'm using the bare Kernel included with the 10.1 stable release. I'll also add that I am using the reiser FS system.. What would be the first thing to check in order to troubleshoot this? Any help is appreciated!

-Jay

mdarby 04-26-2005 06:44 PM

Could you post your lilo.conf?
Have you tried to reinstall the lilo package?

fallout 04-26-2005 07:05 PM

Yes, I've uninstalled it with removepkg and reinstalled it.. Here's my lilo.conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
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/hda2
  label = Linux
  read-only
# Linux bootable partition config ends

Thanks for your reply!

-Jay

mdarby 04-26-2005 07:14 PM

hmm.. this is an interesting one...
Are you sure root= is pointing to the right partition?
What did you do that you'd need to reinstall lilo?

fallout 04-26-2005 07:48 PM

Yep, root is hda2.. hda1 is my swap partition... I didnt do anything where i'd 'NEED' to run lilo. However, I'm a total linux newbie trying to learn things.. So i'm doing a bunch of reading and trying to do things like compiling a kernel, figuring out anomalies in log files, etc. So far i've been fairly successful! A lot of instructions i've read mention running /sbin/lilo and i've been able to mess around on my PC at work (running Windows) using vmware and had no troubles running lilo in a virtual machine.. The only difference in the install was that i used the Reiser file system on my actual PC at home (fresh installation, no vmware) and I used ex3 on the 'virtual' box.. I have no idea what would cause this type of error.. Not sure if it would be of any help, here's my fstab:

Code:

/dev/hda1        swap            swap        defaults        0  0
/dev/hda2        /                reiserfs    defaults        1  1
/dev/hda3        /usr            reiserfs    defaults        1  2
/dev/hda4        /home            reiserfs    defaults        1  2
/dev/cdrom      /mnt/cdrom      iso9660    noauto,owner,ro  0  0
/dev/fd0        /mnt/floppy      auto        noauto,owner    0  0
devpts          /dev/pts        devpts      gid=5,mode=620  0  0
proc            /proc            proc        defaults        0  0

I'll also mention that i have been using the full installation (3GB?) from the 10.1 CDs minus Gnome as well as the bare ide kernel. I'm running an Athlon64 3200+ on a SIS based mobo. However, I'm not using the 64bit version of Slack, nor do I really want to at this point. Any other log or config files I can investigate? Thanks for all the help! :study:

-Jay

mdarby 04-26-2005 08:02 PM

/var/log/syslog would be the place to check.

From what I can tell you've done nothing wrong. Could you attempt to rerun lilo and then post the output from:
Code:

tail -n 100 /var/log/syslog

fallout 04-26-2005 08:29 PM

Here what I get... I've been getting these errors in my syslog both times i've installed slack 10.1. Not very illuminating being that 'Apr 26 20:47:40' was approx. 30 minutes BEFORE running the 'lilo' command! I'll also add that i have reinstalled slack from scratch once but I did leave the /home partition untouched.. I formatted the swap, root and usr partitions. I didnt reformat it and kept my existing 'user' data.. I wouldnt think this would make a difference.. I'm stumped.. Any other suggestions?

-Jay

Code:

user@station:~$ su
Password:

root@station:/home/user# lilo
Floating point exception

root@station:/home/user# tail -n 100 /var/log/syslog
Apr 26 19:16:07 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: init_module: Input/output error
Apr 26 19:16:07 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, includinginvalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 19:16:07 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: insmod block-major-18 failed
Apr 26 19:16:07 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: init_module: Input/output error
Apr 26 19:16:07 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 19:16:07 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: insmod block-major-32 failed
Apr 26 19:28:53 station kernel: Did not find a Sony CDU-535 drive
Apr 26 19:28:53 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: init_module: Input/output error
Apr 26 19:28:53 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 19:28:53 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: insmod block-major-24 failed
Apr 26 19:29:58 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 19:29:58 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 19:29:58 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 19:31:03 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 19:31:03 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 19:31:03 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 19:32:08 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 19:32:08 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 19:32:08 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 19:33:14 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 19:33:14 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 19:33:14 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 19:34:19 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 19:34:19 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 19:34:19 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 19:34:19 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cdu31a.o.gz: init_module: Input/output error
Apr 26 19:34:19 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cdu31a.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 19:34:19 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cdu31a.o.gz: insmod block-major-15 failed
Apr 26 19:34:23 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/mcd.o.gz: init_module: Input/output error
Apr 26 19:34:23 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/mcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 19:34:23 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/mcd.o.gz: insmod block-major-23 failed
Apr 26 19:34:33 station kernel: Trying to free nonexistent resource <00000340-00000343>
Apr 26 19:34:33 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: init_module: Input/output error
Apr 26 19:34:33 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, includinginvalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 19:34:33 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: insmod block-major-18 failed
Apr 26 19:34:33 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: init_module: Input/output error
Apr 26 19:34:33 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 19:34:33 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: insmod block-major-32 failed
Apr 26 19:58:32 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: init_module: Input/output error
Apr 26 19:58:32 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 19:58:32 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: insmod block-major-24 failed
Apr 26 19:58:32 station kernel: Did not find a Sony CDU-535 drive
Apr 26 19:59:37 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 19:59:37 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 19:59:37 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 19:59:44 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: init_module: Input/output error
Apr 26 19:59:44 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 19:59:44 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: insmod block-major-24 failed
Apr 26 19:59:44 station kernel: Did not find a Sony CDU-535 drive
Apr 26 20:00:42 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:00:42 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:00:42 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:01:47 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:01:47 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:01:47 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:02:52 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:02:52 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:02:52 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:28:45 station kernel: Did not find a Sony CDU-535 drive
Apr 26 20:28:45 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: init_module: Input/output error
Apr 26 20:28:45 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 20:28:45 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: insmod block-major-24 failed
Apr 26 20:29:50 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:29:50 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:29:50 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:30:55 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:30:55 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:30:55 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:42:00 station kernel: Did not find a Sony CDU-535 drive
Apr 26 20:42:00 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: init_module: Input/output error
Apr 26 20:42:00 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 20:42:00 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sonycd535.o.gz: insmod block-major-24 failed
Apr 26 20:43:05 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:43:05 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:43:05 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:44:10 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:44:10 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:44:10 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:45:15 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:45:15 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:45:15 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:46:20 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:46:20 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:46:20 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:47:25 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: init_module: Input/output error
Apr 26 20:47:25 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:47:25 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sbpcd.o.gz: insmod block-major-25 failed
Apr 26 20:47:25 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cdu31a.o.gz: init_module: Input/output error
Apr 26 20:47:25 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cdu31a.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 20:47:25 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cdu31a.o.gz: insmod block-major-15 failed
Apr 26 20:47:30 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/mcd.o.gz: init_module: Input/output error
Apr 26 20:47:30 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/mcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 20:47:30 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/mcd.o.gz: insmod block-major-23 failed
Apr 26 20:47:40 station kernel: Trying to free nonexistent resource <00000340-00000343>
Apr 26 20:47:40 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: init_module: Input/output error
Apr 26 20:47:40 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: Hint: insmod errors can be caused by incorrect module parameters, includinginvalid IO or IRQ parameters.      You may find more information in syslog or the output from dmesg
Apr 26 20:47:40 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/sjcd.o.gz: insmod block-major-18 failed
Apr 26 20:47:40 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: init_module: Input/output error
Apr 26 20:47:40 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.      You may find more information in syslog orthe output from dmesg
Apr 26 20:47:40 station insmod: /lib/modules/2.4.29/kernel/drivers/cdrom/cm206.o.gz: insmod block-major-32 failed
root@station:/home/user#


mdarby 04-27-2005 05:48 AM

hmm...

I'm drawing a blank on this one. Was the syslog portion posted above taken right after attempting to rerun lilo?

Did you opt to install lilo to the MBR or to the bootblock of you root partition?

fallout 04-27-2005 10:49 AM

Hey, thanks again! The output of syslog was taken immediately after running the 'lilo' command.. I opt'd to install lilo to the MBR.. Was this a mistake?

-Jay

Matir 04-27-2005 11:05 AM

There have been (at least in the Gentoo community, not sure about slackware) a number of issues with lilo and 64 bit systems. In gentoo, where everything is usually compiled locally, the 64 bit version uses a 32 bit binary instead. Are you installing a binary or from source?

mdarby 04-27-2005 11:23 AM

I normally install lilo to the MBR (easier, IMHO).

fallout 04-27-2005 12:26 PM

Hi Matir... Actually, I have a 64bit CPU but i'm running the 32bit version of Linux.. I installed LILO with the official slackware package on the 10.1 install CDs... I'm at a complete loss...

-Jay

mdarby 04-27-2005 12:34 PM

It must have something to do with the 32/64 mismatch. The oddness of the problem (and the lack of past issues) is screaming *hardware issue*.

Of couse, I could be speaking through my ass too.

Matir 04-27-2005 01:04 PM

The irony of all this is that I can't even think of ONE reason for lilo to use floating point operations...

The following thread may help explain: http://os.newsforge.com/comments.pl?...672&cid=109868

I'd like to be able to refer you to the proper Gentoo bug, but apparently the bugs.gentoo.org bugzilla server is down at the moment.

esp 07-07-2005 11:51 PM

Ok, I'm having the same problem. Here's how I got there - my server runs Slackware, approximately version 9. I decided to use that server as a print server in addition ot its normal tasks, which meant I needed to add parallel port support to the kernel.

So, since I was still using kernel 2.6.7, I decided to get a new kernel, so off to kernel.org, got a nice shiny 2.6.12.2. make oldconfig, make menuconfig, make modules_install, copied my new kernel to my boot partition, added the entry to /etc/lilo.conf, and ran lilo. Floating point exception. darn.

Seems this has happened to others, and nothing much is out there on actually solving it. I tried taking the new entry out of lilo.conf, still no luck. Tried uninstalling and reinstalling lilo package. nothing.

Then I decided to try grub. But, grub seems to require BIOS detection of hard drives. My poor outdated BIOS won't properly detect my new 160GB slave hard drives, so no luck with that option at all, just an Error 21!

So, it looks like I need to get lilo working.

here's a lilo.conf:

Code:

# LILO configuration file
boot = /dev/hda
prompt
timeout = 40
default = Linux-2.6.7

image = /boot/linux-2.6.7
  root = /dev/hda3
  label = Linux-2.6.7
  read-only

image = /boot/linux-2.6.12.2
  root = /dev/hda3
  label = Linux-2.6.12.2
  read-only

and fstab:

Code:

/dev/hda1  /boot      ext2    noauto,noatime  1  1
/dev/hda2  none      swap    sw              0  0
/dev/hda3  /          ext3    noatime          0  0
/dev/hda4  /var      ext3    noatime          0  0
/dev/hdb1  /public    ext3    noatime,rw      0  0
/dev/hdd1  /media    reiserfs noatime,rw      0  0
/dev/cdrom  /cd        iso9660  noauto,ro,users  0  0
devpts      /dev/pts  devpts  gid=5,mode=620  0  0
proc        /proc      proc    defaults        0  0

hda is a 20G WD drive, hdb is an 80G WD drive, and hdd is a 160G Maxtor drive. This is an old K62-400 based system, and bios is set to only detect hda and the CDRom.

Nothing is being written to syslog.

Any help is appreciated.


All times are GMT -5. The time now is 05:31 AM.