You are not logged in.
Hello everyone. I've got some problems with my laptop sometimes not booting up correctly. It works normally until after I've entered my encryption password. Regardless of whether it later finishes booting, I always see some messages before entering the encryption password that I've identified with dmesg (running $ dmesg | grep -i acpi\ error):
[ 0.452870] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 0.452877] ACPI Error: Method parse/execution failed \_SB.BTKL._STA, AE_NOT_FOUND (20170531/psparse-550)
[ 0.452894] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 0.452897] ACPI Error: Method parse/execution failed \_SB.BTKL._STA, AE_NOT_FOUND (20170531/psparse-550)
[ 0.471206] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 0.471212] ACPI Error: Method parse/execution failed \_SB.BTKL._STA, AE_NOT_FOUND (20170531/psparse-550)
[ 0.484500] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 0.484507] ACPI Error: Method parse/execution failed \_SB.BTKL._STA, AE_NOT_FOUND (20170531/psparse-550)
[ 9.248382] ACPI Error: [_OSI] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 9.248431] ACPI Error: Method parse/execution failed \_SB.BTKL._STA, AE_NOT_FOUND (20170531/psparse-550)In the cases when the boot finishes I just get a positive message about the system partition being unlocked and then my display manager starts. When it doesn't boot it shows the two lines repeated above one more time and then nothing happens. If I press the power button it displays "power down" and then powers down.
The OSI-part seems related to the fact that I have:
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_osi="in my /etc/default/grub. I did that so that the function keys would work (https://wiki.archlinux.org/index.php/AS … ction_Keys). Any ideas what might be the problem?
Last edited by SimonT (2017-11-14 12:25:02)
Offline
set it equal to something
Offline
I set it to "acpi_osi=Windows". I'm not sure how the fix in the link works but as far as I've understood some function keys are disabled by BIOS if the kernel reports that Windows isn't running. If that's right, setting it to Windows should keep the function keys functioning. It didn't seem to mess up anything for me. My keys are still working as usual. And the error message is gone. I'll report back if the problem with the boot not finishing comes up again. I'm marking the thread as solved for now.
Last edited by SimonT (2017-11-14 12:25:22)
Offline