On Fri, May 16 2025 at 03:38:04 PM +, Steven J Abner
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
On Fri, May 16 2025 at 03:02:47 PM +, Michel Dänzer
wrote:
FWIW, with GNOME the "max bpc" property value can be set
Issue is pre-DE, gnome or Xorg. A boot param like
'amd_prefcore=disable' could work. Issue then becomes putting into
dmesg so can figure its needed. Blacked out console har
On Thu, May 15 2025 at 05:59:55 PM +, Harry Wentland
wrote:
Are you able to share the specific TV model?
From TV itself: Sansui S55VAUG. From System info within tv menu:
Settings: Device Name: GoogleTV8931 Model: Apollo Premium 4KTV
from cat /sys/class/drm/card0/card0-HDMI-A-1/edid:
bina
On Mon, May 12 2025 at 08:10:40 PM +, Alex Deucher
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 attemp
On Fri, May 9 2025 at 03:01:13 PM +, Steven J Abner
wrote:
On Fri, May 9 2025 at 02:05:16 PM +, Alex Deucher
wrote:
bisect between 6.2.16 and 6.2.17 to identify the commit which broke
Are you asking for a 'diff' output of drm and amdgpu directories
between 6.2.16 (last
On Fri, May 9 2025 at 02:05:16 PM +, Alex Deucher
wrote:
bisect between 6.2.16 and 6.2.17 to identify the commit which broke
Are you asking for a 'diff' output of drm and amdgpu directories
between 6.2.16 (last of the 6.2 series) and 6.3 (start of the 6.3
series)? I can and will if you w
On Fri, May 9 2025 at 01:11:17 PM +, Alex Deucher
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 (n
On Fri, May 9 2025 at 02:05:16 PM +, Alex Deucher
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%
AMD 2400g, Zen1, 'Raven' firmware, igpu, no card.
Code that was added to 6.2.16 to create 6.3 and up, to last tested
6.13.4, breaks the igpu for Ryzen. Kernels with firmware, same as that
used on 6.3 and up, works 100% on 5.4 to 6.2.16. This bug is even in a
Debian/Ubuntu based OS's Mainline do
