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.
I would have posted this to the "Kernel compiling for newbies," but the thread is closed....Running Slack 9.0 with Dropline Gnome on an AMD Athlon XP 2000+. Compiled kernels before on this system and I don't have any problems with that, I have problems with performance of the custom kernels. The stock Slack kernel is faster than the "custom" ones I configure, even though it's set up for Pentium processors, not AMD. I know they are in the same "class," but I thought if I configured a kernel specifically for my processor, it would be faster. Also, which is better: compiling drivers into the kernel, or running them as modules? One more glitch: when I compile a custome kernel, my sound goes to heck - it crackles at the tail end of any sound played. Using SB Live! X-Gamer (emu10k) Stock Slack kernel works fine. Maybe I'm answering my own questions here...! Any hints on this would be appreciated. Thanks!
If the default seems to be practically cooking toast for you, then why are you recompiling?
Anyway...
You just have to toy with the options, you may very well be leaving something out that is slowing down your system, or you might be running a patched kernel that is patching things that slow you down. Who knows
Modules vs Compile in:
If it's essential to the system running, compile it in. If it's not, and you can 'module' it, go for it. I find that by making more modules it seems to speed up my boot sequence a bit, if that makes a difference to you at all.
Sound:
I always use ALSA regardless if the default kernel comes with a 'kernel module' for my card (SB Live MP3+5.1 ) ALSA is simply better IMHO.
If the default seems to be practically cooking toast for you, then why are you recompiling?
Anyway...
You just have to toy with the options, you may very well be leaving something out that is slowing down your system, or you might be running a patched kernel that is patching things that slow you down. Who knows
Modules vs Compile in:
If it's essential to the system running, compile it in. If it's not, and you can 'module' it, go for it. I find that by making more modules it seems to speed up my boot sequence a bit, if that makes a difference to you at all.
Sound:
I always use ALSA regardless if the default kernel comes with a 'kernel module' for my card (SB Live MP3+5.1 ) ALSA is simply better IMHO.
Cool
Well, I asked myself the same question about the speed...guess I'm just picking nits! Thanks for the advice on the modules vs. compiled in, I'll mess with that this weekend.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.