Bug 2533809 - Black screen permanently when booting 7.2.5, 7.2.6 and 7.3-rc3, but no issues on 7.2.4 (AMD cpu+graphics) -> the issue begins when the LUKS/dm-crypt password prompt should appear; ESC to text mode not possible too
Summary: Black screen permanently when booting 7.2.5, 7.2.6 and 7.3-rc3, but no issues...
Keywords:
Status: CLOSED DUPLICATE of bug 2532947
Alias: None
Product: Fedora
Classification: Fedora
Component: linux-firmware
Version: 44
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-15 13:33 UTC by Christopher Klooz
Modified: 2026-09-15 14:30 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-09-15 14:30:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christopher Klooz 2026-09-15 13:33:23 UTC
1. Please describe the problem:
On F44 x86_64, when I boot kernel 7.2.5, 7.2.6 or the rawhide 7.3-rc3 kernel, the screen becomes black at the moment the LUKS/dm-crypt password prompt should appear (my root is encrypted). The black screen remains permanently.

On 7.2.4, the issue does nor occur. 

I can reproduce this 100% when I switch between the kernels.

I tried twice to enter my password while being "blind" and hoped the system would boot and create some logs, but it didn't (did in the process try to "blindly" log into root and shutdown, but there was no response to anything). All logs stored are from working 7.2.4 boots. So given that I cannot decrypt root, I cannot create logs (I'm open to ideas and experiment though!)

I was suggested in bodhi this could be a firmware issue, given the upstream amd bug #5835, and I downgraded all firmware to "20260810-1.fc44", and then tried again: but the issue is unchanged -> 7.2.4 works fine, whereas 7.2.5, 7.2.6, 7.3-rc3 end up with a permanently black screen.

I have a Ryzen 6850U, Lenovo T16 AMD Gen1. I use AMD graphics, without external modules.

I found some kernel reports that have correlations with mine, but none is equal, so I create a separated report.

2. What is the Version-Release number of the kernel:

Broken are:
kernel-7.2.5-200.fc44
kernel-7.2.6-200.fc44
kernel-7.3.0-0.rc3.260914g704340f1cd0d.32.fc46

Everything up to and including 7.2.4-200.fc44.x86_64 work fine.

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

See 2.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Always reproducible with kernel-7.2.5-200, kernel-7.2.6-200, 7.3.0-0.rc3.260914g704340f1cd0d.32.

Never occurring with 7.2.4-200.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes, see above: 7.3.0-0.rc3.260914g704340f1cd0d.32 fails with the same issue.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No, I do not run external modules.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

As described above, that's not possible: but I'm happy to test whatever helps to solve the issue :) 

You might know better what kernel parameter might be worth to test, I'm happy to do so.

Reproducible: Always

Comment 1 Christopher Klooz 2026-09-15 14:04:47 UTC
My bad: I missed to rebuild with dracut when I downgraded the linux-firmware from 20260910-1.fc44 to 20260810-1.fc44.

I did again, and when I rebuild with dracut all new kernels with linux-firmware-20260810-1.fc44, then all three kernels work fine: 7.2.5, 7.2.6, 7.3-rc3.

So the issue is in linux-firmware-20260910-1.fc44, not the kernel. I switch component.

I was suggested this might be related to https://gitlab.freedesktop.org/drm/amd/-/work_items/5835 or https://gitlab.freedesktop.org/drm/amd/-/work_items/5803, but I cannot verify that for obvious reasons: I therefore keep this open, may it be to identify if it's really related to the mentioned upstream issues, or just to have a tracking ticket for upstream.

Again, I'm happy to test or help by whatever means. Just let me know :)

Comment 2 Peter Robinson 2026-09-15 14:26:51 UTC
You also missed the duplicate bug report.

*** This bug has been marked as a duplicate of bug 2532947 ***

Comment 3 Christopher Klooz 2026-09-15 14:29:10 UTC
This COULD be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2532947

I cannot verify anything but the black screen, but ...

```
py0xc3@fedora:~$ lspci | grep 680
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev d1)
```

Comment 4 Christopher Klooz 2026-09-15 14:30:36 UTC
For some reason bugzilla didn't tell me that there was a "this is duplicate" post in between that closed my report. I close it thus again...

*** This bug has been marked as a duplicate of bug 2532947 ***


Note You need to log in before you can comment on or make changes to this bug.