From: Steven J Abner <pheonix.sja@att.net>
To: "Michel Dänzer" <michel.daenzer@mailbox.org>
Cc: Harry Wentland <harry.wentland@amd.com>,
Alex Deucher <alexdeucher@gmail.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: Kernels >= 6.3 disable video output
Date: Fri, 16 May 2025 11:56:31 -0400 [thread overview]
Message-ID: <7Y2DWS.S2B813X7LPJT3@att.net> (raw)
In-Reply-To: <G32DWS.2C801BL0Y0SE2@att.net>
On Fri, May 16 2025 at 03:38:04 PM +0000, Steven J Abner
<pheonix.sja@att.net> wrote:
> A boot param like 'amd_prefcore=disable' could work
But kinda a band aid. What if you just download a Mainline kernel (as I
did to verify not a build/configure issue). Writing bug report to OS
provider could take a while for them to figure out what the issue is.
next prev parent reply other threads:[~2025-05-19 7:15 UTC|newest]
Thread overview: 22+ 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
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 [this message]
[not found] <TAUYVS.CG2JM4H6L6SG2.ref@att.net>
2025-05-08 23:23 ` Steven J Abner
[not found] <1BHYVS.FW7S9BTTF682.ref@att.net>
2025-05-08 18:42 ` Steven J Abner
2025-05-08 21:17 ` Helge Deller
[not found] <CS2XVS.S2O4K4ZU50ZS1.ref@att.net>
2025-05-08 0:31 ` Steven J Abner
2025-05-08 15:39 ` Helge Deller
[not found] <0PKWVS.1URW9ZPYBULQ2.ref@att.net>
2025-05-07 18:00 ` Steven J Abner
2025-05-07 21:24 ` Helge Deller
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=7Y2DWS.S2B813X7LPJT3@att.net \
--to=pheonix.sja@att.net \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=michel.daenzer@mailbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.