On Wed, 2009-05-27 at 23:45 +0200, Torquil Macdonald Sørensen wrote: > Package: x11-utils > Version: 7.4+1 > Severity: normal > > Hello, xdriinfo reports the following: > > t...@debian ~$ xdriinfo > Screen 0: not direct rendering capable. > > However, > > t...@debian ~$ glxinfo | grep direct > direct rendering: Yes
This isn't really adequate anymore, try something like glxinfo|grep render > t...@debian ~$ xdpyinfo | grep -i dri > DRI2 > XFree86-DRI > > Also, this has been reported and fixed over at RedHat: > https://bugzilla.redhat.com/show_bug.cgi?id=495342 This is also fixed in upstream Git mesa_7_5_branch. However, I'm not sure this is relevant for you: > But I am a bit uncertain, since I am not an expert. My Xorg.0.log does > actually say: > > (II) RADEON(0): [DRI] installation complete > (II) RADEON(0): [drm] removed 1 reserved context for kernel > (II) RADEON(0): [drm] unmapping 8192 bytes of SAREA 0xe0840000 at 0xb7806000 > (II) RADEON(0): [drm] Closed DRM master. > (WW) RADEON(0): Direct rendering disabled You don't have 3D hardware acceleration anyway (and if you did, you wouldn't hit the problem above, as the radeon drivers don't support DRI2 yet), do you have the firmware-linux package installed? In summary, I don't think there's a bug here other than #527132. -- Earthling Michel Dänzer | http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org