How can I tell if Ubuntu is using both cores of c2d

[timzak]

Title says it all.

Thanks in advance.

 

[Nothinman]

Gnome System Monitor should have lines for each CPU in it's CPU graph or you can just type 'cat /proc/cpuinfo' and see how many CPUs are reported in there.

 

[timzak]

Thanks. Only one line shows and cat /proc/cpuinfo shows only one cpu:

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz
stepping : 2
cpu MHz : 2435.786
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 4811.16
clflush size : 64

How do I enable the 2nd core?

 

[nweaver]

not sure with the Ubuntu kernels, but you might need to install an SMP aware kernel....I do on Deb Stable

 

[xtknight]

Chances are you're using the -386 kernel branch. Install the -generic which supports SMP and newer CPU features.

$ sudo apt-get install linux-image-generic

 

[Alone]

Originally posted by: xtknight
Chances are you're using the -386 kernel branch. Install the -generic which supports SMP and newer CPU features.

$ sudo apt-get install linux-image-generic

:thumbsup:
The generic kernel should even be used by those with single core processors.

 

[sourceninja]

Default install of feisty uses -generic

Works great here

/$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 35
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
stepping : 2
cpu MHz : 1000.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy ts fid vid ttp
bogomips : 2016.26
clflush size : 64

processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 35
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
stepping : 2
cpu MHz : 1000.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy ts fid vid ttp
bogomips : 2016.26
clflush size : 64

 

[timzak]

I'm using a default install of Feisty and it didn't install on mine. In fact, I just installed -generic, rebooted, and I STILL show only one core! Any ideas?

 

[drag]

What kernel are you using?

I found this in the ubuntu forums:
http://ubuntuforums.org/showthread.php?t=429398&highlight=only+one+core

Apparently you have to use the generic kernel or something like that. To see what kernel your using open up a terminal and type:
uname -a

 

[timzak]

Thanks, I have my own thread going in ubuntuforums on the same topic. Trying to get a quick answer. I installed the generic kernel, but it's still not being recognized. It sounds like I have to boot up with the generic kernel as opposed to the i386 one. The problem is, I have no idea how to do that.

Thanks for any help!

 

[drag]

When you boot up you should be able to select the kernel you want to run. When you installed the kernel it should of automaticly made a new menu entry for it there.


If it didn't try running:
sudo update-grub

Then it should display some stuff and your kernel should show up there.

Since it's probably newer then it should use it by default. If it doesn't, it's there, but you have to press down to select it in grub then you can edit /boot/grub/menu.lst and in there will be a line that says something like:

# default 0

0 is the first number so that will automaticly select the first kernel. If your kernel you want to use the third entries down then you want to use '2'.

The # may or may not be there. It is put at the beginning of a line to make the program ignore it.

So you'd make it look like:
default 2

Or whatever. Only do that when you want to change the default entry.

Works for when you want to make Windows default also.

 

[xtknight]

Originally posted by: timzak
Thanks, I have my own thread going in ubuntuforums on the same topic. Trying to get a quick answer. I installed the generic kernel, but it's still not being recognized. It sounds like I have to boot up with the generic kernel as opposed to the i386 one. The problem is, I have no idea how to do that.

Thanks for any help!

Does the -generic one appear at the GRUB menu list at bootup? If it says press ESC or something to show menu, do that and then select generic. You can then uninstall (purge or "remove completely" the `386 linux image` with synaptic) 386 if you're sure generic installed properly, and then generic should be default and you shouldn't have to do anything special at boot-up.

 

[timzak]

Okay, thanks. I hit ESC on bootup and got the GRUB menu and sure enough, i386 is listed first, followed by -generic.

When I select -generic, the computer fails to boot into Gnome. I get the following error message:

Code:

Failed to start the X server.
(EE)Failed to load module "wfb" (module does not exist, 0)
FATAL: Error running install command for nvidia
(EE)NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE)NVIDIA(0): ***Aborting***
(EE)Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

I just rebooted, chose i386 and booted normally into Gnome.

What's up with that?

 

[phisrow]

Ah, you installed the NVIDIA closed source drivers, didn't you?

I don't know too much about how to do this, as I've never had to deal with them myself, but the NVIDIA closed source drivers are only compatible with specific kernels. You might be able to get away with reinstalling the NVIDIA binary drivers, there might be some more complex fix.

 

[xtknight]

If you used restricted-modules to begin with, install the restricted modules for -generic.

$ sudo apt-get install linux-restricted-modules-generic

Then simply reboot. If you didn't use restricted modules, you'll have to install the binary NVIDIA drivers under the -generic kernel.

 

[timzak]

Originally posted by: xtknight
If you used restricted-modules to begin with, install the restricted modules for -generic.

$ sudo apt-get install linux-restricted-modules-generic

Then simply reboot. If you didn't use restricted modules, you'll have to install the binary NVIDIA drivers under the -generic kernel.

Thank you! Yes, I installed the 9755 drivers (nvidia-glx-new) to see if it would help with some Beryl/Compiz glitches I was having. It didnt, but didn't seem to be hurting anything else (little did I know).

Surprisingly (no disrespect to anyone), I got better, faster help here than at ubuntuforums.

Now I'm going to see if this fixes my other problem (loss of compatibility with evdev to get my side mouse buttons working on a Logitech MX700). If you know of a better way to get my side mouse buttons back, (I hear evdev has problems), I'm all ears.

Thanks again,
Tim

Edit, I just checked nvidia-settings and it says I'm still using 9755 drivers (last I checked, restricted mode drivers were 96XX). Should I be concerned? After all, Gnome is working now...