Bug#348082: xserver-xorg: [ati/radeon] pinkness and interference pattern on Radeon RV250 If [Radeon 9000] rev 1 and TMDS-connected Samsung SyncMaster 213T
On Thu, 2008-05-22 at 08:31 +0200, Brice Goglin wrote: > Branden Robinson wrote: > >>> 6) ...and the byteswapped cursor. > >>> > > Thanks, Alex! This helped a lot. Problems 1), 2), and 3) above are gone. > > 4) is no longer applicable; 5) and 6) remain. > > 5) should be fixed once you switch to Xserver 1.5 and the ati driver > snapshot in experimental. I think you mean 6). -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Problem with performance with Composite and dri
On Tue, 2008-05-20 at 11:10 +, RafałMużyło wrote: > Relevant portion of xorg.conf: > Section "Device" > Identifier "open-radeon" > Driver "radeon" > Option "EnablePageFlip" "true" > Option "AccelDFS" "true" > Option "VGAAccess" "off" > Option "DDCMode" "true" > Option "AccelMethod" "EXA" > EndSection > (dri and composite - enabled) > My problem: program - gvbam (gtk frontend to vbam - on sourceforge) > With fglrx, I get good framerate with both cairo and opengl output. > With this driver: > when dri is enabled: > with cairo: system seems to freeze (I'm not talking about framerate, server > itself gets unresponsive) Does it recover after killing the application? Same problem without Option "AccelDFS" or with XAA instead of EXA? > with opengl: framerate is very low Anything interesting in the application output, in particular on stderr? Does it work better with the environment variable disable_lowimpact_fallback=true set? > when dri gets disabled by running second server on display 1: > with cairo: framerate is very low (but doesn't seems to freeze) Most likely it's falling back to software rendering for some operations. > with opengl: framerate is good It's all done by the CPU in this case. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
x1250 sync to vblank
I, I have these horizontal tearing problems which show as horizontal tearing problems during video playback. I'm using latest git versions of the driver and mesa. Are there plans to support syncing to vblank? Thanks ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#348082: xserver-xorg: [ati/radeon] pinkness and interference pattern on Radeon RV250 If [Radeon 9000] rev 1 and TMDS-connected Samsung SyncMaster 213T
On Thu, May 22, 2008 at 09:32:23 +0200, Michel Dänzer wrote: > On Thu, 2008-05-22 at 08:31 +0200, Brice Goglin wrote: > > Branden Robinson wrote: > > >>> 6) ...and the byteswapped cursor. > > >>> > > > Thanks, Alex! This helped a lot. Problems 1), 2), and 3) above are gone. > > > 4) is no longer applicable; 5) and 6) remain. > > > > 5) should be fixed once you switch to Xserver 1.5 and the ati driver > > snapshot in experimental. > > I think you mean 6). > And it should even be fixed in xorg-server 2:1.4.1~git20080517-1 (if I understood correctly, and the commit entitled "Fix RandR 1.2 driver interface conversion of two colour cursors to ARGB" is the relevant one). Cheers, Julien ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Problem with performance with Composite and dri
Michel Dänzer <[EMAIL PROTECTED]> writes: > > with cairo: system seems to freeze (I'm not talking about framerate, > > server > > itself gets unresponsive) > > Does it recover after killing the application? Same problem without > Option "AccelDFS" or with XAA instead of EXA? > I should explain, what 'system seems to freeze` means in this context. It means: my wm is set to 'focus follows mouse' and I'm running xclock; when I run gvbam with cairo, mouse moves fine, but focus doesn't change and xclock is frozen. If I do Alt+Ctrl+F1/Alt+Ctrl+F7, app looses focus and pauses, so I can kill it and system recovers (well, it recovers as soon as app looses focus). Now, about XAA/EXA and AccelDFS. For now, I tested it only with dri disabled. EXA + no AccelDFS = same freeze as EXA + AccelDFS + dri XAA + AccelDFS = same as EXA + AccelDFS (no dri) XAA + no AccelDFS = decent framerate, but still a bit low. > > with opengl: framerate is very low > > Anything interesting in the application output, in particular on stderr? > Does it work better with the environment variable > disable_lowimpact_fallback=true set? App doesn't have any console output and I'm running with disable_lowimpact_fallback=true by default, cause it affects other programs. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #4 from Roland Scheidegger <[EMAIL PROTECTED]> 2008-05-22 05:14:09 PST --- (In reply to comment #3) > The log with PreferredMode = 2560x1600 still uses the "sloppy heuristic" to > guess the mode; maybe this is related to the earlier line that says: > > (II) RADEON(0): Max desktop size set to 2560x1200 So what happens if you add that Virtual line (Virtual 2560 1600, Section Screen, Subsection Display) to your xorg.conf? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16063] New: xrandr returns nothing on RS480 but the current working resolution
http://bugs.freedesktop.org/show_bug.cgi?id=16063 Summary: xrandr returns nothing on RS480 but the current working resolution Product: xorg Version: 7.2 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/Radeon AssignedTo: xorg-driver-ati@lists.x.org ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Latest 6.8.0 ati driver makes xrandr shows nothing while with the same configuration, previous drivers mades xrandr shows all possible resolution: $ xrandr Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1600 x 1200 VGA-0 disconnected 1280x1024+0+0 (normal left inverted right x axis y axis) 0mm x 0mm DVI-0 disconnected (normal left inverted right x axis y axis) 1280x1024 (0x4e) 90.8MHz h: width 1280 start 1328 end 1360 total 1440 skew0 clock 63.0KHz v: height 1024 start 1027 end 1034 total 1054 clock 59.8Hz It only shows the current working resolution -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16063] xrandr returns nothing on RS480 but the current working resolution
http://bugs.freedesktop.org/show_bug.cgi?id=16063 --- Comment #1 from Thierry Vignaud <[EMAIL PROTECTED]> 2008-05-22 07:46:53 PST --- Created an attachment (id=16683) --> (http://bugs.freedesktop.org/attachment.cgi?id=16683) xorg.conf -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16063] xrandr returns nothing on RS480 but the current working resolution
http://bugs.freedesktop.org/show_bug.cgi?id=16063 --- Comment #2 from Thierry Vignaud <[EMAIL PROTECTED]> 2008-05-22 07:47:33 PST --- Created an attachment (id=16685) --> (http://bugs.freedesktop.org/attachment.cgi?id=16685) xorg's log -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16065] New: 6.8.0 ati driver doesn' t honnor aymore resolution specified in xorg.conf
http://bugs.freedesktop.org/show_bug.cgi?id=16065 Summary: 6.8.0 ati driver doesn't honnor aymore resolution specified in xorg.conf Product: xorg Version: 7.2 Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: Driver/Radeon AssignedTo: xorg-driver-ati@lists.x.org ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Latest 6.8.0 ati driver doesn't honnor resolution specified in /etc/X11/xorg.conf unlike previous 6.6.x versions. On a flat panel, this is especially bad since not using native resolution results in unoptimal display (zomm). I'd to add the following options to make it use the native resolution: Option "Monitor-VGA" "monitor1" Option "PreferredMode" "1280x1024" Maybe linked to that issue, xrandr only list the current working resolution instead of all possible resolutions (see Bug #16063). See https://bugs.freedesktop.org/attachment.cgi?id=16683 for xorg.conf and https://bugs.freedesktop.org/attachment.cgi?id=16685 for xorg.log with the above options. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16065] 6.8.0 ati driver doesn' t honnor aymore resolution specified in xorg.conf
http://bugs.freedesktop.org/show_bug.cgi?id=16065 --- Comment #1 from Thierry Vignaud <[EMAIL PROTECTED]> 2008-05-22 07:54:29 PST --- Created an attachment (id=16689) --> (http://bugs.freedesktop.org/attachment.cgi?id=16689) xorg log without the new options Note that "interestingly", when not using the native resolution of my flat panel, the xorg server segfaults when using mplayer (but gracefully handle the error by killing the client) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16065] 6.8.0 ati driver doesn' t honnor aymore resolution specified in xorg.conf
http://bugs.freedesktop.org/show_bug.cgi?id=16065 --- Comment #2 from Thierry Vignaud <[EMAIL PROTECTED]> 2008-05-22 07:58:09 PST --- You can find stack traces of the segfault which happens in VidModeGetCurrentModeline() at https://qa.mandriva.com/show_bug.cgi?id=40959 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Problem with performance with Composite and dri
On Thu, 2008-05-22 at 11:18 +, RafałMużyło wrote: > Michel Dänzer <[EMAIL PROTECTED]> writes: > > > > with cairo: system seems to freeze (I'm not talking about framerate, > > > server > > > itself gets unresponsive) > > > > Does it recover after killing the application? Same problem without > > Option "AccelDFS" or with XAA instead of EXA? > > > I should explain, what 'system seems to freeze` means in this context. > It means: my wm is set to 'focus follows mouse' and I'm running xclock; > when I run gvbam with cairo, mouse moves fine, but focus doesn't change > and xclock is frozen. If I do Alt+Ctrl+F1/Alt+Ctrl+F7, app looses focus > and pauses, so I can kill it and system recovers (well, it recovers as soon > as app looses focus). Sounds like the app is flooding the X server with requests it can't keep up with, or maybe taking and keeping a grab. > Now, about XAA/EXA and AccelDFS. > For now, I tested it only with dri disabled. > EXA + no AccelDFS = same freeze as EXA + AccelDFS + dri > XAA + AccelDFS = same as EXA + AccelDFS (no dri) > XAA + no AccelDFS = decent framerate, but still a bit low. That doesn't all make sense - AccelDFS can only really be enabled when using EXA with the DRI enabled. So the first one boils down to EXA with DRI disabled, which you said previously was better? And there should be no difference between the XAA cases regardless of AccelDFS. > > > with opengl: framerate is very low > > > > Anything interesting in the application output, in particular on stderr? > > Does it work better with the environment variable > > disable_lowimpact_fallback=true set? > App doesn't have any console output and I'm running with > disable_lowimpact_fallback=true by default, cause it affects other programs. Then it sounds like the app is using OpenGL functionality that the Mesa r300 driver doesn't handle well yet. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16067] New: 6.8. 0 ati driver segfaults when using mplayer after a while
http://bugs.freedesktop.org/show_bug.cgi?id=16067 Summary: 6.8.0 ati driver segfaults when using mplayer after a while Product: xorg Version: 7.2 Platform: Other OS/Version: All Status: NEW Severity: major Priority: medium Component: Driver/Radeon AssignedTo: xorg-driver-ati@lists.x.org ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] After a while, the xorg server segfaults when using mplayer. It "gracefully" handles this error by killing the X client. You can find stack traces of the segfault which happens in VidModeGetCurrentModeline() at: https://qa.mandriva.com/show_bug.cgi?id=40959 Here's the GDB trace: https://qa.mandriva.com/attachment.cgi?id=9985 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16065] 6.8.0 ati driver doesn' t honnor aymore resolution specified in xorg.conf
http://bugs.freedesktop.org/show_bug.cgi?id=16065 --- Comment #3 from Thierry Vignaud <[EMAIL PROTECTED]> 2008-05-22 09:14:48 PST --- I opened a bug report for the segfault at https://bugs.freedesktop.org/show_bug.cgi?id=16067 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#348082: xserver-xorg: [ati/radeon] pinkness and interference pattern on Radeon RV250 If [Radeon 9000] rev 1 and TMDS-connected Samsung SyncMaster 213T
On Thu, May 22, 2008 at 2:13 AM, Branden Robinson <[EMAIL PROTECTED]> wrote: > On Thu, May 22, 2008 at 01:20:45AM -0400, Alex Deucher wrote: >> On Thu, May 22, 2008 at 12:26 AM, Branden Robinson <[EMAIL PROTECTED]> wrote: >> > Unfortunately it looks like things have not improved for me, but gotten >> > worse. Now: >> > >> > 1) My detected screen resolution is 1280x768, which is not only too small, >> > but the wrong aspect ratio for my 4:3 monitor; >> > 2) the xrandr tricks that worked around this problem no longer help; >> > 3) in fact, they make the problem worse by throwing the display into an >> > illegible mess; >> > 4) which I can "recover" from by VT switching to a console and back. >> > 5) But I'm still left with the weird interference pattern, >> > 6) ...and the byteswapped cursor. >> > >> >> Please remove the connector table option from your xorg.conf. > > Thanks, Alex! This helped a lot. Problems 1), 2), and 3) above are gone. > 4) is no longer applicable; 5) and 6) remain. > > In short, I'm now back to the original #348082 status quo, with the added > benefit of not having to use the ConnectorTable option as part of the > workaround. Also, my monitor now detects as DVI-0, and is not located at > DVI-1 as before. Does switching to the other DVI port help? Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16065] 6.8.0 ati driver doesn' t honnor aymore resolution specified in xorg.conf
http://bugs.freedesktop.org/show_bug.cgi?id=16065 Alex Deucher <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #4 from Alex Deucher <[EMAIL PROTECTED]> 2008-05-22 09:28:11 PST --- This is the same issue as bug 16063. The root cause is that DDC is not reliable on XPRESS chips so it's nearly impossible to tell what outputs are connected. *** This bug has been marked as a duplicate of bug 16063 *** -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16063] xrandr returns nothing on RS480 but the current working resolution
http://bugs.freedesktop.org/show_bug.cgi?id=16063 --- Comment #3 from Alex Deucher <[EMAIL PROTECTED]> 2008-05-22 09:28:11 PST --- *** Bug 16065 has been marked as a duplicate of this bug. *** -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #5 from Peter Williams <[EMAIL PROTECTED]> 2008-05-22 09:52:27 PST --- I added a "Virtual" line and changed the preferred mode back to 2560x1600, restarted GDM, and ... my computer rebooted! The monitor went into standby mode for maybe 10 seconds, then I got my POST screen. That was exciting! -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #6 from Peter Williams <[EMAIL PROTECTED]> 2008-05-22 09:59:48 PST --- I should probably add that after the POST, my computer got to the point where the graphical boot would start and again the monitor went into standby mode. I let the computer sit for a little while and it didn't look like it was rebooting again, but it did look like it had hard-locked: the caps lock light wouldn't turn on and off, for instance, and the disk light wasn't flashing the way it would if the computer was actually booting in the background. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #7 from Alex Deucher <[EMAIL PROTECTED]> 2008-05-22 10:46:39 PST --- Does it work any better on the other DVI port (either the 2560 or 1280 modes)? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16067] [NULL dereference in VidModeGetCurrentModeline] 6.8. 0 ati driver segfaults when using mplayer after a while
http://bugs.freedesktop.org/show_bug.cgi?id=16067 Thierry Vignaud <[EMAIL PROTECTED]> changed: What|Removed |Added Summary|6.8.0 ati driver segfaults |[NULL dereference in |when using mplayer after a |VidModeGetCurrentModeline] |while |6.8.0 ati driver segfaults ||when using mplayer after a ||while --- Comment #1 from Thierry Vignaud <[EMAIL PROTECTED]> 2008-05-22 10:47:01 PST --- Further debugging showed that VidModeGetCurrentModeline() blindly dereferences pScrn->currentMode whithout checking if it's NULL -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16067] [NULL dereference in VidModeGetCurrentModeline] 6.8. 0 ati driver segfaults when using mplayer after a while
http://bugs.freedesktop.org/show_bug.cgi?id=16067 Alex Deucher <[EMAIL PROTECTED]> changed: What|Removed |Added Component|Driver/Radeon |Server/general --- Comment #2 from Alex Deucher <[EMAIL PROTECTED]> 2008-05-22 10:51:27 PST --- looks like a server issue. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #8 from Peter Williams <[EMAIL PROTECTED]> 2008-05-22 11:15:49 PST --- (In reply to comment #7) > Does it work any better on the other DVI port (either the 2560 or 1280 modes)? > Oh, man this is annoying. With 1280 on DVI-0, making the the appropriate changes in xorg.conf, it does work. Colors are fine, everything looks happy. But 2560 on DVI-0 won't work, because only DVI-1 has the dual-link connection necessary to drive the monitor at that resolution. I checked this: without the Virtual line, I get a blank screen as before, with the driver attempting to use the weird 1152x864 mode again. (As a side note, this time, the driver said the DPI was set to 96,96, not 53,76 as when on DVI-1.) When I tried 2560 on DVI-0 with the Virtual line, I got another computer reset. Being able to run at 1280 makes my computer usable, at least, but unsurprisingly, I'd very much like to be able to get it to run at 2560 ... -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #9 from Peter Williams <[EMAIL PROTECTED]> 2008-05-22 11:20:27 PST --- Created an attachment (id=16694) --> (http://bugs.freedesktop.org/attachment.cgi?id=16694) Log with DVI-0 and 1280x800 resolution While I have this computer booted up, here's a log from the X server when it worked in 1280 mode with the monitor on DVI-0. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #10 from Alex Deucher <[EMAIL PROTECTED]> 2008-05-22 11:24:26 PST --- (In reply to comment #8) > Oh, man this is annoying. > > With 1280 on DVI-0, making the the appropriate changes in xorg.conf, it does > work. Colors are fine, everything looks happy. > > But 2560 on DVI-0 won't work, because only DVI-1 has the dual-link connection > necessary to drive the monitor at that resolution. I checked this: without the > Virtual line, I get a blank screen as before, with the driver attempting to > use > the weird 1152x864 mode again. (As a side note, this time, the driver said the > DPI was set to 96,96, not 53,76 as when on DVI-1.) When I tried 2560 on DVI-0 > with the Virtual line, I got another computer reset. > > Being able to run at 1280 makes my computer usable, at least, but > unsurprisingly, I'd very much like to be able to get it to run at 2560 ... > The basic root cause of this (barring the xserver picking the wrong mode), is that the bios does not appear to set up the external TMDS encoder to work in duallink mode. The driver attempts to set up the encoder, but it doesn't appear to work in your case. This may also explain the reboot as the external TMDS encoder is hanging off some unknown GPIO on the radeon. Unfortunately, without knowing what chip is used and how it's connected, there's not much we can do. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Problem with performance with Composite and dri
Michel Dänzer <[EMAIL PROTECTED]> writes: > > On Thu, 2008-05-22 at 11:18 +, RafałMużyło wrote: > Sounds like the app is flooding the X server with requests it can't keep > up with, or maybe taking and keeping a grab. > I think it's the former, cause I don't think it makes a grab. > > Now, about XAA/EXA and AccelDFS. > > For now, I tested it only with dri disabled. > > EXA + no AccelDFS = same freeze as EXA + AccelDFS + dri > > XAA + AccelDFS = same as EXA + AccelDFS (no dri) > > XAA + no AccelDFS = decent framerate, but still a bit low. > > That doesn't all make sense - AccelDFS can only really be enabled when > using EXA with the DRI enabled. So the first one boils down to EXA with > DRI disabled, which you said previously was better? And there should be > no difference between the XAA cases regardless of AccelDFS. > I think it's the former, cause I don't think it makes a grab. Well, with dri enabled, it, indeed, doesn't seem to make a difference for XAA, for EXA without AccelDFS, while it slowdowns to about 1/3 of normal, freeze effect does not occur. > > App doesn't have any console output and I'm running with > > disable_lowimpact_fallback=true by default, cause it affects other programs. > > Then it sounds like the app is using OpenGL functionality that the Mesa > r300 driver doesn't handle well yet. > The apps, that were affected printed : File r300_render.c function r300Fallback line 471 Software fallback:ctx->Line.SmoothFlag And one more thing, I don't know whether it's a server or driver issue, but about 7 of 8 times I leave X, I end up with black screen, in this case meaning no video signal (and monitor automaticly turns off), though if I type (blind) `startx`, X starts without any problem. That does not happen, if I have a second server running on a different display. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #11 from Peter Williams <[EMAIL PROTECTED]> 2008-05-22 11:57:46 PST --- Is there any research I can do to help diagnose what needs to be fixed? Some kind of tracing of the fglrx driver or anything? Or even a particular function in the driver that I can futz with to see if anything helps? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16055] Blank screen with Radeon 9600 / RV350
http://bugs.freedesktop.org/show_bug.cgi?id=16055 --- Comment #12 from Alex Deucher <[EMAIL PROTECTED]> 2008-05-22 19:55:11 PST --- (In reply to comment #11) > Is there any research I can do to help diagnose what needs to be fixed? Some > kind of tracing of the fglrx driver or anything? Or even a particular function > in the driver that I can futz with to see if anything helps? > Well, you can identify the chip by looking at the card. It's probably a siliconimage chip of some sort (sil-something). The hard part is figuring out the gpio line and pins used for i2c to configure the chip. You may be able to tell from tracing what the bios or fglrx does when it sets a mode on that ouput. As to the radeon driver, take a look at RADEONInitExtTMDSInfoFromBIOS() and RADEONGetExtTMDSInfoFromBIOS(). The bios has a table for what gpio reg it uses and the commands to set up the chip, but, I'm not sure how to find out what pins it uses or what's needed to enable them. The problem is I think it tends to vary based on the OEM. I'll ask around AMD and see what I can find out. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#348082: xserver-xorg: [ati/radeon] pinkness and interference pattern on Radeon RV250 If [Radeon 9000] rev 1 and TMDS-connected Samsung SyncMaster 213T
On Thu, May 22, 2008 at 12:15:04PM -0400, Alex Deucher wrote: > > In short, I'm now back to the original #348082 status quo, with the added > > benefit of not having to use the ConnectorTable option as part of the > > workaround. Also, my monitor now detects as DVI-0, and is not located at > > DVI-1 as before. > > Does switching to the other DVI port help? Unfortunately, I cannot find out. The other DVI port is an ADC port, and I don't have compatible hardware: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348082#152 -- G. Branden Robinson| I don't care if it has a GUI, or Debian GNU/Linux | command line, or is carved in mud [EMAIL PROTECTED] | with a sharp spoon. http://people.debian.org/~branden/ | -- Barry Smith signature.asc Description: Digital signature ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
