get cpu info from dmesg

dmesg | grep cpu
get cpu info from dmesg

By: kingji
2009-04-03 01:57:04

These Might Interest You

  • this is helpful because dmesg is where i/o errors, etc are logged to... you will also be able to see when the system reboots or someone attaches a thumb drive, etc. don't forget to set yourself up in /etc/aliases to get roots email.

    (crontab -l; echo '* * * * * dmesg -c'; ) | crontab -
    syssyphus · 2009-09-30 18:13:38 0
  • Info about Bluetooth devices. Show Sample Output

    hciconfig;hciconfig -a hci0;lsmod |grep bt;dmesg | grep tooth
    FadeMind · 2013-08-21 12:29:23 0
  • Use sed to color the output of a human-readable dmesg output

    dmesg -T|sed -e 's|\(^.*'`date +%Y`']\)\(.*\)|\x1b[0;34m\1\x1b[0m - \2|g'
    jlaunay · 2012-07-31 22:21:07 13
  • The dmesg will show the kernel it is booting. No more dependency on files Show Sample Output

    sagarsakre · 2014-10-22 10:03:56 0

What Others Think

cat /proc/cpuinfo sounds good
servermanaged · 480 weeks and 2 days ago
when i do dmesg | grep cpu, i get this: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 16.245264] Initializing cgroup subsys cpuacct [ 18.120872] cpuidle: using governor ladder [ 18.120921] cpuidle: using governor menu [ 133.714393] Marking TSC unstable due to: cpufreq changes. Not too helpful. (I'm using Ubuntu)
alperyilmaz · 480 weeks and 2 days ago
sudo dmidecode | awk '/AMD/,/^$/' sudo dmidecode | awk '/Intel/,/^$/'
Williebee · 480 weeks and 2 days ago
try `cat /proc/cpuinfo` for some actually useful info.
sirlewk · 475 weeks ago
You can use lshw or hwinfo hwinfo --cpu lshw -class processor You shouldn't rely on dmesg for hardware info.
unixmonkey4372 · 469 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: