Error of Beryl+AIGLX on i965

Tue Nov 14 22:29:34 PST 2006

>-----Original Message-----
>From: Andrew Barr [mailto:andrew.james.barr at gmail.com]
>Sent: 2006年11月15日 12:17
>To: Wang, Wei Z
>Cc: xorg at lists.freedesktop.org
>Subject: Re: Error of Beryl+AIGLX on i965
>
>On Tuesday 14 November 2006 22:52, Wang, Wei Z wrote:
>> Thank you Adrew for your kind help :)
>>
>> As for the "(II) AIGLX: Loaded and initialized
>> /opt/X11R7/lib/dri/i915_dri.so" Sorry for the typo, it should be
>> _i965_dri.so_ and I am sure I did it on i965 HW. Actually, this AIGLX
>> warnings appear on several of our test machines (i945, i915 and i965), so I
>> just copied and pasted from some i915 machine by mistake. But the warning
>> (WW) is real and exactly as the warning on i965 machines:)
>>
>>
>> And pls. see [Wei] below. Thank you for your attention.
>>
>> >-----Original Message-----
>> >From: Andrew Barr [mailto:andrew.james.barr at gmail.com]
>> >Sent: 2006年11月15日 10:29
>> >To: Wang, Wei Z
>> >Cc: xorg at lists.freedesktop.org
>> >Subject: Re: Error of Beryl+AIGLX on i965
>> >
>> >Here's what I understand: It should work with the latest versions of
>> >everything--xserver, Mesa, and some miscellaenous bits: glproto for
>> >one--except that GLX_ext_texture_from_pixmap support is broken in the
>> >current
>> >xserver git HEAD and fixing it is waiting on GLX 1.3 support.
>>
>> [Wei] Before GLX 1.3 is available, and workaround to enable compiz?
>> We just gave a quick try on FC6 with its compiz+AIGLX, however, everytime
>> we push the "Enable desktop effects" button, it returns us the gnome login
>> screen without any cube effects. -- maybe it is also the
>> "GLX_ext_texture_from_pixmap" 's reason ?
>
>That sounds like an X server crash. In that case, you will find information
>about what happened and a possible backtrace in
>${prefix}/var/log/Xorg.0.log.old, ${prefix} being the root of your X server
>installation.
>

Yep, the X server got crashed. And the backtrace is 
==========================================================
Backtrace:
0: /usr/bin/Xorg(xf86SigHandler+0x71) [0x495ff1]
1: /lib64/libc.so.6 [0x37ece30210]
2: /usr/lib64/dri/i965_dri.so [0x2aaabda6b752]
3: /usr/lib64/dri/i965_dri.so(_mesa_BlendFunc+0x3b) [0x2aaabda7182d]
4: /usr/lib64/xorg/modules/extensions/libglx.so(__glXRender+0xd7) [0x2aaaab3c18a7]
5: /usr/lib64/xorg/modules/extensions/libglx.so [0x2aaaab3c60c8]
6: /usr/bin/Xorg(Dispatch+0x1ca) [0x449c9a]
7: /usr/bin/Xorg(main+0x455) [0x4325d5]
8: /lib64/libc.so.6(__libc_start_main+0xf4) [0x37ece1da44]
9: /usr/bin/Xorg(FontFileCompleteXLFD+0x231) [0x4318c9]

Fatal server error:
Caught signal 11.  Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch
(WW) I810(0): Successfully set original devices
(WW) I810(0): Setting the original video mode instead of restoring
        the saved state
(WW) I810(0): Extended BIOS function 0x5f05 not supported.
(II) I810(0): BIOS call 0x5f05 not supported, setting refresh with VBE 3 method.
(II) I810(0): xf86UnbindGARTMemory: unbind key 7
(II) I810(0): xf86UnbindGARTMemory: unbind key 0
(II) I810(0): xf86UnbindGARTMemory: unbind key 1
(II) I810(0): xf86UnbindGARTMemory: unbind key 3
(II) I810(0): xf86UnbindGARTMemory: unbind key 2
(II) I810(0): xf86UnbindGARTMemory: unbind key 4
(II) I810(0): xf86UnbindGARTMemory: unbind key 5
(II) I810(0): xf86UnbindGARTMemory: unbind key 6
(WW) I810(0): Successfully set original devices (2)
==========================================================

>I have an Intel DG965RY Desktop Board-based system, and I have been
>meaning to
>try Fedora 6 on it. So I think that is something I will do tomorrow and see
>what I can turn up.
>
>> >Currently your screen just turns white because of the missing GL
>> > extension.
>> >
>> >On Tuesday 14 November 2006 21:13, you wrote:
>> >> Hi all:
>> >>
>> >> I am just swamped with enabling AIGLX+beryl on i965 chipset
>(XGL+beryl
>> >> is
>> >> good), and met some problem which is similar to this bug
>> >> (https://bugs.freedesktop.org/show_bug.cgi?id=8155)
>> >>
>> >>
>> >> My environment is:
>> >> OSD: Ubuntu Edgy
>> >> Xorg: 7.1.1
>> >> 3D driver: from tip of Mesa
>> >> ========================================
>> >> This is the options I modified in xorg.conf
>> >>
>> >> 1, in Section "Module":
>> >> 	#Load  "GLcore"
>> >> 	Load "glx"
>> >> 	Load "dbe"
>> >> 2, Section "ServerLayout"
>> >> 	Option "AIGLX" "true"
>> >> 3, Section "Extensions"
>> >> 	Option "Composite" "Enable"
>> >> 4, Section "Device"
>> >> 	Option "XAANoOffscreenPixmaps"
>> >> 5, Section "Screen"
>> >> 	DefaultDepth 24
>> >> 6, Section "DRI"
>> >> 	Mode    0666
>> >> ==================================
>> >
>> >Just a tip for future reference, using 16-bit color depth vastly improves
>> > the performance of Intel hardware--965 included.
>>
>> [Wei] thanks :)
>>
>> >> Xorg.0.log, the following warning appears forever if AIGLX is enabled
>> >>
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x23
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x24
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x25
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x26
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x27
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x28
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x29
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x2a
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x2b
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x2c
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x2d
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x2e
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x2f
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x30
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x31
>> >> (WW) AIGLX: 3D driver claims to not support visual 0x32
>>
>> [Wei] Actually I really want to know the root cause of these warnings :)
>
>The nonsupported visual warnings are harmless and IIRC a fix was recently
>committed for it.
>
>> >> (II) AIGLX: Loaded and initialized /opt/X11R7/lib/dri/i915_dri.so
>> >
>> >As was pointed out on the xorg list, this isn't right. The correct i965
>> > module is i965_dri.so. So are you /sure/ you have i965 hardware?
>> >
>> >> ==================================
>> >> In gnome environment, execution of "beryl-manager" introduces the
>> >> following
>> >> errors (and I got the cube effects with white blinking facets):
>> >>
>> >> LibGL warning: 3D driver claims to not support visual 0x5a
>> >> XGL absent, checking for NVIDIA
>> >> Nvidia Absent, assuming AIGLX
>> >> LibGL warning: 3D driver claims to not support visual 0x5a
>> >> beryl: No stencil buffer. Clipping of transformed windows is not going
>> >> to be correct when screen is transformed.
>> >> Initiating splash
>> >> berly: water: GL_ARB_fragment_program is missing.
>> >> ==================================
>> >
>> >Alot of this is normal and doesn't affect correct operation of
>> > Beryl/Compiz on Intel chipsets.
>>
>> [Wei] do you mean that warning "3D driver claims to not support visual 0x5a
>> " doesn't matter?
>
>Right. This was a harmless bug that was recently fixed.
>
>> My white screen are all due to the missing of
>> "GL_ARB_fragment_program"?
>
>You'll have to ask someone who knows better than I, but the white screen
>issue
>from what I understand, is because the GLX_ext_texture_from_pixmap
>extension
>is currently broken in HEAD.
>
>--
>Andrew Barr
>
>Men go crazy in congregations they only get better one by one.
>	-- Sting, "All This Time" (The Soul Cages, 1991)

- Wei