dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 15 May 2025 12:11:12 -0400	[thread overview]
Message-ID: <OY8BWS.OAO65CCC74TY1@att.net> (raw)
In-Reply-To: <CADnq5_PbeZCPD7WWO0i5HSVMepka7Ao6byfkx3zHkiBfg4amwg@mail.gmail.com>

On Mon, May 12 2025 at 08:10:40 PM +0000, Alex Deucher 
<alexdeucher@gmail.com> wrote:
> See:
> https://docs.kernel.org/admin-guide/bug-bisect.html
> ... identify the exact commit which broke caused your issue.

 One heck of a journey! But tested the solution on the first broken 
kernel 6.3. Too chicken to force revert attempts of 6.12 and 6.6 since 
I really didn't understand why revert spewed out 'nah-ah' for a one 
liner. 6.3 passed simple test of no blackouts for 8 in a row boots.
 Firstly let me qualify the revert, cause it's how i got it to work:
git show c76e483cd9163138e8fc44d829c986819f072d4f | patch --fuzz=999 
-p1 -R
 It seems simple enough of code which appears to set 8 bits of color 
for rgb as maximum, but with struct changes and me having a 
'historical' processor :) didn't want to have a non-expert speak that 
this is the full solution.
 Also note that I didn't 100% follow the bug-bisect guide as mine was 
apparently a unique situation where it had to first learn to connect to 
the internet and I don't use intrd images among other oddities. Also 
did this from last working kernel (6.2.16) to verify it was the last. 
PS had to patch amdgpu Makefile to allow the 6.2 series to compile with 
new gcc (-Wno-error).
 If need other info or need me to test actual patched 'upstream' 
kernel, I'm here.
Thank you!
Steve



  reply	other threads:[~2025-05-15 16:11 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
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 [this message]
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=OY8BWS.OAO65CCC74TY1@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;
as well as URLs for NNTP newsgroup(s).