From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] nct5573D missing fans
Date: Tue, 06 Oct 2015 14:59:18 +0000 [thread overview]
Message-ID: <5613E1C6.2020308@roeck-us.net> (raw)
In-Reply-To: <CAL_Kpj0HDwHZ1bwQZXYWwV0-Acnoqjfe8hzZiGSzUkMBzcRD2A@mail.gmail.com>
On 10/06/2015 03:43 AM, Alexey Orishko wrote:
> Hi guys,
>
> Asrock mobo C2550D4I has NCT5573D chip (at least they say in the mobo manual) and here is sensors-detect output:
> Found `Nuvoton NCT5577D/NCT6776F Super IO Sensors' Success!
> (address 0x290, driver `nct6775')
>
> Motherboard has 6 fan connectors cpu1&2, front 1&2 and rear 1&2, but if I load nct6775 driver on ubuntu 14.04.3-64bit, I do see only fan1 and fan2 (and pwm1 and pwm2) and I have a trouble to control them (manual mode, 4-wire fan). If I use sensor monitoring in build-in BMC web interface, I could at least see all 6 fans...
>
> Is there anything that could be done in the config file or driver changes are required to support this motherboard?
>
ASRock uses gpio multiplexers to switch fan inputs. Configuring those
is tricky. See https://github.com/groeck/nct6775/blob/master/README.ASRock
for some examples. Unfortunately this depends on the board. On top of that,
if BMC accesses the chip, the BMC likely reprograms the multiplexers as
needed, meaning the kernel would never be in full control even if it tried.
Maybe this could somehow be handled, but I have no idea how.
> Regards,
> Alexey
>
> PS. do you have any info why lm-sensors.org <http://lm-sensors.org> is down?
The web site owner moved to Greece and does not respond to queries.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2015-10-06 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:43 [lm-sensors] nct5573D missing fans Alexey Orishko
2015-10-06 14:59 ` Guenter Roeck [this message]
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=5613E1C6.2020308@roeck-us.net \
--to=linux@roeck-us.net \
--cc=lm-sensors@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).