From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 222061] New: [REGRESSION 7.1.8 -> 7.2] Strix Halo HDMI 1080p black after login (kwin framebuffer EINVAL). Full report on drm/amd#5893
Date: Fri, 25 Sep 2026 16:03:31 +0000 [thread overview]
Message-ID: <bug-222061-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=222061
URL: https://gitlab.freedesktop.org/drm/amd/-/work_items/58
93
Bug ID: 222061
Summary: [REGRESSION 7.1.8 -> 7.2] Strix Halo HDMI 1080p black
after login (kwin framebuffer EINVAL). Full report on
drm/amd#5893
Product: Drivers
Version: 2.5
Kernel Version: 7.2.6 (works on 7.1.8; 7.2.7 not tested)
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: miguel@miguelmesa.com
Regression: Yes
Pointer only. The full report, hardware, and the isolation table are here:
https://gitlab.freedesktop.org/drm/amd/-/work_items/5893
Strix Halo iGPU (Radeon 8060S, PCI 1002:1586, DCN 3.5), single HDMI-A-1 at
1920x1080. Kernel 7.1.8 works (Display Core v3.2.378). Kernels 7.2.0 through
7.2.6 leave Plasma and Hyprland black immediately after the greeter. The
greeter and a TTY still work. Log line: kwin_wayland_drm: Failed to create
framebuffer (EINVAL). The LTS kernel did not restore the desktop. This is not
the 7.2 4K YCbCr 4:2:0 HDMI regression (drm/amd#5720, #5743).
Please track the bug on the drm/amd issue above.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2026-09-25 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 16:03 bugzilla-daemon [this message]
2026-09-27 14:08 ` [Bug 222061] [REGRESSION 7.1.8 -> 7.2] Strix Halo HDMI 1080p black after login (kwin framebuffer EINVAL). Full report on drm/amd#5893 bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-222061-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox