From: Michael Zintakis <michael.zintakis@googlemail.com>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Fintek f71882fg ACPI conflict
Date: Tue, 26 Jun 2012 23:56:00 +0000 [thread overview]
Message-ID: <4FEA4C10.2060904@googlemail.com> (raw)
Hello,
I hope this is the right place to place my query!
I am trying to take control and initialise my fan censors and
"sensors-detect" is telling me that the chip on the board is "Fintek
f71869a at 0x290, revision 32". However, when I run sensors (the
service) this driver is not loaded (I can't see any of the fan sensors
either) and dmesg is showing me the following:
[ 2312.804747] f71882fg: Found f71869a chip at 0x290, revision 32
[ 2312.804902] ACPI Warning: 0x00000290-0x00000297 SystemIO conflicts
with Region \_TZ_.IP__ 1 (20120111/utaddress-251)
[ 2312.804919] ACPI Warning: 0x00000290-0x00000297 SystemIO conflicts
with Region \_SB_.PCI0.LPCB.SIO1.RNTR 2 (20120111/utaddress-251)
[ 2312.804934] ACPI: If an ACPI driver is available for this device, you
should use it instead of the native driver
Could anybody tell me what the above means please? Is there a conflict
between ACPI and the Fintek kernel module sensors (the service) is
trying to load? Is there a separate "ACPI driver" I should be using
instead? If so, how can I activate it so that I could get to read my fan
sensors?
When I run "sensors" (the program) I see very limited information, like
this:
acpitz-virtual-0
Adapter: Virtual device
temp1: +48.0°C (crit = +127.0°C)
temp2: +26.8°C (crit = +127.0°C)
temp3: +26.8°C (crit = +100.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +51.0°C (crit = +100.0°C)
Core 1: +51.0°C (crit = +100.0°C)
This is not OK because I don't have any RPMs of any of the fans (I have
3 fans running) and various voltages I have on this board. I am using
Fedora Core 17 with kernel version 3.3.4 with the latest version of
lm_sensors (3.3.2, I think).
Many thanks!
MZ
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2012-06-26 23:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 23:56 Michael Zintakis [this message]
2012-06-27 17:15 ` Fintek f71882fg ACPI conflict Guenter Roeck
2012-06-27 17:15 ` [lm-sensors] " Guenter Roeck
2012-06-27 23:00 ` Michael Zintakis
2012-06-27 23:00 ` Michael Zintakis
2012-06-28 1:45 ` Matthew Garrett
2012-06-28 1:45 ` Matthew Garrett
2012-06-28 11:15 ` Michael Zintakis
2012-06-28 11:15 ` Michael Zintakis
2012-06-28 12:40 ` Jean Delvare
2012-06-28 12:40 ` Jean Delvare
2012-06-28 12:53 ` Michael Zintakis
2012-06-28 12:53 ` Michael Zintakis
2012-06-28 13:27 ` Jean Delvare
2012-06-28 13:27 ` Jean Delvare
2012-06-29 5:35 ` Robert Hancock
2012-06-29 5:35 ` Robert Hancock
2012-06-29 12:11 ` Michael Zintakis
2012-06-29 12:11 ` Michael Zintakis
2012-06-29 16:34 ` Guenter Roeck
2012-06-29 16:34 ` Guenter Roeck
2012-06-28 5:20 ` Guenter Roeck
2012-06-28 5:20 ` Guenter Roeck
2012-06-28 11:31 ` Michael Zintakis
2012-06-28 11:31 ` Michael Zintakis
2012-06-28 17:12 ` Guenter Roeck
2012-06-28 17:12 ` Guenter Roeck
2012-06-28 17:39 ` Michael Zintakis
2012-06-28 17:39 ` Michael Zintakis
2012-06-28 18:57 ` Guenter Roeck
2012-06-28 18:57 ` Guenter Roeck
2012-06-28 3:15 ` Andrey Repin
2012-06-28 11:36 ` Michael Zintakis
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=4FEA4C10.2060904@googlemail.com \
--to=michael.zintakis@googlemail.com \
--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.