Closed undefined-moe closed 5 months ago
This bug also work in Debian 12 with kernal 6.1.0-17-amd64
Hi @undefined-moe , @Lixuannan , I will have a look at it!
@Lixuannan : can you provide the output of the following on your machine?
lscpu
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
dmidecode –t 4
cat /proc/cpuinfo
@undefined-moe ... just to be sure ... your Ubuntu 23.10 is running in VMWare as a client host system (so on an virtual machine), right? On the host itself all is fine? But inside the VMware client we have this behavior?
Can't confirm. I'm just forwarding this bug report from the original issue :(
but it seems that on lots of environments the cpu freq is in BIOS Model name
after Model name
line.
check Jeff Bastian's comment (2021-01-19 15:06:53) on https://bugzilla.redhat.com/show_bug.cgi?id=1882740 .
@undefined-moe @Lixuannan ... should be fixed, can you test this? Version 5.21.23 just released.
Describe the bug On VMware workstation pro 17.5 (client system Ubuntu 23.10 Kernel 6.7.0-rc3),
systeminfo.cpu()
failed to parse cpu speed.node -e "require('systeminformation').cpu().then(console.log)"
returns:Related: https://github.com/hydro-dev/Hydro/issues/708
lscpu
output:refer to https://github.com/sebhildebrandt/systeminformation/blob/5c5efe269eb0eedcb985a3e4be14652e37e75a3b/lib/cpu.js#L735 it parses first occured
Model name
while in this case that information's inBIOS Model name
.