You are not logged in.
Pages: 1
EDIT: Sorry - I should have read a bit further. It wasn't on the Arch wiki, but following the link through to the Gentoo wiki told me where to put the GDMXserverTimeout option now that gdm.conf isn't used anymore.
Add/modify the following commands to the [daemon] section of /usr/share/gdm/defaults.conf. The line:
GdmXserverTimeout=30
That's fixed it, and I now have XGL & Beryl running with GDM.
Fishonadish
Last edited by fishonadish (2007-04-03 11:13:56)
Offline
From reading various forums I've got a setup that works quite nicely and thought I'd add the steps to the wiki page on xgl. However, most of this has been blindly following suggestions without much understanding of what's happening, so I thought I'd better check that this setup isn't specific to ATI cards or my system etc. before making a mess of the wiki page.
Anyway, any comments on the points below would be appreciated.
Here's what I've got in /opt/gnome/etc/gdm/custom.conf:
. . .
[servers]
0=xgl
. . .
[server-Xgl]
name=Xgl
command=/usr/bin/Xgl :0 -fullscreen -ac -xorgAc -accel xv:fbo -accel glx:pbuffer
flexible=true
chooser=false
handled=true
priority=0
. . .(1) Setting GdmXserverTimeout=30 in the gdm defaults seems to be imperative to give xgl time to start. I presume it's always needed?
(2)I seem to recall reading some reason why it was necesssary for xgl to be on display:1 instead of 0 for ATI cards. Is this still necessary with some graphics cards or setups? The above is working for me, anyway.
(3)Adding -xorgAc allows one to run OpenGL games/apps with 'DISPLAY=:93 game', which is useful. Are there any caveats to this?
Provided these settings are all safe enough, it'd save people hunting to stick them in the wiki. Any corrections/thoughts?
Thanks.
Fishonadish
Offline
Pages: 1