Created attachment 32563 [details] [review] dmesg Updating only Mesa from 7.4.4 to 7.6.1 disables DRI for me. Radeon X1300 Pro, pci-e Initial specs: linux 2.6.30.10, Xorg 7.4, ati 6.12.4 Just to be sure, I also updated the kernel to 2.6.32.3 and Xorg to 7.5, but still no direct rendering. Current specs: linux 2.6.32.3, Xorg 7.5, ati 6.12.99 (today's git master). Also tried Mesa 7.7, bug is still present. dmesg | grep drm: [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to userspace modesetting. [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on minor 0 grep drm Xorg.0.log (II) [KMS] drm report modesetting isn't supported. drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci:0000:01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card1 drmOpenByBusid: drmOpenMinor returns -1 ... etc until card15
Created attachment 32564 [details] lspci -vvnn
Created attachment 32565 [details] Xorg.0.log
Forgot to mention the newer Mesa also brought an update to libdrm (2.4.11 with 7.4.4, 2.4.17 with 7.6.1). Apologies if this is a libdrm bug instead. How can I find that out? Found a strange symptom: if X has been run with a working combo, the new combo works as well. The new combo fails straight from a reboot.
(In reply to comment #3) > Forgot to mention the newer Mesa also brought an update to libdrm (2.4.11 with > 7.4.4, 2.4.17 with 7.6.1). > Apologies if this is a libdrm bug instead. How can I find that out? E.g. by downgrading Mesa but keeping the new libdrm. It's certainly not really possible for Mesa to prevent the X server from enabling the DRI... > Found a strange symptom: if X has been run with a working combo, the new combo > works as well. The new combo fails straight from a reboot. Sounds like maybe it's a /dev/dri/card* ownership / permissions issue. These were traditionally determined by X but more recently udev may also play a role, depending on how libdrm is built.
The git master of libdrm works. Something between 2.4.17 and master fixes this. Thanks for your time.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.