![]() you CAN compare the maximum because that should show the same for any of the ways you can analyze the CPU, but the current will always be literally "the current CPU hertz" at the moment you execute it. Note: All the commands above will also give you the CURRENT cpu Hertz, meaning, if you expect to see the same one on lscpu and when doing the cat /proc/cpuinfo it will be near impossible. I am fairly certain there are other ways, just don't remember right now. Will not work in some cases, that is why I posted the dmesg one first.Īnd that's all I can remember from the top of my head. You can also target the current MHz detected by the kernel by querying the log files:Ĭat /var/log/dmesg | grep "MHz processor" - For the current detected MHz speedĬat /var/log/kern.log | grep "MHz processor" - For the current and past detected MHz speeds. Out of all of this, lshw and dmidecode provide the best information out of your CPU. $ sudo dmidecode -t processor | grep Speed Sudo dmidecode -t processor or more precise: sudo dmidecode -t processor | grep "Speed" Will not only give you a MHz in use but also the Maximum you can push / overclock your CPU to. WARNING: output may be incomplete or inaccurate, you should run this program as super-user. WARNING: you should run this program as super-user. Lshw -c cpu or more precise version: lshw -c cpu | grep capacity So if you have an Core 2 Duo, AMD Bulldozer, Core i7, etc. This will give you the individual MHz for each CPU Core. ![]() $ lscpu | grep "MHz".Ĭat /proc/cpuinfo or more precise cat /proc/cpuinfo | grep "MHz". This will give you the general MHz for the CPU. Lscpu or more precise lscpu | grep "MHz".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |