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.
I don't quite believe that. Some older machines hang with SMP enabled. I'm sure there was such a case in this forum.
Really, you should compile your own kernel.
That would depend on what you define as 'older' machine. I've used the SMP kernels on a lot of Intel and AMD processors that most people would class as 'older' without nary a problem. Sure, sometimes a compile was in order to tweak for special hardware but the SMP kernel basically worked.
Compiling a new kernel cleans things up for me. Not done for performance since that would not be the case for trimming. Unless you are booting all the time. You might gain a little on the load time but that would be negligible.
The generic kernels should be used instead of the huge kernels. You will notice that a lot of the problems on LQ are related to people using the huge kernels. They usually don't read the 'txt' files that PV provides;
FWIW when I was investigating installing slackware on our dell inspiron 1501 which has a dual Athlon processor I found that it froze on booting with hugesmp but would boot with huge.s which rather surprised me.
If I do install slackware to it I will compile a custom kernel.
Thanks, it was you that had that problem. I'm just too lazy to look up the post And I don't think that computer is that old either, so it can happen even on newer machines.
I personally don't see much use in having a hugesmp kernel as on install kernel. For an "install kernel" (I know I probably just invented a new term, this means the kernel booted by default in order to install an OS such as Slackware) you don't need SMP, just as many things compiled in as will allow maximum, but safe detection of hardware (HDDs, CD/DVD-ROMS, etc.) without chance of hanging.
A regular "everyday kernel", on the other hand, should have as little compiled into it as possible (only as modules), in order to prevent driver conflicts and other odd problems. This is why generic kernels are recommended. I guess if you combine this with an initrd, there is absolutely no need to compile your own kernel. But, I have to tell you, you're missing out on a unique and somewhat challenging (at first) experience And, who knows ... maybe you can even make your computer run infinitesimally faster by customizing the kernel for your computer (mostly the processor options)
Last edited by H_TeXMeX_H; 11-03-2007 at 03:11 PM.
Yes, the performance increase you will get by moving from the titanic default Slackware kernels to one built specifically for your machine is going to be anything but infinitesimal. It is a very noticeable increase on more modern hardware, though older machines will not reap quite as large of an increase.
I have built custom kernels for machines that have gotten them ridiculous increases in performance. I recall one laptop in particular that had such a large performance increase that we knew it was working better before we even logged into the thing...we could see immediately that even the boot messages were moving much faster than before.