nct6683 not working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lm-sensors (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
On my Lenovo Thinkcentre M710q sensors-detect finds an nct6683:
Found `Nuvoton NCT6683D eSIO' Success!
(address 0xa20, driver `nct6683')
the module is loaded:
# lsmod | grep nct6683
nct6683 20480 0
# dmesg | grep nct6683
[ 32.202596] nct6683: Found NCT6683D or compatible chip at 0x2e:0xa20
but sensors shows nothing from it:
# sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +39.0°C (high = +76.0°C, crit = +92.0°C)
Core 0: +38.0°C (high = +76.0°C, crit = +92.0°C)
Core 1: +37.0°C (high = +76.0°C, crit = +92.0°C)
iwlwifi-virtual-0
Adapter: Virtual device
temp1: N/A
running bionic 18.04.3
kernel 4.15.0-72-generic
Hi Robelix,
quite often that eventually comes down to broken FW/HW.
The kernel often gets quirks added to handle "just another slightly different case".
There isn't much one can do other than:
- reporting to the manufacturer (usually ignored)
- debuggung on your own (or by someone else owning the HW)
The NCT6683 was just added in lm-sensors 2.4 (which is in Bionic), we are at 3.6 now which might be worth a try. But OTOH there seemed to be no related fixes. /github. com/lm- sensors/ lm-sensors/ blob/master/ CHANGES# L90
=> https:/
The best path usually is to try the very latest software stack on not-the-latest HW. /wiki.ubuntu. com/Kernel/ LTSEnablementSt ack#Ubuntu_ 18.04_LTS_ -_Bionic_ Beaver
That means you could try installing a much newer Ubuntu which bings newer kernel and lm-sensors to see if things work there.
The easiest start would probably be just upgrading to the HWE kernel and hoping it might already help.
=> https:/
Step 1 for debugging would be checking the sysfs of the kernel driver: /www.kernel. org/doc/ Documentation/ hwmon/nct6683. rst /www.kernel. org/doc/ Documentation/ hwmon/sysfs- interface
Read:
=> https:/
=> https:/
And then give it a go, is the sysfs iterface available after loading the kernel module?
If not this is a kernel issue and not one in lm-sensors.