Determine sensor actions by checking logs or system records.
Determine sensor actions by checking logs or system records.
You can check what sensors-detect did by reviewing its logs or output files. To view your history, look at the saved records or logs it generates. For answering prompts, you may need to inspect any stored responses or configuration settings. If unsure, consult the program’s documentation or support channels for detailed access options.
You’re likely okay if you went with the defaults. It’s risky when the system begins interacting with unfamiliar devices, as it may begin transmitting basic raw commands. The easiest check is to reboot and observe any disruptions or kernel warnings in "dmesg | grep error".
The spikes in temperature seem linked to applications opening or windows being launched. With your Aorus Z490, these changes could trigger sensor activity causing the rise.
I checked the dmesg output and found an error related to pcieport DPC. The system reported containment issues and several failed operations, including attempts to remount iwlwifi firmware and other direct device loads.
My thoughts on the matter. Every time I tried it, I accepted all prompts without problem—my laptop, the old one from 2005, or the hardware from 2014 worked perfectly. If you kept the settings as they are, I wouldn’t see any issues. If you disagreed with the defaults, I’d say nothing was impacted at all.
Do you have any idea how to check which sensors are being detected by the system? After running the sensor detection, a report appears but it’s unclear. I’d like to see what sensors were identified and their performance. Additionally, I need to know which default temperature sensors Lm-sensors recognize without needing further tests.
You're focusing on specific concerns about sensor detection systems. If everything functions properly now, no harm was done. Generally, the risks associated with running sensor-detect tools can be overstated. Still, potential problems like system freezes, data corruption, or similar issues exist in theory. These concerns are more theoretical, though real risks remain. The greater the complexity and lock-in of the hardware you're using, the higher the danger—though I'm not familiar with all the specifics. It seems manufacturers sometimes don't follow standards or make their sensors accessible for software updates, which adds to the challenge. From the man page of sensors-detect: (the excerpt provided is limited) This might vary slightly across distributions, but usually the lm_sensors package hasn't changed much, so your documentation should reflect this. We can't be certain what sensors-detect actually inspects because it depends on how you interact with it. The script's output shows it only lists kernel modules, not full sensor data. You could examine the script directly or try running it again—perhaps answer "NO" to all prompts initially, but adjust if needed. Observing what lm_sensors identifies by itself can help clarify things. If this isn't clear, share your distribution details and the contents of relevant configuration files; that will give you a better picture. This update was made on January 14, 2021 by Wild Penquin with minor adjustments.
It sends standard raw commands when testing unknown devices to understand what they return. This action may cause the device to freeze, enter unusual sleep modes that can often be fixed by cutting power (including CMOS battery), erase internal parts, or apply incorrect voltages across the board. The potential for harm exists and actual damage happens more frequently than many assume. MSI boards (often seen in popups) and laptops tend to be the most affected. Still, the likelihood of serious issues remains low, particularly on older hardware, but it’s wise to exercise caution.