r/cachyos • u/Firehaven44 • 12h ago
Bug Report Acer Laptop BIOS's and cachyOS are not compatible
So,
As I have used AI, read load of cachyOS forum articles, as well as Reddit posts, every time someone cannot reboot and enter bios, they have always been Acer laptops.
Well guess who installed cachyOs on an Acer laptop, this guy!
Does anyone know if cachyOS is going to try and resolve this, if there actually is a solution or a hardware issue that cannot be fixed with Acer laptops?
I have read some articles stating:
- Acer does not trust Arch based disotros from the BIOS level.
- You need to turn off secure boot
- cachyOS creates too many EDI partitions that confuses the bios.
Only way to fix this is:
- Remove the SSD, reset the bios with the CMOS removal.
- Remove secure boot after above.
- Install a different OS on Acer laptops.
And probably more that I am forgetting. Sounds like cachy's install process is just confusing the BIOS so it hangs at the Acer logo during boot if you try to access the BIOS. Anyone have any new ideas to try?
- Jamming F2 or other keys does not work.
- running CLI commands like "systemctl reboot --firmware-setup" does not work.
- Use Plasma KDE and setting it to reboot into UEFI on next reboot does not work.
- etc.
thanks for reading, but because Acer is just a major laptop brand, I was surprised to find this out because I bought this laptop to specifically install this OS on it.
EDIT:
SOLVED:
Please read this article:
https://discuss.cachyos.org/t/no-bios-access-after-cachyos-install/32156/10
The command:
```
sudo efibootmgr -b 0002 -B
```
Mine too was the same entry within the CLI of 002. That being said, digging deeper into what this command is doing:
- NVRAM Entry vs. Disk Files: This command does not delete any bootloader files from your hard drive (such as files in
/boot/efior the ESP partition). It only removes the pointer inside the motherboard's non-volatile RAM (NVRAM) that tells the UEFI firmware: "Here is an OS named X located at path Y on disk Z." - Why It Solves the Acer/UEFI Lockout Bug: Some buggy motherboard implementations (notably on certain Acer, HP, or Lenovo laptops) crash or hang on the boot logo when trying to enter the BIOS/UEFI setup screen if an NVRAM boot entry contains metadata, arguments, or paths their proprietary firmware parser cannot handle. Deleting the specific NVRAM entry stops the motherboard's setup utility from choking on that entry, restoring your ability to access the BIOS setup menu.
- How CachyOS Still Boots Afterward: If your NVRAM entry for CachyOS is removed, modern UEFI systems will fall back to the generic fallback path (e.g.,
/EFI/BOOT/BOOTX64.EFI) or rely on your primary bootloader (likesystemd-bootor GRUB) to discover and launch the OS.

