My current PC is Windows 11 Pro with UEFI as the boot mode.
I’m trying to install Fedora Silverblue 41
to an external SSD and have done the following:
Created the boot media on a USB thumb drive using Fedora Writer
for Windows (recommended method)
Chose download automatically
and then Fedora Silverblue 41
in the wizard
Wrote the downloaded image to the drive and it checked that files were written correctly
Restarted Windows PC
Booted from USB thumb drive
Chose test boot media and install
option
A blue warning message appears: invalid 7-bit I2C address 0xffff
Continues loading…
Then shows this:
Fatal Python error: _PyEval_EvalFrameDefault: Executing a cache
it then shows a code block with errors regarding _bootstrap
and _find_and_load
.
Is this a known issue for booting in UEFI mode?
1 Like
vekruse
(Villy Kruse)
December 12, 2024, 4:40am
2
It has been reported that Windows would modify the contents of the thumb device in a way that make the test fail, but not otherwise compromise the important parts.
Try install without the test.
1 Like
tried that it passes the test phase and shows the same errors.
1 Like
tqcharm
(Mike B.)
December 14, 2024, 10:35am
4
Do you have another PC to test booting from the created image? If the issue replicates, then it’s probably an issue with the thumb drive, or the way it was written onto it.
Or you could try directly with another USB drive.
1 Like
Thanks all for the suggestions.
I tried another USB thumb drive and the error continued.
I then tried VenToy loading the ISO and another new error appears:
Service org.fedoraproject.Anaconda.Modules.Storage has failed to start: Process org.fedoraproject.Anaconda.Modules.Storage exited with status 139
For the moment I give up on Fedora. Installation should not be this finicky.
Maybe the next big release will solve this?
tqcharm
(Mike B.)
December 20, 2024, 2:16pm
7
There were some reports with failed Silverblue installations. The workaround was to first install Fedora Workstation, and Fedora Silverblue right afterwards, in case you’re willing to give it a another go.
See the filed issue for details:
opened 09:53AM - 11 Nov 24 UTC
bug
upstream
f41
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_.
2 Likes
emilio2022
(Emilio Livi)
January 24, 2025, 5:03pm
8
Hi just to be sure I understand this correct first I install workstation and then I install Silverblue. I have the last two days tried installing Silverblue I used to have on it on my Asus as daily driver but now it gives me the error active device and then pop up if I want to report this to fedora project ?
tqcharm
(Mike B.)
January 24, 2025, 8:03pm
9
Yes, that’s what’s been suggested in the bug report .
Should the workaround not work for you, please open another thread, as you might experience a different issue.
1 Like
emilio2022
(Emilio Livi)
January 26, 2025, 11:08am
10
Hi I had to do asus cloud recovery and then install all the things that my laptop came with. and then reinstall Fedora Silverblue
1 Like