Bug 298721 - Google Earth fails to init 3D (Interrupt problem)
Google Earth fails to init 3D (Interrupt problem)
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: Dave Airlie
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-09-20 13:57 EDT by Ralf Ertzinger
Modified: 2009-07-14 11:03 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 10:57:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ralf Ertzinger 2007-09-20 13:57:46 EDT
Description of problem:
Intel 945GM chipset, intel driver. 3D in general works (glxgears, compiz,

GoogleEarth, however, fails to use 3D acceleration.
Starting it prints the following to the console:
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.

The kernel logs the following:
[drm:i915_vblank_swap] *ERROR* Invalid pipe 1

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start google earth on the above system
Actual results:
Above warning at the console and the kernel log, GE is very slow.

Expected results:
"normal" 3d speed

Additional info:
Comment 1 Kyle McMartin 2008-01-09 10:32:13 EST
Can you try the rpms here:

They incorporate a possible fix.

cheers, Kyle
Comment 2 Bug Zapper 2008-05-13 23:15:35 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 3 Thomas J. Baker 2008-05-28 18:04:30 EDT
I'm still seeing this with F9 and xorg-x11-drv-i810-2.2.1-24.fc9.x86_64. I get
these at startup:

continuity> googleearth 
Failed to initialize TTM buffer manager.  Falling back to classic.
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.

I don't get any dmesg kernel warnings though. Same bug?
Comment 4 Jens Lautenbacher 2008-06-15 17:34:41 EDT
I have the same problem here with Fedora 9 and the intel driver (everything up
to date). Google earth is unusably slow, other 3D stuff works...
Comment 5 Bug Zapper 2009-06-09 18:51:20 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 6 Bug Zapper 2009-07-14 10:57:02 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.