You are not logged in.
Not sure what happened, ran an update and the non-ARCH kernel I'm using was renamed and would no longer boot, but I was totally hosed. Editing the "config" at the bootloader (EFI via systemd) only seems to allow changing "options" rather than the actual boot config as you can with grub. Since I didn't have any live media with me, I had a brick all day at work. Is systemd really that crippled as a bootloader or am I missing something?
Offline
What was updated? Are you referring to editing the kernel line? Probably.
Moving to NC...
Offline
systemd-boot is not a bootloader. It's a simple menu that lets you run EFI applications, so yes, it very simplistic compared to GRUB.
You're talking about when you hit "e" at the systemd-boot menu?
Offline
systemd-boot is not a bootloader. It's a simple menu that lets you run EFI applications, so yes, it very simplistic compared to GRUB.
You're talking about when you hit "e" at the systemd-boot menu?
Yeah. I would think you'd be able to edit the whole .conf but it seems to only be usable for passing options.
Offline
If you download the UEFI Shell and copy it to $ESP/shellx64.efi then systemd-boot will autogenerate a menu entry for it and you can then use `bcfg` to create custom NVRAM entries.
https://wiki.archlinux.org/index.php/Un … UEFI_Shell
EDIT: perhaps a less vitriolic thread title would be more productive?
Last edited by Head_on_a_Stick (2016-11-29 19:46:00)
Offline