Red Hat Bugzilla – Bug 439889
radeon_tp: 3D driver returned no fbconfigs
Last modified: 2012-04-17 16:07:27 EDT
Description of problem:
I'm trying out the new radeon_tp driver included in the RHEL 5.2 beta.
(BTW: NICE JOB getting it this far along. I've been REALLY frustrated
by the behavior of the VESA driver on my Radeon X1300 platform.)
When I run glxgears to see how fast we're doing frame updates,
or glxinfo to learn about the GL behavior, I get the error:
Version-Release number of selected component (if applicable):
unknown chip id 0x7183, can't guess.
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
Is this normal at the present evolution of the driver?
Or is there some 3d initialization that should be done to get out to the
Mesa OpenGL library that isn't being done.
How can I help?
100%. Every time.
Steps to Reproduce:
1. log in
2. run glxgears
Created attachment 299763 [details]
output of glxinfo
Created attachment 299764 [details]
X server log output
Created attachment 299765 [details]
xorg config file. Fresh install RHEL 5.2 beta
I'm sorry to be a pest here, but I'd REALLY like enough of the radeon_tp driver
to be working for it to be what MIT, and anybody else who buys Dell Optiplex
Desktops, to standardize upon as quickly as possible.
Could someone at least answer for me: Is the driver known to be not fleshed out
far enough to do the 3d detection properly?
there is no 3D support for these chips available yet. Upstream has reached a
point where gears is runnable, but there is a fair bit of work on the 3D engine
before it could be considered shippable
Thanks very much for that information. I'm sure 3D support will eventually work
in the fullness of time. At least now I know that it's missing functionality, not
something "broken" per se.
No further hardware enablement updates are planned for RHEL5's X stack. If this issue remains in RHEL6, please update the affected product version and reopen this bug.