[Bug 204807] Hardware monitoring sensor nct6798d doesn't work unless acpi_enforce_resources=lax is enabled

bugzilla-daemon
2022-11-23T23:01:36Z

--- Comment #275 from Denis Pauk (pauk.denis@gmail.com) ---
(In reply to Slawomir Stepien from comment #274)
> (In reply to Slawomir Stepien from comment #273)
> > (In reply to Denis Pauk from comment #272)
> > > (In reply to Slawomir Stepien from comment #271)
> > > > Created attachment 303265 [details]
> > > > Add support for ROG STRIX B660-I GAMING WIFI
> > > >
> > > > This adds support for ROG STRIX B660-I GAMING WIFI into the "Asus WMI
> for
> > > > nct6775 v6.0 base (2022.11.12)" patch.
> > >
> > > Thank you! I will add your code to the next patch version.
> > >
> > > Just for recheck, could you please share error place on init when you
> added
> > > your board to asus_acpi_boards(x670 generation methods) or
> > > asus_wmi_boards(b550/x570 generation methods)? Are both of methods of
> > access
> > > failed?
> > >
> > > I have hoped B660 boards have same access method as x670 boards at least
> > :-(
> >
> > [93233.798384] nct6775: Can't read ChipID by Asus WMI.
> > [93233.798386] nct6775: No dmi definition `ROG STRIX B660-I GAMING
> > WIFI`:`ASUSTeK COMPUTER INC.`
> > [93233.798446] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
> > [93233.798449] ACPI Warning: SystemIO range
> > 0x0000000000000295-0x0000000000000296 conflicts with OpRegion
> > 0x0000000000000290-0x0000000000000299 (\RMTW.SHWM) (20220331/utaddress-204)
> > [93233.798452] ACPI: OSL: Resource conflict; ACPI support missing from
> > driver?
>
> But if I add the board to the asus_acpi_boards, it works but with:
>
> [93515.558164] nct6775: Using Asus ACPI to access 0xc1 chip.
> [93515.558166] nct6775: No dmi definition `ROG STRIX B660-I GAMING
> WIFI`:`ASUSTeK COMPUTER INC.`
> [93515.558229] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
>
> So I guess this is a better approach for my case?

It should be, its near to correct way as its designed by ASUS. Its not clear
for now how to make such calls by WMI, i suppose that they have changed WMI
method ID to some different or hide it behind other methods.

Look to the X670 patch discussion: