From: Marcello M. <ha...@gm...> - 2005-02-24 00:04:38
Attachments:
xorg.conf
|
Hi all, I've a problem with lastest DRI (from CVS) drivers and Xscreensavers that use OpenGL. I've tried nearly all of them , from "Bubble 3D" to "Rubik Cube" all these simply flicker like hell when are executed . I don't know why, so I ask you an info about this. Please help :( melchior@melchior:~$ glxinfo name of display: :0.0 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_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig 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_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 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_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI R200 20041207 AGP 4x x86/MMX+/3DNow!+/SSE TCL OpenGL version string: 1.3 Mesa 6.3 OpenGL extensions: GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, 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_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_compression_s3tc, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_ATI_blend_equation_separate, GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_light_max_exponent, GL_NV_texture_rectangle, GL_NV_texgen_reflection, GL_NV_vertex_program, GL_OES_read_format, GL_SGI_color_matrix, GL_SGI_color_table, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_S3_s3tc glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess 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 ---------------------------------------------------------------------- 0x23 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x24 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x25 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x26 24 tc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x27 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x28 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x29 24 tc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x2a 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2b 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x2c 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x2d 24 dc 0 32 0 r . . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x2e 24 dc 0 32 0 r . . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow 0x2f 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x30 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None 0x31 24 dc 0 32 0 r y . 8 8 8 8 0 24 0 16 16 16 16 0 0 Slow 0x32 24 dc 0 32 0 r y . 8 8 8 8 0 24 8 16 16 16 16 0 0 Slow melchior@melchior:~$ Bye Marcello |
From: Michel <mi...@da...> - 2005-02-24 04:02:59
|
On Wed, 2005-02-23 at 20:50 +0100, Marcello Maggioni wrote: >=20 > I've a problem with lastest DRI (from CVS) drivers and Xscreensavers > that use OpenGL. >=20 > I've tried nearly all of them , from "Bubble 3D" to "Rubik Cube" all > these simply flicker like hell when are executed . If you're running them manually with -root, it's probably because the root window isn't double buffered. Otherwise, does disabling colour tiling or page flipping make a difference? --=20 Earthling Michel D=C3=A4nzer | Debian (powerpc), X and DRI develop= er Libre software enthusiast | http://svcs.affero.net/rm.php?r=3Ddaenzer |
From: Marcello M. <ha...@gm...> - 2005-02-24 14:41:31
|
---------- Forwarded message ---------- From: Marcello Maggioni <ha...@gm...> Date: Thu, 24 Feb 2005 14:26:27 +0100 Subject: Re: [R200] Nearly all xscreensavers GL flicker To: Michel D=E4nzer <mi...@da...> On Wed, 23 Feb 2005 23:02:37 -0500, Michel D=E4nzer <mi...@da...> wr= ote: > On Wed, 2005-02-23 at 20:50 +0100, Marcello Maggioni wrote: > > > > I've a problem with lastest DRI (from CVS) drivers and Xscreensavers > > that use OpenGL. > > > > I've tried nearly all of them , from "Bubble 3D" to "Rubik Cube" all > > these simply flicker like hell when are executed . > > If you're running them manually with -root, it's probably because the > root window isn't double buffered. Otherwise, does disabling colour > tiling or page flipping make a difference? > > -- > Earthling Michel D=E4nzer | Debian (powerpc), X and DRI develope= r > Libre software enthusiast | http://svcs.affero.net/rm.php?r=3Ddaenze= r > I run them from KDE Control Center and disabling Page flipping doesn't make a difference. I don't know what is colour tiling :/ Marcello |
From: Michel <mi...@da...> - 2005-02-24 15:30:59
|
[ Please don't follow up just to me privately ] On Thu, 2005-02-24 at 14:26 +0100, Marcello Maggioni wrote: > On Wed, 23 Feb 2005 23:02:37 -0500, Michel D=C3=A4nzer <mi...@da...= t> wrote: > > On Wed, 2005-02-23 at 20:50 +0100, Marcello Maggioni wrote: > > > > > > I've a problem with lastest DRI (from CVS) drivers and Xscreensavers > > > that use OpenGL. > > > > > > I've tried nearly all of them , from "Bubble 3D" to "Rubik Cube" all > > > these simply flicker like hell when are executed . > >=20 > > If you're running them manually with -root, it's probably because the > > root window isn't double buffered. Otherwise, does disabling colour > > tiling or page flipping make a difference? >=20 > I run them from KDE Control Center [...] IIRC some versions of KDE are known to be buggy in this regard. --=20 Earthling Michel D=C3=A4nzer | Debian (powerpc), X and DRI develop= er Libre software enthusiast | http://svcs.affero.net/rm.php?r=3Ddaenzer |
From: Marcello M. <ha...@gm...> - 2005-02-24 15:54:45
|
On Thu, 24 Feb 2005 10:30:03 -0500, Michel D=E4nzer <mi...@da...> wr= ote: >=20 > [ Please don't follow up just to me privately ] >=20 Sorry, I just pushed the wrong button :P > IIRC some versions of KDE are known to be buggy in this regard. >=20 Really? I'll try to run the screensaver separately and then report |
From: Vladimir D. <vo...@mi...> - 2005-02-24 16:39:06
|
On Thu, 24 Feb 2005, Michel [ISO-8859-1] D=E4nzer wrote: > > [ Please don't follow up just to me privately ] > > On Thu, 2005-02-24 at 14:26 +0100, Marcello Maggioni wrote: >> On Wed, 23 Feb 2005 23:02:37 -0500, Michel D=C3=A4nzer <michel@daenzer.n= et> wrote: >>> On Wed, 2005-02-23 at 20:50 +0100, Marcello Maggioni wrote: >>>> >>>> I've a problem with lastest DRI (from CVS) drivers and Xscreensavers >>>> that use OpenGL. >>>> >>>> I've tried nearly all of them , from "Bubble 3D" to "Rubik Cube" all >>>> these simply flicker like hell when are executed . >>> >>> If you're running them manually with -root, it's probably because the >>> root window isn't double buffered. Otherwise, does disabling colour >>> tiling or page flipping make a difference? >> >> I run them from KDE Control Center [...] > > IIRC some versions of KDE are known to be buggy in this regard. Yep - if you start them from KDE they are all run without double=20 buffering. (or at least this appeared to be so each time I tried) I have no idea why. Try running xscreensaver directly. best Vladimir Dergachev > > > --=20 > Earthling Michel D=C3=A4nzer | Debian (powerpc), X and DRI devel= oper > Libre software enthusiast | http://svcs.affero.net/rm.php?r=3Ddaenze= r > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dclick > -- > _______________________________________________ > Dri-devel mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-devel > |
From: Marcello M. <ha...@gm...> - 2005-02-24 18:27:40
|
On Thu, 24 Feb 2005 11:38:10 -0500 (EST), Vladimir Dergachev <vo...@mi...> wrote: >=20 >=20 > On Thu, 24 Feb 2005, Michel [ISO-8859-1] D=EF=BF=BDnzer wrote: >=20 > > > > [ Please don't follow up just to me privately ] > > > > On Thu, 2005-02-24 at 14:26 +0100, Marcello Maggioni wrote: > >> On Wed, 23 Feb 2005 23:02:37 -0500, Michel D=C3=A4nzer <michel@daenzer= .net> wrote: > >>> On Wed, 2005-02-23 at 20:50 +0100, Marcello Maggioni wrote: > >>>> > >>>> I've a problem with lastest DRI (from CVS) drivers and Xscreensavers > >>>> that use OpenGL. > >>>> > >>>> I've tried nearly all of them , from "Bubble 3D" to "Rubik Cube" all > >>>> these simply flicker like hell when are executed . > >>> > >>> If you're running them manually with -root, it's probably because the > >>> root window isn't double buffered. Otherwise, does disabling colour > >>> tiling or page flipping make a difference? > >> > >> I run them from KDE Control Center [...] > > > > IIRC some versions of KDE are known to be buggy in this regard. >=20 > Yep - if you start them from KDE they are all run without double > buffering. (or at least this appeared to be so each time I tried) > I have no idea why. >=20 > Try running xscreensaver directly. >=20 > best >=20 > Vladimir Dergachev >=20 > > > > > > -- > > Earthling Michel D=C3=A4nzer | Debian (powerpc), X and DRI dev= eloper > > Libre software enthusiast | http://svcs.affero.net/rm.php?r=3Ddaen= zer > > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users= . > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dclick > > -- > > _______________________________________________ > > Dri-devel mailing list > > Dri...@li... > > https://lists.sourceforge.net/lists/listinfo/dri-devel > > >=20 With XSCREENSAVER alone it effectively runs without problems , but I wonder why ... There's a logical explanation for this?? O_o Bye Marcello |
From: Roland S. <rsc...@hi...> - 2005-02-24 21:23:40
|
Marcello Maggioni wrote: >>Try running xscreensaver directly. > > With XSCREENSAVER alone it effectively runs without problems , but I > wonder why ... > > There's a logical explanation for this?? O_o IIRC the root window isn't double buffered, thus you can't use that in a useful way for 3D. Roland |
From: Adam J. <aj...@nw...> - 2005-02-25 15:47:24
|
On Thursday 24 February 2005 13:27, Marcello Maggioni wrote: > With XSCREENSAVER alone it effectively runs without problems , but I > wonder why ... > > There's a logical explanation for this?? O_o Yeah. KDE's screensaver module probably opens its own fullscreen window an= d=20 tells the screensaver to draw on that. Since the window is already created= =20 the screensaver can't change its visual, which means if the window was=20 created in a single buffer visual you're stuck. =2D ajax |
From: Dieter <Die...@ha...> - 2005-02-25 17:04:49
|
Am Freitag, 25. Februar 2005 16:47 schrieb Adam Jackson: > On Thursday 24 February 2005 13:27, Marcello Maggioni wrote: > > With XSCREENSAVER alone it effectively runs without problems , but I > > wonder why ... > > > > There's a logical explanation for this?? O_o > > Yeah. KDE's screensaver module probably opens its own fullscreen window > and tells the screensaver to draw on that. Since the window is already > created the screensaver can't change its visual, which means if the window > was created in a single buffer visual you're stuck. So someone should send a bug report to fix that before KDE 3.4 arise...;-) Greetings, Dieter |
From: Stephan K. <co...@kd...> - 2005-02-25 17:54:57
|
Am Friday 25 February 2005 18:03 schrieb Dieter N=FCtzel: > Am Freitag, 25. Februar 2005 16:47 schrieb Adam Jackson: > > On Thursday 24 February 2005 13:27, Marcello Maggioni wrote: > > > With XSCREENSAVER alone it effectively runs without problems , but = I > > > wonder why ... > > > > > > There's a logical explanation for this?? O_o > > > > Yeah. KDE's screensaver module probably opens its own fullscreen win= dow > > and tells the screensaver to draw on that. Since the window is alrea= dy > > created the screensaver can't change its visual, which means if the w= indow > > was created in a single buffer visual you're stuck. >=20 > So someone should send a bug report to fix that before KDE 3.4 arise...= ;-) How? We create a fullscreen window for all screen savers. Greetings, Stephan |
From: Adam J. <aj...@nw...> - 2005-02-25 18:06:16
|
On Friday 25 February 2005 12:54, Stephan Kulow wrote: > Am Friday 25 February 2005 18:03 schrieb Dieter N=FCtzel: > > Am Freitag, 25. Februar 2005 16:47 schrieb Adam Jackson: > > > On Thursday 24 February 2005 13:27, Marcello Maggioni wrote: > > > > With XSCREENSAVER alone it effectively runs without problems , but I > > > > wonder why ... > > > > > > > > There's a logical explanation for this?? O_o > > > > > > Yeah. KDE's screensaver module probably opens its own fullscreen > > > window and tells the screensaver to draw on that. Since the window is > > > already created the screensaver can't change its visual, which means = if > > > the window was created in a single buffer visual you're stuck. > > > > So someone should send a bug report to fix that before KDE 3.4 > > arise...;-) > > How? We create a fullscreen window for all screen savers. Run glxinfo and look at the output near the bottom: 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 =2D--------------------------------------------------------------------- 0x23 24 tc 0 24 0 r y . 8 8 8 0 0 0 0 0 0 0 0 0 0 None 0x24 24 tc 0 24 0 r . . 8 8 8 0 0 0 0 0 0 0 0 0 0 None 0x25 24 tc 0 24 0 r y . 8 8 8 0 0 24 8 0 0 0 0 0 0 None 0x26 24 tc 0 24 0 r . . 8 8 8 0 0 24 8 0 0 0 0 0 0 None 0x27 24 tc 0 24 0 r y . 8 8 8 0 0 0 0 16 16 16 0 0 0 Slow 0x28 24 tc 0 24 0 r . . 8 8 8 0 0 0 0 16 16 16 0 0 0 Slow 0x29 24 tc 0 24 0 r y . 8 8 8 0 0 24 8 16 16 16 0 0 0 Slow 0x2a 24 tc 0 24 0 r . . 8 8 8 0 0 24 8 16 16 16 0 0 0 Slow Note the 'db' column, indicating a double-buffered visual. By default X=20 windows are not created in double-buffered visuals. The way to find a=20 double-buffered visual is something like: int attribs[] =3D { GLX_DOUBLEBUFFER, /* ..., */ None }; XVisualInfo *vis =3D glXChooseVisual(dpy, DefaultScreen(dpy), attribs); There's also a way to do this within the DBE extension, which one or two of= =20 the xscreensaver hacks want, but I don't know it offhand. I expect Qt has = an=20 idiom for this as well. =2D ajax |
From: Vladimir D. <vo...@mi...> - 2005-02-25 18:11:33
|
On Fri, 25 Feb 2005, Stephan Kulow wrote: > Am Friday 25 February 2005 18:03 schrieb Dieter N=FCtzel: >> Am Freitag, 25. Februar 2005 16:47 schrieb Adam Jackson: >>> On Thursday 24 February 2005 13:27, Marcello Maggioni wrote: >>>> With XSCREENSAVER alone it effectively runs without problems , but I >>>> wonder why ... >>>> >>>> There's a logical explanation for this?? O_o >>> >>> Yeah. KDE's screensaver module probably opens its own fullscreen windo= w >>> and tells the screensaver to draw on that. Since the window is already >>> created the screensaver can't change its visual, which means if the win= dow >>> was created in a single buffer visual you're stuck. >> >> So someone should send a bug report to fix that before KDE 3.4 arise...;= -) > How? We create a fullscreen window for all screen savers. Wouldn't it be possible to create a double-buffered subwindow for those=20 that use GL ? A hack, admittedly... best Vladimir Dergachev > > Greetings, Stephan > |