https://bugs.freedesktop.org/show_bug.cgi?id=100919
Thomas R. changed:
What|Removed |Added
Status|REOPENED
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #15 from Harry Wentland ---
Please open a separate ticket for the issue with amd-stg and the 2nd monitor,
including
* dmesg log with amdgpu.dc_log=1 and drm.debug=0x6 kernel options
* model of both monitors
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #14 from Thomas R. ---
Harry, I tried amd-staging-drm-next and there is no corruption on the primary,
but my second monitor is dead. It may be something like bug #91202 or something
else entirely,
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #13 from Harry Wentland ---
Are you able to test amd-staging-drm-next
(https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next)? The
issue should be fixed there and you wouldn't have to fiddle
https://bugs.freedesktop.org/show_bug.cgi?id=100919
Thomas R. changed:
What|Removed |Added
Status|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=100919
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #11 from Thomas R. ---
Forgot to add a note: I'm not actually using HDMI or any converters, I had this
problem with going directly DVI card <-> display.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #10 from Thomas R. ---
Can confirm it works for me, too (although I accidentally also updated to 4.11
while testing it, but the relevant DC code looks unchanged and the patch
applied, so I presume
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #9 from Nikola Forró ---
Thanks Harry,
I've just tested the patch and I can confirm it fixes the problem.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=100919
Harry Wentland changed:
What|Removed |Added
Attachment #131276|0 |1
is
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #7 from Nikola Forró ---
Hi Alex,
yes, that's exactly what I meant.
Sorry for not being clear.
Nikola
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #6 from Alex Deucher ---
what about the else case? Shouldn't the logic be:
if (dc_is_dvi_signal(stream->signal)) {
if (stream->public.timing.pix_clk_khz >
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #5 from Harry Wentland ---
Nikola, this line from the patch should take care of your concern:
+ if (dc_is_dvi_signal(stream->signal) &&
Other signal types shouldn't be affected.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #4 from Nikola Forró ---
Comment on attachment 131276
--> https://bugs.freedesktop.org/attachment.cgi?id=131276
Patch to fix this (hopefully)
Review of attachment 131276:
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #3 from Harry Wentland ---
Created attachment 131276
--> https://bugs.freedesktop.org/attachment.cgi?id=131276=edit
Patch to fix this (hopefully)
Hi Nikola, Thomas.
Thanks for reporting this.
Try this
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #2 from Thomas R. ---
Created attachment 131274
--> https://bugs.freedesktop.org/attachment.cgi?id=131274=edit
Relevant dmesg
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=100919
--- Comment #1 from Thomas R. ---
I arrived here by way of having a similar problem and bisecting it down to the
very same commit. When running a kernel containing it, on my R9 285,
modesetting on my two DVI
https://bugs.freedesktop.org/show_bug.cgi?id=100919
Michel Dänzer changed:
What|Removed |Added
Summary|"Out of range" on a display |[DC] "Out of range"
18 matches
Mail list logo