Results 1 to 7 of 7

Thread: ACPI Bios Error

  1. #1
    Join Date
    2022-Jun
    Posts
    1

    ACPI Bios Error

    I'm using latest and up-to-date version of Kali linux.
    Distributor ID: Kali
    Description: Kali GNU/Linux Rolling
    Release: 2022.2
    Codename: kali-rolling

    After updating kernel from 5.16 to 5.17, I'm getting this error while booting Kali linux. While laptop is booting fine, but this error always showed up while booting. Any ways to solve this error or I just have to ignore since I tried searching this issue on many forums but didn't able to find any solutuion. My laptop is Lenovo Ideapad 330, i5 8250u with MX 150 GPU.


    [ 0.986016] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986031] ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986108] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986118] ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986223] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986232] ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986353] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986362] ACPI Error: Aborting method \_PR.PR04._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986464] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986473] ACPI Error: Aborting method \_PR.PR05._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986551] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986560] ACPI Error: Aborting method \_PR.PR06._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986665] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986674] ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)

  2. #2
    Join Date
    2022-Jul
    Posts
    3
    Quote Originally Posted by art23 View Post
    I'm using latest and up-to-date version of Kali linux.
    Distributor ID: Kali
    Description: Kali GNU/Linux Rolling
    Release: 2022.2
    Codename: kali-rolling

    After updating kernel from 5.16 to 5.17, I'm getting this error while booting Kali linux. While laptop is booting fine, but this error always showed up while booting. Any ways to solve this error or I just have to ignore since I tried searching this issue on many forums but didn't able to find any solutuion. My laptop is Lenovo Ideapad 330, i5 8250u with MX 150 GPU.


    [ 0.986016] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986031] ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986108] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986118] ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986223] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986232] ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986353] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986362] ACPI Error: Aborting method \_PR.PR04._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986464] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986473] ACPI Error: Aborting method \_PR.PR05._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986551] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986560] ACPI Error: Aborting method \_PR.PR06._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.986665] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.986674] ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    I'm observing the same issue and I think we'll have to wait for a patched kernel. You'll find more information on this page: https://github.com/intel/linux-intel-lts/issues/22

  3. #3
    Join Date
    2021-May
    Location
    UK
    Posts
    603
    Try updating your boot config..

    sudo grub-mkconfig -o /boot/grub/grub.cfg

  4. #4
    There are a lot of people complaining that they run into a blue screen with an ACPI_BIOS_ERROR. They didn?t know what happened and want to know the useful solutions to fix the ACPI BIOS error. Noticing this, I decide to introduce such BSOD error (Blue Screen of Death error) first; then, provide the exact steps to fix it on a Windows PC.
    To sum up, there are two root reasons for causing ACPI BIOS error Windows 10.


    First, the Advanced Configuration and Power Interface (ACPI) Basic Input / Output System (BIOS) is not compliant with ACPI prompts the error message. There are obvious differences between the ACPI in the OS and BIOS; the differences will have an impact on the outcome of simultaneous read & write operations and the frequently used features, such as Plug and Play (PnP) and Power Management.


    Second, users have added the Random Access Memory (RAM) to computer during hibernation; the operating system will detect this change while the file Hiberfil.sys is loaded.

    This may help you,
    Rachel Gomez

  5. #5
    Join Date
    2022-Jul
    Posts
    3
    Hi Fred and everyone. Sorry for the delay in replying - I've had a pretty busy week. Thanks for your suggestions. I tried grub-mkconfig, but unfortunately, it didn't remove the error. This is my initial error list:

    sudo dmesg | grep -i ERROR
    [ 0.922850] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.922864] ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.922943] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.922950] ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.923019] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.923027] ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 27.614066] snd_soc_skl 0000:00:1f.3: Direct firmware load for 9d71-ACRSYS-ACRPRDCT-2-tplg.bin failed with error -2
    [ 27.614139] snd_soc_skl 0000:00:1f.3: Direct firmware load for skl_hda_dsp_generic-tplg.bin failed with error -2
    [ 27.651878] snd_soc_skl 0000:00:1f.3: Direct firmware load for dfw_sst.bin failed with error -2
    [ 27.651889] snd_soc_skl 0000:00:1f.3: ASoC: error at snd_soc_component_probe on 0000:00:1f.3: -2
    [ 27.652014] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -2


    And this is what I got after updating GRUB configuration:

    sudo dmesg | grep -i ERROR
    [ 0.924904] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.924917] ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.924987] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.924995] ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 0.925056] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330)
    [ 0.925062] ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
    [ 23.799954] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
    [ 23.799962] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    [ 23.799965] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
    [ 26.940077] snd_soc_skl 0000:00:1f.3: Direct firmware load for 9d71-ACRSYS-ACRPRDCT-2-tplg.bin failed with error -2
    [ 26.940125] snd_soc_skl 0000:00:1f.3: Direct firmware load for skl_hda_dsp_generic-tplg.bin failed with error -2
    [ 27.044862] snd_soc_skl 0000:00:1f.3: Direct firmware load for dfw_sst.bin failed with error -2
    [ 27.044887] snd_soc_skl 0000:00:1f.3: ASoC: error at snd_soc_component_probe on 0000:00:1f.3: -2
    [ 27.045160] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -2
    [ 35.723949] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
    [ 35.723961] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    [ 35.723965] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
    [ 35.806630] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
    [ 35.806654] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    [ 35.806661] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
    [ 35.944852] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
    [ 35.944879] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    [ 35.944887] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
    [ 1141.589737] pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
    [ 1141.589749] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    [ 1141.589751] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000


    I'm pretty sure that apart from the PCIe alerts, which have been around since the beginning, I used not to see the rest of these errors. I must have introduced them after updating Kali at some point (and it must have been rather recently).

    Another potentially related thing is that I can't access UEFI. It was possible earlier, but now my computer just shows a black screen when I try to do this. Also, Windows entry has been removed from my GRUB screen.
    I dual-boot a preinstalled Windows 10 and Kali on this computer. Each of the systems is installed on a separate hard drive, and the computer itself is Acer Swift. In the past, I'd just select which system I wanted to launch from the GRUB screen, and now there is only Kali there. I've found on the internet several pages suggesting this UEFI problem may be happening quite frequently to the users of Acer machines. I guess I'll try to investigate it more. Any further ideas of how to go about solving this are welcome though

    My kernel version is 5.18.

  6. #6
    Join Date
    2021-May
    Location
    UK
    Posts
    603
    I like the reFind boot manager, it is happy to 'find' and boot all OS's you may have installed easily with no fuss, and saves fighting with Windows and Linux etc;

    https://www.rodsbooks.com/refind/installing.html

  7. #7
    Join Date
    2022-Jul
    Posts
    3
    Hi all!
    I had to put this problem off for a while to focus on some more urgent stuff, but eventually, it looks like I got rid of all the issues I was experiencing Here is what worked for me - maybe it will help some other people too:



    (1) restoring Windows entry on GRUB screen


    I needed to add in /etc/default/grub the following line and only after this upgrading GRUB worked as expected:

    GRUB_DISABLE_OS_PROBER=false

    The line was completely missing from my configuration file, but some people have it and it's just commented out in their grub files. This line enabled OS-Prober which detected Windows and added it to my GRUB screen.
    If anyone faces the same issue as I did, do remember to make a backup of your grub configuration before editing it:
    cp /etc/default/grub ~/grub
    And after adding the OS-Prober line, update your GRUB with:
    sudo update-grub
    This command will probably output something like 'Found Windows Boot Manager (...) Adding boot menu entry for UEFI Firmware Settings'. And after restarting your computer, you should see the missing Windows Bootloader entry back on your GRUB screen.



    (2) fixing broken UEFI


    To regain access to my UEFI, I decided to reset its battery using the pinehole reset button on the bottom part of my laptop chase. In the case of my computer, it has a battery symbol next to it and one should be pressing this button for ~30 seconds with a paper clip or something like this, and then leave the computer turned off for a while.
    My computer still launched GRUB the first time I turned it on after this operation. I then started Windows and installed every available update there. It began booting directly into Windows and skipping GRUB after that, but I could access UEFI again. My UEFI actually got upgraded as a result of these steps. I checked its version before and after resetting the computer (here are a few Windows cmd commands to check BIOS version: wmic bios get smbiosbiosversion ; systeminfo | findstr /i bios ; powershell Get-WmiObject win32_bios). And finally, I restored GRUB Bootloader by changing the boot priority order in UEFI, in its Boot tab. I simply set GRUB to be at the top of the list and saved the change. I also made sure that Secure Boot was disabled (making this change required first setting a temporary supervisor password for my BIOS). And the next time I restarted my computer, it happily launched GRUB rather than Windows Bootloader.



    (3) ACPI BIOS Error


    I did the things above and then I also updated Kali. My kernel got upgraded to version 6.0, and the ACPI BIOS Error was already gone at this stage. I'm not sure if it was upgrading BIOS, upgrading my Linux kernel or something else that fixed this. Maybe the next person having the same issue will be able to examine it in more detail for us

Similar Threads

  1. Dual boot issue: ACPI BIOS Error (bug) Could not resolve (bug)
    By KrakenTech in forum Installing Archive
    Replies: 0
    Last Post: 2019-10-26, 05:26
  2. Acpi bios error ae_already_exists
    By elkia23 in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2019-03-05, 14:47
  3. "ACPI Error BIOS AE_NOT_FOUND" after installing kali linux
    By BintangAjie in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2018-10-25, 05:10

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •