Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2243263 - dtb files no longer copied into /boot
Summary: dtb files no longer copied into /boot
Keywords:
Status: CLOSED DUPLICATE of bug 2243060
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 39
Hardware: aarch64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F39FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2023-10-11 13:44 UTC by Dennis Gilmore
Modified: 2023-10-11 18:23 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-11 18:23:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Dennis Gilmore 2023-10-11 13:44:55 UTC 
after updating to systemd-udev-254.5-2.fc39.aarch64 the dtb files on a new kernel install are not copied into /boot 

lrwxrwxrwx.  1 root root       26 Oct  9 08:21 dtb -> dtb-6.5.6-300.fc39.aarch64
drwxr-xr-x. 18 root root     4096 Sep 25 13:25 dtb-6.5.4-300.fc39.aarch64
drwxr-xr-x. 18 root root     4096 Sep 26 11:32 dtb-6.5.5-300.fc39.aarch64


Is the contents in /boot dtb is a broken symlink. I have had this happen on two systems. For some systems, such as my espressobins the result is a system that no longer boots because the dtb file can not be found.

Reproducible: Always
Comment 1 Dennis Gilmore 2023-10-11 15:27:45 UTC 
possibly it is due to https://github.com/systemd/systemd/commit/2bca841137833edeaf3779542d6475f0dc3aa5a7 not being in our build
Comment 2 Adam Williamson 2023-10-11 16:59:36 UTC 
This looks like https://bugzilla.redhat.com/show_bug.cgi?id=2243060 ?
Comment 3 Dennis Gilmore 2023-10-11 18:16:12 UTC 
likely, I updated a couple of other systems and they are not seeing the issue
Comment 4 Adam Williamson 2023-10-11 18:23:00 UTC 
okay, let's call it a dupe...you can try updating the affected system to grub2 -104, I guess...

*** This bug has been marked as a duplicate of bug 2243060 ***
Note You need to log in before you can comment on or make changes to this bug.