You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On older RedHat EL and CentOS systems quite a lot of fields are missing when running CPU-X, even when done as root. Also, there is no GUI support thanks to only a part of GTK3 being present (but that part is fine, the user can rely on the text user interface instead).
Test system:
OS: CentOS 6.x Linux x86_64
CPU: Intel Core i7 980X
Mainboard: ASUS P6T Deluxe V2
GPU: AMD Radeon RX 550 (I think..)
Here's the results when CPU-X is being run as root:
Missing info on the CPU tab, processor part: Vendor, code name, technology, specification, family, model, Ext. family, Ext. model, stepping, instructions.
Missing info on the CPU tab, cache part: Everything.
Missing info on the CPU tab, core part: Everything.
Missing info on the Caches tab: Everything.
Missing info on the Motherboard tab: Vendor, model.
Wrongly reported info on the Memory tab: DRAM manufacturer & module part numbers (not provided correctly by dmidecode).
Missing info on the Memory tab: DRAM latencies. Those would likely require reading model-specific registers (MSRs) though, so probably not easy to do.
Missing info on the System tab: Distribution. Please see the following error:
grep: /etc/os-release: No such file or directory
CPU-X:util.c:212: an error occurred while running command 'grep PRETTY_NAME= /etc/os-release | awk -F '"|"' '{print $2}'' (fgets)
Note that SYSV init based Linux systems (which don't have systemd) sometimes won't have /etc/os-release. On Red Hat based systems, a simple pretty name is stored in /etc/redhat-release, but a better fallback at least for classic Linux systems would maybe be the output of $ lsb_release -d.
Wrongly reported info on the System tab: Uptime plus the entire memory information.
Missing info on the Graphics tab: Everything.
Thank you very much!
The text was updated successfully, but these errors were encountered:
You're right, # cpu-x -V reported no libcpuid being linked in. I checked out and compiled the source code of libcpuid 0.4.1, installed it, created the proper links for your build system to find everything and then reconfigured and recompiled CPU-X.
It's all working now, thank you! :)
Unfortunately, there's no libcpuid in the RHEL6 package repositories, but no matter. Just one more library to compile.
About lsb_release: I'm not sure whether it exists on all modern distributions, but I assume it should, given that it's been a part of the Linux Standard Base specification for a long time now. I just checked, and it's in the latest LSB 5.0 spec as well.
On older RedHat EL and CentOS systems quite a lot of fields are missing when running CPU-X, even when done as root. Also, there is no GUI support thanks to only a part of GTK3 being present (but that part is fine, the user can rely on the text user interface instead).
Test system:
OS: CentOS 6.x Linux x86_64
CPU: Intel Core i7 980X
Mainboard: ASUS P6T Deluxe V2
GPU: AMD Radeon RX 550 (I think..)
Here's the results when CPU-X is being run as root:
Details:
Note that SYSV init based Linux systems (which don't have systemd) sometimes won't have
/etc/os-release
. On Red Hat based systems, a simple pretty name is stored in/etc/redhat-release
, but a better fallback at least for classic Linux systems would maybe be the output of$ lsb_release -d
.Thank you very much!
The text was updated successfully, but these errors were encountered: