https://bugs.freedesktop.org/show_bug.cgi?id=44755
Christopher M. Penalver changed:
What|Removed |Added
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #10 from Florian Mickler flor...@mickler.org 2012-03-12 15:21:47
PDT ---
A patch referencing this bug report has been merged in Linux v3.3-rc7:
commit 38aa4a568ba4c3ccba83e862a01e3e60e3b811ee
Author: Alex Deucher
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #8 from the...@gmail.com 2012-03-07 14:45:11 PST ---
I've tested against a kernel with this patch, as well as mainline kernel (both
built by ubuntu kernel team), and am still seeing the same behavior. So seems
like this change
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #9 from Alex Deucher ag...@yahoo.com 2012-03-07 16:03:51 PST ---
Created attachment 58148
-- https://bugs.freedesktop.org/attachment.cgi?id=58148
fix
This patch should fix it. Your chip is limited to 165 Mhz single link tmds.
The
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #7 from Florian Mickler flor...@mickler.org 2012-02-01 13:09:58
PST ---
A patch referencing this bug report has been merged in Linux v3.3-rc2:
commit 9aa59993e226af94088adaee993eb8cfd33ae295
Author: Alex Deucher
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #1 from Bryce Harrington br...@canonical.com 2012-01-13 06:50:09
PST ---
Created attachment 55541
-- https://bugs.freedesktop.org/attachment.cgi?id=55541
BootDmesg.txt
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #2 from Bryce Harrington br...@canonical.com 2012-01-13 06:50:57
PST ---
Created attachment 55542
-- https://bugs.freedesktop.org/attachment.cgi?id=55542
CurrentDmesg.txt
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #3 from Bryce Harrington br...@canonical.com 2012-01-13 06:51:27
PST ---
Created attachment 55543
-- https://bugs.freedesktop.org/attachment.cgi?id=55543
XorgLog.txt
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=44755
the...@gmail.com changed:
What|Removed |Added
CC||the...@gmail.com
--
Configure
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #4 from Alex Deucher ag...@yahoo.com 2012-01-13 08:25:54 PST ---
The problem is the modeline from your monitor for the 1920x1080 mode is greater
than 165 Mhz which is the current cut off for single link mode in the driver:
(II)
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #5 from Alex Deucher ag...@yahoo.com 2012-01-13 08:34:21 UTC ---
Created attachment 7
-- https://bugs.freedesktop.org/attachment.cgi?id=7
possible fix
This patch against drm-next or Linus git should fix the issue.
--
https://bugs.freedesktop.org/show_bug.cgi?id=44755
--- Comment #6 from the...@gmail.com 2012-01-13 08:53:54 PST ---
confirmed that the following sequence displays a non-garbled 1920x1080 display
on the external monitor:
# xrandr --newmode 1920x1080R 138.50 1920 1968 2000 2080 1080 1083 1088
12 matches
Mail list logo