public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: jurgenacc@tutanota.com
To: Guenter Roeck <linux@roeck-us.net>
Cc: "linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>
Subject: Re: ASRock B650E Taichi support
Date: Fri, 19 May 2023 15:59:34 +0200 (CEST)	[thread overview]
Message-ID: <NVoIkKr--3-9@tutanota.com> (raw)
In-Reply-To: <94fd7588-dd3a-4530-bfe8-a213b68dfc33@roeck-us.net>

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
>


  reply	other threads:[~2023-05-19 14:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <NUjvz8u--3-9@tutanota.com>
2023-05-06 12:59 ` ASRock B650E Taichi support Guenter Roeck
2023-05-15 14:36   ` jurgenacc
2023-05-19 13:49     ` Guenter Roeck
2023-05-19 13:59       ` jurgenacc [this message]
2023-05-19 17:47         ` Guenter Roeck
2023-05-19 18:51           ` jurgenacc
2023-06-13  3:42             ` jurgenacc
2023-06-13  4:57               ` Guenter Roeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NVoIkKr--3-9@tutanota.com \
    --to=jurgenacc@tutanota.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox