-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Predictable Sensor Name #40
Comments
Forgot to mention it's Arch, kernel version 5.19.9-arch1-1. Intel 12600k, Asus z690-i motherboard. |
From the viewpoint of the driver, no, there isn't. We don't control when we get loaded, only that it must happen after the HID bus. However, I found this blog post, perhaps you'll find it useful. |
That appears to be just what I need, thank you so much! |
I have the same problem with KDE System Monitor. Can this be re-opened and fixed? |
As I wrote in #40 (comment), there's nothing that can be done from within the driver - it does not control when it's being loaded. You can look at the instructions at the linked post in that comment, maybe it helps your case. |
I'm not sure if this is a driver issue or an issue with lm-sensors but each time I reboot, the octo is assigned a different name (eg: octo-hid-3-11 and the next reboot it may be 3-10 or 3-12 instead). While this doesn't cause issue when using sensors in the command line, it does cause issues when trying to use the plasma thermal monitor because it's expecting the same source name each time. Is there a way to make the name predicable each boot?
The text was updated successfully, but these errors were encountered: