https://bugs.freedesktop.org/show_bug.cgi?id=80531
Priority: medium Bug ID: 80531 Assignee: dri-devel@lists.freedesktop.org Summary: 3.16-rc2 hdmi output resolution out of range Cape Verde PRO [Radeon HD 7750] Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fredrik@obra.se Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI
Created attachment 101759 --> https://bugs.freedesktop.org/attachment.cgi?id=101759&action=edit dmesg with drm.debug=1
With 3.16-rc2 my tripple screen setup breaks.
DisplayPort-0 connected 1920x1200 <- ok HDMI-0 connected 1920x1080 <- (tv) resolution out of range DVI-0 connected 1680x1050 <- ok
All screens work during bootup before X starts. ddx driver 7.3.0.
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #1 from fredrik@obra.se --- Created attachment 101760 --> https://bugs.freedesktop.org/attachment.cgi?id=101760&action=edit Xorg log
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #2 from Alex Deucher agd5f@yahoo.com --- Can you attach the dmesg with drm.debug=1 before you start X? All the important information is cut off. E.g., boot into single user mode (append 1 to the kernel command line in grub).
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #3 from fredrik@obra.se --- Created attachment 101762 --> https://bugs.freedesktop.org/attachment.cgi?id=101762&action=edit proper kernel-log
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #4 from Alex Deucher agd5f@yahoo.com --- Created attachment 101763 --> https://bugs.freedesktop.org/attachment.cgi?id=101763&action=edit limit bpc to 10
Does this patch help?
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #5 from fredrik@obra.se --- Not really. Now i get a "no signal" error from my TV.
https://bugs.freedesktop.org/show_bug.cgi?id=80531
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #101763|0 |1 is obsolete| |
--- Comment #6 from Alex Deucher agd5f@yahoo.com --- Created attachment 101773 --> https://bugs.freedesktop.org/attachment.cgi?id=101773&action=edit testing patch
Does this patch help?
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #7 from fredrik@obra.se --- No, still no signal
https://bugs.freedesktop.org/show_bug.cgi?id=80531
Alex Deucher agd5f@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #101773|0 |1 is obsolete| |
--- Comment #8 from Alex Deucher agd5f@yahoo.com --- Created attachment 101866 --> https://bugs.freedesktop.org/attachment.cgi?id=101866&action=edit testing patch
Does this help? Can you also attach a copy of your vbios? To get a copy of your vbios:
(as root) (use lspci to get the bus id) cd /sys/bus/pci/devices/<pci bus id> echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #9 from fredrik@obra.se --- Created attachment 101887 --> https://bugs.freedesktop.org/attachment.cgi?id=101887&action=edit vbios.rom
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #10 from fredrik@obra.se --- I applied the latest patch on a vanilla source-tree and i still get no signal.
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #11 from fredrik@obra.se --- (In reply to comment #10)
I applied the latest patch on a vanilla source-tree and i still get no signal.
Correction - I get a "resolution out of range" with the latest patch
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #12 from Alex Deucher agd5f@yahoo.com --- Created attachment 102075 --> https://bugs.freedesktop.org/attachment.cgi?id=102075&action=edit add deep color module option
This patch disables the deep color support by default which should resolve your issue. You can set radeon.deep_color=1 on the kernel command line in grub to re-enable it. Hopefully we can resolve this properly for 3.17 and enable deep color by default.
https://bugs.freedesktop.org/show_bug.cgi?id=80531
--- Comment #13 from fredrik@obra.se --- (In reply to comment #12)
Created attachment 102075 [details] [review] add deep color module option
This patch disables the deep color support by default which should resolve your issue. You can set radeon.deep_color=1 on the kernel command line in grub to re-enable it. Hopefully we can resolve this properly for 3.17 and enable deep color by default.
Indeed it does. I've tested with 3.16-rc4 and all is well again. Sorry for the delayed reply. If I can be useful in further testing please let me know. Thanks.
https://bugs.freedesktop.org/show_bug.cgi?id=80531
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED
--- Comment #14 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/507.
dri-devel@lists.freedesktop.org