If anyone cares... the solution was that I created the wrong symlink to
vmlinuz -> System.map-ide-2.4.26
it should have been vmlinuz -> vmlinuz-ide-2.4.26.
----- Original Message -----
From: "Aaron Steimle" <asteimle@washpat.com>
To: <slug@nks.net>
Sent: Sunday, August 22, 2004 9:58 PM
Subject: [SLUG] lilo error on slackware 10
> I switch to Slackware 10. FWIW I was able to install KDE 3.3. (don't
> use konstruct, do it manually itsfaster and works)
>
> I am in the process of installing the 2.6.7 kernel that comes with
> Slackware 10. It doesn't give option to install so you have to do it
> separately.
> I followed the following steps:
>
> ----------------------------------------------------------
> installpkg kernel-generic-2.6.7-i486-3.tgz
> installpkg kernel-modules-2.6.7-i486-2.tgz
> cd /boot
> mkinitrd -c -k 2.6.7 -m reiserfs
> ----------------------------------------------------------
>
> I the made commented out changed in below lilo.conf file ( option to
> boot to 2.6.7 or old kernel)
> After blowing the process and not being able to boot. I took a closer
> look at the /boot directory before and after running mkinitrd. In my
> infinite wisdom I didn't save file that had the changes after I ran
> mkinitrd. Below is the before listing and what it is currently.
>
> What you can't see it that after running mkinitrd it changed the link of
> System.map to System.map-generic-2.6.7, config to config-generic-2.6.7,
> and vmlinuz to vmlinuz-generic-2.6.7. Afraid for my system, again, I
> decided to change the links to the original configuration. Knowing I
> will be pointing to them anyway in the lilo.conf file.
>
> Also, I have one disk hda1 with reiserfs and only one mount point /. ( I
> know, I know, I wasn't paying attention and didn't partition it up)
>
> after making the changes to lilo.conf I ran the lilo command and I get
> this error:
> --------------------------------------------------------------------------
---------------------------------------
> Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot
> loader
> --------------------------------------------------------------------------
---------------------------------------
> I get this error with and without then new changed in the file.
>
> Any ideas on what to try? I have been unable to find any real help online.
>
>
>
>
>
>
>
> --------------------------------------------------------------------------
-----------
> # 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 @ 800x600x64k
> vga = 773
>
> # End LILO global section
> # Linux bootable partition config begins
> image = /boot/vmlinuz
> root = /dev/hda1
> label = Linux
> read-only
>
> #image = /boot/vmlinuz-generic-2.6.7
> # initrd = /boot/initrd.gz
> # root = /dev/hda1
> # label = Linux267
> # read-only
> # Linux bootable partition config ends
> --------------------------------------------------------------------------
-------
> BEFORE:
>
> README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
> System.map -> System.map-ide-2.4.26
> System.map-ide-2.4.26
> boot.0300
> boot_message.txt
> config -> config-ide-2.4.26
> config-ide-2.4.26
> diag1.img
> map
> vmlinuz -> vmlinuz-ide-2.4.26
> vmlinuz-ide-2.4.26
> --------------------------------------------------------------------------
--------
> AFTER:
>
> README.initrd -> /usr/doc/mkinitrd-1.0.1/README.initrd
> System.map -> System.map-ide-2.4.26
> System.map-generic-2.6.7
> System.map-ide-2.4.26
> boot.0300
> boot_message.txt
> config -> config-ide-2.4.26
> config-generic-2.6.7
> config-ide-2.4.26
> diag1.img
> initrd-tree/
> initrd.gz
> map
> vmlinuz -> System.map-ide-2.4.26
> vmlinuz-generic-2.6.7
> vmlinuz-ide-2.4.26
>
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 15:22:21 EDT