CPU-X is a Free software that gathers information on CPU, motherboard and more.
CPU-X is similar to CPU-Z (Windows), but CPU-X is a Free and Open Source software designed for GNU/Linux; also, it works on *BSD.
This software is written in C and built with CMake tool.
It can be used in graphical mode by using GTK or in text-based mode by using NCurses. A dump mode is present from command line.
- Dependencies
- Download/Install
- Usage
- Screenshots
- Translate/Contributions
- Troubleshooting
- Bugs/Improvements/Request features
- Links
These dependencies are needed to manually build CPU-X (e.g you can safely remove them after build):
These dependencies are needed to manually build and run CPU-X (e.g you can't remove a dependency if CPU-X was built with):
- GTK3+ (minimum supported version is 3.8, version 3.16 or newer recommended)
- NCurses
- Libcpuid (version 0.2.2 or newer is recommended)
- Libpci
- Procps-ng (Linux) / Libstatgrab (*BSD)
- Curl / Wget (optionnal)
You can download binary packages to easily install CPU-X on your system. A lot of distributions are supported, see the download section or the wiki page about GNU/Linux packages.
For step-by-step guide, you can see the wiki page (GNU/Linux or *BSD).
On some GNU/Linux distributions, you need to install the appropriate -dev package.
You can disable components in CPU-X before build by passing argument -D<var>=0
when running CMake:
-DWITH_GTK=0
will disable support of GUI in GTK3+
-DWITH_NCURSES=0
will disable support of TUI in NCurses
-DWITH_LIBCPUID=0
will avoid calls to Libcpuid (not recommended)
-DWITH_LIBPCI=0
will avoid calls to Libpci (not recommended)
-DWITH_LIBSYSTEM=0
will avoid calls to Libprocps/Libstatgrab (not recommended)
-DWITH_DMIDECODE=0
will not compile built-in Dmidecode (not recommended)
-DWITH_BANDWIDTH=0
will not compile built-in Bandwidth (not recommended)
- If you want to install CPU-X on your system, do:
mkdir build && cd build
cmake ..
make
make install
By default, CPU-X will be installed in /usr/local. If you want to change it, add option cmake -DCMAKE_INSTALL_PREFIX=<absolute_path> ..
on CMake invocation.
- If you want to build a portable binary, do:
mkdir pbuild && cd pbuild
cmake -DPORTABLE_BINARY=1 ..
make
Note: portable binary is accomplished/bin/cpu-x, in directory pbuild. Don't do make install
after.You can move this runnable file where you want.
CPU-X is available in a portable version (Linux 32/64-bit, FreeBSD 32/64-bit), like CPU-Z.
You can find the last release which depends on GTK here. All others needed librairies are included in the binary.
Also, if GTK librairies are not present on your system, you can use this instead.
You can find all downloads on this page.
After downloading tarball, you need to extract his content to be able to run CPU-X portable.
You can use this portable version on a lot of system, so you can leave a binary on a USB stick for instance.
Start program with root privileges allows CPU-X to access some special devices, minimizing empty labels count.
Application is put in the desktop menus, in System Tools category: entry CPU-X run CPU-X as regular user, and entry CPU-X (Root) grant root privileges.
Else, you can use command cpu-x
, or double-click on cpu-x
binary is also possible (if program won't start, check if file has executable bit set).
If GTK and NCurses are supported, you can start CPU-X in NCurses mode by taping in a shell (as root) cpu-x --ncurses
.
Use cpu-x --help
for other commands and help.
You can see how CPU-X looks here: https://github.com/X0rg/CPU-X/wiki/Screenshots
You want to have CPU-X in a foreign language but no translation exists? See the following wiki page:
https://github.com/X0rg/CPU-X/wiki/Translate
You want to contribute to CPU-X? In the top-right corner of the page, click Fork.
- CPU-X won't start: check binary permissions (do a
chmod 755
if they are wrong). - CPU-X still won't start: run it from a shell with
--verbose
argument, and look output. - Some labels are empty: CPU-X needs root privileges to run fine. If you manually build CPU-X, check dependencies. Or else, if a label is still empty, your hardware isn't recognized by a library.
Please open a new issue.
For bugs, you can attach cpu-x -V
and # cpu-x -ovd
outputs to issue.
Official webpage made by GitHub Pages.
Official wiki, still on GitHub.