FS#23156 - [kernel26/drm radeon] Two displays don't works correctly with ati r100
Attached to Project:
Arch Linux
Opened by bogdan (nicknill) - Saturday, 05 March 2011, 21:25 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 23 October 2011, 16:24 GMT
Opened by bogdan (nicknill) - Saturday, 05 March 2011, 21:25 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 23 October 2011, 16:24 GMT
|
Details
Description:
I have KMS enabled. I try to connect second display to the my notebook. When it was connected I seen an graphical artifacts on second display, and at half of the my notebook display. When I try to set resolution of second display the same as my notebook it works fine. Then I try to disable kms. I don't see an artifacts, but if the resolution are different (on my notebook it's 1024x768, display 1280x1024) than on the notebook display i don't see edge of the screen. Sorry for my english. Additional info: in dmesg is one new string [drm:radeon_vga_detect] *ERROR* VGA-1: probed a monitor but no|invalid EDID OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI R100 (RV200 4C57) 20090101 x86/MMX/SSE2 TCL DRI2 OpenGL version string: 1.3 Mesa 7.10.1 Steps to reproduce: Try to connect second display in VGA input for R100 ati driver |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Sunday, 23 October 2011, 16:24 GMT
Reason for closing: No response
Sunday, 23 October 2011, 16:24 GMT
Reason for closing: No response
Upstream recommends to use KMS but I'm not sure how well old r100 cards are supported.
I am using radeon RV350 with KMS, up to date archlinux (gnome 3 in fallback mode because I dislike gnome-shel) and have exactly the same problem. As soon as I touch to xrandr, the screen is no longer displayed correctly. Many artefacts on primary display, secondary is no longer updated EXCEPT the mouse, which is displayed correctly.
Moreover, mouse cursor changes if it hover for example a link in Firefox… but the display is not correct (freezed on secondary, MANY artefacts making it unreadable on primary).
It does it if it ask for any changes on resolution AFTER booting. Dual screen works if I boot with secondary plugged AND that secondary supports the primary's resolution. It does not work if secondary asks for a lower resolution.
It seems due to a bug either in X, in radeon driver, something else ? It worked however just after the gnome3 update, but before some others (probably radeon or X update).