On 12/24/19 7:59 AM, PGNet Dev wrote:
On 12/24/19 6:25 AM, Guenter Roeck wrote:
You'll probably see a note about an ACPI resource conflict. If the board
with NCT6796D wasn't yours, that may not be the case.
this certainly looks like it might be the source of the problem,
...
[33002.934396] nct6775: Found NCT6793D or compatible chip at 0x2e:0x290
[33002.934401] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[33002.934406] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[33017.944153] nct6775: Found NCT6795D or compatible chip at 0x2e:0x290
[33017.944158] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[33017.944164] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[33033.152135] nct6775: Found NCT6793D or compatible chip at 0x2e:0x290
[33033.152140] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[33033.152146] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[33085.807200] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
[33085.807205] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[33085.807209] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[33519.421923] usb 4-1.4.3: reset SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[34160.099747] it87: Found IT8728F chip at 0xfff8, revision 15
[34160.099769] it87: Beeping is supported
[34160.099844] it87: Found IT8728F chip at 0xfff8, revision 15
[34160.099865] it87: Beeping is supported
[34212.426003] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
[34212.426008] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[34212.426014] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[35066.143893] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
[35066.143900] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[35066.143907] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
...
if it is, iiuc your earlier comments, sounds like a BIOS issue.
The problem is - most likely - that the BIOS (or, rather, ACPI) accesses the
same memory range, and there is no synchronization. You could try to boot with
"acpi_enforce_resources=lax" command line option, but that would be on your
own risk, and some recent boards don't even boot if that command line option
is present.
You should not try to load the it87 driver on ASUS boards.
Did you try to load "asus_atk0110" ?
Guenter
