-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 More recent linux kernels now have a seperate scheduler for hyperthreaded CPUs which is different from the one used on true SMP machines. A hyper-threaded CPU is still only one CPU, it is not actually dual core, treating it as such had some problems. Since I do not have a P4 to test with, I do not know if this is the cause of your processor showing up differently in /proc/cpuinfo
Out of curiosity what kernel version are you currently running (uname -r)? To import your current config, copy /boot/config`uname -r` to /path/to/extracted/kernel/source/.config cd into the kernel source, then type: make oldconfig The option you are looking for is under "Processor type and features" -> SMT (Hyperthreading) scheduler support To check if your current kernel has this support: grep CONFIG_SCHED_SMT /boot/config-`uname -r` Johnny Stork wrote: > I had some problems with the graphical installer and so had to install > FC7 in text mode on my primary workstation (Intel P4, 3ghz > Hyperthreaded) but I noticed that my Hyperthreaded Intel CPU, which is > recognized as dual cpu's on all other distros of Linux and Windows, only > shows as having 1 cpu? I realize that SMP support is now built into the > single kernel, but how can I re-enable SMP support? Do I need to rebuild > the kernel? If so, it has been years since I did this so if I do need to > rebuild the kernel, can someone describe how I can > > 1: Call up the existing configuration > 2: Just make changes needed to get the hyperthreaded cpu recognised as > dual cpu's? > > > grep processor /proc/cpuinfo > processor : 0 > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHIPyvwRXgH3rKGfMRAqn0AKCvfpPfb2L6XPbGUm8eOzICErgCtwCcDe31 fjpOufQP++8Mf2hIVRHyvNw= =Urg5 -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
