Comment 17 for bug 355495

Yes, I talked about the 8.602 version.

It doesn't work for me in jaunty, as well as the version from its
repository (8.600). As I said, I always get screen corruption with those
drivers when starting up and then it freezes. So that's why I can't
accurately tell you what has changed.

If you're not experiencing this, it may be a bug specific for my
platform, the version of jaunty I am using is RC x86_64. Or just an
upgrade problem? I'm upgrading my testing jaunty copy from alpha 5, I
think. Not sure.

However, I tried the new driver also in intrepid. It worked well, video
(including also tvtime, audio visualization in totem, 3d games, etc.) no
more flickers with composite enabled, but the performance with composite
is very, very poor. At least 4x slower (according to my glxgears test).
And finally, video in totem is not stretched to the window size (if not
in fullscreen) but it's cropped. And if I try to toggle fullscreen, my
screen goes dark, then the numlock and capslock LEDs on my keyboard
blink simultaneously (which means kernel panic, I think) and PC becomes
unresponsive. Sometimes it doesn't happen on the first attempt, but
that's exactly what I was experiencing with the Catalyst 9.3, so no
improvement here. That's why I decided to stay with my tested Catalyst
8.12.

Really sad that they can't make fully working drivers after so much time
(4 months from 8.12), as Patrick said. But maybe you'll have more luck.