FYI: Some beryl changes

brain0 · 2006-11-10 16:38:19

I updated beryl-svn again and there is an important change: Beryl doesn't use texture-from-pixmap by default any more. This makes it usable on even more graphics cards, but is quite experimental. Everything looked funky on my nvidia, so I had to reenable tfp:

* Enable "Use Texture-From-Pixmap" in beryl-manager
or
* Start beryl with beryl --use-tfp or beryl-xgl --use-tfp

It works fine again now.

Tatey · 2006-11-11 13:06:13

Thanks for the information. Working fine here now

Gullible Jones · 2006-11-11 14:29:41

Thanks, I'll see if Beryl doesn't start working on my box now.

FWIW, I think the problem isn't lack of texture-from-pixmap support on certain cards, but Beryl somehow not recognizing it. Mine has texture-from-pixmap according to glxinfo, but Beryl seems to think otherwise.

dongiovanni · 2006-11-11 15:07:33

Hi,

I had to delete my beryl configs and then I had to activate tfp again. After that, everything works fine again

DonGiovanni

brain0 · 2006-11-11 15:25:11

New beryl version again, two improvements:

* Beryl now uses tfp by default again
* The non-tfp mode now works with nvidia

Gullible Jones · 2006-11-11 15:58:12

Hmm, I get problems whether or not using TFP, though AIGLX is working.

[proteus@chameleon ~]$ beryl --indirect-rendering --strict-binding --replaceXGL Absent, checking for NVIDIA
Nvidia Absent, assuming AIGLX
beryl: Another window manager is already running on screen: 0
beryl: No manageable screens found on display :0.0

Here's the output from glxinfo:

name of display: :0.0
libGL warning: 3D driver claims to not support visual 0x46
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, 
    GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, 
    GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_video_sync, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig
OpenGL vendor string: VIA Technology
OpenGL renderer string: Mesa DRI UniChrome (KM400) 20060710 x86/MMX+/3DNow!+/SSE
OpenGL version string: 1.2 Mesa 6.5.1
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, 
    GL_ARB_point_parameters, GL_ARB_texture_env_add, 
    GL_ARB_texture_env_combine, GL_ARB_texture_mirrored_repeat, 
    GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, 
    GL_EXT_blend_color, GL_EXT_blend_minmax, GL_EXT_blend_subtract, 
    GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_convolution, 
    GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, 
    GL_EXT_histogram, GL_EXT_packed_pixels, GL_EXT_point_parameters, 
    GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, 
    GL_EXT_separate_specular_color, GL_EXT_stencil_wrap, GL_EXT_subtexture, 
    GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, 
    GL_EXT_texture_env_add, GL_EXT_texture_env_combine, 
    GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_vertex_array, 
    GL_APPLE_packed_pixels, GL_IBM_rasterpos_clip, 
    GL_IBM_texture_mirrored_repeat, GL_MESA_window_pos, GL_NV_blend_square, 
    GL_NV_light_max_exponent, GL_NV_texgen_reflection, GL_OES_read_format, 
    GL_SGI_color_matrix, GL_SGI_color_table, GL_SGIS_texture_edge_clamp, 
    GL_SGIS_texture_lod

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x22 24 tc  0 32  0 r  y  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x23 24 tc  0 32  0 r  .  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x24 24 tc  0 32  0 r  y  .  8  8  8  8  0 16  0  0  0  0  0  0 0 None
0x25 24 tc  0 32  0 r  .  .  8  8  8  8  0 16  0  0  0  0  0  0 0 None
0x26 24 tc  0 32  0 r  y  .  8  8  8  8  0  0  0  0  0  0  0  0 0 None
0x27 24 tc  0 32  0 r  .  .  8  8  8  8  0  0  0  0  0  0  0  0 0 None
0x28 24 tc  0 32  0 r  y  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x29 24 tc  0 32  0 r  .  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x2a 24 tc  0 32  0 r  y  .  8  8  8  8  0 16  0 16 16 16 16  0 0 Slow
0x2b 24 tc  0 32  0 r  .  .  8  8  8  8  0 16  0 16 16 16 16  0 0 Slow
0x2c 24 tc  0 32  0 r  y  .  8  8  8  8  0  0  0 16 16 16 16  0 0 Slow
0x2d 24 tc  0 32  0 r  .  .  8  8  8  8  0  0  0 16 16 16 16  0 0 Slow
0x46 32 tc  0 32  0 r  .  .  8  8  8  8  0  0  0  0  0  0  0  0 0 Ncon

GL_EXT_texture_from_pixmap is there, not sure if anything's wrong though.

Also, AIGLX does seem to be working, though with some odd warnings:

[proteus@chameleon ~]$ cat /var/log/Xorg.0.log | grep -i aiglx
(**) Option "AIGLX"
(**) AIGLX enabled
(WW) AIGLX: 3D driver claims to not support visual 0x22
(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
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/unichrome_dri.so

brain0 · 2006-11-11 16:31:19

Always try to start beryl from beryl-manager, it is much more reliable.

Gullible Jones · 2006-11-11 23:27:53

Still get the same thing:

libGL warning: 3D driver claims to not support visual 0x46
XGL Absent, checking for NVIDIA
Nvidia Absent, assuming AIGLX
libGL warning: 3D driver claims to not support visual 0x46
beryl: Support for non power of two textures missing
beryl: Failed to manage screen: 0
beryl: No manageable screens found on display :0.0

Beryl fails to start, and I have to kill beryl-manager and restart metacity.

brain0 · 2006-11-12 02:05:06

Gullible Jones wrote:

Still get the same thing:

libGL warning: 3D driver claims to not support visual 0x46
XGL Absent, checking for NVIDIA
Nvidia Absent, assuming AIGLX
libGL warning: 3D driver claims to not support visual 0x46
beryl: Support for non power of two textures missing
beryl: Failed to manage screen: 0
beryl: No manageable screens found on display :0.0

Beryl fails to start, and I have to kill beryl-manager and restart metacity.

First, I think you should learn to read. It is not the same message. Second, you can restart metacity using beryl-manager by just selecting it as a window manager.
I don't know anything about the missing textures thing, but you might wanna try to use non-tfp mode (select it in beryl-manager) or check your xorg configuration for the right AIGLX settings.

Gullible Jones · 2006-11-12 03:35:19

Sorry, that was stupid... :oops:

Anyway, I tried again without TFP, and this time *did* get the same message. I'm starting to think that, in spite of what glxinfo and Xorg.0.log say, my hardware doesn't support AIGLX to a usable extent.

brain0 · 2006-11-12 09:37:02

It seems it DOES support AIGLX, but that isn't enough, you also need certain textures supported, obviously. Maybe you can solve this by setting another xorg.conf option. If so, please add a comment to the Beryl wiki page on Archwiki,

Gullible Jones · 2006-11-12 19:14:20

Okay, I did a bit more research and discovered that it also affects Savage. Here's what I came up with:

http://bugs.beryl-project.org/ticket/641
http://www.mail-archive.com/dri-devel@l … 28895.html

Apparently support for non-power-of-two textures is an optional OpenGL extension which isn't supported by Savage or Unichrome hardware, but shouldn't be necessary for Beryl to work properly. The Beryl and Compiz people say this is a driver bug, and I guess they know what they're talking about, though I don't quite get how that would lead to Beryl or Compiz screwups as opposed to problems with all kinds of GL apps.

Anyway, I'll see if I can find a workaround or a patch...

Gullible Jones · 2006-11-15 01:54:34

As far as I can tell, there's no patch for either the driver or Beryl, and the only potential workaround I found doesn't apply to Unichrome or Savage.

brain0 · 2006-11-22 20:16:16

Just FYI: I built the experimental beryl 3d world plugin. It's not in the repo as it will be merged into beryl-plugins anyway at some point, but you can get it at http://www.archlinux.org/~thomas/beryl/ … pkg.tar.gz

There is another issue I'd like some opinions about: Is it already worth putting a release (0.1.2) of beryl into extra? As far as I can see, the releases lack many features very quickly and there won't be many people choosing release over svn.

Romashka · 2006-11-22 20:56:05

brain0 wrote:

There is another issue I'd like some opinions about: Is it already worth putting a release (0.1.2) of beryl into extra? As far as I can see, the releases lack many features very quickly and there won't be many people choosing release over svn.

But most people don't use Unstable (or scare to do this), so it's not easy for newbies to install beryl. Putting release in Extra won't harm anyway, even when if -svn versions become more featured very quickly. Those users who really want more features and not just to try beryl will use -svn versions from Unstable anyway.

BTW, which package require seom-svn?

brain0 · 2006-11-22 21:07:29

Romashka wrote:

But most people don't use Unstable (or scare to do this), so it's not easy for newbies to install beryl. Putting release in Extra won't harm anyway, even when if -svn versions become more featured very quickly. Those users who really want more features and not just to try beryl will use -svn versions from Unstable anyway.

Thanks for your input on this, it is as always appreciated. The point is that we don't have to waste Arch's bandwidth and my compile time if noone will use the "stable" releases (they aren't THAT stable anyway). Currently, the stable version lacks vidcap, heliodor, aquamarine, some effects and some important plugin improvements, as well as the better beryl-manager (compared to today's svn).

BTW, which package require seom-svn?

It's for vidcap. seom does OpenGL capturing.

Romashka · 2006-11-22 21:14:37

brain0 wrote:

Thanks for your input on this, it is as always appreciated. The point is that we don't have to waste Arch's bandwidth and my compile time if noone will use the "stable" releases (they aren't THAT stable anyway). Currently, the stable version lacks vidcap, heliodor, aquamarine, some effects and some important plugin improvements, as well as the better beryl-manager (compared to today's svn).

Ah, I got the point. You are probably right.

McQueen · 2006-11-23 06:00:15

brain0 wrote:

There is another issue I'd like some opinions about: Is it already worth putting a release (0.1.2) of beryl into extra? As far as I can see, the releases lack many features very quickly and there won't be many people choosing release over svn.

I wouldn't be interested in installing anything other than the svn Beryl releases at this point, primarily because I accept the project as a whole to be a testing ground and I would prefer to have all of the currently available options and plugins at my disposal. I can imagine a possible downside to this being that many users may not be comfortable delving into the unstable repo, but then again the xfce-svn packages seem to be widely used so maybe this is a moot point.

brain0 · 2006-11-26 23:24:43

Okay, new beryl revisions uploaded. New seom-svn fixes video capture and playback (seom-filter was broken before).

Beryl plugin ABI version changed again, so make sure to upgrade everything at once. A new beryl-3d-plugin build is here: http://www.archlinux.org/~thomas/beryl/ … pkg.tar.gz

Romashka · 2006-11-27 16:21:40

brain0 wrote:

A new beryl-3d-plugin build is here: http://www.archlinux.org/~thomas/beryl/ … pkg.tar.gz

Why it's not in Unstable?

tardo · 2006-11-27 16:44:14

My problem with beryl is that starting beryl-manager kills my desktop, then everything on the desktop starts ghosting. If I move a window around you can still see the remnants of the last window position. I'm using i810, anyone else have this problem?

brain0 · 2006-11-27 18:25:43

Romashka wrote:

brain0 wrote:
A new beryl-3d-plugin build is here: http://www.archlinux.org/~thomas/beryl/ … pkg.tar.gz
Why it's not in Unstable?

It will be merged into beryl-plugins at some point, probably within the next few days or weeks. So there is no point in uploading it to the repo now.

brain0 · 2006-12-02 19:43:45

Okay, new beryl packages are up. Some of my beryl settings were lost after the update, so back them up just to be sure.

The 3d plugin has been merged into beryl-plugins now.

brain0 · 2006-12-12 00:33:14

New beryl-svn builds are up and I have another goodie: http://www.archlinux.org/~thomas/beryl/ … pkg.tar.gz
Works with the latest builds and brings snow to beryl. Have fun.

once · 2006-12-12 02:04:31

ya, snowing in warm winter here, but cpu over 85% loaded.

Arch Linux

#1 2006-11-10 16:38:19

FYI: Some beryl changes

#2 2006-11-11 13:06:13

Re: FYI: Some beryl changes

#3 2006-11-11 14:29:41

Re: FYI: Some beryl changes

#4 2006-11-11 15:07:33

Re: FYI: Some beryl changes

#5 2006-11-11 15:25:11

Re: FYI: Some beryl changes

#6 2006-11-11 15:58:12

Re: FYI: Some beryl changes

#7 2006-11-11 16:31:19

Re: FYI: Some beryl changes

#8 2006-11-11 23:27:53

Re: FYI: Some beryl changes

#9 2006-11-12 02:05:06

Re: FYI: Some beryl changes

#10 2006-11-12 03:35:19

Re: FYI: Some beryl changes

#11 2006-11-12 09:37:02

Re: FYI: Some beryl changes

#12 2006-11-12 19:14:20

Re: FYI: Some beryl changes

#13 2006-11-15 01:54:34

Re: FYI: Some beryl changes

#14 2006-11-22 20:16:16

Re: FYI: Some beryl changes

#15 2006-11-22 20:56:05

Re: FYI: Some beryl changes

#16 2006-11-22 21:07:29

Re: FYI: Some beryl changes

#17 2006-11-22 21:14:37

Re: FYI: Some beryl changes

#18 2006-11-23 06:00:15

Re: FYI: Some beryl changes

#19 2006-11-26 23:24:43

Re: FYI: Some beryl changes

#20 2006-11-27 16:21:40

Re: FYI: Some beryl changes

#21 2006-11-27 16:44:14

Re: FYI: Some beryl changes

#22 2006-11-27 18:25:43

Re: FYI: Some beryl changes

#23 2006-12-02 19:43:45

Re: FYI: Some beryl changes

#24 2006-12-12 00:33:14

Re: FYI: Some beryl changes

#25 2006-12-12 02:04:31

Re: FYI: Some beryl changes

Board footer