Arch Linux

lunu lochlaena

Member

Registered: 2026-03-29

Posts: 2

[SOLVED] Adding kernel parameters when using EFI boot stub

Hello,

My laptop requires some kernel parameters to enable some fn+keys.

I followed this bootloader option, so I don't have a bootloader.
The wiki says that in my situation, editing params with EFI bootstub I should edit the /boot/loader/entries/arch.conf file, adding the paras desired, but mine didn't exist, so I ran

bootctl install

to generate one. Editing it doesn't seem to do anything.

My only chance to have added these options was when I ran the efibootmgr comand in the live enviorment. Would I be able to re-run my original efibootmgr command with the options? I have no idea what would happen, nor what approiate changes to make to it now that it's an installed system... out of my depth!

I'm not sure it matters, but the specific params I wish to add are 

pcie_aspm=force

and

acpi_osi=

as recomended for my laptop on the wiki.

Any advice would be greatly appreciated!

- Lunu

Last edited by lunu lochlaena (2026-03-31 16:34:56)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 74,673

Re: [SOLVED] Adding kernel parameters when using EFI boot stub

https://wiki.archlinux.org/title/Kernel … stemd-boot is systemd-boot, which you're apparently not using

https://wiki.archlinux.org/title/Unifie … efibootmgr
You can check

sudo efibootmgr --unicode

https://wiki.archlinux.org/title/EFI_bo … efibootmgr actually shows how to create entries, you'll have to apply the parameter there, then see https://wiki.archlinux.org/title/Unifie … efibootmgr again for how to delete entries or control the order.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

lunu lochlaena

Member

Registered: 2026-03-29

Posts: 2

Re: [SOLVED] Adding kernel parameters when using EFI boot stub

Ah, thank you. The similar naming really confuses me.
As the wiki says, the only way to edit and add parameters is to re-write the efibootmgr command, and so it advises you to write a shell script to keep it handy!
Re-wrote it, set it as next boot (then had to fix things with chroot..) now it all works
Thanks,

- lunu