Hello, I remembered this topic since I was installing a new system and I read in the logs: Please run `/usr/sbin/sensors-detect' in order to setup "/etc/modules-load.d/lm_sensors.conf". You might want to add lm_sensors to your default runlevel to make sure the sensors get initialized on the next startup. Be warned, the probing of hardware in your system performed by sensors-detect could freeze your system. __ I wondered if it's still the case at present days. It has been years of me simply installing lm-sensors to execute "sensors" and I simply get everything working as soon as needed drivers are build in the kernel (inside or as modules). Taking into account all the warnings about sensors-detect maybe freezing the system and so on... I am not sure if we could maybe review the output to only tell people to use sensors-detect when they don't get them working. I also wonder about it playing with /etc/modules-load.d/lm_sensors.conf as udev looks to load everything fine by itself Thanks a lot
This is still very much the case. On the one hand, what typically allows "sensors" to work out of the box on amd64 systems is ACPI and not all sensor information is exposed via ACPI methods; not to mention that there are quite a few arches out there which do not support ACPI at all. On the other, many hwmon modules - including such non-exotic ones as "it87" or "drivetemp" - haven't got magic device aliases so one must either know in advance which modules to use, or use sensors-detect as recommended. The comment about potential system freezes reflects the upstream stance on this and I would rather be safe than sorry here. Especially given I *have* observed sensors-detect freeze X during the more aggressive scanning.
ok, thanks a lot for the info!
