Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Gurus, this is one for you. What am I to do? I want to use the latest kernel, I've carefully studied the options when configuring it, I've checked and updated the dependancies, checked for errors when building it and it's modules, got none, installed it, and it still won't boot... The screen goes black after lilo has asked me to choose kernel to boot, and that is just sooo irritating. I cannot possibly suck so much that I fail six times in a row while following every imaginable tutorial and how-to there is on this subject. There has got to be some little option or configuration in the system I've overlooked.
Okay, I just realized something.... I have no rc.sysinit file what so ever... Is that file system specific (created automatically) or can I just use the contence of another linux box's rc.sysinit?
Ah, didn't know that. there was no rc.sysinit in slack. Yes, I did run lilo after copying the kernel and System.map to boot. And I did make appropriate changes to the lilo.conf.
Does any of this apply to me? The guy uses redhat, yes, but do I need to make similar changes in slack?
Last edited by NonSumPisces; 06-17-2004 at 11:13 AM.
Slackware 9.1 is "2.6 ready" so you can just plug in a 2.6 kernel and it will work, without upgrade module-init-tools and the like. I have compiled several 2.6 kernels for Slack 9.1 and just dropped 'em in and everything was fine. As someone else said, your issue is probably with the framebuffer. Go into your lilo.conf and see which framebuffer you have selected. Try the normal VGA framebuffer. This page might help.
Thx, the kernel will load, but it's DAMN slow. Is 1780kb big for a kernel? And oh, check out this , I ran into some, err, "minor" problems later on........................................ *many more dots*
The 2.4.26 kernel I built recently is about 1.2 MB (sadly my Slackware 9.1 box with a 2.6 kernel is still packed up as I am moving, or I would've checked it for you), so that kernel, while largeish, isn't overwhelmingly gigantic. What are the symptoms of the slowness? Is it slow in general or just doing one thing (like disk writes)? Check top to see if there's a user process or kernel thread eating lots of CPU and check vmstat to see if IO operations are slow for some reason. Without a few more details, it's going to be hard to diagnose exactly what is going on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.