Getting Processor Information
I have just ran
lshwto get some information about a machine I know nothing about, and I just wanted to confirm something.
Does this basically mean it is a dual core 64 bit processor that is installed?
*-logicalcpu:0 description: Logical CPU physical id: 0.1 width: 64 bits capabilities: logical *-logicalcpu:1 description: Logical CPU physical id: 0.2 width: 64 bits capabilities: logical
Looking further down I see this
*-cpu:1 physical id: 1 bus info: [email protected] version: 6.7.6 serial: 0001-0676-0000-0000-0000-0000 size: 3150MHz capabilities: vmx ht configuration: id=0 *-logicalcpu:0 description: Logical CPU physical id: 0.1 capabilities: logical *-logicalcpu:1 description: Logical CPU physical id: 0.2 capabilities: logical
Which makes me almost certain it is dual core but not convinced on the 64 bit.
Any help for this n00b would be greatly appreciated!
Might be wrong, but that looks more like a single core doing hyperthreading, which presents two "logical cores".
I'm no expert on lshw, Toby, sorry. I've amended my answer to reflect the output from my core2Duo processor (no hyperthreading). Hope this helps.
It's often overlooked, so worth a shot. Sorry if this is insultingly obvious :
Also, when I ran
sudo lshw | grep -i cpu, I see a line which says cpus=2.
Ha, thanks - that **was** overlooked! That has listed two processors both Core 2 Duos @3.16GHz. What it doesn't do it confirm if this is a 64 bit machine or not.. (or am I being dense and that fact is staring me in the face?)
`uname -r` should help with that, surely? Or the same screenshot shows that I'm running 32-bit (my kernel is "generic").
I didn't set up the machine in the first place and I think the person who did erred on the site of caution and may have went for generic when they could have went higher. Thanks so much for your help. I have all the information I need now!
Actually, `uname -m` tells you whether the OS is 64 bits or not. On a 64-bits machine, it returns `x86_64`.
I'd stick with generic myself, Toby. Arguments for both sides... AGAINST : http://blog.pault.ag/post/3107062816/why-64-bit-computing-is-really-dumb-right-now and FOR : http://jldugger.livejournal.com/41896.html. Unless you're a developer or heavy power user video editor type thingymajig... 32-bit is fine for a while longer.
@Scaine: 64 bits vs 32 bits is an off-topic discussion here. 64 bits applications cannot run on a 32 bits OS, but the reverse is possible. As 64 bits is the future (even if it is available since 2000), I'll stick to an 64 bits OS and recommend others 64 bits as well.
Horses for courses. I'm with you actually - the next build I do will be 64-bit, but all I'm saying is that 32-bit is still very much alive and kicking. But you're quite right. This *is* OT. :-)
If you stick with 32bit, at least use the -generic-pae kernel so you can get access to all your memory and gain the NX bit for security.
To get the Processor model use the below command in a terminal.
cat /proc/cpuinfo | grep 'name'| uniq
To get the information about number of processors
cat /proc/cpuinfo | grep process| wc -l
For future Googlers - this command doesn't work on ARM processors as the output is very different in at least 18.04. The `lscpu` command below works well.
The simplest way to do this is to use the command created for that,
[email protected]:~$ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 55 Model name: Intel(R) Celeron(R) CPU N2840 @ 2.16GHz Stepping: 8 CPU MHz: 697.301 CPU max MHz: 2582,3000 CPU min MHz: 499,8000 BogoMIPS: 4331.60 Virtualization: VT-x L1d cache: 24K L1i cache: 32K L2 cache: 1024K NUMA node0 CPU(s): 0,1 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 syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
This command will tell you your chipset's characteristics as well as any supported instructions (or flags) in an easy-to-use and simple-to-read manner.
In ubuntu 14.04 desktop, the system monitor tool no longer has a "System" tab. You should see roughly the same screen like this:
- click the settings wheel (to clarify: the taskbar icon in the absolute upper-right hand corner of the screen: )
- choose "About this Computer"
This no longer works on Ubuntu 16. You need to click on the item title "Details" from the "System Settings"
The Hardware Lister application (lshw-gtk) from the default Ubuntu repositories is a user-friendly GUI application that displays detailed information about your computer's hardware including the model name and architecture (32-bit or 64-bit) of the CPU.
Simply select a category to obtain detailed information about a hardware component from the main interface.
archcommand from the terminal.
For a 64-bit processor and kernel, the command will output
Those commands output "x86_64" which identifies that 64-bit software is being used. However, it doesn't answer question of whether or not there is a dual core processor. Using `sudo lshw -class CPU` will provide model number of processor which can be googled to get full specifications of that chip which could be single core, hyper-threaded.
Note, though, that with this result, your system will not output `x86_64` if you do not have the 64-bit kernel installed on your system.
The simplest way is from
This identifies both your CPU model number and whether 32-bit or 64-bit software is running. It also displays other useful information such as amount of RAM.
Now take your CPU model number in google search engine type
3630QM number of cores:
3630QMwith the model number you get from the first display.
All the other answers are great answers but if you really want the "simplest" way of doing this I believe this is the preferred method without opening a terminal session or installing new software.