Bug 15441

Summary:	"Error: couldn't find RGB GLX visual or fbconfig" after upgrading to current git
Product:	Mesa	Reporter:	Bernhard Rosenkraenzer <bero>
Component:	Drivers/DRI/r300	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	git
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Bernhard Rosenkraenzer 2008-04-10 12:17:20 UTC

Upgrading to a current git xorg/Mesa/libdrm/drm kernel modules combo on a box with an onboard Radeon Mobility 9600 (works great with the latest release versions; xorg.conf remained the same), DRI doesn't work - glxinfo says "Error: couldn't find RGB GLX visual or fbconfig".

Neither "LIBGL_DEBUG=verbose glxinfo" nor "Xorg -verbose 9" give any indication of what is going wrong.

The same git versions work fine on an Intel 945GM and an ATI 9200.

Comment 1 Michael de Lang 2008-04-10 12:45:55 UTC

On 10/04/2008, bugzilla-daemon@freedesktop.org <
bugzilla-daemon@freedesktop.org> wrote:
>
> http://bugs.freedesktop.org/show_bug.cgi?id=15441
>
>            Summary: "Error: couldn't find RGB GLX visual or fbconfig"
> after
>                     upgrading to current git
>            Product: Mesa
>            Version: CVS
>           Platform: Other
>         OS/Version: All
>             Status: NEW
>           Severity: normal
>           Priority: medium
>          Component: Drivers/DRI/r300
>         AssignedTo: dri-devel@lists.sourceforge.net
>         ReportedBy: bero@arklinux.org
>
>
> Upgrading to a current git xorg/Mesa/libdrm/drm kernel modules combo on a
> box
> with an onboard Radeon Mobility 9600 (works great with the latest release
> versions; xorg.conf remained the same), DRI doesn't work - glxinfo says
> "Error:
> couldn't find RGB GLX visual or fbconfig".
>
> Neither "LIBGL_DEBUG=verbose glxinfo" nor "Xorg -verbose 9" give any
> indication
> of what is going wrong.
>
> The same git versions work fine on an Intel 945GM and an ATI 9200.


Yeah, I had the same problem. It was fixed for me yesterday or so, when they
put commit 2771862adcbc163c0a3f3eaaf4b58c658e72f680 in the mesa tree.

Comment 2 Bernhard Rosenkraenzer 2008-04-13 02:04:15 UTC

Confirmed fixed in current git

Comment 3 Adam Jackson 2009-08-24 12:29:51 UTC

Mass version move, cvs -> git

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.