There seems to also be some continuing confusion on the initrd business. The Slackware 2.6.7 kernel that came with 10.0 has no filesystems compiled in other than ext2. So I assume the elegin was following Pat's instructions which were IF you had another filesystem then you had to mkinitrd and add the line to lilo. So if that is what he did, he absolutely has to have the line in lilo. The kernel can not boot without it.

i bet that's it. :cool: i was thinking about taking that line out when i pasted his lilo.conf from above, but seeing the "dangerous" there made me scared to. :p

regarding initrd: i installed slack 10 using reiserfs and the default kernel, and booted lilo without having/needing initrd. :confused: are you saying running mkintrd itself creates the need for initrd? i guess i don't get the initrd thing (which is probably why i don't use it :scratch: ).

I removed change-rule and reset and I still get the same error.

If I uninstall lilo i might as well install grub. I only want to do that as the last option.

elegin, run "fdisk -l" as root, and give us the output, please.

synaptical, if you are booting the 2.6.7 kernel that comes in testing on disc 3, then you should have to use an initrd to boot.
ftp://ftp.slackware.at/slackware-10..../README.initrd

Think I finally figured it out. This was in your after section cited:

vmlinuz -> System.map-ide-2.4.26

Don't look like a bootable kernel to me. You need to change that symlink to point vmlinuz to the kernel you want to boot.

I can't boot to the new kernel becuase I can't make changes to Lilo.conf without lilo give me the error.



fdisk -l

Disk /dev/hda: 30.7 GB, 30750031872 bytes
255 heads, 63 sectors/track, 3738 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 3484 27985198+ 83 Linux
/dev/hda2 3485 3738 2040255 82 Linux swap

elegin- did you check the symlink that I listed above. In your original post you show that as the after link in /boot. That would be incorrect you need to delete that link and create a new one point vmlinuz to the 2.4.26 kernel.

SOVLED
 

ringwraith

You were right. I had created wrong symlink.
I am glad that is solved.
Now when someone googles that error they should see this thread and look at their symlinks.

Thank you ringwraith.

my mistake -- i compiled 2.6.7 myself come to think of it, so that must be the reason. i just installed it on roommate's machine to test and haven't messed around with it much. thanks for the info -- now i'll know never to use the slack 10 2.6.7 kernel to avoid all the initrd nastiness. :p

Hi elegin!
I had the same problem and solved it by taking the bzImage instead of the vmlinux.bin for my image.It seems that the alert:
Fatal:setup length exceeds 31 maximum....
refers to the image size.

Good Luck,
jff