If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
3D is great, but I would settle for some good 2D. Neither the fglrx driver or the radeonhd driver give usable performance in 2D yet. I have little hope for fglrx, even the catalyst driver for Windows is terrible. Try dragging a window around with show contents turned on, it's slower than it was a decade ago!
torham, can you please start another thread and pastebin your xorg log, conf and dmesg output ? It sounds as if acceleration isn't enabled on your system for some reason.
As a quick check, see if xvinfo finds textured video adapters.
I guess anyone with GDB debugging experience could start hammer on those bugs without knowing anything about graphics?
Yes, more or less. In addition, there is a programming guide, shader ISA documentation, and register specs available for download: http://www.x.org/docs/AMD/
So with GDB and specs you can get a general idea of what's going on in the mesa code by just tracing the code. The redbook demos are very simple.
Sooo, pretty soon I'll have a 100% open source OS, including WiFi.
On fglrx: Seems to all work fine for me, except maximizing windows with compiz has a 1-2 second lag on it (so I turn compiz off, 'ray)
Phenom II X3 720 BE
Biostar TA790GX AM2+ board
Integrated Radeon 3300
1440 x 900 monitor
3 x 500GiB HDD
Ubuntu 9.04 32bit.
Don't know why maximizing windows has such bad latency, everything else is pretty sharp.
bridgman: You're the man now, dog!
I have a 1-2 second lag with unminimization in gnome, as in: minimize a window, then focus on it again. Maximization and restoring works fine here. Happens only when using compositing (in gnome I use compiz as compositing window manager).
The funny thing is, I also get that lag when using KDE's KWin. when I enable the KWin plugin for performance tracking, a clear spike to the maximum of the scale is noticeable (I assume that cpu usage is being tracked).
It's a damn shame too, because this means that the fault lies with fglrx. I think that if this issue were to be fixed in Catalyst 9.6 that it certainly would make the wait for FOSS radeon(hd) 3D support for the R600/R700 cards a bit less painful.
The delay resulted from an xserver patch being backed out to fix a corruption issue on Intel HW AFAIK - reapplying the patch seems to make the delay go away. My understanding is that this is an xserver issue not a driver issue; you hear similar complaints from people with different hardware and drivers as well.
My understanding is that this is an xserver issue not a driver issue; you hear similar complaints from people with different hardware and drivers as well.
But then why does it not happen with radeon/radeonhd/intel? The thing that surprised me the most when switching from fglrx to radeon was the great performance with composite. That includes resizing/maximizing (no noticeable lag).
The reports I have seen indicated a similar delay with the open source driver when running compositing. All the reports saying there was no delay with the open source drivers were on 6xx/7xx where the lack of 3D support prevents the use of GL-based compositing.
I have also seen a number of posts from Intel users discussing the tradeoffs associated with the patch; screen corruption vs delays.
Are you seeing something different, and if so which GPU are you using ?
Using the open drivers in Jaunty with a 200M you can notice a slight delay with Compiz while maximizing/minimizing. Kwin is not that bad, but you can indeed notice some lag when maximizing/minimizing as well. Using xterm with the open drivers is smooth as silk however, whereas with fglrx its simply painful; Metacity takes at least 3 seconds to update, and Kwin bogs down to a crawl.
Yep, this works. Not only are the Compiz issues resolved, but the CCC no longer that +5 seconds to load.
Indeed, I can confirm that the xserver from the PPA d2kx provided, works.
Running KDE 4.3 RC1 right now with compositing turned on, on a radeon HD4870 card.
@bridgman: I was indeed aware that the direct cause for this performance regression was the removal of a xorg patch. The reason, however, that I said the fault lay with catalyst is that I was (and still am, to be honest) under the impression that nvidia's blob reaches acceptable performance on their cards. If this incorrect, I apologise.
I do wonder, regardless of where the blame lies, about what can be so computationally intensive about unminimizing a window that, when a certain patch is removed from xorg, the performance for that functionality drops to a level where lag is noticeable.
The fact that this happens tells me that the performance for that operation wasn't too high to start with (although this doesn't HAVE to be the case, I guess that would also depend on the invasiveness of the xorg patch in question).
I assume the window has to be rendered again, but with modern gfx cards that shouldn't be an issue; it is what the hardware is built for