The script is meant to identify the driver and kernel module responsible
for exporting a given hardware monitoring chip.
Signed-off-by: Ondřej Lysoněk <olysonek@redhat.com>
Input routing and scaling for this board was read from schematic of a
similar MSI MS-7B00 (B350 Gaming Pro Carbon) board.
temp5 on the MS-7B00 schematic is a thermistor under the B350 chip itself.
However, on my MS-7A34 board the reading is stuck at 23°C.
Judging from MS-7A34 board sensor readings that other people had posted
online the sensor seems to work properly for them, so I have left it
enabled.
Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
Input routing and scaling for this board was read from its schematic,
verified on a real specimen.
This config is likely also valid for other members of GA-F2A88XM-x family,
as differences between them seem pretty minor.
It might also be valid for GA-F2A85XM-HD3 board considering that
GA-F2A88XM-HD3 schematic has the former board name as title in many places.
Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
Values as per nuvoton nct6779D datasheetSection 8.5 Analog Inputs (Page 54,55).
Is based on nct6779 which uses a 2.048V input range, all inputs above that are scaled using a voltage divider.
Specific inputs like the ADC, AVCC, VBAT, 3VSB and 3VCC utilize an integrated voltage divider.
Signed-off-by: Rigo Reddig <rigo.reddig@gmail.com>
Add an option `-1`/`--oneline` that logs the updates sensor value with
the chip and adapter on the same line.
This makes it easier to parse and uniquely identify sensors without
labels, such as `temp1` in the example below.
Without `--oneline`:
```
Chip: iwlwifi-virtual-0
Adapter: Virtual device
temp1: 35.0 C
Chip: coretemp-isa-0000
Adapter: ISA adapter
Package id 0: 46.0 C
Core 0: 43.0 C
Core 1: 43.0 C
Core 2: 39.0 C
Core 3: 41.0 C
Chip: acpitz-virtual-0
Adapter: Virtual device
temp1: 25.0 C
Chip: dell_smm-virtual-0
Adapter: Virtual device
Processor Fan: 2512 RPM
Video Fan: 2498 RPM
CPU: 46.0 C
Ambient: 54.0 C
Ambient: 47.0 C
Other: 40.0 C
Chip: pch_skylake-virtual-0
Adapter: Virtual device
temp1: 66.0 C
```
With `--oneline`:
```
Chip: iwlwifi-virtual-0 Adapter: Virtual device temp1: 34.0 C
Chip: coretemp-isa-0000 Adapter: ISA adapter Package id 0: 47.0 C
Chip: coretemp-isa-0000 Adapter: ISA adapter Core 0: 42.0 C
Chip: coretemp-isa-0000 Adapter: ISA adapter Core 1: 43.0 C
Chip: coretemp-isa-0000 Adapter: ISA adapter Core 2: 39.0 C
Chip: coretemp-isa-0000 Adapter: ISA adapter Core 3: 41.0 C
Chip: acpitz-virtual-0 Adapter: Virtual device temp1: 25.0 C
Chip: dell_smm-virtual-0 Adapter: Virtual device Processor Fan: 2512 RPM
Chip: dell_smm-virtual-0 Adapter: Virtual device Video Fan: 2501 RPM
Chip: dell_smm-virtual-0 Adapter: Virtual device CPU: 46.0 C
Chip: dell_smm-virtual-0 Adapter: Virtual device Ambient: 54.0 C
Chip: dell_smm-virtual-0 Adapter: Virtual device Ambient: 48.0 C
Chip: dell_smm-virtual-0 Adapter: Virtual device Other: 40.0 C
Chip: pch_skylake-virtual-0 Adapter: Virtual device temp1: 66.0 C
```
Signed-off-by: Lucas Magasweran <lucas.magasweran@ieee.org>
It seems Nuvoton NCT6796D also has the same hardwired inputs.
This was determined experimentally on an ASUS PRIME B360M-A board.
Signed-off-by: Roy Zhang <pudh4418@gmail.com>
SFP modules measure the transmit power of the lazer. The sensor has
expected minimum values, and alarms when these minimams are reached.
Add support to sensors to print these.
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Do command substitution in double quotes to prevent word splitting.
The issue was reported by Coverity Scan.
Signed-off-by: Ondřej Lysoněk <olysonek@redhat.com>
Changes refer to issue #88. This change is backward compatible and is only a suggestion, a reference how the dmi and other information could be simply added into the config file for a board.
It looks like Nuvoton NCT6795D has the same hardwired inputs as other
members of its family, so let's add it to the appropriate section of
sensors.conf.default.
This was determined experimentally on a MSI MS-7A34 (B350 TOMAHAWK) board.
Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>