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.
It is becoming increasingly apparent that the Linux kernel 2.6 is not yet ready for mass consumption. This is especially true for many desktop systems, where a large variety of hardware combination often means that a certain piece of hardware that worked fine under 2.4 is no longer operational under 2.6. Most major distributions deploy various kernel patches to address some of the issues; however the patches have potential to introduce new bugs into the kernel.
So when will the new kernel be ready? One interesting indication of its acceptance for general deployment is Slackware's "current" branch. Once the new kernel is in Slackware "current", we know that there is enough confidence by the Slackware developers (who have more than 10 years of development experience), to impose the new kernel on any system. The reason for this is simple - Slackware Linux is the only major distribution that uses the original kernel without any patches. If Slackware "current" still does not have the 2.6 kernel (despite the fact that the distribution's 9.1 release was declared "kernel 2.6 ready"), then we know that it still has plenty of unresolved issues.
This is not to say that the kernel 2.6 is unusable - there are undoubtedly many people who use it without any trouble. But if you happen to have some unlucky hardware, you'll be better off with kernel 2.4 for the time being.
I had perfect success with kernel 2.6 and slackware. I think they haven't included it as it still needs a little testing and refinement for all users. Some have more problems with it then others.
And if you see no difference then something is wrong. I notice a good 20% increase of performance between standarc 2.4 and kernel 2.6.4-ck1
Last edited by Crazy Travis; 03-24-2004 at 05:17 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.