Michael Kjorling wrote:
export LIBGL_DRIVERS_PATH=/usr/X11R6/lib32/modules/dribefore launching the binary. However, I don't have any such directory: /usr/X11R6/lib32/modules only contains a directory "extensions", and setting LIBGL_DRIVERS_PATH to that provides no improvement whatsoever.
This was a fix for the ATI DRI (closed source) drivers, not the xorg DRI drivers. Also, after upgrading to the latest ATI drivers, I had to remove this setting the get 3D support working again.
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 (II) RADEON(0): [drm] DRM interface version 1.0 (II) RADEON(0): [drm] drmSetBusid failed (7, pci:0000:01:00.0), Permission denied (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
I know it's considered bad mojo to run X as root, but what I do in these situations shut down all X servers, log into the console as root and run X > x.log 2>&1 Once I get the lovely grey checkered screen, kill the server <CTRL> + <ALT> + <BACKSPACE> I then review the x.log and /var/log/Xorg.0.log for errors. If you still see "Permission denied", then the problem is most likely with a missing driver/module (which is what I am guessing is your problem). If there are no permission errors, I then run startx as root, and look at the glxinfo output. You should see a line like: direct rendering: Yes Once you see that, you know you have 3D support working as root, then repeat the tests as a noraml user. Since I have a Radeon 9800XT, I can not use the Xorg DRI drivers for 3D support. As I mentioned earlier, I recently upgraded my ATI drivers, and 3D support stopped working for my normal user account. I went through the procedure above, and found 3D support worked for root. After double checking all kernel settings, rebuilding all modules, I finally decided to remove the LIBGL_DRIVERS_PATH, and 3D support started working for my normal user again. I know this is not the same problem, but it may help you in troubleshooting. In addition to the xorg.conf and Xorg.0.log files you have posted, you may want check the output of dmesg, and double check your kernel settings in Device Drivers -> Character Devices (AGP and DRI), and do a lsmod to make sure all the correct drivers are loaded. Regards, Brett -- [email protected] mailing list
