Arch Linux

ForsakenCommander

Member

Registered: 2014-08-09

Posts: 8

Problem with the correct (order of) efi boot parameters

Hello,

I have a problem regardinge the correct (order of) kernel boot parameters.
ucode gets not loaded and i have problems with standby. (acpi_osi gets not recognized?)

~/ journalctl -k --grep=microcode
Mai 03 22:37:33 companion kernel: microcode: CPU0: patch_level=0x08200103
Mai 03 22:37:33 companion kernel: microcode: CPU1: patch_level=0x08200103
Mai 03 22:37:33 companion kernel: microcode: Microcode Update Driver: v2.2.

microcode: microcode updated early to new patch_level=FOO

is missing.
Here is my efiboot entry maker script and the efiboot output:

~/ cat efiboot
#!/bin/zsh
efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Arch Linux" -l /vmlinuz-linux -u 'cryptdevice=/dev/nvme0n1p2:arch root=/dev/mapper/arch ro initrd=\amd-ucode.img initrd=\initramfs-linux.img acpi_osi=Windows 2018' -v

~/ efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0012,0013,0014,0015,0016,0017
Boot0000* Arch Linux    HD(1,GPT,685c4c9c-955f-b34f-8125-a8d89c17d25d,0x800,0x32000)/File(\vmlinuz-linux)c.r.y.p.t.d.e.v.i.c.e.=./.d.e.v./.n.v.m.e.0.n.1.p.2.:.a.r.c.h. .r.o.o.t.=./.d.e.v./.m.a.p.p.e.r./.a.r.c.h. .r.o. .i.n.i.t.r.d.=.\.a.m.d.-.u.c.o.d.e...i.m.g. .i.n.i.t.r.d.=.\.i.n.i.t.r.a.m.f.s.-.l.i.n.u.x...i.m.g. .a.c.p.i._.o.s.i.=.W.i.n.d.o.w.s. .2.0.1.8.
Boot0010  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu     FvFile(86488440-41bb-42c7-93ac-450fbf7766bf)
Boot0012* NVMe: SKHynix_HFM256GDHTNI-87A0B              PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,AC-E4-2E-00-1A-06-05-38)....2.LN........
Boot0013* ATA HDD:      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot0014* USB HDD: Generic Flash Disk   PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(9,0)3.!..3.G..A.....
Boot0015* USB LAN:      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,e854bca4cae7704ca322b00da0376322)
Boot0016* USB FDD:      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0017* USB CD:       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)

Could someone please point the right direction.
Thank you in advance

ForsakenCommander

Member

Registered: 2014-08-09

Posts: 8

Re: Problem with the correct (order of) efi boot parameters

lscpu = AMD 3020e with Radeon Graphics

Linux companion 5.17.5-arch1-1 #1 SMP PREEMPT Wed, 27 Apr 2022 20:56:11 +0000 x86_64 GNU/Linux

System is updated to latest packages

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,285

Re: Problem with the correct (order of) efi boot parameters

If the parameters are visible in /proc/cmdline then they are correctly passed to the kernel.

If your microcode is already the latest it can be, you won't see the early patch message. Setting acpi_osi is a desperate attempt at trying to lie to your BIOS/firmware about your operating system and has absolutely no guarantee to fix anything (... though it may do so, but again no guarantee).

As such this feels like you're chasing a possible red herring because you think there must be some sort of visible and notable reaction to these parameters, but that really isn't guaranteed. Which actual laptop model? What are your actual suspension issues? How do they show itself? Does the system not wake up? Can you reboot? If you were able to reboot from a wakeup post

sudo journalctl -b

FWIW the acpi_osi= needs to be a string so the proper way to pass it would be acpi_osi="Windows 2018"

Last edited by V1del (2022-05-04 09:06:11)