Red Hat Bugzilla – Bug 217185
Open GL Fails on Radeon 9250
Last modified: 2018-04-11 04:50:33 EDT
Description of problem: When trying to run any OpenGL program (such as glxgears)
the program exits and prints:
drmRadeonCmdBuffer: -22 (exiting)
"libGL warning: 3D driver claims to not support visual 0x4b"
before the above two errors.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Using a Radeon 9250, start any OpenGL program.
The above commands are printed, and the program exits.
The program starts normally.
I have tried this with two 9250's, and the results were the same, ruling out a
bad card. Also, OpenGL starts fine on my onboard graphics hardware using
xorg-x11-drv-i810, so my motherboard is not at fault.
Thanks for the bug report. We have reviewed the information you
have provided above, and there is some additional information we
require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X
server log file (/var/log/Xorg.*.log) to the bug report as individual
uncompressed file attachments using the bugzilla file attachment link
below. Could please also attach output of the command dmesg (e.g., the file
which is created by dmesg >filename)?
Also don't you have by chance 64-bit computer. There seems to be related
discussion at http://thread.gmane.org/gmane.comp.freedesktop.xorg/6514 about
similar issue with mixing 64bit and 32bit libraries.
We will review this issue again once you've had a chance to attach
Thanks in advance.
Created attachment 143461 [details]
xorg configuration file
Created attachment 143463 [details]
X11 Log file
Created attachment 143465 [details]
X11 Log File
Created attachment 143466 [details]
X11 Log File
I have have a 32-bit architecture, not 64. Also, I doubt the xorg.conf file to
be the problem here. I've attached all the Xorg.*.log files.
Created attachment 143472 [details]
Output of dmesg
2.6.19-1.2888.fc6 kernel fixes the bug.
*** Bug 202442 has been marked as a duplicate of this bug. ***
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Marking fixed per comment #8.