From: Harald Judt <h.judt@gmx.at>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] NCT6776 global registers 0x1c=0 and 0x24=0x5c onASRock
Date: Wed, 21 Dec 2011 14:50:31 +0000 [thread overview]
Message-ID: <4EF1F237.7000107@gmx.at> (raw)
In-Reply-To: <20110410160433.GA22075@localhost>
Hi,
> On Tue, 12 Apr 2011 19:02:19 +0200, Ian Dobson wrote:
>> Hi,
>>
>> --------------------------------------------------
>> From: "Mike Campin" <lm_sensors at ootsa.homelinux.net>
>> Sent: Sunday, April 10, 2011 6:04 PM
>> To: <lm-sensors at lm-sensors.org>
>> Subject: [lm-sensors] NCT6776 global registers 0x1c=0 and 0x24=0x5c onASRock
>> Extreme4
>>
>> > Hi,
>> >
>> > Only 2 of the 5 fans are showing up on my ASRock P67 Extreme4 motherboard.
>> > It due to the NCT6776 global configuration register 0x1c and 0x24 values.
>> > The fans work if I modify these registers prior to loading the w83627ehf
>> > driver.
>> >
>> > My question is where are these registers initialized? Should I ask ASRock
>> > to fix the BIOS?
>> >
>> > isadump -y -k 0x87,0x87 0x2e 0x2f
>> >
>> > 0 1 2 3 4 5 6 7 8 9 a b c d e f
>> > 00: ff ff 00 ff ff ff ff 02 ff ff ff ff ff ff ff ff
>> > 10: ff ff ff ff ff ff ff ff ff ff f8 0e 00 00 ff ff
>> > 20: c3 33 ff 00 5c 00 00 98 00 ff 20 00 80 00 00 01
>> > 30: 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> >
>> > isaset -y -f 0x2e 0x87
>> > isaset -y -f 0x2e 0x87
>> > isaset -y 0x2e 0x2f 0x1c 0x3
>> > isaset -y 0x2e 0x2f 0x24 0x1c
>> >
>> > Thanks, Mike
>> >
>> > --
>> > Mike Campin
>> > lm_sensors at ootsa.homelinux.net
>> >
>> > _______________________________________________
>> > lm-sensors mailing list
>> > lm-sensors at lm-sensors.org
>> > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>
>> ASRock designed the board, so they should setup the hardware monitoring chip
>> correctly. Allowing users to change the chip configuration is a really bad
>> idea, as many of the pins can have different functionality/electrical
>> spcifications depending on the config. Setting up a pin incorrectly could
>> blow the chip (Configuring a pin so that it's a source that's connected to
>> an unprotected/limited sink for example).
>>
>> So ASRock should fix the BIOS.
>
> Seconded. But before flaming Asrock, two things worth checking:
> * Availability of a BIOS update fixing the issue.
> * Options in the BIOS to enable/disable the monitoring of specific
> fans. I can imagine that the BIOS skips the configuration steps for
> fans for which monitoring was disabled (although that would probably
> mean more code than just doing it unconditionally...)
>
> --
> Jean Delvare
I own an Asrock P67 Extreme4 too and have the same problem. It can be
solved by following Mike Campin's instructions, which I successfully
incorporated into /etc/init.d/lm_sensors. There is no BIOS available
that fixes this issue, but I noticed that SpeedFan for Windows
(www.almico.com/speedfan.php) seems to do something similar, otherwise
it would show only 2 fans too. So maybe we could get that into
lm_sensors, even if the BIOS is at fault here?
Regards,
Harald
--
`Experience is the best teacher.'
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-12-21 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 16:04 [lm-sensors] NCT6776 global registers 0x1c=0 and 0x24=0x5c on Mike Campin
2011-04-12 17:02 ` [lm-sensors] NCT6776 global registers 0x1c=0 and 0x24=0x5c Ian Dobson
2011-04-12 17:09 ` Jean Delvare
2011-12-21 14:50 ` Harald Judt [this message]
2011-12-21 17:01 ` Guenter Roeck
2011-12-21 17:55 ` Ian Dobson
2011-12-21 20:55 ` Ira W. Snyder
2011-12-21 22:26 ` Guenter Roeck
2011-12-21 22:43 ` Harald Judt
2012-01-05 14:39 ` Jean Delvare
2012-01-05 14:45 ` Jean Delvare
2012-01-06 11:36 ` Harald Judt
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=4EF1F237.7000107@gmx.at \
--to=h.judt@gmx.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.