View Full Version : [SOLVED] [dri] RADEONDRIGetVersion failed to open the DRM
September 17th, 2009, 03:39 AM
I just ran an update on this laptop to the latest version of the kernel (.31), in preparation for Karmic, and I've been having issues with the ATI card in the computer. Specifically, I can't get compositing back.
The most relevant error I have been able to find is in the Xorg.0.log from x startup:
[dri] RADEONDRIGetVersion failed to open the DRM
Any recommendations? I have tried moving between fglrx versions, I have tried switching to the opensource drivers, but nothing get's compositing back.
September 17th, 2009, 08:46 PM
WHat card do you have????
September 20th, 2009, 03:36 PM
Same problem here, card is 01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3450.
September 21st, 2009, 05:34 AM
Make sure the intel modules aren't loaded and interfering. This is a known, high-priority bug: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/392039
Fortunately, you can work around it (read the comments in that bug report).
September 22nd, 2009, 03:53 AM
Mobility Radeon HD 3400 Series is the card I'm using.
I have tried the module blacklisting that you shared from the Launchpad bug. It looks like the modules were loading, but I have added the blacklist and prevented from drm and i915 from loading (tried having each running), and fglrx is loading properly.
glxinfo still returns:
name of display: :0.0
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 135 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 16
Current serial number in output stream: 16
/var/log/Xorg.0.log reports the following errors with the card:
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
(EE) RADEON(0): Acceleration initialization failed
(EE) GLX error: Can not get required symbols.
September 22nd, 2009, 08:36 AM
The log indicates you're using the open-source radeon driver, but you keep mentioning Catalyst/fglrx. Check that your xorg.conf is set to load flgrx, and if necessary, run:
sudo aticonfig --initial
September 22nd, 2009, 02:15 PM
Wow, that fixed it.
I distinctly remember fglx being specified in my xorg.conf file at many points throughout this ordeal. It must have gotten reset at some point while trying to install/upgrade/downgrade/reinstall fglrx (which required me to remake the xorg.conf file probably 10-16 times).
I wonder if it was the combination of the blacklisting and the actually specifying the fglrx driver that fixed it, or if it was the 8.660 version that came out.
THANK YOU SO MUCH!
Powered by vBulletin® Version 4.2.2 Copyright © 2017 vBulletin Solutions, Inc. All rights reserved.