Talk: Boot fails with “bad shim signature” in atomic desktops and IoT

Ask Fedora
, , , , , ,
1

This is a discussion topic for the following Common Issue:

You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.

If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.

2

Please see the Common Issue for solution/workarounds:

3

I’m unable to upgrade to the latest working version mentioned in the article. From a fresh Silverblue 39 installation, updated to 39.20240610.0:

root@fedora:~# rpm-ostree deploy 39.20240616.0 
Resolving version '39.20240616.0'
1 metadata, 0 content objects fetched; 592 B transferred in 2 seconds; 0 bytes content written
error: Version 39.20240616.0 not found in fedora:fedora/40/x86_64/silverblue

Is there another working version we should be using to test this solution?
Also, is there a way to find a list of all the {release}.{date}.x versions available?

4

Added atomic-desktops, grub, kinoite, secure-boot, silverblue-team, sway-atomic, uefi

5

Ping @siosm

6

If you’re already running any Fedora 40 release then you don’t need to update beforehand and you can skip this part and do the bootloader update directly.

The cleanup and deploy step is only needed if you are running Fedora 39 or an older Fedora IoT:

If you are running a Fedora Atomic Desktop based on Fedora 39 and have not yet updated to Fedora 40, you first need to update to the latest working Fedora 39 version with those commands:

1 Like
7

Are you sure that this is a fresh Fedora Silverblue 39 installation and not a 40 one?

8
1 Like
9

I’d say the common issue here BTW is a duplicate of that already existing common issue (which just does not mention IoT):

10

@rugk The error output is different. Also, the older error is from May, while this new error was caused in June. My impression was that those are two different errors, that’s why I created a separate topic. But I’m happy to be corrected.

1 Like
11

They are indeed two different errors but they are solved the same way.

1 Like