Bug 91045 - problems with 10.6.x and glamor
Summary: problems with 10.6.x and glamor
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 10.6
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-21 16:44 UTC by gabriele balducci
Modified: 2015-06-23 01:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf (2.39 KB, text/plain)
2015-06-21 16:44 UTC, gabriele balducci
Details
Xorg.0.log (34.94 KB, text/plain)
2015-06-21 16:45 UTC, gabriele balducci
Details

Description gabriele balducci 2015-06-21 16:44:09 UTC
Created attachment 116632 [details]
xorg.conf

hello,

not sure that I'm sending this to the right mesa component: if not,
apologies and please redirect me

Starting with 10.6.0-rc1, mesa-10.6.x somehow breaks glamor (or it's
the other way around).

If I boot X11 with glamor enabled (`Option "AccelMethod" "glamor"' in
xorg.conf) and mesa-10.6.x, I get a black screen background (despite
"xsetroot -bg violet -fg white -mod 16 16" in my .xinitrc). Moreover,
xterms and in general all other windows have a black background; no
visible cursor in the xterms, but if I play with window exposure (by
lowering/raising them), I can see parts of them with the expected
appearance (eg xterm: white bg and violet fg).

If I run xrefresh, everything disappears into the black background;
then, if I focus the windows by moving the mouse upon them, the
decorations of the WM emerge (the windows' background remains black,
though)

It seems to be only a matter of background/appearance, in general:
functionality of the different clients seems to be fine, as far as I
can say (eg the shells in the xterms do work fine etc).

Everything is restored to normality if I boot X11 with mesa-10.6.x and
glamor disabled in xorg.conf.

Also, absolutely no problem with glamor enabled and mesa-10.5.x

Here are my specs:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]

kernel          4.0.5
mesa            10.6.0
libdrm          2.4.61
xorg-server     1.17.2
xf86-video-ati  7.5.0
glamor-egl      0.6.0
llvm            3.6.1

mesa built with:

     --enable-texture-float
     --enable-gles1
     --enable-gles2
     --disable-openvg
     --enable-xa
     --enable-gbm
     --enable-gallium-gbm
     --enable-r600-llvm-compiler
     --enable-glx-tls
     --with-egl-platforms="drm,x11,wayland"
     --with-gallium-drivers="nouveau,r300,r600,radeonsi,svga,swrast" 
     --with-dri-drivers='radeon,nouveau,swrast'


I have no idea which might be the problem.

I will be happy to provide any other information which might be
useful in this regard

thank you very much in advance for any help
Comment 1 gabriele balducci 2015-06-21 16:45:53 UTC
Created attachment 116633 [details]
Xorg.0.log
Comment 2 Michel Dänzer 2015-06-22 01:50:04 UTC
> (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> (II) Module glamoregl: vendor="X.Org Foundation"
> 	compiled for 1.17.0, module version = 0.6.0

You're using the old standalone glamor. Please try current glamor from the xserver tree (if you build xserver yourself, make sure --enable-glamor is passed to its configure script).
Comment 3 gabriele balducci 2015-06-22 13:54:51 UTC
(In reply to Michel Dänzer from comment #2)
> > (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> > (II) Module glamoregl: vendor="X.Org Foundation"
> > 	compiled for 1.17.0, module version = 0.6.0
> 
> You're using the old standalone glamor. Please try current glamor from the
> xserver tree (if you build xserver yourself, make sure --enable-glamor is
> passed to its configure script).

thanks a lot: everything is working nicely again (10.6.0+glamor)
apologies for the noise
Comment 4 Michel Dänzer 2015-06-23 01:21:32 UTC
Glad it's working again!


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.