https://bugs.freedesktop.org/show_bug.cgi?id=106718
Bug ID: 106718 Summary: On Ubuntu Bionic with kernels 4.15 and above, RX480 Displayport outputs don't work (dmesg reports "not connected) Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: icekhaos@hotmail.com
Anything from at least 4.15 up to 4.17-rc1 under Bionic makes the Displayport connections fail to even detect a display, while anything 4.14.x works and detects it perfectly.
Is the PCI ROM error related? Is this a duplicate? I can provide xorg logs later today.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
Pixie icekhaos@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|On Ubuntu Bionic with |On Ubuntu Bionic with |kernels 4.15 and above, |kernels 4.15 and above, |RX480 Displayport outputs |RX480 Displayport outputs |don't work (dmesg reports |don't work (dmesg reports |"not connected) |"not connected")
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #1 from Michel Dänzer michel@daenzer.net --- Please attach the dmesg output as well as the Xorg log file.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #2 from Pixie icekhaos@hotmail.com --- Alright. Will do in a couple hours, when booted on newer kernels. Currently booted on an old one, probably good to include it as well for comparison's sake. Google turned up nothing on this issue either, so I came here.
Would a Displayport to DVI converter have anything to do with recent changes?
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #3 from Alex Deucher alexdeucher@gmail.com --- Can you narrow down the regression or better yet bisect?
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #4 from Pixie icekhaos@hotmail.com --- If instructed how, I would definitely be willing to bisect.
Power went out, fell asleep, no xorg logs during the day. Sorry for the delay, a working log/dmesg combo on 4.14.35 coming up shortly, for reference.
This breaks on any kernel 4.15 and above, by the way. Decided to report it against whatever is present in 4.17, since the issue still persists there.
And if I can get rc4 to install, I'll test that and provide the logs from that.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #5 from Pixie icekhaos@hotmail.com --- Created attachment 139875 --> https://bugs.freedesktop.org/attachment.cgi?id=139875&action=edit dmesg log on a working setup (kernel 4.14.35, latest stable mesa)
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #6 from Pixie icekhaos@hotmail.com --- Created attachment 139876 --> https://bugs.freedesktop.org/attachment.cgi?id=139876&action=edit Xorg log on the same functional 4.14.35 setup.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #7 from Pixie icekhaos@hotmail.com --- Logs from working software submitted. Booting promptly into a newer kernel and salvaging logs from there.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #8 from Pixie icekhaos@hotmail.com --- Nope, fell flat on its face. rc1 logs coming shortly.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #9 from Pixie icekhaos@hotmail.com --- Created attachment 139877 --> https://bugs.freedesktop.org/attachment.cgi?id=139877&action=edit dmesg from a broken 4.17-rc1 setup; look here for the errors
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #10 from Pixie icekhaos@hotmail.com --- Created attachment 139878 --> https://bugs.freedesktop.org/attachment.cgi?id=139878&action=edit Xorg log on the broken 4.17-rc1 setup
The broken Xorg log doesn't even seem to acknowledge the monitor exists through a quick grep.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #11 from Pixie icekhaos@hotmail.com --- Seems somewhere between what looks like versions 3.19 and 3.25.
Gonna guess 4.15 has an earlier version; gonna fetch logs from that shortly.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #12 from Pixie icekhaos@hotmail.com --- Seems like I had the right idea.
4.15 runs amdgpu 3.23. May install a Mesa git version from a PPA after this to check.
Really want the new kernels, so I'm probably gonna do that right away after posting the two logs.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #13 from Pixie icekhaos@hotmail.com --- Created attachment 139879 --> https://bugs.freedesktop.org/attachment.cgi?id=139879&action=edit Broken dmesg on 4.15
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #14 from Pixie icekhaos@hotmail.com --- Created attachment 139880 --> https://bugs.freedesktop.org/attachment.cgi?id=139880&action=edit Broken Xorg log on 4.15
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #15 from Pixie icekhaos@hotmail.com --- That Git install doesn't seem to have changed anything visible. Doesn't show in logs either, which is weird.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #16 from Pixie icekhaos@hotmail.com --- Running glxgears gives me a GL version of 3.1 Mesa 18.2.0-devel, that the one I'm looking for?
https://bugs.freedesktop.org/show_bug.cgi?id=106718
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |harry.wentland@amd.com
--- Comment #17 from Michel Dänzer michel@daenzer.net --- Does amdgpu.dc=0 on the kernel command line work around the problem?
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #18 from Pixie icekhaos@hotmail.com --- Where would I enter that?
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #19 from Alex Deucher alexdeucher@gmail.com --- on the kernel command line in grub.
https://bugs.freedesktop.org/show_bug.cgi?id=106718
--- Comment #20 from Pixie icekhaos@hotmail.com --- Sorry for the late reply; yes, amdgpu.dc=0 fixes it.
What does that even do?
https://bugs.freedesktop.org/show_bug.cgi?id=106718
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED
--- Comment #21 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/406.
dri-devel@lists.freedesktop.org