ACPI error after installing Ubuntu 22.04

[szovatilevente]

Can anyone help me please? I installed 22.04 on my Asus f506lh laptop.(without dual boot).After booting the system I got an error. Interesting cause the system works fine after booting.i have secure boot disabled.Can someone help me please ? thank you!

 

[Bartman]

Probably not the answer you expected.

ACPI errors are a common occurrence with Linux based on my experience using Linux.

ACPI errors are a regular occurrence on several of my Linux computers and never cause any problems on my computers.

I believe it's a bug in Linux and the Linux developers don't consider it to be any major concern.

If all is working fine I wouldn't worry.

ACPI bios error... still boots fine.

I am getting this bug when booting. I think it started appearing after my most recent update. What is it?

www.linux.org

 

[szovatilevente]

Probably not the answer you expected.

ACPI errors are a common occurrence with Linux based on my experience using Linux.

ACPI errors are a regular occurrence on several of my Linux computers and never cause any problems on my computers.

I believe it's a bug in Linux and the Linux developers don't consider it to be any major concern.

If all is working fine I wouldn't worry.

I understand, thank you so much for the explication.

 

[Lord Boltar]

You can get rid of those ACPI Error messages by

1. Open '/etc/default/grub' in an editor with root access. In your case I believe Ubuntu uses gedit as it's text editor

sudo gedit /etc/default/grub

2. The line with 'GRUB_CMDLINE_LINUX_DEFAULT', add the loglevel=3 part. The original looks like

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'

Change it to this:

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash loglevel=3'

Then save the changes and close it, now open a terminal and run:

sudo update-grub

Reboot and see the results

 

[Bartman]

You can get rid of those ACPI Error messages by

1. Open '/etc/default/grub' in an editor with root access. In your case I believe Ubuntu uses gedit as it's text editor

sudo gedit /etc/default/grub

2. The line with 'GRUB_CMDLINE_LINUX_DEFAULT', add the loglevel=3 part. The original looks like

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'

Change it to this:

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash loglevel=3'

Then save the changes and close it, now open a terminal and run:

sudo update-grub

Reboot and see the results

I'm curious does this actually solve the errors or does it just hide the errors from being displayed.

 

[Lord Boltar]

Some BIOS/UEFI developers are just lazy and don't implement the entire ACPI specification into their BIOS/UEFI, or more worse, they implement it in the wrong way. When Linux tries to read some specific ACPI parameters, which don't exist, or are wrong, it fails and reports this kind of error. There is not a lot you can do about these errors, except try to upgrade the BIOS - my above post hides the errors it changes the log reporting so it is no longer seen but Loglevel 3, is identified by the KERN_ERR string, it’s the next in the scale. Messages adopting this level are often used to notify the user about non-critical errors. So adding loglevel=3 will not notify you of non-critical errors.
As far as I know there is no fix except maybe upgrading your BIOS or changing your BIOS from UEFI to Legacy which may help

 

[Bartman]

I read something similar to what you posted here.

ACPI error on every boot

I recently switched from Windows 10 to Ubuntu. So far so good, but I get these errors on every boot. I was not getting these when on Windows 10 (not sure if it is because Windows didn't have these ...

askubuntu.com

I figured since you have Linux wisdom that I don't that you may have found a solution.

Most of my Linux computers are outdated and no bios updates for any improvements etc.

I can live with the ACPI errors along with a few other errors I seem to have

Just part of using outdated computers on my end.

Thanks.

 

[szovatilevente]

Some BIOS/UEFI developers are just lazy and don't implement the entire ACPI specification into their BIOS/UEFI, or more worse, they implement it in the wrong way. When Linux tries to read some specific ACPI parameters, which don't exist, or are wrong, it fails and reports this kind of error. There is not a lot you can do about these errors, except try to upgrade the BIOS - my above post hides the errors it changes the log reporting so it is no longer seen but Loglevel 3, is identified by the KERN_ERR string, it’s the next in the scale. Messages adopting this level are often used to notify the user about non-critical errors. So adding loglevel=3 will not notify you of non-critical errors.
As far as I know there is no fix except maybe upgrading your BIOS or changing your BIOS from UEFI to Legacy which may help

Thank you!

 

[szovatilevente]

You can get rid of those ACPI Error messages by

1. Open '/etc/default/grub' in an editor with root access. In your case I believe Ubuntu uses gedit as it's text editor

sudo gedit /etc/default/grub

2. The line with 'GRUB_CMDLINE_LINUX_DEFAULT', add the loglevel=3 part. The original looks like

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'

Change it to this:

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash loglevel=3'

Then save the changes and close it, now open a terminal and run:

sudo update-grub

Reboot and see the results

I will try and come back with news.thank you

 

[szovatilevente]

You can get rid of those ACPI Error messages by

1. Open '/etc/default/grub' in an editor with root access. In your case I believe Ubuntu uses gedit as it's text editor

sudo gedit /etc/default/grub

2. The line with 'GRUB_CMDLINE_LINUX_DEFAULT', add the loglevel=3 part. The original looks like

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash'

Change it to this:

GRUB_CMDLINE_LINUX_DEFAULT='quiet splash loglevel=3'

Then save the changes and close it, now open a terminal and run:

sudo update-grub

Reboot and see the results

it worked thank you so much