Failed to write boot loader configuration

Framework Laptop 13 Linux
1

Which Linux distro are you using? Bluefin GTS

Which release version?
(if rolling release without a release version, skip this question)

(If rolling release, last date updated?)

Which kernel are you using?

Which BIOS version are you using? 03.01

Which Framework Laptop 13 model are you using? Intel Core Ultra Series 1

I’m trying a fresh install of Bluefin on my new DIY Framework 13 Intel Core Ultra.

Memory and SSD installed okay and are recognized by BIOS. I made a bootable USB using Fedora Media Writer and a new ISO from the Bluefin project site, selecting my Framework 13 Intel Core during the hardware selection.

Upon completion, I ran into the below error (Failed to write boot loader configuration).

PXL_20241129_030708457.MP
PXL_20241129_030708457.MP1920×2550 223 KB

The process has created all expected partitions, including an EFI boot partition at /boot/efi. However, it is not bootable. When attempting to boot without the USB I get this:

PXL_20241129_032119240.MP
PXL_20241129_032119240.MP1920×1446 72.4 KB

The process appears to create a second EFI Boot device (a copy of the existing SSD):

PXL_20241129_032345661.MP
PXL_20241129_032345661.MP1920×2550 173 KB

I have tried creating a new Fedora Media Writer USB stick with a new download ISO. I have tried disabling secure boot. When I run the Bluefin installer I select “Custom” and see the EFI boot partition as well as all partitions created during the install process under “Unknown”. I set the Bluefin installer to destroy all of these partitions and create new ones, but each time I wind up with an additional Fedora entry in the EFI boot manager that doesn’t boot.

I have tried manually deleting the Fedora entries by rebooting into the Arch installer using a Ventoy stick, running efibootmgr, and removing the entries. Upon reboot the BIOS adds a single entry. Running the Bluefin installation process adds an additional entry each time it fails.

I’m running out of ideas. I’m thinking maybe my next step is to either try to manually update the BIOS first, or to try using a standard Fedora distro installation instead of Bluefin.

2

The installation seems to fail when its creating the grub bootloader so the system cannot boot as grub is not completely installed.

Have you checked the downloaded ISO and its SHA sum that they match? It really much sounds like a corrupted ISO at this point.

You could also try to download the Bluefin stable ISO and try installation with that. Of course you would get Fedora 41 base with that ISO.

Have you tried to different settings for the iGPU vram (or what was it named in the BIOS)?

note: you can keep Secure boot on as Bluefin supports secure boot (and its also prefrered to keep it on)

4

Verified the checksums on both copies of the ISO that I tried. Doesn’t seem to be an issue of corrupted ISO files. I also did a clean install of Fedora Media Writer on a different USB stick when I downloaded the second copy of the ISO.

I’m prepping a new USB with the Bluefin stable build now.

Any clues for the iGPU VRAM settings in BIOS? I’m looking through BIOS now and I’m not seeing any setting that looks relevant to either GPU or VRAM.

I did initially start with secure boot since I’ve seen that Bluefin supports it, but disabled it early on in my troubleshooting trying to eliminate potential problem sources. Once I get a working OS I will try turning it back on.

5

Tried using the Bluefin stable ISO (also checked the checksum) and same results.

6

Oh you have Intel. Not sure if the Intel Core ultras have the igpu thing

IMG_0033
IMG_00334284×5712 3.67 MB

That is where it’s on AMD bios

1 Like
7

for boot problems, try to use the BIOS “Boot from file” option, and find the correct EFI file to select.
it will be either:
shimx64.efi
grubx64.efi

Then there should be a grub.cfg file that it loads.
All these should be on a FAT32 partition.

8

Just installed Fedora 41 using Fedora Media Writer. It worked without issue. I still see two copies of Fedora (24451R802408-WD_BLACK SN770 2TB) in my BIOS boot manager under EFI Boot Devices, so something wonky still seems to be happening, but it works.

I’m going to try rebuilding a Bluefin bootable ISO one more time, and if that doesn’t work I’ll just look for a different distro.

9

You can also try to install Silverblue and then rebase to bluefin.

EDIT: The two bootloader entries, if I remember correctly is sometimes normal on Fedora. I remember having two Fedora entries after installing Bluefin on my FW13

10

Tried again, this time selecting automatic for the disk selection/formatting portion. I instructed it to reclaim the BTRFS partition created during the Fedora installation. I wound up with a new error, which is identical to what was reported in this thread. Except I’m not trying to setup a dual boot.

I didn’t tell it to reclaim the efi boot partition because that’s the step that’s been failing.

I’ll give Silverblue one shot, and if it installs I’ll see if I can figure out how to rebase to bluefin (I’m relatively new to Linux and this is my first time trying an immutable distro). If not, I’ll just look for something else. At this point it does seem to be an issue with Bluefin rather than the laptop itself, since Fedora works fine, so that’s at least good progress.

Thanks for your help!

11

The anaconda installer that Fedora (and also Bluefin) uses can be really picky sometimies.

My old Thinkpad pretty much always fails if I have old bootloader entries (especially if they are Fedora ones) still lingering in EFI when installing. So on that one I always had to use simething like Gparted Live CD and wipe the whole disk (like create a new layout) before trying to install.

It is pretty sure to fail if you have an existing EFI partition that you don’t “reclaim” during the installer, that is my experience.

But I don’t have any issues installing Bluefin and replacing for example my CachyOS (Arch) installation. On my FW i can just use the automatic partitioning and have to just check the “reclaim space” option in the partition menu and then deleting all the partition in the popup window. But on the thinkpad that generally don’t work.

They have a pretty active Discord server with atleast few FW core ultra users, so might pop in there and ask if anyone has any tips.

12

Reclaimed all partitions including the EFI boot and Silverblue installed without issue. Rebased to the unsigned version of Bluefin-DX, then rebased to the signed version.

Everything seems to be working. Next is to reenable secure boot and make sure I can register the key.

Thanks again for all the help!

1 Like
13

Nice to hear.

The SB key should be just one ujust command and then reboot → enroll the key and turn on secure boot :slight_smile: