Re: nct6775 on Asus Z97-A not working with new BIOS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 24, 2014 at 7:33 PM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
> That's what I thought. That might be an oversight by ASUS, or the BIOS is
> now genuinely accessing the chip. You can boot with
> acpi_enforce_resources=lax,
> on your own risk.

That did it!
kern.log:
-------
Sep 24 19:49:12 glados kernel: [    0.000000] DMI: ASUS All
Series/Z97-A, BIOS 1008 05/29/2014
[...]
Sep 24 19:49:12 glados kernel: [    1.370262] nct6775: Enabling
hardware monitor logical device mappings.
Sep 24 19:49:12 glados kernel: [    1.370272] nct6775: Found NCT6791D
or compatible chip at 0x2e:0x290
Sep 24 19:49:12 glados kernel: [    1.370275] ACPI Warning:
0x0000000000000295-0x0000000000000296 SystemIO conflicts with Region
\_GPE.HWM_ 1 (20131115/utaddress-251)
Sep 24 19:49:12 glados kernel: [    1.370278] ACPI: This conflict may
cause random problems and system instability
Sep 24 19:49:12 glados kernel: [    1.370279] ACPI: If an ACPI driver
is available for this device, you should use it instead of the native
driver
Sep 24 19:49:12 glados kernel: [    1.375243] ppdev: user-space
parallel port driver
-------
I guess I'll have to see if I encounter any system instabilities.
sensors now reads
-------
nct6791-isa-0290
Adapter: ISA adapter
in0:                    +0.90 V  (min =  +0.00 V, max =  +1.74 V)
in1:                    +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                    +3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                    +3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                    +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                    +2.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                    +0.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                    +3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                    +3.25 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                    +1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                   +0.00 V  (min =  +0.00 V, max =  +0.00 V)
in11:                   +0.83 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                   +0.00 V  (min =  +0.00 V, max =  +0.00 V)
in13:                   +0.00 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                   +0.00 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                     0 RPM  (min =    0 RPM)
fan2:                   688 RPM  (min =    0 RPM)
fan3:                     0 RPM  (min =    0 RPM)
fan4:                     0 RPM  (min =    0 RPM)
fan5:                     0 RPM  (min =    0 RPM)
fan6:                     0 RPM
SYSTIN:                 +24.0°C  (high =  +0.0°C, hyst =  +0.0°C)
ALARM  sensor = thermistor
CPUTIN:                 +30.0°C  (high = +80.0°C, hyst = +75.0°C)
sensor = thermistor
AUXTIN0:               -128.0°C    sensor = thermistor
AUXTIN1:               -128.0°C    sensor = thermistor
AUXTIN2:                +35.0°C    sensor = thermistor
AUXTIN3:               +127.0°C    sensor = thermistor
PECI Agent 0:           +29.0°C
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C
PCH_CHIP_TEMP:           +0.0°C
PCH_CPU_TEMP:            +0.0°C
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:           disabled
-------

Thanks a lot for your help!
 Ulrike



> You could also try to decode the DSDT to find out what
> the BIOS is doing, but that is not easy.
>
> Problem is that ASUS doesn't support Linux on their PC boards, so they won't
> help you much.
>
> Guenter
>

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux