[lm-sensors] ATK0110 on older Asus board

frollic nilsson frollic at gmail.com
Mon Feb 22 21:19:57 CET 2010


On Mon, Feb 15, 2010 at 5:08 PM, Luca Tettamanti <kronos.it at gmail.com> wrote:
> On Mon, Feb 15, 2010 at 4:31 PM, frollic nilsson <frollic at gmail.com> wrote:
>> On Fri, Feb 12, 2010 at 11:05 AM, Luca Tettamanti <kronos.it at gmail.com> wrote:
>>> On Thu, Feb 11, 2010 at 9:10 PM, frollic nilsson <frollic at gmail.com> wrote:
>>>> On Thu, Feb 11, 2010 at 5:25 PM, Luca Tettamanti <kronos.it at gmail.com> wrote:
>>>>> On Thu, Feb 11, 2010 at 04:36:53PM +0100, frollic nilsson wrote:
>>>>>
>>>>> Ok, this means that ACPI core is not even calling the add method.
>>>>> I guess that I can happen if _STA reports that the device is not functional.
>>>>
>>>> with the extra code inserted, I get a AIDI = 1 in the logs
>>>
>>> As I suspected the device is disabled by the BIOS (AI-whatever is the
>>> commercial name of the hwmon features, I guess AIDI = AI DIsable).
>>> You should try and see if there's a relevant option in the BIOS setup
>>> screen (btw, is there a monitoring page? does it work?)
>>
>> Yeah, I got the cpu temp and fan RPMs displayed in BIOS.
>
> Nothing to enable the hwmon or "AI-something"?
> What about the voltages? Do you see them? Is "Vcore" is spelled all upper case?
>
>> Parts from the messages log file (I grep:ed for "ACPI"), I restarted
>> the systenm three days ago:
>
>> Feb 12 22:41:28 atlantis kernel: ACPI: I/O resource w83627ehf
>> [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
>> Feb 12 22:41:28 atlantis kernel: ACPI: If an ACPI driver is available
>> for this device, you should use it instead of the native driver
>> Feb 12 22:51:12 atlantis kernel: ACPI: I/O resource w83627ehf
>> [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
>> Feb 12 22:51:12 atlantis kernel: ACPI: If an ACPI driver is available
>> for this device, you should use it instead of the native driver
>> Feb 12 22:51:43 atlantis kernel: ACPI: I/O resource w83627ehf
>> [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
>> Feb 12 22:51:43 atlantis kernel: ACPI: If an ACPI driver is available
>> for this device, you should use it instead of the native driver
>
> The resources are reserved even if the ATK0110 device itself is disabled, weird.
> This looks like a BIOS bug to me: the device is explicitly disabled,
> but ACPI still clams the ioports for the monitoring chip.
> I'm not sure how to handle this mobo, but clearly it's safe to use
> acpi_enforce_resources=lax and load the native driver.
>
> Luca
>

Well, tried the lax as well got the same "error"

w83627ehf: Found W83627EHG chip at 0x290
ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region
HWRE [0x290-0x299]
ACPI: This conflict may cause random problems and system instability
ACPI: If an ACPI driver is available for this device, you should use
it instead of the native driver

:D




More information about the lm-sensors mailing list