On Saturday 23 March 2002 12:09, Jon Clausen wrote:
Now there's a thought... "go check if the BIOS has options like that..."
-which, indeed, it does... I changed that, and now this part of the setup works The Matrox card's in there but dormant, as it should be. :) Next I went and tried going to rl3, and started twm thusly: startx twm works, and from there opening an xterm and starting RtCW works nicely too (maybe even a smidgen faster and more responsive, due to the lack of kde2-resource-hogging in the background?). I wanted to test the 'gaming' situation first, because it's the closest to the present config, so none of the dual-head stuff, just yet. Next I went to try out the startx -xf86config option. (I should mention that at present XF86Config is a symlink pointing to XF86Config-single, a remnant from last weekend) So i did (still from rl3): startx -xf86config /etc/X11/XF86Config-single - in various forms with and without specifying twm as the WM. This gets me tons of: /etc/X11/XF86Config-single: Section: command not found /etc/X11/XF86Config-single: FontPath: command not found /etc/X11/XF86Config-single: FontPath: command not found /etc/X11/XF86Config-single: FontPath: command not found /etc/X11/XF86Config-single: ModulePath: command not found /etc/X11/XF86Config-single: RgbPath: command not found /etc/X11/XF86Config-single: EndSection: command not found /etc/X11/XF86Config-single: Section: command not found /etc/X11/XF86Config-single: Option: command not found /etc/X11/XF86Config-single: EndSection: command not found -which looks to me as if XF86Config-single is attempted *executed* (?) What am I misunderstanding here? Does not the -xf86config option tell startx to use <file> as the config, instead of the default ? (/etc/X11/XF86Config) Also from the top of the err file: (==) Log file: "/var/log/XFree86.0.log", Time: Sat Mar 23 13:26:52 2002 (==) Using config file: "/etc/X11/XF86Config" -which certainly would suggest that indeed XF86Config-single is not being used (?!) I have the impression, that once I get this part to work, then setting up dual-head for the 'work-config' will be basically a matter of retracing my steps from last weekend, so at this point it would seem that I just need to get X to use the other XF86Config... TIA Jon