SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
Originally posted by ringwraith Try commenting out or removing the change-rules and reset lines. You are telling lilo that you want the defaults removed that you are going to make your own rules, but then you don't make any.
i bet that's it. 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.
regarding initrd: i installed slack 10 using reiserfs and the default kernel, and booted lilo without having/needing initrd. 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 ).
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.
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.
Originally posted by ringwraith 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
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.