Bug 22174

Summary:	xorg ati driver: unknown chip
Product:	Mesa	Reporter:	Premysl Vohnout <premek>
Component:	Drivers/DRI/r300	Assignee:	xf86-video-ati maintainers <xorg-driver-ati>
Status:	RESOLVED NOTABUG	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Premysl Vohnout 2009-06-09 08:01:14 UTC

when I want to run googleearth I get this error:
unknown chip id 0x7145, can't guess.                          
libGL warning: 3D driver returned no fbconfigs.               
libGL error: InitDriver failed                                
libGL error: reverting to (slow) indirect rendering  

I have ATI x1400 (r500). Using xf86-video-ati-6.12.2, xorg-server-1.5.3. Gentoo linux. glxgears and glxinfo is ok

Comment 1 Alex Deucher 2009-06-09 08:37:25 UTC

Looks like you have an old 3d driver without r5xx support floating around.

Comment 2 Premysl Vohnout 2009-06-09 08:40:02 UTC

I have mesa-7.5_rc3. Sorry that I don't mention this. This problem is from mesa-7.1.

Comment 3 Alex Deucher 2009-06-09 08:42:22 UTC

(In reply to comment #2)
> I have mesa-7.5_rc3. Sorry that I don't mention this. This problem is from
> mesa-7.1. 
> 

mesa 7.1 didn't support r5xx chips.

Comment 4 Premysl Vohnout 2009-06-09 08:44:16 UTC

I've tried 7.2, 7.3, 7.4, 7.5-rc1, 7.5-rc2 and now I have 7.5-rc3.

Comment 5 Alex Deucher 2009-06-09 08:48:05 UTC

googleearth is trying to load an old 3D driver.  Search you system for r300_dri.so and make sure you don't have an old one floating around.

Comment 6 Michel Dänzer 2009-06-09 08:49:57 UTC

Note that Google Earth is a 32 bit application.

Comment 7 Premysl Vohnout 2009-06-09 08:53:32 UTC

ok that's the problem in /usr/lib64 is new r300_dri.so but in /usr/lib32 is old one

Comment 8 Premysl Vohnout 2009-06-09 08:54:58 UTC

problem is that in gentoo are emulated libraries from 20081109

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.