Cristan maakte ons er correct op attent dat AMD van de week niet alleen zijn Catalyst 7.11 voor Windows XP en Vista uitgebracht heeft, maar dat er ook een voor Linux beschikbaar is. Voor het eerst loopt het versienummer in pas met de Windows-versie, een nummer wat het jaar en maand van uitgave weergeeft. Versie 7.11 van de Linux-driver kan overweg versies 6.7 tot en met 7.3 van X.org, Linux Kernel 2.6 en hoger en glibc 2.2 of 2.3. Linux Kernel 2.4 en XFree86 4.3 worden niet langer ondersteund. De laatste versie die dat deed was versie 8.42.3. De release notes van Catalyst Linux Display Driver 7.11 zien er als volgt uit:
New FeaturesResolved Issues
- This release of the ATi Catalyst Linux driver introduces early-look support for the following new operating systems:
- Red Hat Enterprise Linux 4.6 (tested Snapshot 6)
- Red Hat Enterprise Linux 5.1 (tested Snapshot 7)
- Ubuntu 7.10
- RedFlag 6.0 DT (tested with RC)
- OpenSUSE 10.3 (tested with RC1)
Known Issues
- Launching a new terminal un RHEL5 32bit version no longer results in an inconsistent background colors appearing each time the window is minimized and maximized
- The kernel module is now working on kernel version 2.6.23
- An error message no longer appears during installation if dash is used as /bin/sh
[break]
- There is no support for video playback on the second head in dual head mode. Further details can be found in topic number 737-26985
- 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
- A black screen may be observed on some hardware when switching to the console or leaving the X window system when a Vesa framebuffer console driver is used. Further details can be found in topic number 737-30687
- An error message appears during installation if dash is used as /bin/sh. A topic number is not available for this issue
- Several distribution-specific packaging scripts are not up-to-date in this release. In particular packaging for 64-bit Ubuntu versions is known to be broken. A topic number is not available for this issue