tqcharm
July 28, 2025, 7:19pm
2
I would expect a bug in the kernel to only make the last deployment unbootable, but not the previous one, which had worked before.
There are some strange things happening with Framework 13 laptops and Fedora Atomic desktop installations. Maybe your issue is somehow connected (even though the report below describes issues during fresh installs)?
opened 09:53AM - 11 Nov 24 UTC
bug
upstream
f41
# Current workaround
Install Fedora Workstation first, do all the package updat… es, reboot, do all the firmware updates, reboot, then try installing Silverblue again.
---
# Original issue
I’ve just received a brand new DIY Framework 13 and I wanted to give Silverblue a try. I created an install USB using Fedora Mediawriter and started the installation. I used the automatic disk formatting option but ticked the box to encrypt my data and chose a passphrase and then let the installer get on with it.
At some point I received an error that read something like “failed to write boot loader configuration”. I click to let it continue installing but on reboot I got a GRUB error screen.
At first I thought this might be a failure in the hardware, so just to check I created a Fedora Workstation install USB on the same USB stick and installed that using the same options and that worked fine.
This reproduces reliably. I've tried using different USB sticks and I've also encountered the same issue when attempting to install Bluefin. I would love to provide you with some logs but it wasn't immediately obvious to me how to get them off of the device during installation. I'm quite happy to run through the installation again and take photographs of the screen if that would help, just let me know what I should be getting photographs _of_.
Was there a recent firmware update maybe?
1 Like