A system profiler is a utility that presents information about the hardware attached to a computer. Having access to information about your hardware can be indispensable when you need to establish exactly what hardware is installed in your machine. For example, the information helps a technical support individual diagnose problems, or help evaluate whether a system will support certain software or hardware.
This type of software lets individuals establish hardware details without opening the computer case. This may not be an option if you do not have direct access to the hardware, relying on the internet to connect to the machine. System profilers let you remotely interrogate a system.
In Windows circles, CPU-Z is a popular freeware tool that gathers information on the main devices of a system without having to conduct technical and manual searching. CPU-Z lays out the raw technical data out to read in easy-to-read tables and is well presented.
CPU-X is a similar tool to CPU-Z but differs in a few important ways. First, CPU-X is free and open source software. Second, it’s a tool designed for Linux. It can be used in graphical mode (GTK) or in text-based mode (NCurses or dump).
Installation
On our Manjaro systems, CPU-X is present in the Official Repositories. Installation is therefore trivial.
The project provides support for Debian, openSUSE, and Ubuntu.
What if there’s not a convenient package in your distribution? You’ve got unfettered access to the source code, so you can compile the program for yourself. It’s not difficult.
An easier solution is to use the project’s official AppImage. AppImage is a format for distributing portable software on Linux without needing superuser permissions to install the application. All that’s required is to download the AppImage, and make the file executable.
Next page: Page 2 – In Operation
Pages in this article:
Page 1 – Introduction / Installation
Page 2 – In Operation
Page 3 – Text-based user interface
Page 4 – Summary
Complete list of articles in this series:
| Essential System Tools | |
|---|---|
| ps_mem | Accurate reporting of software's memory consumption |
| gtop | System monitoring dashboard |
| pet | Simple command-line snippet manager |
| Alacritty | Innovative, hardware-accelerated terminal emulator |
| inxi | Command-line system information tool that's a time-saver for everyone |
| BleachBit | System cleaning software. Quick and easy way to service your computer |
| catfish | Versatile file searching software |
| journalctl | Query and display messages from the journal |
| Nmap | Network security tool that builds a "map" of the network |
| ddrescue | Data recovery tool, retrieving data from failing drives as safely as possible |
| Neofetch | System information tool written in Bash |
| Timeshift | Similar to Windows' System Restore functionality, Time Machine Tool in Mac OS |
| GParted | Resize, copy, and move partitions without data |
| Clonezilla | Partition and disk cloning software |
| fdupes | Find or delete duplicate files |
| Krusader | Advanced, twin-panel (commander-style) file manager |
| nmon | Systems administrator, tuner, and benchmark tool |
| f3 | Detect and fix counterfeit flash storage |
| QJournalctl | Graphical User Interface for systemd’s journalctl |
| QDirStat | Qt-based directory statistics |
| Firejail | Restrict the running environment of untrusted applications |
| VeraCrypt | Strong disk encryption software |
| Unison | Console and graphical file synchronization software |
| hyperfine | Command-line benchmarking tool |
| TLP | Must-have tool for anyone running Linux on a notebook |
| nnn | Portable terminal file manager that's amazingly frugal |
| Glances | Cross-platform system monitoring tool written in Python |
| CPU-X | System profiler with both a GUI and text-based |
| Ventoy | Create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files |
| Fail2ban | Ban hosts that cause multiple authentication errors |
| dust | More intuitive version of du written in Rust |
| Pingnoo | Graphical representation for traceroute and ping output |
inxi is much better to be fair for sharing system information with others.
It’s what people usually recommend as far as I’ve seen. I’d have to check out how CPU-X differs before making any claims though.