[ Date Index ][
Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
On Tuesday 30 April 2002 8:32 am, Simon Waters wrote:
Keith Abraham wrote:Doing "init 3" is revealing. The log shows xdm shutting down. I always thought I was using kdm? So perhaps xdm isn't configured correctly. Under the old yast1 it was easy to switch from xdm to kdm but where is can you do this in yast2?By default SuSE used xdm, which starts the manager of choice, it may have changed. Since you can run these at the command line as root ( /etc/init.d/xdm start , /usr/init.d/xdm stop ) I suggest you figure out first what you want it to do at start up and if it works without errors. Also check various log files (boot, syslog, and the XF86 log - see /var/log). My slightly older version of SuSE doesn't appear to have a decent graphical run level editor, it has the KDE SysV-init, but it is never convinced it is being run as root (Running X as root goes against the basic instincts of most admins anyway). yast2 doesn't provide an editor for the run levels either on my box. So perhaps it is time to understand how your system starts and stops, it isn't rocket science, although annoyingly it isn't as well thought out as SySV Unix either despite the name of the editor. Basically the rc5.d directory links back to /etc/init.d, using numbers to specify the order of start up (or shutdown). "S" at the start of a link name means start.
Thanks guys for your helpful comments
I found out to switch to kdm in yast2 rebooted and found this in the
boot log:-
Apr 30 14:10:10 kalinux /etc/hotplug/net.agent[682]: No HW description found
... exiting
Apr 30 14:10:11 kalinux kdm[952]: Server for display :0 terminated
unexpectedly
Apr 30 14:10:14 kalinux last message repeated 3 times
Apr 30 14:10:14 kalinux kdm[952]: Display :0 is being disabled (restarting too
fast)
Apr 30 14:11:12 kalinux init: Switching to runlevel: 3
Apr 30 14:11:29 kalinux init: Switching to runlevel: 5
Apr 30 14:11:31 kalinux kdm[1332]: Server for display :0 terminated
unexpectedly
Apr 30 14:11:34 kalinux last message repeated 3 times
Apr 30 14:11:34 kalinux kdm[1332]: Display :0 is being disabled (restarting
too fast)
Apr 30 14:11:58 kalinux kernel: nvidia: loading NVIDIA NVdriver Kernel Module
1.0-2880 Tue Mar 26 08:12:38 PST 2002
Then went to kdm.log and found this:-
Data incomplete in file //XF86Config
at least one Device section is required
(EE) Problem parsing the config file
(EE) Error from XF86HandleConfigFile()
Fatal server error
no screens found.
On my system there are 2 XF86Config files:-
/etc/XF86Config
and
/etc/X11/XF86Config
The latter is the one generated by Sax2 and has the NVidia setup
The former config file does NOT contain the NVidia setup.
The "//" in Kdm.log seems to suggest that kdm is looking in /etc/XF86Config
whereas it should be looking in /etc/X11/XF86Config.
Does this sound plausible? And would it be worth copying the /etc/X11
config to /etc/?
By the way Yast2 does provide it's own runlevel editor on SuSE 8.0.
To this novice it looks OK..
And I MUST do some heavy reading about init.d etc.
In a perverse way I'm enjoying this!!
Keith
--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe.