https://bugs.freedesktop.org/show_bug.cgi?id=108139
Bug ID: 108139 Summary: My HDMI stopped working at Linux 4.18.8 Product: DRI Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: duncan_roe@optusnet.com.au
At Linux 4.18.8 the HDMI monitor started to report "No Signal" although Xorg can see a screen when it's started.(There's no signal with or without X). Using bisection, I found the change that caused this is commit to be 691f2d763d0731224439686ecf2d440df8fe910e:
+++ b/drivers/gpu/drm/amd/display/dc/bios/command_table.c @@ -808,6 +808,24 @@ static enum bp_result transmitter_control_v1_5( * (=1: 8bpp, =1.25: 10bpp, =1.5:12bpp, =2: 16bpp) * LVDS mode: usPixelClock = pixel clock */ + if (cntl->signal == SIGNAL_TYPE_HDMI_TYPE_A) { + switch (cntl->color_depth) { + case COLOR_DEPTH_101010: + params.usSymClock = + cpu_to_le16((le16_to_cpu(params.usSymClock) * 30) / 24); + break; + case COLOR_DEPTH_121212: + params.usSymClock = + cpu_to_le16((le16_to_cpu(params.usSymClock) * 36) / 24); + break; + case COLOR_DEPTH_161616: + params.usSymClock = + cpu_to_le16((le16_to_cpu(params.usSymClock) * 48) / 24); + break; + default: + break; + } + }
if (EXEC_BIOS_CMD_TABLE(UNIPHYTransmitterControl, params)) result = BP_RESULT_OK;
Inserted printk stmts showed my monitor reports COLOR_DEPTH_121212. I suspect the clock speed is too high for the video card, so the code needs to check the card model before bumping the speed, but I don't know how to do that. Here are all the details I an think of: Video card (from lspci): VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Radeon R2 Graphics (rev ea) Monitor (from /var/log/Xorg.0.log): Monitor name: DELL U2711 Ranges: V min: 49 V max: 86 Hz, H min: 29 H max: 113 kHz, PixClock max 285 MHz Hardware name (from /var/log/debug): HP HP Laptop 15-bw0xx/8330, BIOS F.11 07/05/2017
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #1 from Duncan Roe duncan_roe@optusnet.com.au --- Still need to pull the patch at 4.18.11
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #2 from Nicholas Kazlauskas nicholas.kazlauskas@amd.com --- Do you mind posting a full dmesg log for your 4.18 kernel? It would probably help to have drm.debug=4 in your boot parameters as well for this.
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #3 from Duncan Roe duncan_roe@optusnet.com.au --- Created attachment 141963 --> https://bugs.freedesktop.org/attachment.cgi?id=141963&action=edit dmesg output as requested
Added dmesg output as requested
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #4 from Duncan Roe duncan_roe@optusnet.com.au --- commit 691f2d763d0731224439686ecf2d440df8fe910e is on branch linux-4.18.y of git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git. It was merged into branch master as part of commit 54dbe75bbf1e189982516de179147208e90b5e45
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #5 from Alex Deucher alexdeucher@gmail.com --- (In reply to Nicholas Kazlauskas from comment #2)
Do you mind posting a full dmesg log for your 4.18 kernel? It would probably help to have drm.debug=4 in your boot parameters as well for this.
Is deep color support on Stoney limited? IIRC, there were some limitations.
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #6 from Duncan Roe duncan_roe@optusnet.com.au --- Created attachment 142387 --> https://bugs.freedesktop.org/attachment.cgi?id=142387&action=edit Current work-around patch
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #7 from Duncan Roe duncan_roe@optusnet.com.au --- I am currently running Linux 4.19.1 with Attachment 142387 and not seeing the problem. Might it be possible to instead use an approach like Attachment 142350 to Bug 108139 to conditionally obey this code instead of removing it?
https://bugs.freedesktop.org/show_bug.cgi?id=108139
--- Comment #8 from Duncan Roe duncan_roe@optusnet.com.au --- I am currently running Linux 4.19.1 with Attachment 142387 and not seeing the problem. Might it be possible to instead use an approach like Attachment 142350 to Bug 108577 to conditionally obey this code instead of removing it?
https://bugs.freedesktop.org/show_bug.cgi?id=108139
Duncan Roe duncan_roe@optusnet.com.au changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #9 from Duncan Roe duncan_roe@optusnet.com.au --- Since Linux 5.1, I do not see this bug any more. So I guess it is "fixed".
dri-devel@lists.freedesktop.org