I just noticed from the suse radeonhd mailing list that some important bug(s) got closed in the official suse radeonhd bugzilla as 'not our bug':
(1) OPENGL Locks up your Kernel Example: try to resize glxdemo and the system freezes (2) OPENGL screen corruptions Example resize the glxgears window or nicer: ppracer, watch snow, quit ppracer and enjoy a new window decoration style. Something that also can crash your system and at least causes screen corruption: (3) Not enough Video memory for textures not handled, screen corruptions If I use BIOS to set the UMA video buffer size (chipset graphics) to 32 MBytes then in ppracer for example some text is no longer correctly displayed. After quitting ppracer some (KDE-)Gui elements are no longer drawn correctly. Some other things that were not mentioned in the radeonhd mailing list: (4) radeonhd not usable without dri installed/enabled (with KDE) Many desktop actions like opening a menu or clicking a desktop icon cause the server to crash. (5) radeonhd xvideo broken without dri installed/enabled XVideo does not honour hsync. Artefacts (diagonal structures) become visible. Also the system may freeze when (KDE's kwin) draws focus rectangles above the xvideo window. ---- To me it looks as if the non-dri stuff never got tested because the developers wanted to implement the dri stuff. Without dri radeonhd is definitively not usable (for KDE users), with dri enabled it might be partially usable for some people. Some GUI frameworks (other then KDE/QT) might use different drawing primitives not causing the problems described above. In my bug report I always referred to KDE 3.5.9/10 using KDM (as currently in testing). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
