[i855] No direct rendering for Intel 82852/855GM in Jaunty

[George]

Direct rendering doesn't seem to work with the Intel 82852/855GM video adapter in Jaunty. Because of this, I cannot run certain programs. It used to work fine in older releases, but doesn't work since Intrepid. I hoped it would be fixed in Jaunty, but it's not.

Here's some info on the system (Dell Latitude D505 laptop):

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

$ glxinfo | grep direct
direct rendering: No (LIBGL_ALWAYS_INDIRECT set)

xorg.conf:

Section "Device"
    Identifier "Configured Video Device"
EndSection

Section "Monitor"
    Identifier "Configured Monitor"
EndSection

Section "Screen"
    Identifier "Default Screen"
    Monitor "Configured Monitor"
    Device "Configured Video Device"
EndSection

[Bryce Harrington (bryce)]

Hi gapop,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[George (gapop)]

Hello, Bryce.

I have attached the requested info. This issue is permanent, it's not
something that I can reproduce on occasion. Apparently, it affects all
programs that use OpenGL. The programs have serious redrawing issues
which makes them unusable. I ran one such program right before
attaching the logs (I don't know how else to "reproduce" the issue).

Thanks,
George

On Thu, Jul 30, 2009 at 05:23, Bryce
Harrington<email address hidden> wrote:
> Hi gapop,
>
>
> Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue.  If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.
>
> [This is an automated message.  Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-xorglog
>
> ** Tags added: needs-lspci-vvnn
>
> ** Changed in: xserver-xorg-video-intel (Ubuntu)
>       Status: New => Incomplete
>
> ** Summary changed:
>
> - No direct rendering for Intel 82852/855GM in Jaunty
> + [i855] No direct rendering for Intel 82852/855GM in Jaunty
>
> --
> [i855] No direct rendering for Intel 82852/855GM in Jaunty
> https://bugs.launchpad.net/bugs/368995
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Albert Damen (albrt)]

Hi George,

to debug this issue, we need a bit more information:
- please attach the file .xsession-errors (from your home directory)
- please run the command glxinfo > glxinfo.txt and attach the file glxinfo.txt

Most likely LIBGL_ALWAYS_INDIRECT is set by compiz. Can you disable compiz and let us know if your applications work correctly without compiz?
(You can disable compiz via the System menu --> Preferences --> Appearance --> tab Visual Effects and select None)

[George (gapop)]

Hi, Albert.

I have attached the info you requested.

Indeed, the applications work if I disable Compiz. Sorry if I
mistakenly reported this bug, but I used to be able to work with these
apps on Feisty + Beryl.

On Thu, Jul 30, 2009 at 14:53, Albert Damen<email address hidden> wrote:
> Hi George,
>
> to debug this issue, we need a bit more information:
> - please attach the file .xsession-errors (from your home directory)
> - please run the command glxinfo > glxinfo.txt and attach the file glxinfo.txt
>
> Most likely LIBGL_ALWAYS_INDIRECT is set by compiz. Can you disable compiz and let us know if your applications work correctly without compiz?
> (You can disable compiz via the System menu --> Preferences --> Appearance --> tab Visual Effects and select None)
>
> --
> [i855] No direct rendering for Intel 82852/855GM in Jaunty
> https://bugs.launchpad.net/bugs/368995
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Albert Damen (albrt)]

Those lines in xsession-errors confirm compiz sets LIBGL_ALWAYS_INDIRECT:
Checking for texture_from_pixmap: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.

However, your X log shows texture_from_pixmap is supported by the driver:
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support

[Bryce Harrington (bryce)]

Well, next I'd like to forward this issue upstream, but first it must be retested on latest development version of Karmic to make sure the issue still happens there with the latest code. ISO images are available via http://www.ubuntu.com/testing/. If you can reproduce it in the LiveCD environment, you shouldn't need to modify your installed system. Also please attach a fresh Xorg.0.log and dmesg from this testing.

[George (gapop)]

The Karmic Alpha 4 LiveCD gets stuck in the booting sequence on my
system, and leaves me with a black screen and no keyboard or mouse
response. So I couldn't test anything.

I give up on this one.

On Wed, Aug 19, 2009 at 03:05, Bryce
Harrington<email address hidden> wrote:
> Well, next I'd like to forward this issue upstream, but first it must be
> retested on latest development version of Karmic to make sure the issue
> still happens there with the latest code.  ISO images are available via
> http://www.ubuntu.com/testing/.  If you can reproduce it in the LiveCD
> environment, you shouldn't need to modify your installed system.  Also
> please attach a fresh Xorg.0.log and dmesg from this testing.
>
> ** Changed in: xserver-xorg-video-intel (Ubuntu)
>       Status: Confirmed => Incomplete
>
> --
> [i855] No direct rendering for Intel 82852/855GM in Jaunty
> https://bugs.launchpad.net/bugs/368995
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.