XGL (Part 6)

Message

mushroom blue · Post by **mushroom blue** » Fri Sep 08, 2006 11:11 am

hi there. having a problem compiling x11-drm (so I can, you know, use XGL).

* Building DRM in /var/tmp/portage/x11-drm-20060608/work/drm/linux-core...
/bin/sh: line 0: [: too many arguments
Makefile:290: *** CONFIG_X86_CMPXCHG needs to be enabled in the kernel.  Stop.
 * Portage could not build the DRM modules. If you see an ACCESS DENIED error,
 * this could mean that you were using an unsupported kernel build system. All
 * 2.4 kernels are supported, but only 2.6 kernels at least as new as 2.6.6
 * are supported.

!!! ERROR: x11-base/x11-drm-20060608 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  x11-drm-20060608.ebuild, line 111:   Called die_error
  x11-drm-20060608.ebuild, line 235:   Called die

!!! Unable to build DRM modules.
!!! If you need support, post the topmost build error, and the call stack if relevant.

checked my kernel .config, and CONFIG_X86_CMPXCHG is enabled in the kernel. in fact, it's enabled in every kernel that uses a processor type above 386 (I use K7). so either my kernel is lying, x11-drm is retarded, or I'm experiencing something neat and new.

output of glxinfo is kinda neat, too:

Code: Select all

name of display: :0.0
display: :0  screen: 0
direct rendering: No
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_copy_sub_buffer,
    GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample,
    GLX_SGIX_fbconfig, GLX_EXT_texture_from_pixmap
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R200 20060602 AGP 4x x86/MMX+/3DNow!+/SSE TCL
OpenGL version string: 1.2 (1.3 Mesa 6.5.1)
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
    GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
    GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
    GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_window_pos,
    GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_func_separate,
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
    GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord,
    GL_EXT_multi_draw_arrays, 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_edge_clamp,
    GL_EXT_texture_env_add, GL_EXT_texture_env_combine,
    GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, GL_EXT_texture_object,
    GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels,
    GL_ATI_texture_env_combine3, GL_ATI_texture_mirror_once,
    GL_ATIX_texture_env_combine3, GL_IBM_texture_mirrored_repeat,
    GL_INGR_blend_func_separate, GL_MESA_pack_invert, GL_MESA_ycbcr_texture,
    GL_NV_blend_square, GL_NV_texgen_reflection, GL_NV_texture_rectangle,
    GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp,
    GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays
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  y  .  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 24  0  0  0  0  0  0 0 None
0x25 24 tc  0 32  0 r  y  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x26 24 tc  0 32  0 r  y  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow
0x27 24 tc  0 32  0 r  .  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x28 24 tc  0 32  0 r  .  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None
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  .  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow
0x2b 24 dc  0 32  0 r  y  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x2c 24 dc  0 32  0 r  y  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None
0x2d 24 dc  0 32  0 r  y  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x2e 24 dc  0 32  0 r  y  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow
0x2f 24 dc  0 32  0 r  .  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x30 24 dc  0 32  0 r  .  .  8  8  8  8  0 24  0  0  0  0  0  0 0 None
0x31 24 dc  0 32  0 r  .  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x32 24 dc  0 32  0 r  .  .  8  8  8  8  0 24  0 16 16 16 16  0 0 Slow

normally the renderer string would say something about Mesa GLX Indirect. but nope. it's just waiting on the new x11-drm.

here's some versions:
media-libs/mesa-6.5.1_rc2-r20060831
x11-base/x11-drm-20060608
x11-base/xorg-server-1.1.1-r2
x11-drivers/xf86-video-ati-6.6.2

should also mention that I've tried kernels 2.6.15-r5 and 2.6.16-r13, and both have the same issue. re-did the config entirely, in order to make sure.

any ideas?

tranquilcool · Post by **tranquilcool** » Fri Sep 08, 2006 11:55 am

dpshark,
followed the debug step by step as you suggested and evrything works fine.
if i log into kdm it just doesn't work anymore.

DISPLAY=:1 dbus-launch csm

beats me .

Janax · Post by **Janax** » Fri Sep 08, 2006 12:39 pm

pem wrote:The "state" plugin does not appear under csm-0.4. Does somebody know if it has been removed?

It's still there for me - but instead of being labelled 'state', it's "Set Window Attribs by various criteria". Right after that, of course, is '[state]'.

tranquilcool · Post by **tranquilcool** » Fri Sep 08, 2006 1:13 pm

now with this compiz-decorator script;

compiz --replace dbus csm &
sleep 2
dbus-launch compiz dbus csm --replace &

it works until the kde icon starts flashing in the kde splash screen.

don't know what's the matter.

Bloot · Post by **Bloot** » Fri Sep 08, 2006 5:20 pm

tranquilcool wrote:now with this compiz-decorator script;

compiz --replace dbus csm &
sleep 2
dbus-launch compiz dbus csm --replace &

it works until the kde icon starts flashing in the kde splash screen.

don't know what's the matter.

Try this:

Code: Select all

dbus-launch compiz --replace dbus csm &
sleep 2
dbus-launch cgwd &

tranquilcool · Post by **tranquilcool** » Fri Sep 08, 2006 6:16 pm

have tried that but it doesn't work at all.
oin the third line if i write cgwd instead of compiz, it doesn't work either.
what beats me is why it works only with the script i mentioned until the kde icon starts flashing in the splash screen

nesl247 · Post by **nesl247** » Fri Sep 08, 2006 6:53 pm

For those of you wish issues compiling compiz-quinnstorm, csm, compiz-plugins, can you please make sure you have synced the overlay? I compiled these myself, so it would be odd for that to happen..

tranquilcool · Post by **tranquilcool** » Fri Sep 08, 2006 7:05 pm

finally works with the cvs versions and this script.

dbus-launch compiz --replace dbus csm &
sleep 2
dbus-launch cgwd &

thanks to everybody.

Specter64 · Post by **Specter64** » Fri Sep 08, 2006 9:13 pm

I have rev 433 and although the the errors for csm and compiz-quinnstorm-plugins have been fixed I'm getting this error for compiz-manager.

* Running eautoreconf in '/var/tmp/portage/compiz-manager-0.4' ...
* Running aclocal ... [ !! ]
* Failed Running aclocal !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/compiz-manager-0.4/temp/aclocal-19488.out

!!! ERROR: x11-misc/compiz-manager-0.4 failed.
Call stack:
ebuild.sh, line 1546: Called dyn_compile
ebuild.sh, line 937: Called src_compile
compiz-manager-0.4.ebuild, line 24: Called eautoreconf
autotools.eclass, line 65: Called eaclocal
autotools.eclass, line 102: Called autotools_run_tool 'aclocal'
autotools.eclass, line 193: Called die

and this is from /var/tmp/portage/compiz-manager-0.4/temp/aclocal-19488.out

***** aclocal *****

aclocal-1.9: `configure.ac' or `configure.in' is required

nesl247 · Post by **nesl247** » Fri Sep 08, 2006 9:19 pm

Sync it will work. I merely forgot S="${WORKDIR}/${PN}".

Frelon · Post by **Frelon** » Fri Sep 08, 2006 9:25 pm

sammartin says

A couple days ago when everyone seemed to be having upgrade problems I ran into one myself that doesn't seem to have come up. My Xgl server (started via gdm) now only shows on one display instead of two. The X log shows that twinview seems to be going properly, the second monitor is definitely on and not in standby, but the mouse is confined to one screen and there's no gdm login box. I'm guessing that's on the second display, wherever that output got sent.

Has anyone else had trouble with dual monitors in the past week or so? I should probably mention that at the same time as I upgraded the xgl package I also updated to xorg-7.1, so it'll be difficult to tell which caused the problem My only clue so far is an error at the bottom of my X log about the keyboard:
Code:
(EE) Error loading keymap /usr/share/X11/xkb/compiled/server-94.xkm

I have got the same.
First time, I launched Xgl like that :

Code: Select all

stan@hermes /usr/portage/local/layman/portage-xgl $ ./startxgl 1 gnome ati

And no problems, it works like a charm.
Next time I tried, same as you, with some logs qith "can't open display" (hard to see, I can't scroll).

The weird thing is if try on display:2, gnome runs (almost), but I have a bugbuddy report on a blank screen.
If I re-try on the same display, I have the pre-previous error, nothing start, just a grey screen with the uggly cross.

The same with display:3, etc....

Any idea ???

Zarathustra[H] · Post by **Zarathustra[H]** » Fri Sep 08, 2006 11:02 pm

I followed the official Wiki, and have some problems.

I couldn't build compiz-quinnstorm because of the following problem:

Code: Select all

!!! All ebuilds that could satisfy "x11-misc/compiz-manager" have been masked.
!!! One of the following masked packages is required to complete your request:
- x11-misc/compiz-manager-9999 (masked by: missing keyword)
- x11-misc/compiz-manager-0.4 (masked by: ~amd64 keyword)

...so instead I opted to go with the straight compiz.

It seems to start with many of the plugins working, but the menu plugin continually fails, and renders it almost useless:

Code: Select all

compiz: dlsym: /usr/lib/libmenu.so: undefined symbol: getCompPluginInfo
compiz: Failed to lookup getCompPluginInfo in 'libmenu.so' plugin
compiz: Couldn't load plugin 'menu'

Any ideas?

Frelon · Post by **Frelon** » Fri Sep 08, 2006 11:27 pm

maybe add this to /etc/portage/package.keywords :

Code: Select all

x11-wm/compiz-quinnstorm-9999 -*

and in package.unmask :

Code: Select all

=compiz-quinnstorm-9999

Specter64 · Post by **Specter64** » Sat Sep 09, 2006 2:50 am

The official wiki seems to be a bit out of date on what packages are being used...
If you add
>=x11-misc/compiz-manager-0.4 ~amd64
to package.keywords it will work fine (there will probably be others too)
the manager provides an icon in your system tray that allows quick access to compiz settings manager and compiz theme manager
also it allows you to switch back to your normal window manager (though it doesnt turn direct rendering back on from what i can tell)

And although the wiki says to use gconf-editor or gset-compiz the settings manager for compiz-quinnstorm (i dont know about regular compiz) is now csm
Theres is a script to launch compiz-quinnstorm is provide too and its called compiz-start

grimz · Post by **grimz** » Sat Sep 09, 2006 3:17 am

eep

Code: Select all

leigh@gardiner_desk ~/.kde/Autostart $ sudo layman -s portage-xgl
* Running command "/usr/bin/svn update /usr/portage/local/layman/portage-xgl"...svn: PROPFIND request failed on '/xgl-coffee/trunk'
svn: PROPFIND of '/xgl-coffee/trunk': could not connect to server (http://svn.xgl-coffee.org)
* Successfully synchronized overlay "portage-xgl".

Looks like it's down at the moment...

strc · Post by **strc** » Sat Sep 09, 2006 3:36 am

grimz wrote: Looks like it's down at the moment...

Same here... and coffeebuzz's forums too. I wonder if we should tell coffeebuzz, or if he already knows...

Headrush · Post by **Headrush** » Sat Sep 09, 2006 4:10 am

strc wrote:
grimz wrote: Looks like it's down at the moment...
Same here... and coffeebuzz's forums too. I wonder if we should tell coffeebuzz, or if he already knows...

Still down today. Figures the night I finally have free time to try XGL again.

Anyone able to provide a tarball of the overlay from their machine?

Roguelazer · Post by **Roguelazer** » Sat Sep 09, 2006 4:13 am

Unfortunately, the overlay was broken for a while (.48 assumed that the mesa/ source was in the same directory as the compiz/ source), and then there was a post on the xgl-coffee forums that the problem had been fixed and we all needed to svn up, then the forums and the svn server went down. So a tarball would be rather unhelpful.

Roguelazer · Post by **Roguelazer** » Sat Sep 09, 2006 4:56 am

'tis back up

May-C · Post by **May-C** » Sat Sep 09, 2006 11:14 am

hello,

i have a problem and don't find any solution...
actually xgl is just running fine... at least with the account of my wife or as root.
with my account it doesn't work... so i thought it can't be a big problem.
i deleted everything like .compiz .gconf .... in my home directory but still no go!
anybody who can give me an advice to solve my problem?

Janax · Post by **Janax** » Sat Sep 09, 2006 2:29 pm

May-C wrote:hello,

i have a problem and don't find any solution...
actually xgl is just running fine... at least with the account of my wife or as root.
with my account it doesn't work... so i thought it can't be a big problem.
i deleted everything like .compiz .gconf .... in my home directory but still no go!
anybody who can give me an advice to solve my problem?

Just taking a wild guess, but are you a member of the 'video' group?

May-C · Post by **May-C** » Sat Sep 09, 2006 2:32 pm

yes:

groups: wheel audio cdrom video games usb users portage plugdev bluetooth

Where are the settings stored for compiz?

I have to mention it did work a few days ago... so i have no idea, what's causing this effect.
Oh and by the way there I noticed an error message:
No managable screens found on ...

May-C · Post by **May-C** » Sat Sep 09, 2006 6:16 pm

so tracked the problem a little down:

the problem is in .kde/share/config/*

m4chine · Post by **m4chine** » Sat Sep 09, 2006 7:17 pm

I can't seem to emerge xgl or digest it, any suggestions?

Code: Select all

 emerge -v =x11-base/xgl-0.0.1_pre20060714-r1
Calculating dependencies... done!
>>> Emerging (1 of 1) x11-base/xgl-0.0.1_pre20060714-r1 to /
>>> checking ebuild checksums
!!! Digest verification failed:
!!! /usr/portage/local/layman/portage-xgl/x11-base/xgl/xgl-0.0.1_pre20060714.ebuild
!!! Reason: Filesize does not match recorded size
!!! Got: 2242
!!! Expected: 2453

Code: Select all

ebuild digest xgl-0.0.1_pre20060714-r1.ebuild
'/usr/portage/local/layman/portage-xgl/x11-base/xgl/digest' does not exist.
mkdir digest
ebuild digest xgl-0.0.1_pre20060714-r1.ebuild
!!! x11-base does not follow correct package syntax.

May-C · Post by **May-C** » Sat Sep 09, 2006 7:31 pm

found the solution!!!

If you use kde there is an option, something like don't show symbols on desktop.
DON'T USE THIS OPTION!!!

I spent hours now to find out that this option is incompatible with compiz...