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 10:38:52 -0400 [thread overview]
Message-ID: <SO00WS.37KCGL8UH4LW@att.net> (raw)
In-Reply-To: <CADnq5_NvoPfgTxOxjBCc-iGR7k8w7oR7VKkXQtWga8VP7vBViQ@mail.gmail.com>
On Fri, May 9 2025 at 02:05:16 PM +0000, Alex Deucher
<alexdeucher@gmail.com> wrote:
> Can you narrow down where it broke?
Have built kernels from 5.15 thru 6.2.16 (last of the 6.2 series),
have no issues, ran Xorg server as test. Kernels 6.13.4 down to 6.3
builds, more builds focused in the 6.3 series, have the 70% failure
rate of monitor saying "no input", not just the normal blackout you can
get from a bad configure setting. Kernel runs of 6.3 thru 6.13.4, on
igpu disconnect, will perform the normal console functions of login,
password, reboot and message sending via redirect, along with full
/var/log files logging up to rebooting.
Initial build, started with 6.13.4, had this bug detected prior to
even install of any other software, Xorg, mesa or gdb. All other
kernels had Xorg/mesa added, gdb was added after decided 6.1.137 would
be base, cause it works and hopefully not the last LTS that will
(6.6.89 fails, 70% blackouts).
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
2025-05-09 14:05 ` Alex Deucher
2025-05-09 14:38 ` Steven J Abner [this message]
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=SO00WS.37KCGL8UH4LW@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