I tried to test Xair with a Radeon M9 card on FC5test3 for the last days, and it fails to correctly initialize DRM (as far as I can see). The card is detected as Chipset: "ATI Radeon Mobility 9000 (M9) Lf (AGP)" (ChipID = 0x4c66) Xair -version gives me[ralph@logout ~]$ Xair -version X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.15-1.1948_FC5 i686Red Hat, Inc. Current Operating System: Linux logout.strg-alt-entf.org 2.6.15-1.1977_FC5 #1 Thu Feb 23 14:53:53 EST 2006 i686 Build Date: 22 February 2006 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present When I try to run anything OpenGL related, I get [ralph@logout ~]$ glxinfo name of display: :0.0 libGL error: open DRM failed (Operation not permitted) libGL error: reverting to (slow) indirect rendering I'll attach the output of a strace of glxinfo. When starting Xair, I see some error on the console, which I'll also attach. I've been trying desperately to get Xair to dump core on me, so I could attach a backtrace, but to no avail. Even with Option "NoTrapSignals" "1" in the xorg.conf, Xair still starts up "normally", so I don't have any more output than that in the attached files. Regards, Ralph
Created attachment 4767 [details] Strace of glxinfo resulting in a LibGL error This happens when I strace glxinfo on Xair
Created attachment 4768 [details] This error gets dumped to the console when starting Xair This is what I get on the console when starting Xair. Xair starts up normally, but DRM/DRI doesn't work.
This is indeed a double free happening with the accel_indirect_glx branch. It prevents direct rendering from working, but other than that it's harmless. It's fixed on the accel_indirect_branch branch, which is what will be merged to cvs head. We'll have updated RPMs up soon, but for now I'm closing this bug.
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.