Hmmm... ok - somehow i can't reproduce the "working state" with "nomodeset" any more now, after hibernating ...
of course i forgot the add the command line to the kernel when it booted, but of course it is now nevertheless in effect again (after switching to the old ram state image...) so googleearth i think worked _once_ with full 3d support after a clean nomodeset boot ... but i couldn't put my signature on it any more now. just before, it allways complained about not beeing started in "DirectX" mode and asked to switch to DirectX, which i affirmed, but then it was somehow still in "compatibility graphics mode" and running quiet slow (earth rotation) after unchecking "compatibility mode" in graphics options and restarting a few times, now when i start it the _whole_ application is unuseable slow. (i.e. even the menus react only with a 10s delay) i realize "direct rendering" whatever it really means these days is somehow only halfway enabled ... the (II) GLX: Initialized DRI2 GL provider for screen 0 line from the xorg.0.log, which i pasted in comment 37 has diappeared from the log and instead (II) AIGLX: Screen 0 is not DRI2 capable is there now. /usr/bin/glxinfo from the mesa-utils package reports "direct rendering: Yes" ONCE ... compiz seems to be working with it but googleearth not... (so compiz works with dri1 as well but googleearth (wine?) requires dri2, which is buggy ???) ja... i don't know.. but hopefully somebody can shed some light on this and/or make use these infos ... -- OpenGL graphic errors in google earth https://bugs.launchpad.net/bugs/570879 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-driver-ati. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
