Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
No, its a matter of you have the kernel pre-compiled for uniprocessors by the kids over at RH. I think, I've only ever run smp under slack. To find out for certain:
if there are 2 chips up, there should be two entries.
If not, its a kernel re-compile. in /usr/src/linux/ Redhat put in a directory called config or some such with a bunch of .config files for different hardware setups. You can simply copy one of those up a directory level and compile that. Make certain to re-name the directory though so that when you compile the modules, they don't over-write the pre-existing /lib/modules folder. You want to keep that old kernel as a boot option in case something doesn't come out right.
Actually, if you've never done it, best to go over to linux-doc and read the kernel compiling how-to.
Hi jyusko. I've found that if you use the RPM command it can make installing another kernel very easy.
For instance, if you are currently running kernel-2.4.18-5, then to install the smp kernel, just download kernel-smp-2.4.18-5.i686.rpm and run the command:
rpm -ivh kernel-smp-2.4.18-5.i686.rpm
and it will install the smp version and even place it in Grub for you as a 2nd choice when you boot.
I run RH 7.2 on my duel 600. The new kernels all come with the default set for smp, and if I'm not wrong I think that the guys at RH also left it that way in RH7.3. So what you should do is go into the gnome menu, which I'm assuming you are running since it's Redhats default to run Gnome, then go to System and then to System information, if you see under CPU information, info about CPU 0 and CPU1, then that means that the kernel was by default set with SMP support, so you should feel very good about this. Otherwise, you do have to recompile your kernel, and I suggest you don't recompile by using rpms...rpms don't work always.