[i915] GL screensavers only drawn on top 1/3 of screen

[Bradley T Hughes]

After updating to the Breezy release candidate, all GL screensavers are only drawn on the top 1/3 of the screen. I did
the update yesterday, and saw the breakage immediately. I hadn't for around a week before that, so it's hard to say
exactly when the breakage occurred.

[Matt Zimmerman (mdz)]

Attach /etc/X11/xorg.conf and /var/log/Xorg.0.log

[Bradley T Hughes (bhughes)]

Created an attachment (id=4661)
xorg.conf

[Bradley T Hughes (bhughes)]

Created an attachment (id=4662)
Xorg.0.log

[Daniel Stone (daniels)]

do you see the same effect with glxgears, if you make it full-screen?

[Bradley T Hughes (bhughes)]

No, I don't, not with glxgears or any other GL application. It's only the screensaver. It might be worth mentioning that it's only the
GL screensavers that do this; all "normal" screensavers look ok.

My particular screensaver of choice is Solar Winds, and if I run ksolarwinds.kss from the command line, I see this effect even in the WM
decorated window. If I run 'ksolarwinds.kss --root', I don't see the effect... I can even make it full screen and it looks ok.

With the --setup argument, the small preview is also cut off, but in a different way (I only see a small strip at the bottom). Resizing
the setup window makes no difference, the preview is always cut off.

[Bradley T Hughes (bhughes)]

I've been meaning to add a comment to this bug for a while now, but only got to it now. I noticed that this report has been passed to
the xserver-xorg-driver-i810 package. I originally reported this against kscreensaver, because it is *only* the kde screensavers that
have this problem, and it happened after the upgrade from 3.4.2 to 3.4.3. The GNOME OpenGL screensavers do not have this problem, nor do
any other GL applications.

[Jakob Petsovits (jpetso)]

I've got the same issue (i915 on a Samsung X20).
When trying to get hardware acceleration working, I first had the replacement i810 driver from
http://www.fairlite.demon.co.uk/intel.html together with the xorg.conf Option "ForceBIOS" "1280x1024=1400x1050".
That worked, but disabled hardware acceleration due to libGL complaining about something.
The screensavers were unaccelerated, but fit properly into the screen.

The cut-off screensavers came into play when I tried it the other way, with the standard driver
and the 855resolution tool setting the VBIOS values to mode 58 (1400x1050).
That way hardware acceleration is working, but the screensavers suffer from the described issues.

My xorg.conf is a completely standard one with i180 driver and no special options.

[Jakub Stachowski (stachowski)]

The same problem with Fujitsu-Siemens Amilo Pro v8010. Affected are KDE GL screensavers and Google Earth beta 4.

[mrc (s-canady)]

Same problem occurs on a Compaq Presario SR1220NX using the i810 driver for an 845G chipset. I have the problem with both the screensavers (Kubuntu) and Google Earth Beta 4.

[mrc (s-canady)]

I forgot to mention that I'm running Dapper using Google Earth Beta 4. On Breezy, Google Earth 4 worked just fine (same problem with KDE GL screensavers, though), but on Dapper I now have this problem.

[Hannes Hauswedell (hannes-hauswedell)]

i can confirm on Dell Inspiron 640m.

[manuel (manuel-soto)]

I can confirm on Acer 3210

Ubuntu Dapper 6.06
Linux 2.6.15-26-686

Programs: Google Eath beta4 and bzflag. All screen savers ok

(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 7872 kB
(II) I810(0): VESA VBE OEM: Intel(r)915GM/910ML/915MS Graphics Chip Accelerated
VGA BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)915GM/910ML/915MS Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): Allocated 128 kB for the ring buffer at 0x0
(II) I810(0): Allocating at least 512 scanlines for pixmap cache
(II) I810(0): Initial framebuffer allocation size: 5120 kByte
...

[Fred H (fred-public)]

I can confirm on Dell Latitude D510, with Dapper Drake

[Manuel Teira (manuel-teira-telefonica)]

Same problem happens on a:
Toshiba Satellite L20
under Ubuntu 6.06.1 LTS

The problem also appears using:
glxgears -fullscreen.

Only a top fraction of the red gear is visible, and rendering is bad.
Google Earth also renders bad and works pretty slowly.

Card is a Intel 915GM configured as default by the Dapper installer. I'm attaching xorg.conf and the log.

[Donatas Glodenis (dgvirtual)]

I can confirm this problem on Asus A8F using kscreensaver. Have not tested google earth though.

[Donatas Glodenis (dgvirtual)]

Forgot to mention: i945GM chipset, Ubuntu dapper drake, the original 386 and subsequent kernel versions, including 686 kernel.

The report is marked as „needs info“. What info could the users provide re. this problem for it to be solved?

[Nick (nickz)]

The same here with a Toshiba Satellite Pro U200,
under Ubuntu 6.06.1 LTS and standard 686 kernel.

[Nick (nickz)]

I forgot to mention that glxgears in fullscreen mode give me the same problem.
If you need any log just tell me.

[Chris Jones (cmsj)]

I can confirm this (or at least very similar sounding behaviour) from Google Earth. When I first run it, it only renders 3d in the top section of its window (although, interestingly, it's rendering the bottom of its 3d section there). If I resize the window it corrects itself, providing I don't make the window too big.

[Paul Sladen (sladen)]

It could be running out of video buffer (two people have mentioned "making it larger" as showing off the problem.

[Chris Jones (cmsj)]

Yeah, on dapper I would reach a certain size of googleearth and have to stop making it larger.
However, I just tried it on edgy and it seems to be all good, the googleearth window renders correctly when I open it and I can fullscreen it with no ill effects :)

[manuel (manuel-soto)]

the box rendered is a 640x489 window size. If the application run fullscreen at this resolution all works propertly. bzflag mey be used to test

[Chris Jones (cmsj)]

Is there anyone not seeing this fixed with Edgy? If not this seems like it should be set to fixed.

[Charlie Figura (cfigura)]

I've updated to Edgy, and am no longer experiencing this problem.

[Timo Aaltonen (tjaalton)]

Closing bogus component.

[Timo Aaltonen (tjaalton)]

Closing the bug since it was reported to be fixed. Thanks!

[Donatas Glodenis (dgvirtual)]

Can confirm that it now works normally - on Edgy.

[Dominik Holler (dominik-holler)]

is this bug fixed in dapper, too ?

[manuel (manuel-soto)]

I do certify that hits bug was fixed in dapper too