Bug 30412

Summary: opengl doesn't work when using gallium and xorg state tracker
Product: Mesa Reporter: Martin Stolpe <martinstolpe>
Component: Drivers/Gallium/r300Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
See Also: https://bugs.freedesktop.org/show_bug.cgi?id=30405
Whiteboard:
i915 platform: i915 features:
Attachments: xorg log file

Description Martin Stolpe 2010-09-28 01:14:17 UTC
glxgears fails to run with the following error:
  "Error: couldn't get an RGB, Double-buffered visual"
Comment 1 Michel Dänzer 2010-09-28 01:21:47 UTC
Please attach the full Xorg.0.log and the output of

LIBGL_DEBUG=verbose glxinfo 2>&1
Comment 2 Martin Stolpe 2010-09-28 01:50:18 UTC
Output of
 $ LIBGL_DEBUG=verbose glxinfo 2>&1
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig

The xorg log file is completly full with statements with this content:
"[  2351.450] (II) radeon(0): xorg_composite_accelerated fallback Component alpha not supported with source alpha and source value blending. (op=3)"
Comment 3 Michel Dänzer 2010-09-28 02:06:23 UTC
(In reply to comment #2)
> The xorg log file is completly full with statements with this content:
> "[  2351.450] (II) radeon(0): xorg_composite_accelerated fallback Component
> alpha not supported with source alpha and source value blending. (op=3)"

We still need to see it. Feel free to gzip it if you're concerned about the size.
Comment 4 Martin Stolpe 2010-09-28 02:41:04 UTC
Created attachment 39003 [details]
xorg log file

Attached xorg log file.
Comment 5 Martin Stolpe 2010-09-28 02:57:39 UTC
I was looking at the xorg log with ksystemlog and it didn't show me the head of the log.

3D is working now. Fixed it with a soft link:
  ln -sf /usr/lib/xorg/modules/dri/r300_dri.so /usr/lib/xorg/modules/dri/radeon_dri.so

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.