open /sys/class/hwmon/hwmon6/name: no such file or directory
wallentx opened this issue Β· comments
Installed on Arch from AUR. It just crashes as soon as I try to run it.
Are you on x86 processor ? with stock kernel ?
Yes, and sorry for the late reply. I had forgotten I opened this, and then rediscovered the issue tonight, and came here to report it π
This is on a clean install of Arch from just a few days ago, with zftop Installed from the AUR.
Here's a tree view of my /sys/class/hwmon
/sys/class/hwmon
.
βββ hwmon0 -> ../../devices/pci0000:00/0000:00:03.0/0000:08:00.0/0000:09:11.0/0000:0e:00.0/nvme/nvme3/hwmon0
β βββ device -> ../../nvme3
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_alarm
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_label
β βββ temp1_max
β βββ temp1_min
β βββ uevent
βββ hwmon1 -> ../../devices/pci0000:00/0000:00:03.0/0000:08:00.0/0000:09:13.0/0000:10:00.0/nvme/nvme5/hwmon1
β βββ device -> ../../nvme5
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_alarm
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_label
β βββ temp1_max
β βββ temp1_min
β βββ uevent
βββ hwmon2 -> ../../devices/pci0000:00/0000:00:03.0/0000:08:00.0/0000:09:0a.0/0000:0c:00.0/nvme/nvme1/hwmon2
β βββ device -> ../../nvme1
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_alarm
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_label
β βββ temp1_max
β βββ temp1_min
β βββ uevent
βββ hwmon3 -> ../../devices/pci0000:00/0000:00:03.0/0000:08:00.0/0000:09:12.0/0000:0f:00.0/nvme/nvme4/hwmon3
β βββ device -> ../../nvme4
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_alarm
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_label
β βββ temp1_max
β βββ temp1_min
β βββ uevent
βββ hwmon4 -> ../../devices/pci0000:00/0000:00:03.0/0000:08:00.0/0000:09:10.0/0000:0d:00.0/nvme/nvme2/hwmon4
β βββ device -> ../../nvme2
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_alarm
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_label
β βββ temp1_max
β βββ temp1_min
β βββ uevent
βββ hwmon5 -> ../../devices/pci0000:00/0000:00:03.0/0000:08:00.0/0000:09:09.0/0000:0b:00.0/nvme/nvme0/hwmon5
β βββ device -> ../../nvme0
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_alarm
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_label
β βββ temp1_max
β βββ temp1_min
β βββ uevent
βββ hwmon6 -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ACPI000D:00/hwmon/hwmon6
β βββ device -> ../../../ACPI000D:00
β βββ power
β βββ subsystem -> ../../../../../../class/hwmon [recursive, not followed]
β βββ uevent
βββ hwmon7 -> ../../devices/pci0000:00/0000:00:02.2/0000:04:00.1/hwmon/hwmon7
β βββ device -> ../../../0000:04:00.1
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_label
β βββ temp1_max
β βββ uevent
βββ hwmon8 -> ../../devices/pci0000:00/0000:00:1c.4/0000:02:00.0/hwmon/hwmon8
β βββ device -> ../../../0000:02:00.0
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_max
β βββ uevent
βββ hwmon9 -> ../../devices/pci0000:00/0000:00:1c.4/0000:02:00.1/hwmon/hwmon9
β βββ device -> ../../../0000:02:00.1
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_max
β βββ uevent
βββ hwmon10 -> ../../devices/pci0000:00/0000:00:1c.4/0000:02:00.2/hwmon/hwmon10
β βββ device -> ../../../0000:02:00.2
β βββ name
β βββ power
β βββ subsystem -> ../../../../../../class/hwmon [recursive, not followed]
β βββ temp1_crit
β βββ temp1_input
β βββ temp1_max
β βββ uevent
βββ hwmon11 -> ../../devices/pci0000:00/0000:00:1c.4/0000:02:00.3/hwmon/hwmon11
βββ device -> ../../../0000:02:00.3
βββ name
βββ power
βββ subsystem -> ../../../../../../class/hwmon [recursive, not followed]
βββ temp1_crit
βββ temp1_input
βββ temp1_max
βββ uevent
49 directories, 75 files
Maybe this is a quirk of multi-CPU setups?
I think it depend on hwmon driver that u cpu uses.
Try to test this branch https://github.com/ssleert/zfxtop/tree/hwmn-name-fix.
And if it works, i merge it in master/
After some exploring online, it appears this is a power meter, and might be an HPE specific thing? Or at least there were lots of results about ProLiant owners seeing (harmless?) errors related to this, and them just blacklisting acpi_power_meter
.. but this appears to only have been common for a few periods where there were other dependent modules that were never getting loaded.
On my system, my power meter was providing an average power usage value.
I did rmmod it, and my hwmon6 went away entirely.
But it might be desirable to mitigate an outright failure in zfxtop if it fails to find a value like this.
Ah! And as I type this, I see that you just replied with a change! I'll give it a shot now and will report back.
Try to test this branch
hwmn-name-fix
. And if it works, i merge it in master/
It wasn't working, but after playing around with some stuff, I got it going! I'm far from a golang expert, but I've opened a PR to your branch, if you are interested #20
i merged it, but my math teacher scolded me for being distracted from class)