Can you bisect? Sounds like the monitor does not keep the EDID powered up when
the display is off as is required by the vesa spec.
Alex
From: Tom Reddish [mailto:tom.redd...@mediavuesystems.com]
Sent: Wednesday, May 31, 2017 12:20 PM
To: Deucher, Alexander; Koenig, Christian
Cc: amd-gfx@lists.f
o:tom.redd...@mediavuesystems.com]
Sent: Wednesday, May 31, 2017 12:44 PM
To: Deucher, Alexander
Cc: Koenig, Christian; amd-gfx@lists.freedesktop.org; Brian Kane
Subject: Re: Linux Kernel 4.4.0-66 Possible DRM connector_status Bug For LG
Displays
What do you mean by bisect?
My gut is telling me it&#
What do you mean by bisect?
My gut is telling me it's something that changed in the kernel. Maybe the
kernel is correctly parsing the information it is being given from the display
now and in the older kernel it was handling that information differently? With
the exact same display and no setti
; Alex
>
> From: Tom Reddish [mailto:tom.redd...@mediavuesystems.com]
> Sent: Wednesday, May 31, 2017 12:44 PM
> To: Deucher, Alexander
> Cc: Koenig, Christian; amd-gfx@lists.freedesktop.org; Brian Kane
> Subject: Re: Linux Kernel 4.4.0-66 Possible DRM connector_status Bug For LG
> D
p.org; Brian Kane
Subject: Re: Linux Kernel 4.4.0-66 Possible DRM connector_status Bug For LG
Displays
I can do that. I've looked through the changelog between the two and theres a
number of things related to drm and radeon but I'm not exactly sure what I
should be looking for. Are the
M
> To: Deucher, Alexander
> Cc: Koenig, Christian; amd-gfx@lists.freedesktop.org; Brian Kane
> Subject: Re: Linux Kernel 4.4.0-66 Possible DRM connector_status Bug For LG
> Displays
>
> I can do that. I've looked through the changelog between the two and theres a
> nu
Subject: Re: Linux Kernel 4.4.0-66 Possible DRM connector_status Bug For LG
Displays
So I am still working through the bisect, having issues building the kernel
correctly from source at intermediate commits. I have been able to narrow it
down a specific package (linux-image-4.4.0-57-generic
