This is a tracking bug for Change: Changes/Automatic DTB selection for aarch64 EFI systems For more details, see: https://fedoraproject.org/wiki/Changes/Automatic_DTB_selection_for_aarch64_EFI_systems Make the aarch64 Fedora Live ISO images work OOTB on Windows on ARM (WoA) laptops by automatically selecting the right DTB at boot. If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Stubble has been packaged and systemd and grub changes are in place. kernel-uki-dtbloader package is passing CI and has been tested through mockbuilds. Waiting for PR review: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/4318 + merging. fedora-kiwi-description changes are ready and have been tested locally with kernel-uki-dtbloader package from mockbuild: https://pagure.io/fedora-kiwi-descriptions/pull-request/262 The kernel PR needs to be merged + build before the kiwi changes can be merged.
Hi amoloney, how goes this change for F44? The testable deadline is today, February 03, 2026, and changes need to be in good shape at this point https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones Please let me know if you need to defer this to F45, otherwise if you're good to go for the change to be ready to meet the testable requirements, please update the status of the tracker bug to MODIFIED. Thanks!
Note this change is not being made by Amoloney but by me (Hans), so something was wrong with the assignee here (fixed now). I already added a comment with the status and moved this to modified yesterday.
Hi Hans, thank you for the updates here. I apologize for any confusion here. I attempted to update the ticket to add you as Assignee, but failed to find the match-- thanks for properly assigning it. This was my first time running the incomplete changes report and now I am noticing a discrepancy between the SOP and the instructions I have from my onboarding. The SOP (https://docs.fedoraproject.org/en-US/operations/pgm_guide/sop/changes-contingency/#_report_incomplete_changes) does state to comment on bugs that block the Changes tracking bug that do are not at least as far as MODIFIED (testable deadline) or ON_QA (100% complete deadline). Given this, your change does seem to be in the correct state for the testable deadline today (my instructional guide state to comment on issues that were not yet ON_QA yet). Thanks so much and sorry for the confusion!
Starting with 20260213 nightly images all the necessary changes to test are in place. See: https://fedoraproject.org/wiki/Changes/Automatic_DTB_selection_for_aarch64_EFI_systems#How_To_Test
Note the changes have been (temporary?) reverted due to them breaking some openQA tests, so this cannot be tested atm. The problem is after this change newly installed aarch64 systems do not boot due to bug 2440010.
The anaconda bug has been resolved and the fedora-kiwi-description changes for this change have been re-applied. Moving to ON_QA.
I tried to test this on a Thinkpad x13s (sc8280xp) using Fedora-Workstation-Live-Rawhide-20260227.n.0.aarch64.iso. Grub2 boots as expected, I edited the command line parameters to add 'clk_ignore_unused pd_ignore_unused', however it stays hung on the "Booting a command list" with no other output. I let it sit for over 10 minutes. I booted a second time, added the two parameters, and removed 'quiet' and 'rhgb' in an attempt to see if any messages would appear. It still sits at "Booting a command list". Do you have any suggestions for ways to get more verbose output out of this? Also, thank you for working on this feature BTW.
Brian, rawhide is not at a good point in the kernel cycle to use for testing atm, with 7.0-rc1 just having been released. Support for these Qualcomm arch64 laptops is still fragile and it looks like something has broken in 7.0-rc1, at least for me on a x1e T14s with Fedora-Workstation-Live-Rawhide-20260228.n.0.aarch64.iso I just get a blue screen at boot instead of the expected Fedora logo + spinner followed by GNOME. For starters please give the latest F44 nightly (Fedora-Workstation-Live-44_Beta-1.2.aarch64.iso) a try, that does work for me on the T14s.
I am not sure where to download Fedora-Workstation-Live-44_Beta-1.2.aarch64.iso. I downloaded Fedora-Workstation-Live-44-20260301.n.0.aarch64.iso, removed quiet and rhgb from the kernel command line, added clk_ignore_unused pd_ignore_unused in their place. It still hangs at "Booting a command list", and been there for 10+ minutes at this point. The kernel isn't even booting yet. No blue screen. I'm familiar with what happens if clk_ignore_unused is not included. Any way to get some debugging output from stubble?
(In reply to Brian Masney from comment #10) > I am not sure where to download > Fedora-Workstation-Live-44_Beta-1.2.aarch64.iso. > > I downloaded Fedora-Workstation-Live-44-20260301.n.0.aarch64.iso, Ok, that should be fine, when I posted that comment the F44 nightly link posted to a beta candidate. > removed quiet and rhgb from the kernel command line, added clk_ignore_unused > pd_ignore_unused in their place. It still hangs at "Booting a command list", > and been there for 10+ minutes at this point. The kernel isn't even booting > yet. No blue screen. I'm familiar with what happens if clk_ignore_unused is > not included. > > Any way to get some debugging output from stubble? I've filed a separate bug to discuss this further: bug 2443936 . I've also added a comment with some initial questions there.
Some older QC platforms, such as the Thinkpad x13s laptop, also require the arm64.nopauth kernel parameter in order to boot.
I got this to work on the x13s laptop. In case this helps someone on another QC platform, I have to boot with 'clk_ignore_unused pd_ignore_unused arm64.nopauth modprobe.blacklist=qcom_q6v5_pas quiet'. More details are on the x13-specific bug https://bugzilla.redhat.com/show_bug.cgi?id=2443936.