Subject: Re: Bump: Re: Help request: BIOS Bug: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

Hi everyone,
thanks for your feedback. For context, I am using a slightly older board (gigabyte arous elite v1). I had initially thought just to ignore it, however then (and re-enforced by your feedback) I have pinned this to being responsible for some system crashes I experienced with my wifi/GPU having conflicting regions logged .
While I have worked around this by changing the wifi initialisation settings, I am worried this will still come up to bite me in the future.
I am thinking to try

- acpi_osi=Linux

first if the kernel is currently ignoring the message, as it may be needed for this function to be called / work correctly. I had initially just been ignoring it until I pinned this down to being underlying cause of my graphics card not initialising correctly - was a lot of starring at logs to get to that conclusion and put them together!
Kind regards,
Ryan
Sent with [Proton Mail](https://pr.tn/ref/64KQPP9W) secure email.
On Monday, 6 April 2026 at 19:41, Cliff Hayes <chayes74@msn.com> wrote:

I'm not sure this is anything to be really concerned about, but you might be able to clear the ACPI warning by inserting the following into your GRUB boot params - "acpi_enforce_resources=lax"

Looks like the BIOS and Linux kernel are battling over some memory allocation.

https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt

acpi_enforce_resources= [ACPI]
{ strict | lax | no }
Check for resource conflicts between native drivers
and ACPI OperationRegions (SystemIO and SystemMemory
only). IO ports and memory declared in ACPI might be
used by the ACPI subsystem in arbitrary AML code and
can interfere with legacy drivers.
strict (default): access to resources claimed by ACPI
is denied; legacy drivers trying to access reserved
resources will fail to bind to device using them.
lax: access to resources claimed by ACPI is allowed;
legacy drivers trying to access reserved resources
will bind successfully but a warning message is logged.
no: ACPI OperationRegions are not marked as reserved,
no further checks are performed.

As for the "firmware bug", that appears to be a remnant from an old check that BIOS programmers used to see if someone is running Linux. Modern Linux kernels ignore the request which is what I believe is being reported there.

You can "quiet down" these errors, if you want, by changing GRUB_CMDLINE_LINUX_DEFAULT to "quiet loglevel=3". That's going to only show messages that hit level 3 and not BIOS warnings which should be level 4.

What motherboard and BIOS version are you using?

---------------------------------------------------------------

From: subscriptionstome@protonmail.ch <subscriptionstome@protonmail.ch>
Sent: Monday, April 6, 2026 5:48 AM
To: debian-user@lists.debian.org <debian-user@lists.debian.org>
Subject: Bump: Re: Help request: BIOS Bug: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

Hi guys,

sorry to bump this one up but would appreciate a bit of guidance its stressng me out!

thanks

Sent from [Proton Mail](https://proton.me/mail/home) for Android.

-------- Original Message --------
On Sunday, 04/05/26 at 13:18 subscriptionstome@protonmail.ch wrote:

Hi team,

I have seen this error from day one on my system, however ignored it until (when my wifi and GPU were agressively competing for memory allocation) caused black screen until I stabilised the wifi up/down...

ACPI Warning: SystemIO range 0x...B00-0x...B08 conflicts with OpRegion ... (\GSA1.SMBI)
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

While resolved for now worried this could cause an issue in the future. I have seen various ideas and solutions online, inc setting:

- acpi_osi=Linux
-

acpi_osi=!

-

acpi_osi="Windows 2009"

etc.

Is this something you have encountered? Anyone have any suggestions?

thanks!

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: Bump: Re: Help request: BIOS Bug: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

Hi everyone,
good news - I implemented the acpi_osi=Linux parameter and can now see that the kernel logs it can read the ACPI tables correctly and many of my startup errors are resolved so this is encouraging. I can now move onto my next project knowing it isn't likely to break again (for this reason).
Thanks for the help.
Sent with [Proton Mail](https://pr.tn/ref/64KQPP9W) secure email.
On Tuesday, 7 April 2026 at 12:10, subscriptionstome@protonmail.ch <subscriptionstome@protonmail.ch> wrote:

Hi everyone,

thanks for your feedback. For context, I am using a slightly older board (gigabyte arous elite v1). I had initially thought just to ignore it, however then (and re-enforced by your feedback) I have pinned this to being responsible for some system crashes I experienced with my wifi/GPU having conflicting regions logged .

While I have worked around this by changing the wifi initialisation settings, I am worried this will still come up to bite me in the future.

I am thinking to try

- acpi_osi=Linux

first if the kernel is currently ignoring the message, as it may be needed for this function to be called / work correctly. I had initially just been ignoring it until I pinned this down to being underlying cause of my graphics card not initialising correctly - was a lot of starring at logs to get to that conclusion and put them together!

Kind regards,

Ryan

Sent with [Proton Mail](https://pr.tn/ref/64KQPP9W) secure email.

On Monday, 6 April 2026 at 19:41, Cliff Hayes <chayes74@msn.com> wrote:

I'm not sure this is anything to be really concerned about, but you might be able to clear the ACPI warning by inserting the following into your GRUB boot params - "acpi_enforce_resources=lax"

Looks like the BIOS and Linux kernel are battling over some memory allocation.

https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt >>
acpi_enforce_resources= [ACPI]
{ strict | lax | no }
Check for resource conflicts between native drivers
and ACPI OperationRegions (SystemIO and SystemMemory
only). IO ports and memory declared in ACPI might be
used by the ACPI subsystem in arbitrary AML code and
can interfere with legacy drivers.
strict (default): access to resources claimed by ACPI >> is denied; legacy drivers trying to access reserved
resources will fail to bind to device using them.
lax: access to resources claimed by ACPI is allowed;
legacy drivers trying to access reserved resources
will bind successfully but a warning message is logged. >> no: ACPI OperationRegions are not marked as reserved, >> no further checks are performed.

As for the "firmware bug", that appears to be a remnant from an old check that BIOS programmers used to see if someone is running Linux. Modern Linux kernels ignore the request which is what I believe is being reported there.

You can "quiet down" these errors, if you want, by changing GRUB_CMDLINE_LINUX_DEFAULT to "quiet loglevel=3". That's going to only show messages that hit level 3 and not BIOS warnings which should be level 4.

What motherboard and BIOS version are you using?

---------------------------------------------------------------

From: subscriptionstome@protonmail.ch <subscriptionstome@protonmail.ch>
Sent: Monday, April 6, 2026 5:48 AM
To: debian-user@lists.debian.org <debian-user@lists.debian.org>
Subject: Bump: Re: Help request: BIOS Bug: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

Hi guys,

sorry to bump this one up but would appreciate a bit of guidance its stressng me out!

thanks

Sent from [Proton Mail](https://proton.me/mail/home) for Android.

-------- Original Message --------
On Sunday, 04/05/26 at 13:18 subscriptionstome@protonmail.ch wrote:

Hi team,

I have seen this error from day one on my system, however ignored it until (when my wifi and GPU were agressively competing for memory allocation) caused black screen until I stabilised the wifi up/down...

ACPI Warning: SystemIO range 0x...B00-0x...B08 conflicts with OpRegion ... (\GSA1.SMBI)
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored

While resolved for now worried this could cause an issue in the future. I have seen various ideas and solutions online, inc setting:

- acpi_osi=Linux
-

acpi_osi=!

-

acpi_osi="Windows 2009"

etc.

Is this something you have encountered? Anyone have any suggestions?

thanks!

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)