If your installation was normal, then I think that processor should show 2 cores and 4 threads. Maybe it is set to one core in the BIOS (but you said windows was O.K. so maybe not). Maybe the setting mentioned by jackyboy633 is done in the config file. Look at /boot/config* (the most recent). Example:
Code:
doug@doug-64:~$ ls -l /boot/config*
-rw-r--r-- 1 root root 140505 Dec 5 10:22 /boot/config-3.2.0-35-generic
-rw-r--r-- 1 root root 140505 Jan 8 14:25 /boot/config-3.2.0-36-generic
-rw-r--r-- 1 root root 140505 Jan 24 08:08 /boot/config-3.2.0-37-generic
doug@doug-64:~$ grep APIC /boot/config-3.2.0-37-generic
CONFIG_X86_X2APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_PCI_IOAPIC=y
CONFIG_KVM_APIC_ARCHITECTURE=y
Also have a look at the log files for the CPU detection part of the boot process. Example (/var/log/kern.log):
Code:
Feb 14 13:39:54 s15 kernel: [ 0.062917] CPU0: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz stepping 07
Feb 14 13:39:54 s15 kernel: [ 0.168899] Performance Events: PEBS fmt1+, SandyBridge events, Intel PMU driver.
Feb 14 13:39:54 s15 kernel: [ 0.168904] PEBS disabled due to CPU errata.
Feb 14 13:39:54 s15 kernel: [ 0.168906] ... version: 3
Feb 14 13:39:54 s15 kernel: [ 0.168908] ... bit width: 48
Feb 14 13:39:54 s15 kernel: [ 0.168909] ... generic registers: 4
Feb 14 13:39:54 s15 kernel: [ 0.168911] ... value mask: 0000ffffffffffff
Feb 14 13:39:54 s15 kernel: [ 0.168913] ... max period: 000000007fffffff
Feb 14 13:39:54 s15 kernel: [ 0.168914] ... fixed-purpose events: 3
Feb 14 13:39:54 s15 kernel: [ 0.168916] ... event mask: 000000070000000f
Feb 14 13:39:54 s15 kernel: [ 0.169023] NMI watchdog enabled, takes one hw-pmu counter.
Feb 14 13:39:54 s15 kernel: [ 0.169073] Booting Node 0, Processors #1
Feb 14 13:39:54 s15 kernel: [ 0.169076] smpboot cpu 1: start_ip = 98000
Feb 14 13:39:54 s15 kernel: [ 0.276955] NMI watchdog enabled, takes one hw-pmu counter.
Feb 14 13:39:54 s15 kernel: [ 0.277020] #2
Feb 14 13:39:54 s15 kernel: [ 0.277022] smpboot cpu 2: start_ip = 98000
Feb 14 13:39:54 s15 kernel: [ 0.384897] NMI watchdog enabled, takes one hw-pmu counter.
Feb 14 13:39:54 s15 kernel: [ 0.384957] #3
Feb 14 13:39:54 s15 kernel: [ 0.384958] smpboot cpu 3: start_ip = 98000
Feb 14 13:39:54 s15 kernel: [ 0.492832] NMI watchdog enabled, takes one hw-pmu counter.
Feb 14 13:39:54 s15 kernel: [ 0.492893] #4
Feb 14 13:39:54 s15 kernel: [ 0.492894] smpboot cpu 4: start_ip = 98000
Feb 14 13:39:54 s15 kernel: [ 0.600670] NMI watchdog enabled, takes one hw-pmu counter.
Feb 14 13:39:54 s15 kernel: [ 0.600739] #5
Feb 14 13:39:54 s15 kernel: [ 0.600741] smpboot cpu 5: start_ip = 98000
Feb 14 13:39:54 s15 kernel: [ 0.708617] NMI watchdog enabled, takes one hw-pmu counter.
Feb 14 13:39:54 s15 kernel: [ 0.708681] #6
Feb 14 13:39:54 s15 kernel: [ 0.708683] smpboot cpu 6: start_ip = 98000
Feb 14 13:39:54 s15 kernel: [ 0.816558] NMI watchdog enabled, takes one hw-pmu counter.
Feb 14 13:39:54 s15 kernel: [ 0.816619] #7 Ok.
Feb 14 13:39:54 s15 kernel: [ 0.816621] smpboot cpu 7: start_ip = 98000
Feb 14 13:39:54 s15 kernel: [ 0.924495] NMI watchdog enabled, takes one hw-pmu counter.
Feb 14 13:39:54 s15 kernel: [ 0.924521] Brought up 8 CPUs
Feb 14 13:39:54 s15 kernel: [ 0.924523] Total of 8 processors activated (54577.36 BogoMIPS).
There have been bizarre cases where linux does not realize there are more CPU's, but as far as I know those were with AMD processors.
Bookmarks