You are not logged in.

#1 2025-03-28 13:36:25

lolowond
Member
Registered: 2025-03-28
Posts: 1

efi boot stub dell latitude 7480

Hi,

A few times ago I installed arch on a thinkpad and successfully used efi boot stub, using efibootmgr to record a «boot entry» (i'm not sure to fully understand uefi so correct me if i'm using the wrong terms)

Yesterday I put my ssd in a dell latitude 7480, and was unable to boot using the same method. I booted a usb arch iso, ran the same efibootmgr command that for my thinkpad, the computer succeed to list the arch usb uefi, but not the ssd one. With efibootmgr, i can see that my new entry was added, and that it is the first boot option in the BootOrder

In the bios, there is a weird configuration page where it seems i can add «boot entry», and it seems to list files from my efi partition. I can add a boot entry there, but using this i got a kernel panic. I think its because it didn't load the initramfs, or maybe because i couldn't add kernel parameters needed (the root partition is encrypted). The kernel panic was something about it didn't find a block device (if you're curious i can try again and take a pic of the error)

Finally, I got arch booting with systemd-boot, just with a bootctl install / adding the correct entry.

So thats okay my computer works now but can someone help me understand what happened here ?
Does systemd-boot place a file in a standard location that i didn't do with efibootmgr ? I believed if an entry was added with efibootmgr, the computer should see it but it seems thats not the case.
Disk uuid seems to be the same (which is the goal of disk uuid i guess ?), so apart that this laptop maybe dont respect uefi spec or something like this, i don't understand

Thank for any pointers !

Offline

#2 2025-03-28 19:28:21

qu@rk
Member
Registered: 2021-07-28
Posts: 89

Re: efi boot stub dell latitude 7480

Sometimes efibootmgr doesn't properly work for whatever reasons. Make sure you don't have "noefi" kernel parameter.
I just go into efi shell and work with bcfg
https://wiki.archlinux.org/title/Unifie … rface#bcfg
Was way more reliable for me. List boot entries, delete/add what you want directly. The older entry probably has the old SSD ID or something.

FS0:/FS1: etc are drive partitions. You can

ls FS0:

to list files on it to make sure you're linking the correct one.

Last edited by qu@rk (2025-03-28 19:30:38)

Offline

Board footer

Powered by FluxBB