Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] CPU-X doesn't report the CPU after update to 5.1.0
@ 2024-10-28 11:13 xeroxslayer
  2024-10-28 13:54 ` [ISSUE] [CLOSED] " sgn
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: xeroxslayer @ 2024-10-28 11:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 4189 bytes --]

New issue by xeroxslayer on void-packages repository

https://github.com/void-linux/void-packages/issues/52810

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.58_1 x86_64 GenuineIntel uptodate rrrmFFFFFFFFF

### Package(s) Affected

CPU-X-5.1.0_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

It's supposed to show the CPU info in the CPU tab.

### Actual behaviour

It doesn't show the CPU info in the CPU tab.

![CPU-X](https://github.com/user-attachments/assets/7ddd7f08-49c8-48fa-a677-dd411f032812)

<details>
<summary>cpu-x</summary>

````
failed to call vkCreateInstance (VK_ERROR_INCOMPATIBLE_DRIVER)
set_gpu_kernel_driver(/sys/bus/pci/devices/0000:00:02.1): read_symlink: value=2 message=No such file or directory
Your GPU user mode driver is unknown for vendor Intel: 2.1 Mesa 24.2.4
failed to call vkCreateInstance (VK_ERROR_INCOMPATIBLE_DRIVER)
an error occurred while opening file '/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq'
failed to retrieve CPU frequency (fallback mode)
an error occurred while opening file '/sys/bus/pci/devices/0000:00:02.0/drm/card0/gt_cur_freq_mhz'
failed to retrieve all monitoring data for Card 0
set_gpu_kernel_driver(/sys/bus/pci/devices/0000:00:02.1): read_symlink: value=2 message=No such file or directory
DRM path for Card 1 is unknown
Driver for Card 1 doesn't report frequencies
````

</details>

Every other detection seems to work fine, except the CPU info detection. `lscpu` detects the CPU just fine.

<details>
<summary>lscpu</summary>

````
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          36 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   4
  On-line CPU(s) list:    0-3
Vendor ID:                GenuineIntel
  Model name:             Intel(R) Core(TM)2 Quad CPU    Q9550  @ 2.83GHz
    CPU family:           6
    Model:                23
    Thread(s) per core:   1
    Core(s) per socket:   4
    Socket(s):            1
    Stepping:             10
    BogoMIPS:             5666.31
    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bt
                          s rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti tpr_shadow flexpriority vpid dtherm vnmi
Virtualization features:  
  Virtualization:         VT-x
Caches (sum of all):      
  L1d:                    128 KiB (4 instances)
  L1i:                    128 KiB (4 instances)
  L2:                     12 MiB (2 instances)
NUMA:                     
  NUMA node(s):           1
  NUMA node0 CPU(s):      0-3
Vulnerabilities:          
  Gather data sampling:   Not affected
  Itlb multihit:          KVM: Mitigation: VMX disabled
  L1tf:                   Mitigation; PTE Inversion; VMX EPT disabled
  Mds:                    Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
  Meltdown:               Mitigation; PTI
  Mmio stale data:        Unknown: No mitigations
  Reg file data sampling: Not affected
  Retbleed:               Not affected
  Spec rstack overflow:   Not affected
  Spec store bypass:      Vulnerable
  Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:             Mitigation; Retpolines; STIBP disabled; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
  Srbds:                  Not affected
  Tsx async abort:        Not affected
````

</details>

Also, when I did `xbps-remove -ROov` afterwards, it reported that `libcpuid` is no longer needed, so I removed it. I tried adding it afterwards, but it didn't make a difference, it still reported nothing.

I also tested this on another rig I have Void running on (1st gen i7) and it doesn't report anything in the CPU tab as well.

### Steps to reproduce

1. Install CPU-X.
2. Run it.
3. Open the CPU tab.

^ permalink raw reply	[flat|nested] 7+ messages in thread
end of thread, other threads:[~2024-10-29  7:17 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-10-28 11:13 [ISSUE] CPU-X doesn't report the CPU after update to 5.1.0 xeroxslayer
2024-10-28 13:54 ` [ISSUE] [CLOSED] " sgn
2024-10-28 13:54 ` sgn
2024-10-28 14:49 ` 1is7ac3
2024-10-28 22:20 ` xeroxslayer
2024-10-29  2:02 ` classabbyamp
2024-10-29  7:17 ` xeroxslayer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).