Kernel 220.127.116.11 make modules_install returns error
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
framebuffer console support module. if you don't use a framebuffer console ( if you use lilo with the "normal" display, not one like 800x600x 64k colors) then it's ok. otherwise, if you want the framebuffer console, you'll need to resolve the symbol ( find out where it is supposed to come from, probably another module) first.
So now I need to know which additional module I need to install, since I use the framebuffer console...
And all this trouble just to get a lilo bootsplash working
First I tried just to recompile the 2.4.29-kernel after applying a patch to it (that was for the wrong kernel, but the website said to choose the closest match). This resulted in errors when compiling modules, as I expected. Then I tried with the 18.104.22.168 kernel, and the closest matching patch, which also resulted in errors (as expected), but then I tried to compile the 2.6 kernel without the patch (deleted the folder and extracted from .bz2 again) and no errors when running "make modules" but then this happened when running "make modules_install"...
This is my first kernel compilation, because I always thought it was too much trouble recompiling a kernel, and apparently, I was right...
Anyone know a simple way to get Lilo Bootsplash working on slackware 10.1, with the 2.4.29 or 22.214.171.124 kernel?
I still can't boot the new kernel, I must have put some bat choises, and now not even the 2.4.29 kernel work :S It stops at activatng hotplug, after saying there is some problem with agpgart..
Kernel 2.6 stops with kernel panik: can't mount root filesystem. This is pretty bad. I think I'll have to reinstall the 2.4 kernel, but I don't know how to do that without a slackware reinstall... I have a working knoppix cdrom, so it should be bossible. I'll just have to try something...
kernel panic: Unable to mount root filesystem - this usually means either your bootloader configuration is wrong or ( more likely, it's easy to overlook -->) you either didn't compile support for your filesystem or compiled it as a module and are not using an initrd. (if you are not using an initrd your filesystem will have to be compiled directly into the kernel, because the boot routine has not had a chance to load any modules before it mounts your root filesystem).
for rebooting your old install, recompiling a new kernel shouldn't have any impact on your 2.4.29 kernel. if you want to turn hotplug off to do some troubleshooting, repair:
install your slack cd ( the 1st cd) and boot off of it, don't boot your install just hit enter like you are going to install
next go into the setup and configure the target to match your installed system, then go down to configure system and say no to hotplug being enabled at boot. whenever you get your system fixed, run pkgtool to undo the change and have hotplug start at boot again.
OK, removed the 2.6 kernel, reinstalled the 2.4 kernel and recompiled after copying the .config from the slackware cdrom, and now slack works again. I couldn't copy the config before, 'cause I installed from a cuple of RWs (alredy had the 10.0 on R-cd) that I had erased (and didn't keep the ISOs), but I redownloaded the ISOs (was prepared for a complete reinstall) and now it seems to work. I'll have to try to get the splash thing working now.