From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset
Date: Wed, 01 Sep 2010 13:54:05 +0000 [thread overview]
Message-ID: <20100901155405.06b119a7@hyperion.delvare> (raw)
In-Reply-To: <4C7934CC.4020902@fidit.com>
On Wed, 01 Sep 2010 15:07:50 +0200, support RG wrote:
> as i read in Re: [lm-sensors] lmsensors doesn't detect core-i7 sensors
>
> i launch latest release from svn
> pass one step more than ever
>
> Do you want to probe the I2C/SMBus adapters now? (YES/no):
> Using driver `i2c-i801' for device 0000:00:1f.3: Intel 3400/5 Series (PCH)
>
> as before
> _>Do you want to probe the I2C/SMBus adapters now? (YES/no):
> >Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3._
> >Sorry, no supported PCI bus adapters found.
>
> but sensors view no more and dmesg already says conflict
>
> fidit@de100816A:~/lm-sensors-r5857-20100823/prog$ dmesg | grep conflict
> [ 17.201490] ACPI: resource 0000:00:1f.3 [0xf000-0xf01f] conflicts
> with ACPI region SMBI [0xf000-0xf00f]
>
> could you help me ?
Poster avec un nom bidon, ça n'aide pas à avoir des réponses. La
prochaine fois, postez avec un vrai nom...
Your problem is that the ACPI BIOS requested the I/O ports of the SMBus
control, so they are no longer available for native Linux drivers. What
the BIOS uses the ports for, I can't tell without disassembling the
DSDT table of the machine.
> finaly, _with or without i2c-i801_ and//or k8temp load at startup
> sensors return only
Why the hell would you load the k8temp driver on an Intel system?
If anything, you would load the coretemp driver, which is meant for
Intel CPUs.
> fidit@de100816A:~$ sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1: +39.5°C (crit = +100.0°C)
This is quite possibly why the ACPI BIOS needed access the SMBus.
> under everest on seven, 6 temp are detect.
This is awfully vague. Which temperatures? From what devices?
It is entirely possible that Everest decided to bypass the ACPI
resource conflict. Something you definitely don't want to do on a
production machine, at least not before a complete analysis of the DSDT.
If you aren't happy with the situation, I suggest that you contact the
hardware vendor and ask they how you are supposed to do hardware
monitoring on that model.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2010-09-01 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 16:09 [lm-sensors] i2c-i801 module conflict with 3400 Series Chipset support RG
2010-08-31 23:50 ` support RG
2010-09-01 13:07 ` support RG
2010-09-01 13:54 ` Jean Delvare [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=20100901155405.06b119a7@hyperion.delvare \
--to=khali@linux-fr.org \
--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.