As I anounced some days ago in the mailing list I would try to use two Dell 3007WFP-HC (each at 2560x1600@60Hz) for my little home workstation. But the result is very disappointing: - no compositing at all (was very smooth with one of them) - window manager operations very, very slow - glxgears less than half of the performance as with only one monitor - corruption appears when running OpenGL apps Additionally with even only one monitor I have to set the virtual line because otherwise I wouldn't get the native resolution and only 1280x800 instead. But to say some good things, here they are: - video-playback is still "tear-free" - scrolling in most applications is still smooth (except gecko-based) I know that OpenGL texture limits on that card is 4096x4096 texel and my 5120x1600 setup exceeds that for sure but I also had another setup with a screen size of 4160x1600 (2560x1600 + 1600x1200) and that one was very smooth at least without composite and it also exceeded the texture size limit. Although the card in the other setup was a HD2400PRO instead of a X1950XTX I thought that R5xx chips are even better supported than R6xx is and as it is the very high-end of those chip series I assume it has enough power to do that. Keep in mind that the new R8xx chips support even 3 of those monitors driven at a time. So there should be adequate support for that too.
Created attachment 32006 [details] lspci -vnvn
Created attachment 32007 [details] Xorg.0.log
Created attachment 32008 [details] xorg.conf
Created attachment 32009 [details] glxinfo -v
Created attachment 32010 [details] glxinfo -l
Created attachment 32011 [details] xvinfo
Created attachment 32012 [details] xvattr
Created attachment 32013 [details] xdpyinfo -ext all
Created attachment 32014 [details] STDERR of 'xdpyinfo -ext all'
Created attachment 32015 [details] fullscreen snapshot This snapshot shows the corruptions appeared when running glxgears and additionally shows how slow the rendering is when doing window manager things. I should also say that the glxgears window content is not visible. Sometimes there are a few lines visible at the top of the glxgears content but most of it is just black and remains black.
You desktop exceeds the render limits of your r5xx card. The texture and render buffer limit on r6xx/r7xx (your HD2400PRO is r6xx based) is 8192x8192 pixels which is why there are no problems on that card.
(In reply to comment #11) > You desktop exceeds the render limits of your r5xx card. The texture and > render buffer limit on r6xx/r7xx (your HD2400PRO is r6xx based) is 8192x8192 > pixels which is why there are no problems on that card. > OK, understand that. I'll test then with a newer card. Where can I get such information about the hardware? Are there some spec documents available from ATI/AMD?
Created attachment 32063 [details] glxinfo -l (HD2400PRO) OK, just confused on the HD2400PRO that it gives the same OpenGL limits as the X1950XTX: GL_MAX_VIEWPORT_DIMS: 4096 GL_MAX_TEXTURE_SIZE: 4096 So at least the interface says that it can't deal with anything larger. So I assume it's some DRI code that makes it fast on HDxxxx cards? But then shouldn't that be reflected through the interface and the OpenGL limits? Thanx for clearing here, Ancoron
(In reply to comment #12) > Where can I get such information about the hardware? Are there some spec > documents available from ATI/AMD? http://www.x.org/docs/AMD/ (In reply to comment #13) > Created an attachment (id=32063) [details] > glxingo -l (HD2400PRO) > > OK, just confused on the HD2400PRO that it gives the same OpenGL limits as the > X1950XTX: > > GL_MAX_VIEWPORT_DIMS: 4096 > GL_MAX_TEXTURE_SIZE: 4096 Mesa doesn't currently support textures larger than 4k even if the hardware does. However, for EXA, the full hardware limit is supported.
(In reply to comment #14) > http://www.x.org/docs/AMD/ Thanx a lot for that. > Mesa doesn't currently support textures larger than 4k even if the hardware > does. However, for EXA, the full hardware limit is supported. That explains it, of course. Thanx again. :)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.