Markus Strobl wrote: > Roland Scheidegger wrote: >> On 15.03.2009 19:18, Markus Strobl wrote: >> >>> Just wondering if there's any work ongoing to fix the issue with >>> googleearth where it exits with "no fragment shader" Using >>> xf86-video-ati? It works fine with fglrx. >>> >>> Everything else works fine with xf86-video-ati: Composited desktop (KDE4 >>> w/ effects), glxgears etc. Just googleearth refuses to work. >>> >>> Graphics are a R430 (ATI X800XL), xf86-video-ati-6.12, mesa-7.3. >>> >> This is independent from xf86-video-ati. I suggest you try a newer mesa >> version (it looks to me like the error you quote there can only come >> from a pre-7.0 mesa version, in fact). >> >> Roland >> > Thanks, Roland. That helped in that I found I had an old parallel > install of googleearth installed that I cleaned out and I also found a > newer 32-bit mesa (the machine is 64-bit). Unfortunately it still > doesn't work. The googleearth screen comes up but when it tries to > render the earth it crashes with this: > > Warning: Unable to create prefs directory '/home/markus/.googleearth'. > File exists. > libGL warning: 3D driver claims to not support visual 0x69 > libGL warning: 3D driver claims to not support visual 0x21 > libGL warning: 3D driver claims to not support visual 0x21 > libGL warning: 3D driver claims to not support visual 0x21 > libGL warning: 3D driver claims to not support visual 0x21 > libGL warning: 3D driver claims to not support visual 0x21 > libGL warning: 3D driver claims to not support visual 0x21 > libGL warning: 3D driver claims to not support visual 0x21 > libGL warning: 3D driver claims to not support visual 0x22 > libGL warning: 3D driver claims to not support visual 0x22 > libGL warning: 3D driver claims to not support visual 0x22 > libGL warning: 3D driver claims to not support visual 0x22 > libGL warning: 3D driver claims to not support visual 0x22 > libGL warning: 3D driver claims to not support visual 0x22 > libGL warning: 3D driver claims to not support visual 0x22 > libGL warning: 3D driver claims to not support visual 0x22 > *********************************WARN_ONCE********************************* > File r300_render.c function r300Fallback line 428 > Software fallback:ctx->Line.SmoothFlag > *************************************************************************** > Try R300_SPAN_DISABLE_LOCKING env var if this hangs. > *********************************WARN_ONCE********************************* > File r300_state.c function r300_setup_rs_unit line 1391 > fragprog wants coords for tex0, vp doesn't provide them! > *************************************************************************** > drmRadeonCmdBuffer: -22 (exiting) > > I tried setting the R300_SPAN_DISABLE_LOCKING var but it did the same > thing (the R300_SPAN_DISABLE_LOCKING line in the console printout > disappeared, otherwise the same). > > Anything else I can try? > > /Markus
In driconf, disable low-impact fallbacks. This will eliminate at least one of the error messages, and keep it from falling back to software rendering. ~ C. _______________________________________________ xorg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xorg
