SENSORS-DETECT(8)
๐ SENSORS-DETECT(8) ๐
okay bestie, welcome to the sensors-detect page from the System Manager's Manual, and lemme tell you, this one is a whole journey ๐ซถ
โจ NAME โจ
sensors-detect โ detect hardware monitoring chips
๐ธ SYNOPSIS ๐ธ
sensors-detect [ --auto ]
๐ฆ DESCRIPTION ๐ฆ
so sensors-detect is an interactive program, meaning it literally walks you through the whole process of scanning your system for hardware monitoring chips (aka sensors) that are supported by libsensors(3), or honestly just by the lm_sensors tool suite in general. it's giving tour guide energy ๐ง
here's the order it looks for stuff in, and yes the order matters:
- sensors embedded in CPUs, south bridges and memory controllers.
- sensors embedded in Super I/O chips.
- hardware monitoring chips accessed through ISA I/O ports.
- hardware monitoring chips reachable over the SMBus or more generally any I2C bus on your system.
now here's the tea โ โ those last two detection steps can cause trouble on some systems, so normally they just... don't get attempted if step two already found a Super I/O chip with complete hardware monitoring features. but you're always free to ask for all the detection steps if that's what you want, no one's stopping you ๐ that can actually be useful if a given system has more than one hardware monitoring chip. some vendors are known to do this, most notably Asus and Tyan.
๐ OPTIONS ๐
--autoโ run in automatic, non-interactive mode. it just assumes default answers to all the questions. note that this isn't necessarily safe since the internal logic may lead to potentially dangerous probes being attempted. see the WARNING section below, bestie, i'm serious.--statโ display I2C address statistics. slay, numbers โจ
๐ WARNING ๐
okay this is the part where we get real. sensors-detect needs to access the hardware for most of the chip detections. by definition, it doesn't know which chips are there before it manages to identify them. which means it can access chips in a way these chips do not like, causing problems ranging from SMBus lockup to permanent hardware damage (a rare case, thankfully ๐).
the authors made their best to make the detection as safe as possible, and it turns out to work just fine in most cases, however it is impossible to guarantee that sensors-detect will not lock or kill a specific system. so, as a rule of thumb:
๐จ do not runsensors-detecton production servers. and do not runsensors-detectif you can't afford replacing a random part of your system. also, it is recommended to not force a detection step which would have been skipped by default, unless you know what you are doing. periodt.
๐ SEE ALSO ๐
๐ AUTHOR ๐
Frodo Looijaard and Jean Delvare โ absolute icons, fr fr ๐
and that's the whole page bestie!! this was lm-sensors 3, dated September 2013 ๐ธ thanks for reading, mwah, stay safe out there and don't fry ur motherboard ๐ โจ
๐ฆ where this page comes from
- debian trixie: lm-sensors 1:3.6.2-2
- ubuntu questing: lm-sensors 1:3.6.2-2
- ubuntu resolute: lm-sensors 1:3.6.2-2build1
- ubuntu stonking: lm-sensors 1:3.6.2-2build1
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms