Der neue Treiber ist da, mit neuen Features und Bugfixes. Wird per Copy&Paste weiter unten erläutert. (Weil sehr viel
)-> Release Notes
Download (57.7 MB)
[url=http://wiki.linuxgaming.de/index.php/ATI_Treiber_Installation]Installations How-To im Wiki[/url]
Neue Features:
- This release of the Catalyst™ Linux software driver introduces UYVY and YUY2 pixel format support. This support provides interleaved stream support for video playback applications such as TVTime and MythTV.
Behobene Probleme:
- Enemy Territory: Quake Wars: Playing the demo on a system running X no longer results in corruption being noticed. Further details can be found in topic number 737-35208
- Maya 2008: An incorrect colormap is no longer displayed for texture selector on systems running X. Further details can be found in topic number 737-35207
- Quake 3 Arena (demo): Segmentation faults no longer occur when attempting to play the game. Further details can be found in topic number 737-35206
- Quake3: Corruption is no longer noticed when changing the display resolution when the game is running. Further details can be found in topic number 737-35209
- SECAM, NTSC or PAL signal changes when using aticonfig or Catalyst Control Center and now gets applied to the TV display output. Further details can be found in topic number 737-34297
- Running X server without a window manager no longer results in the X server flashing green for a moment, going black, and the computer becoming unresponsive. Further details can be found in topic number 737-34299
- Corruption is no longer noticed when connecting a DFP display device to a system running X after setting the TV mode to 1080i. Further details can be found in topic number 737-34301
- Clock Gating is now supported and enable under the Linux operating system. Further details can be found in topic number 737-35191
- The desktop background color is no longer displayed incorrectly when using xcommgr. Further details can be found in topic number 737-35192
- Using the wrong delimiter in aticonfig --set-dispattrib=<disp>,<attr>, <value> no longer results in a segmentation fault. Further details can be found in topic number 737-35194
- Audio out is now functioning after the installation of the ATI graphics drivers for Ubuntu 7.10. Further details can be found in topic number 737-35196
- Bandwidth corruption is no longer noticed when setting the desktop resolution to 2048x1536 on systems containing an ATI Radeon HD 3200 series of product. Further details can be found in topic number 737-33499
- Playing a video clip using mplayer with the Xv extension enabled no longer results in an error indicating that Xv could not find a free Xv port. Further details can be found in topic number 737-35198
- Corruption is no longer noticed when enabling Big Desktop on systems containing an ATI FireGL X1 series of product and running X. Further details can be found in topic number 737-35199
- Running the X server generations test no longer results in the operating system failing to respond or a Kernel panic to occur after first server generation on SuSE 10.3 64 bit. Further details can be found in topic number 737-35200
- Attempting to resize a 2D application window no longer results in poor performance being noticed when composing is enabled. Further details can be found in topic number 737-35201
- Screen flicker is no longer noticed after running amdcccle in X. Further details can be found in topic number 737-35202
- Corruption is no longer noticed when connecting a DFP display device to a system running X after setting the TV mode to 1080i. Further details can be found in topic number 737-35203
- Glxgears corruption is no longer noticed in big desktop mode. Further details can be found in topic number 737-35204
- Starting glxgears and/or fgl_glxgears no longer results in the gears failing to render on SuSE 10.2 x86_64. Further details can be found in topic number 737-35205
- FGL_GLXGEARS or GLXGEARS: X no longer fails to respond when launching either of the applications. Further details can be found in topic number 737-35210
Bekannte Probleme:
- DiscoveryStudio1.7: The print preview and save as functions may fail to work properly. Further details can be found in topic number 737-35219
- Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-29578
- Bandwidth corruption may be noticed when setting the desktop resolution to 2048x1536 on systems containing an ATI Radeon HD 3200 series of product. Further details can be found in topic number 737-33499
- Connecting a CRT display device to a system containing an ATI Mobility Radeon X1600 product may result in the display device flashing multiple times or failing to display an image when attempting to launch the Catalyst Control Center. Further details can be found in topic number 737-34300
- DiscoveryStudio1.7: The print preview and save as functions may fail to work properly. Further details can be found in topic number 737-34278
- Setting the Overscan to an invalid value may result in segmentation faults. Further details can be found in topic number 737-35211
An incorrect error message may be returned when applying an unsupported TV geometry in a console terminal. Further details can be found in topic number 737-35212
- Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-35213
- An X segmentation fault may occur when launching SUZI/textured video. Further details can be found in topic number 737-35214
Creating two successive connections may result in direct GL context to fail. Further details can be found in topic number 737-35215
Moving the mouse or tapping a key may fail to close an OpenGL screen-saver and bring the user back to the x desktop. Further details can be found in topic number 737-35216
- The X Server may fail to reset clearly when AIGLX is enabled. Further details can be found in topic number 737-35217
- Opening a terminal and running semiautomated DPPT tests via lnxtest.sh may result in the operating system failing to respond. Further details can be found in topic number 737-35218
