All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven J Abner <pheonix.sja@att.net>
To: deller@gmx.de
Cc: linux-fbdev@vger.kernel.org, pheonix.sja@att.net
Subject: Re: Kernels >= 6.3 disable video output
Date: Wed, 07 May 2025 20:31:24 -0400	[thread overview]
Message-ID: <CS2XVS.S2O4K4ZU50ZS1@att.net> (raw)
In-Reply-To: CS2XVS.S2O4K4ZU50ZS1.ref@att.net

 > Kernels 6.2 and 6.3 are around 2 years old. Nobody will invest time 
there.

Sorry I guess I phased incorrectly. 6.2.16 is the last working kernel. 
It's mentioned because 6.3 is breaking code. This applies to all code 
after and including 6.3. My current build or home OS is 6.1.137 since 
it's long term and working. Orginal build was 6.13.4, Failed kernel 
from both build and Mainline of a Debian/Ubuntu based OS distribution 
of 6.8. Failed build of 6.6.89. Kernels I know to work are 5.4 thru 
6.2.16. Kinda did a bsearch type build to zero in on breaking kernel. 
It was the place I know factually that needs code regressed to fix all 
kernels >= 6.3. It could be fb related, I forget my test results based 
off of original 6.13.4. If I recall, both with and without firmware 
produced igpu shut off, yet kernel will run to full console use. Don't 
quote me on that :)
Steve



       reply	other threads:[~2025-05-08  1:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CS2XVS.S2O4K4ZU50ZS1.ref@att.net>
2025-05-08  0:31 ` Steven J Abner [this message]
2025-05-08 15:39   ` Kernels >= 6.3 disable video output Helge Deller
     [not found] <6DWYVS.BXJ4YUZ0KN5B3.ref@att.net>
2025-05-09  0:07 ` 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
     [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] <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=CS2XVS.S2O4K4ZU50ZS1@att.net \
    --to=pheonix.sja@att.net \
    --cc=deller@gmx.de \
    --cc=linux-fbdev@vger.kernel.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.