Being very satisfied with SUSE 11.0 I decided yesterday to make the switch to the latest and shiniest. As a regular reader of this forum I decided to follow the general advice to do a fresh install of 11.1. As I had little problems with the install of SUSE in the past, I started without headaches. After a very clean install SUSE gave me a hard landing on the command prompt. No beautiful KDE plasma screen but a text mode invitation to log in. After logging in and typing startx the xserver starts. After reboot of the computer I find myself back at the command prompt. Does anyone knows how to start the xserver automatically.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Set the default runlevel to ‘5’ instead of 3. With that in mind you can
use the ‘runlevel’ command to see what your current runlevel is. It
will probably say something like ‘N 3’ which means you just booted and
now you are at runlevel 3. What you need it to say, after you boot, is
‘N 5’. Yast: System: System Services (Runlevel): Advanced something or
another. Set the default runlevel to 5. You can also search for ‘id’
in /etc/inittab and change the ‘3’ there to ‘5’ assuming it is set to ‘3’:
grep ‘id’ /etc/inittab
Good luck.
cloggers wrote:
> Being very satisfied with SUSE 11.0 I decided yesterday to make the
> switch to the latest and shiniest. As a regular reader of this forum I
> decided to follow the general advice to do a fresh install of 11.1. As I
> had little problems with the install of SUSE in the past, I started
> without headaches. After a very clean install SUSE gave me a hard
> landing on the command prompt. No beautiful KDE plasma screen but a text
> mode invitation to log in. After logging in and typing startx the
> xserver starts. After reboot of the computer I find myself back at the
> command prompt. Does anyone knows how to start the xserver
> automatically.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJUA2K3s42bA80+9kRAjhrAJ9T3nkr8SLW2HrMKjRDoMmrIJHuTgCdEI6s
FCLvaZgQdToE2z07MzgGfuo=
=rd+g
-----END PGP SIGNATURE-----
I changed the default runlevel from 3 to 5 in etc/inittab, rebooted and landed on the command prompt again.
A closer look at /var/log/messages showed some kdm errors.
Dec 22 23:32:12 linux-bg8r kdm[2320]: X server for display :0 cannot be started, session disabled
Dec 23 11:27:02 linux-bg8r kdm_config[2335]: Multiple occurrences of key ‘Language’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Dec 23 11:27:02 linux-bg8r kdm_config[2335]: Multiple occurrences of key ‘ShowUsers’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Dec 23 11:27:02 linux-bg8r kdm_config[2335]: Multiple occurrences of key ‘Theme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Dec 23 11:27:02 linux-bg8r kdm_config[2335]: Multiple occurrences of key ‘UseBackground’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Dec 23 11:27:02 linux-bg8r kdm_config[2335]: Multiple occurrences of key ‘UseTheme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Dec 23 11:27:02 linux-bg8r kdm_config[2335]: Multiple occurrences of key ‘AllowShutdown’ in section [X-:-Core] of /usr/share/kde4/config/kdm/kdmrc
Dec 23 11:27:02 linux-bg8r kdm_config[2335]: Multiple occurrences of key ‘AutoLoginEnable’ in section [X-:0-Core] of /usr/share/kde4/config/kdm/kdmrc
Dec 23 11:27:02 linux-bg8r kdm_config[2335]: Multiple occurrences of key ‘AutoLoginUser’ in section [X-:0-Core] of /usr/share/kde4/config/kdm/kdmrc
Dec 23 11:27:19 linux-bg8r kdm[2334]: X server startup timeout, terminating
So still looking for answers.
Just had the same problem after the upgrade to 11.1, I have figured out that it is because the computer is a bit old (PIII processor) and there were a lot of other things loaing at the same time.
Worked ok if you use startx at the command line, so it was not a kdm error.
I have fixed the problem by editing the file
/etc/init.d/.depend.start
and adding a lot of the other modules to the dependency list for xdm: thus it starts this last with no other things happening.
I hope this helps!
I had the same problem (in another thread) but Axeia cured it for me!
The problem was that kgreeter-plugins was not installed. Install it through yast, although, I guess you could zypper it in. Once this was installed, I got the greeter screen where I picked my user (I only had one and I couldn’t stop the autologin since greeter was missing) and, more importantly, I picked the session to start with kde 4.2!
When I first looked at the session setting in the greeter, nothing was chosen. Hope this solves your problem as easy as it did mine.
wbhenshaw’s diagnosis and solution worked for me. I too have an old laptop that’s a bit slow. xdm would not start automatically at boot but startx worked fine from the command line after login.
I edited /etc/init.d/.depend.start as suggested.
xdm: nfs syslog kbd earlyxdm acpid ntp nscd single smartd smb xinetd
I suspect that there’s a real dependency there but I don’t have the knowledge, time or the patience to work out exactly which one is correct.
The problem with editing the /etc/init.d/.depend.start file directly is that it keeps getting overwritten by insserv.
In order to deal with this, it is also necessary to edit the INIT INFO block in /etc/init.d/xdm.
I have made the following change to /etc/init.d/.depend.start:
xdm: nfs syslog kbd earlyxdm acpid vsftpd cups single cron smb xinetd
I have made the following change to /etc/init.d/xdm:
Should-Start: ypbind $syslog gpm firstboot kbd resmgr earlyxdm winbind acpid vsftpd cups single cron smb xinetd
The second change ensures that the first one stays in place when .depend.start is regenerated.