Can the hardware IDs be fixed after a reboot?
Can the hardware IDs be fixed after a reboot?
You're experiencing instability in your hwmon IDs after reboots on your Arch Linux setup. This can be due to system configuration changes or driver behavior. There are ways to stabilize it—consider using a more robust monitoring tool, adjusting PWM settings, or verifying hardware compatibility. It’s not necessarily a fixed issue but something you can manage with proper tuning.
Rebuild the kernel using modules listed in /sys/class/hwmon as "built in". Scrape /sys/class/hwmon/hwmon*/name with a wrapper script around impacted programs and adjust config/commands. I crafted a small Python hack to locate my AMD card in hwmon because module unloading affects GPU passthrough. The script searches for "amdgpu" inside files under the appropriate directories and outputs the matching paths.
I aim to avoid searching for IDs, as they’re easy to locate. My goal is to keep them stable across reboots. Fancontrol depends on pwmconfig to manage settings, and IDs are saved in a configuration file.
Device names are typically stable through udev tools. A web search confirms this approach. Additional resources include archived discussions and Linux documentation references.
I've adjusted your configuration file using the provided code. Consider precompiling the relevant modules into the kernel for stability. Avoid relying on udev for future updates—plan for eventual changes by creating dedicated hwmon files and linking them via a service. Since fancontrol runs from the command line, you could simplify it further by switching to a more robust framework like Theocontrol, which automatically identifies hardware without manual tuning.