You are not logged in.
Pages: 1
Hello,
I have Arch Linux updated with the latest Kernel (5.8.13).
When I put in the terminal:
dmesg | grep ACPI
I get the following two errors:
ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\_SB.PCI0.SMB.SMB0) (20200528/utaddress-204)
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
I don't know what they mean or how I can isolate them.
Offline
The second message means the manufacturer of the firmware expects it to be used exclusively with Other OS .
Usually linux is able to workaround this, sometimes we have to pretend to be that Other OS .
The first message requires more info to determine if it could give problems.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I have a similar line; I narrowed it down to a conflict with the Super-IO chip my mobo uses (NCT-6793D).
In order for the chip to properly monitor, I have to put this in my kernel command line:
acpi_enforce_resources=laxAnd, that brings that message up.
It's never caused any problems other than that line in dmesg.
Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '
Offline
The second message means the manufacturer of the firmware expects it to be used exclusively with Other OS .
Usually linux is able to workaround this, sometimes we have to pretend to be that Other OS .The first message requires more info to determine if it could give problems.
How can I solve the second message?
Offline
I have a similar line; I narrowed it down to a conflict with the Super-IO chip my mobo uses (NCT-6793D).
In order for the chip to properly monitor, I have to put this in my kernel command line:
acpi_enforce_resources=laxAnd, that brings that message up.
It's never caused any problems other than that line in dmesg.
what does that kernel command line do?
Offline
Really the best option here is to just ignore them. You can't fix your firmware not responding to the fact that your using Linux and it largely doesn't matter, and the other is simply an information that the acpi declares certain information incorrectly.
The only thing that can fix these properly is an UEFI update, otherwise you shouldn't worry too much.
Offline
Really the best option here is to just ignore them. You can't fix your firmware not responding to the fact that your using Linux and it largely doesn't matter, and the other is simply an information that the acpi declares certain information incorrectly.
The only thing that can fix these properly is an UEFI update, otherwise you shouldn't worry too much.
The UEFI is now up to date.
What do you mean by "ignore"? You mean the option "acpi_enforce_resources = lax"?
Offline
You can ignore both messages.
Like @V1del says, the
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignoredis due to the way ACPI is implemented in your BIOS. While your BIOS may be up to date, it still has incompatibilities with the Linux kernel. Unless (and until) your hardware maker and BIOS developer fix the BIOS, you'll get that warning.
If you don't see any errors, you can safely ignore it.
Your other message
ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\_SB.PCI0.SMB.SMB0) (20200528/utaddress-204)is caused by a resource conflict between ACPI and some other piece of software (most likely lm-sensors).
If your hardware monitoring (fans, temps, etc) is working you can ignore this message, too (and don't even worry about the command-line parameter in my first post).
Last edited by merlock (2020-10-09 02:12:07)
Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '
Offline
Pages: 1