Hi, With googleearth I get: do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try running with LIBGL_THROTTLE_REFRESH and LIBL_SYNC_REFRESH unset. and it takes age to start. After that googleearth run quite smoothly. radeon driver version: 6.7.197 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
Please attach (as opposed to paste) the full xorg.conf and Xorg.0.log files and the output of xrandr --verbose. Which version of Mesa are you using?
Created attachment 13584 [details] xorg.conf
Created attachment 13585 [details] Xorg.0.log
Created attachment 13586 [details] xrandr
Bugzilla Upgrade Mass Bug Change NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO. - benjsc fd.o Wrangler
Does this also happen if another 3D application (e.g. glxgears) is running when you start Google Earth?
Happens for me too. mesa 7.0.2/xserver 1.4.0.90/ati git driver from 20080227 (post 1.6.8), kernel 2.6.24 Setting: <option name="vblank_mode" value="0" /> in drirc makes googleeart start (but machine locks up later)
More info, X600 mobile radeon, XAA. Tried running googleearth while glxgears was already running - no change. Still got "do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try running with LIBGL_THROTTLE_REFRESH and LIBL_SYNC_REFRESH unset." In my case this is like: googlearth &; splash shows; do_wait error is displayed on console and it looks like it never progress - splash is displayed all the time.
After getting some more information on IRC, it looks like this is a Mesa bug related to whatever extension Google Earth uses for sync-to-vblank (sync-to-vblank seems to be generally working, e.g. using the vblank_mode driconf setting). It would be interesting to know if this still happens with the mesa Git master branch.
still happening with 7.0.3~rc2
http://gitweb.freedesktop.org/?p=mesa/mesa.git;a=commitdiff;h=2407e48f2805e27e76e2e1d7083926c4077d9032;hp=5b91ee27c0f6e6379a9dc0bb41f4aef2f66b6346 applied on top of 7.0.2 fixes (or workarounds) the problem for me.
Fix backported to 7.0 branch, it'll be in the 7.0.3 release.
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.