Re: ASRock B650E Taichi support

Re: ASRock B650E Taichi support

[Guenter Roeck]

On 5/6/23 00:21, jurgenacc@tutanota.com wrote:
> Hi,
> 
> I found this repo (https://github.com/petersulyok/asrock_z390_taichi <https://github.com/petersulyok/asrock_z390_taichi>) mentioning that the ASRock z390 Taichi was able to see the sensors through lm-sensors if the nct6775 driver was loaded since it is using a Nuvoton NCT6791D. I have the ASRock B650E Taichi motherboard, but it has a different chip, I believe it is the Nuvoton NCT6796D-S. I tried enabling the ntc6775 driver to see if I was lucky, but I get an error: "modprobe: ERROR: could not insert 'nct6775': No such device".
> 
> The author of the repo suggested me asking you if support for the Nuvoton NCT6796D-S is there. If not, I can help test it. if there is, I would love to make it work in my PC.
> 

First of all, please copy linux-hwmon@vger.kernel.org on all inquiries regarding the
hwmon subsystem in the Linux kernel. If you do not want your query to be public,
please don't ask.

Yes, the kernel does support NCT6796D. I don't know about NCT6796D-S. Please provide
output of sensors-detect. It may be possible that the driver does not load because the
chip memory space is reserved by ACPI. If that is the case, you should see an error
message with dmesg. Also, of course, the kernel may not support the chip if you are
running an old kernel version.

Guenter

Re: ASRock B650E Taichi support

[jurgenacc]

Hi,

Here is the output for sensors-detect:

# sensors-detect version 3.6.0+git
# System: ASRock B650E Taichi [Default string]
# Kernel: 6.3.1-arch1-1 x86_64
# Processor: AMD Ryzen 9 7900X 12-Core Processor (25/97/2)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):  
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
AMD Family 19h thermal sensors...                           No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):  
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xd802
   (logical device B has address 0x290, could be sensors)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xd441

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):  
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):  
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):  
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively):  
Client found at address 0x49
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Client found at address 0x4b
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `Analog Devices ADT7481'...                     No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Client found at address 0x73
Probing for `FSC Poseidon I'...                             No
Probing for `FSC Poseidon II'...                            No
Probing for `FSC Scylla'...                                 No
Probing for `FSC Hermes'...                                 No
Probing for `FSC Heimdal'...                                No
Probing for `FSC Heracles'...                               No
Probing for `FSC Hades'...                                  No
Probing for `FSC Syleus'...                                 No
Probing for `FTS Teutates'...                               No

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively):  

Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-2)
Do you want to scan it? (YES/no/selectively):  

Next adapter: AMDGPU SMU 0 (i2c-3)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU SMU 1 (i2c-4)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-5)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-6)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-7)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-8)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM aux hw bus 0 (i2c-9)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM aux hw bus 1 (i2c-10)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM aux hw bus 2 (i2c-11)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-12)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-13)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM i2c hw bus 2 (i2c-14)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM i2c hw bus 3 (i2c-15)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM aux hw bus 1 (i2c-16)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM aux hw bus 2 (i2c-17)
Do you want to scan it? (yes/NO/selectively):  

Next adapter: AMDGPU DM aux hw bus 3 (i2c-18)
Do you want to scan it? (yes/NO/selectively):  

Sorry, no sensors were detected.
Either your system has no sensors, or they are not supported, or
they are connected to an I2C or SMBus adapter that is not
supported. If you find out what chips are on your board, check
https://hwmon.wiki.kernel.org/device_support_status for driver status.

I did a dmesg --clear first, tried mounting the nct6775 kernel module and printing dmesg next, but the buffer was empty.

Thanks,
Jurgen.


May 6, 2023, 8:59 AM by linux@roeck-us.net:

> On 5/6/23 00:21, jurgenacc@tutanota.com wrote:
>
>> Hi,
>>
>> I found this repo (https://github.com/petersulyok/asrock_z390_taichi <https://github.com/petersulyok/asrock_z390_taichi>) mentioning that the ASRock z390 Taichi was able to see the sensors through lm-sensors if the nct6775 driver was loaded since it is using a Nuvoton NCT6791D. I have the ASRock B650E Taichi motherboard, but it has a different chip, I believe it is the Nuvoton NCT6796D-S. I tried enabling the ntc6775 driver to see if I was lucky, but I get an error: "modprobe: ERROR: could not insert 'nct6775': No such device".
>>
>> The author of the repo suggested me asking you if support for the Nuvoton NCT6796D-S is there. If not, I can help test it. if there is, I would love to make it work in my PC.
>>
>
> First of all, please copy linux-hwmon@vger.kernel.org on all inquiries regarding the
> hwmon subsystem in the Linux kernel. If you do not want your query to be public,
> please don't ask.
>
> Yes, the kernel does support NCT6796D. I don't know about NCT6796D-S. Please provide
> output of sensors-detect. It may be possible that the driver does not load because the
> chip memory space is reserved by ACPI. If that is the case, you should see an error
> message with dmesg. Also, of course, the kernel may not support the chip if you are
> running an old kernel version.
>
> Guenter
>

Re: ASRock B650E Taichi support

[Guenter Roeck]

On Mon, May 15, 2023 at 04:36:55PM +0200, jurgenacc@tutanota.com wrote:
> Hi,
> 
> Here is the output for sensors-detect:
> 
> # sensors-detect version 3.6.0+git
> # System: ASRock B650E Taichi [Default string]
> # Kernel: 6.3.1-arch1-1 x86_64
> # Processor: AMD Ryzen 9 7900X 12-Core Processor (25/97/2)
> 
> This program will help you determine which kernel modules you need
> to load to use lm_sensors most effectively. It is generally safe
> and recommended to accept the default answers to all questions,
> unless you know what you're doing.
> 
> Some south bridges, CPUs or memory controllers contain embedded sensors.
> Do you want to scan for them? This is totally safe. (YES/no):  
> Silicon Integrated Systems SIS5595...                       No
> VIA VT82C686 Integrated Sensors...                          No
> VIA VT8231 Integrated Sensors...                            No
> AMD K8 thermal sensors...                                   No
> AMD Family 10h thermal sensors...                           No
> AMD Family 11h thermal sensors...                           No
> AMD Family 12h and 14h thermal sensors...                   No
> AMD Family 15h thermal sensors...                           No
> AMD Family 16h thermal sensors...                           No
> AMD Family 17h thermal sensors...                           No
> AMD Family 15h power sensors...                             No
> AMD Family 16h power sensors...                             No
> Hygon Family 18h thermal sensors...                         No
> AMD Family 19h thermal sensors...                           No
> Intel digital thermal sensor...                             No
> Intel AMB FB-DIMM thermal sensor...                         No
> Intel 5500/5520/X58 thermal sensor...                       No
> VIA C7 thermal sensor...                                    No
> VIA Nano thermal sensor...                                  No
> 
> Some Super I/O chips contain embedded sensors. We have to write to
> standard I/O ports to probe them. This is usually safe.
> Do you want to scan for Super I/O sensors? (YES/no):  
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor/ITE'...               No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
> Found unknown chip with ID 0xd802
>    (logical device B has address 0x290, could be sensors)

This is a NCT6799D. Support for it is pending.

> Probing for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor/ITE'...               No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
> Found unknown chip with ID 0xd441

This is a NCT6686D. It _should_ be supported by the nct6683 driver, though
the vendor may use an unknown vendor ID. WHat happens if you try loading
the nct6683 driver ?

Guenter

Re: ASRock B650E Taichi support

[jurgenacc]

Hi,

Loading the nct6683 did not give an error. However the sensors-detect gives the same output "Sorry, no sensors were detected."

Do I need to reboot or do a force_id option to load the driver differently?

Thanks,
Jurgen.

May 19, 2023, 9:49 AM by linux@roeck-us.net:

> On Mon, May 15, 2023 at 04:36:55PM +0200, jurgenacc@tutanota.com wrote:
>
>> Hi,
>>
>> Here is the output for sensors-detect:
>>
>> # sensors-detect version 3.6.0+git
>> # System: ASRock B650E Taichi [Default string]
>> # Kernel: 6.3.1-arch1-1 x86_64
>> # Processor: AMD Ryzen 9 7900X 12-Core Processor (25/97/2)
>>
>> This program will help you determine which kernel modules you need
>> to load to use lm_sensors most effectively. It is generally safe
>> and recommended to accept the default answers to all questions,
>> unless you know what you're doing.
>>
>> Some south bridges, CPUs or memory controllers contain embedded sensors.
>> Do you want to scan for them? This is totally safe. (YES/no):  
>> Silicon Integrated Systems SIS5595...                       No
>> VIA VT82C686 Integrated Sensors...                          No
>> VIA VT8231 Integrated Sensors...                            No
>> AMD K8 thermal sensors...                                   No
>> AMD Family 10h thermal sensors...                           No
>> AMD Family 11h thermal sensors...                           No
>> AMD Family 12h and 14h thermal sensors...                   No
>> AMD Family 15h thermal sensors...                           No
>> AMD Family 16h thermal sensors...                           No
>> AMD Family 17h thermal sensors...                           No
>> AMD Family 15h power sensors...                             No
>> AMD Family 16h power sensors...                             No
>> Hygon Family 18h thermal sensors...                         No
>> AMD Family 19h thermal sensors...                           No
>> Intel digital thermal sensor...                             No
>> Intel AMB FB-DIMM thermal sensor...                         No
>> Intel 5500/5520/X58 thermal sensor...                       No
>> VIA C7 thermal sensor...                                    No
>> VIA Nano thermal sensor...                                  No
>>
>> Some Super I/O chips contain embedded sensors. We have to write to
>> standard I/O ports to probe them. This is usually safe.
>> Do you want to scan for Super I/O sensors? (YES/no):  
>> Probing for Super-I/O at 0x2e/0x2f
>> Trying family `National Semiconductor/ITE'...               No
>> Trying family `SMSC'...                                     No
>> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
>> Found unknown chip with ID 0xd802
>>    (logical device B has address 0x290, could be sensors)
>>
>
> This is a NCT6799D. Support for it is pending.
>
>> Probing for Super-I/O at 0x4e/0x4f
>> Trying family `National Semiconductor/ITE'...               No
>> Trying family `SMSC'...                                     No
>> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
>> Found unknown chip with ID 0xd441
>>
>
> This is a NCT6686D. It _should_ be supported by the nct6683 driver, though
> the vendor may use an unknown vendor ID. WHat happens if you try loading
> the nct6683 driver ?
>
> Guenter
>

Re: ASRock B650E Taichi support

[Guenter Roeck]

On Fri, May 19, 2023 at 03:59:34PM +0200, jurgenacc@tutanota.com wrote:
> Hi,
> 
> Loading the nct6683 did not give an error. However the sensors-detect gives the same output "Sorry, no sensors were detected."
> 
??? The sensors-detect command and kernel drivers have no relationship
to each other.

Question is if you see any sensors after loading the nct6683 driver.

Guenter

Re: ASRock B650E Taichi support

[jurgenacc]

My bad. I'm relatively new to Linux. This is the output of the "sensors" command:

amdgpu-pci-0300
Adapter: PCI adapter
vddgfx:      825.00 mV 
fan1:           0 RPM  (min =    0 RPM, max = 3300 RPM)
edge:         +34.0°C  (crit = +100.0°C, hyst = -273.1°C)
                       (emerg = +105.0°C)
junction:     +38.0°C  (crit = +110.0°C, hyst = -273.1°C)
                       (emerg = +115.0°C)
mem:          +38.0°C  (crit = +100.0°C, hyst = -273.1°C)
                       (emerg = +105.0°C)
PPT:          38.00 W  (cap = 303.00 W)

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +44.6°C  
Tccd1:        +35.8°C  
Tccd2:        +40.9°C  

nvme-pci-4700
Adapter: PCI adapter
Composite:    +40.9°C  

amdgpu-pci-5000
Adapter: PCI adapter
vddgfx:        1.32 V  
vddnb:         1.15 V  
edge:         +42.0°C  
PPT:          46.25 W  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +30.0°C  

nvme-pci-4f00
Adapter: PCI adapter
Composite:    +36.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +36.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +42.9°C  (low  = -273.1°C, high = +65261.8°C)

These are the same as before, so no new sensors.

Thanks,
Jurgen.


May 19, 2023, 1:47 PM by linux@roeck-us.net:

> On Fri, May 19, 2023 at 03:59:34PM +0200, jurgenacc@tutanota.com wrote:
>
>> Hi,
>>
>> Loading the nct6683 did not give an error. However the sensors-detect gives the same output "Sorry, no sensors were detected."
>>
> ??? The sensors-detect command and kernel drivers have no relationship
> to each other.
>
> Question is if you see any sensors after loading the nct6683 driver.
>
> Guenter
>

Re: ASRock B650E Taichi support

[jurgenacc]

Is there anything I can do to help getting the support for NCT6799D? Also, is it normal that I don't see any sensors after loading NCT6686D?

Thanks,
Jurgen.


May 19, 2023, 2:51 PM by jurgenacc@tutanota.com:

> My bad. I'm relatively new to Linux. This is the output of the "sensors" command:
>
> amdgpu-pci-0300
> Adapter: PCI adapter
> vddgfx:      825.00 mV 
> fan1:           0 RPM  (min =    0 RPM, max = 3300 RPM)
> edge:         +34.0°C  (crit = +100.0°C, hyst = -273.1°C)
>                        (emerg = +105.0°C)
> junction:     +38.0°C  (crit = +110.0°C, hyst = -273.1°C)
>                        (emerg = +115.0°C)
> mem:          +38.0°C  (crit = +100.0°C, hyst = -273.1°C)
>                        (emerg = +105.0°C)
> PPT:          38.00 W  (cap = 303.00 W)
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> Tctl:         +44.6°C  
> Tccd1:        +35.8°C  
> Tccd2:        +40.9°C  
>
> nvme-pci-4700
> Adapter: PCI adapter
> Composite:    +40.9°C  
>
> amdgpu-pci-5000
> Adapter: PCI adapter
> vddgfx:        1.32 V  
> vddnb:         1.15 V  
> edge:         +42.0°C  
> PPT:          46.25 W  
>
> iwlwifi_1-virtual-0
> Adapter: Virtual device
> temp1:        +30.0°C  
>
> nvme-pci-4f00
> Adapter: PCI adapter
> Composite:    +36.9°C  (low  = -273.1°C, high = +81.8°C)
>                        (crit = +84.8°C)
> Sensor 1:     +36.9°C  (low  = -273.1°C, high = +65261.8°C)
> Sensor 2:     +42.9°C  (low  = -273.1°C, high = +65261.8°C)
>
> These are the same as before, so no new sensors.
>
> Thanks,
> Jurgen.
>
>
> May 19, 2023, 1:47 PM by linux@roeck-us.net:
>
>> On Fri, May 19, 2023 at 03:59:34PM +0200, jurgenacc@tutanota.com wrote:
>>
>>> Hi,
>>>
>>> Loading the nct6683 did not give an error. However the sensors-detect gives the same output "Sorry, no sensors were detected."
>>>
>> ??? The sensors-detect command and kernel drivers have no relationship
>> to each other.
>>
>> Question is if you see any sensors after loading the nct6683 driver.
>>
>> Guenter
>>
>
>

Re: ASRock B650E Taichi support

[Guenter Roeck]

On 6/12/23 20:42, jurgenacc@tutanota.com wrote:
> Is there anything I can do to help getting the support for NCT6799D? Also, is it normal that I don't see any sensors after loading NCT6686D?
> 
I think I'll probably just apply the current code for v6.5. It isn't perfect -
temperature sensor support is incomplete - but better incomplete support than
nothing.

For NCT6686D: You could try setting the "force" module parameter.

Guenter

> Thanks,
> Jurgen.
> 
> 
> May 19, 2023, 2:51 PM by jurgenacc@tutanota.com:
> 
>> My bad. I'm relatively new to Linux. This is the output of the "sensors" command:
>>
>> amdgpu-pci-0300
>> Adapter: PCI adapter
>> vddgfx:      825.00 mV
>> fan1:           0 RPM  (min =    0 RPM, max = 3300 RPM)
>> edge:         +34.0°C  (crit = +100.0°C, hyst = -273.1°C)
>>                         (emerg = +105.0°C)
>> junction:     +38.0°C  (crit = +110.0°C, hyst = -273.1°C)
>>                         (emerg = +115.0°C)
>> mem:          +38.0°C  (crit = +100.0°C, hyst = -273.1°C)
>>                         (emerg = +105.0°C)
>> PPT:          38.00 W  (cap = 303.00 W)
>>
>> k10temp-pci-00c3
>> Adapter: PCI adapter
>> Tctl:         +44.6°C
>> Tccd1:        +35.8°C
>> Tccd2:        +40.9°C
>>
>> nvme-pci-4700
>> Adapter: PCI adapter
>> Composite:    +40.9°C
>>
>> amdgpu-pci-5000
>> Adapter: PCI adapter
>> vddgfx:        1.32 V
>> vddnb:         1.15 V
>> edge:         +42.0°C
>> PPT:          46.25 W
>>
>> iwlwifi_1-virtual-0
>> Adapter: Virtual device
>> temp1:        +30.0°C
>>
>> nvme-pci-4f00
>> Adapter: PCI adapter
>> Composite:    +36.9°C  (low  = -273.1°C, high = +81.8°C)
>>                         (crit = +84.8°C)
>> Sensor 1:     +36.9°C  (low  = -273.1°C, high = +65261.8°C)
>> Sensor 2:     +42.9°C  (low  = -273.1°C, high = +65261.8°C)
>>
>> These are the same as before, so no new sensors.
>>
>> Thanks,
>> Jurgen.
>>
>>
>> May 19, 2023, 1:47 PM by linux@roeck-us.net:
>>
>>> On Fri, May 19, 2023 at 03:59:34PM +0200, jurgenacc@tutanota.com wrote:
>>>
>>>> Hi,
>>>>
>>>> Loading the nct6683 did not give an error. However the sensors-detect gives the same output "Sorry, no sensors were detected."
>>>>
>>> ??? The sensors-detect command and kernel drivers have no relationship
>>> to each other.
>>>
>>> Question is if you see any sensors after loading the nct6683 driver.
>>>
>>> Guenter
>>>
>>
>>
>