"copy" rendering path broken?

[ianni67]

On my notebook (beryl 0.3.0svn + Intel Graphics Card + Ubuntu Feisty), I cannot select the "copy" rendering path anymore. It used to work with Ubuntu Edgy.
I also tested both Beryl 0.2.0 and 0.2.1, too. Same issue.
When I select the "copy" rendering path, the screen becomes messy and eventually I cannot read the whole screen anymore and have to restart the window manager and immediately switch to "Texture from pixmap" or "automatic" rendering path.

Anyone else having the same trouble? I'd like to fix it in some way, as I remember this rendering path being faster that the other one (at least with my notebook).

[ianni67]

*bump*
any hints?

[sp_nz]

*bump*
any hints?


This will be of little help to you but the ONLY way I've managed to get Beryl to run is with enabling the copy option. Up until then I could not get past the dreaded WSOD (white screen of death).

But, now whenever I start to move or minimise a window I lose all ability to work (I can't open new windows, existing windows stop taking input) but all the beryl cube still works. Recovery is by CTL-ALT-BACKSPACE only :(

I'd like to know if you find resolution as it's likely our problems are related :(

Thanks
Scott

AMD 3400+
ATI 9700
Feisty + Beryl 0.20 + glx + v8.36.5 driver

[ianni67]

I cannot give you much help: I currently run beryl on my notebook which has an intel graphics card so cannot tell you anything about ATI drivers.

I'm running a beryl 0.3.0git version: it comes from the Telperion Blog, and it correctly deals with the White Cube of Death. But it does not play nice with the "copy rendering path", in both Aiglx and Xgl.

I also ran beryl 0.2.0 and 0.2.1: same story. Looks like it's a feisty problem, as everything with Xgl and Ubuntu Edgy was great: I had wonderful performances with the copy rendering path.

[Kristian]

There is no support for Beryl beyond 0.2.1 and 0.2.0.

And there's a good reason for that: The 0.3.x series was a development series, we never made a release, and it didn't have too many fascinating changes for most people. Since we are merging with compiz, we are working on the collected code, and Copy rendering is one thing that is still missing, because it needs to be redesigned and implemented as a plugin.

If you need it, you should use the Beryl 0.2 branch.

[ianni67]

Thank you very much for your explaination Kristian, so finally I'm understanding something more.

So you mean, that in 0.2.1 the copy rendering path should work?

[ianni67]

Nope.
I removed everyting related to 0.3.0 and reinstalled 0.2.1.
Same movie: copy rendering path is a mess.

At this point I moved back to the future, to 0.3.0.
I think I'll stick to 0.3.0 until opencompositing has a .deb pakaging and most plugins working... :-)

[Kristian]

Can you possibly supply screenshots of this "mess", or describe it in more detail?

A full paste of the output Beryl generates when starting up would also be helpfull, along with the driver version you're using.

[ianni67]

Can you possibly supply screenshots of this "mess", or describe it in more detail?

A full paste of the output Beryl generates when starting up would also be helpfull, along with the driver version you're using.


Not easy to describe: I apologise in advance for the huge screenshots.
http://visilab.unime.it/~ianni/messed-up-beryl-01.png


http://visilab.unime.it/~ianni/messed-up-beryl-02..png

[ianni67]

Here is the copy/paste of the complete output of beryl when launched from the shell:
[code:5cb22]ianni@morpheus:~/Desktop$ beryl --replace --use-copy &
[1] 31771
ianni@morpheus:~/Desktop$ ************************************************** ************
* Beryl system compatibility check *
************************************************** ************

Detected xserver : AIGLX

Checking Display :0.0 ...

Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed

Checking Screen 0 ...

Checking for GLX_SGIX_fbconfig : passed
Checking for GLX_EXT_texture_from_pixmap : passed
Checking for non power of two texture support : passed
Checking maximum texture size : passed (2048x2048)
[/code:5cb22]

Please, note that the current version is 0.3.0 but I got the same problems (identical problems) with beryl 0.2.1 yesterday, after removing 0.3.0 and reistalling 0.2.1.

lspci answers:
[code:5cb22]00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
[/code:5cb22]

[Kristian]

I'm no Intel expert, but that looks like something that might be fixed with tuning the driver options. Can you paste your xorg.conf ?

[ianni67]

Here you are. :-) thank you for your help!
[code:ac00d]# /etc/X11/xorg.conf (xorg X Window System server configuration file)

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
# Load "GLcore"
Load "bitmap"
Load "ddc"
Load "dbe"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "it"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection



Section "Device"
Identifier "Intel Corporation 82852/855GM Integrated Graphics Device"
Driver "i810"
Option "XAANoOffscreenPixmaps"
BusID "PCI:0:2:0"
#Option "UseFBDev" "true"
EndSection

Section "Monitor"
Identifier "Monitor Generico"
Option "DPMS"
HorizSync 28-51
VertRefresh 43-60
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation 82852/855GM Integrated Graphics Device"
Monitor "Monitor Generico"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSection

Section "ServerLayout"
#Option "AIGLX" "true"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Synaptics Touchpad"
EndSection

Section "DRI"
Mode 0666
EndSection
#Section "Extensions"
# Option "Composite" "0"
#EndSection[/code:ac00d]