From: Steven J Abner <pheonix.sja@att.net>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Kernels >= 6.3 disable video output
Date: Fri, 09 May 2025 09:39:16 -0400 [thread overview]
Message-ID: <GXXZVS.Q1GIIU1M9VBL1@att.net> (raw)
In-Reply-To: <CADnq5_Pk41iOvibFSjt7+Wjj=FXWR--XMt+OCqmkWWveLfU_ig@mail.gmail.com>
On Fri, May 9 2025 at 01:11:17 PM +0000, Alex Deucher
<alexdeucher@gmail.com> wrote:
> What display(s) are you using and how are they connected? Can you
> bisect?
Not sure the question, but it's a tv thru HDMI.
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected primary (normal left inverted right x axis y
axis)
HDMI-A-0 connected 1920x1080+0+0 (normal left inverted right x axis y
axis) 575mm x 323mm
1920x1080 60.00*+ 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98
And hopefully to verify, 3 OSs run fine: Ubuntu/Elementary 5.4, PearlOS
5.15, and LFS 5.15 thru 6.2.16. 6.3 and above has 70% fail rate with
firmware built in to kernel, no fail if no firmware. Mainline 6.8 was
on PearlOS.
Steve
next prev parent reply other threads:[~2025-05-11 12:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6DWYVS.BXJ4YUZ0KN5B3.ref@att.net>
2025-05-09 0:07 ` Kernels >= 6.3 disable video output Steven J Abner
2025-05-09 13:11 ` Alex Deucher
2025-05-09 13:39 ` Steven J Abner [this message]
2025-05-09 14:05 ` Alex Deucher
2025-05-09 14:38 ` Steven J Abner
2025-05-09 15:01 ` Steven J Abner
2025-05-12 20:07 ` Steven J Abner
2025-05-12 20:10 ` Alex Deucher
2025-05-15 16:11 ` Steven J Abner
2025-05-15 16:16 ` Alex Deucher
2025-05-15 17:59 ` Harry Wentland
2025-05-15 18:42 ` Steven J Abner
2025-05-16 15:02 ` Michel Dänzer
2025-05-16 15:38 ` Steven J Abner
2025-05-16 15:56 ` Steven J Abner
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=GXXZVS.Q1GIIU1M9VBL1@att.net \
--to=pheonix.sja@att.net \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.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