How do I make a SUSE 10 box boot to the gui login screen? As configured, it boots to a login prompt, from which if I log in and run "startx" I get to the gui, but I want it to boot me to a login within the gui. How?

Thanks,

gtennant

edit /etc/inittab
change the line that says something like "id:3:initdefault:" to "id:5:initdefault:"

Thanks, spooon. Good counsel, however, my /etc/inittab was already set to runlevel 5. Please take a look at it below:

# # /etc/inittab # # Copyright (c) 1996-2002 SuSE Linux AG, Nuernberg, Germany. All rights reserved. # # Author: Florian La Roche, 1996 # Please send feedback to http://www.suse.de/feedback # # This is the main configuration file of /sbin/init, which # is executed by the kernel on startup. It describes what # scripts are used for the different run-levels. # # All scripts for runlevel changes are in /etc/init.d/. # # This file may be modified by SuSEconfig unless CHECK_INITTAB # in /etc/sysconfig/suseconfig is set to "no" # # The default runlevel is defined here id:5:initdefault: # First script to be executed, if not booting in emergency (-b) mode si::bootwait:/etc/init.d/boot # /etc/init.d/rc takes care of runlevel handling # # runlevel 0 is System halt (Do not use this for initdefault!) # runlevel 1 is Single user mode # runlevel 2 is Local multiuser without remote network (e.g. NFS) # runlevel 3 is Full multiuser with network # runlevel 4 is Not used # runlevel 5 is Full multiuser with network and xdm # runlevel 6 is System reboot (Do not use this for initdefault!) # l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 #l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # what to do in single-user mode ls:S:wait:/etc/init.d/rc S ~~:S:respawn:/sbin/sulogin # what to do when CTRL-ALT-DEL is pressed ca::ctrlaltdel:/sbin/shutdown -r -t 4 now # special keyboard request (Alt-UpArrow) # look into the kbd-0.90 docs for this kb::kbrequest:/bin/echo "Keyboard Request -- edit /etc/inittab to let this work." # what to do when power fails/returns pf:owerwait:/etc/init.d/powerfail start pn:owerfailnow:/etc/init.d/powerfail now #pn:owerfail:/etc/init.d/powerfail now po:owerokwait:/etc/init.d/powerfail stop # for ARGO UPS sh:12345owerfail:/sbin/shutdown -h now THE POWER IS FAILING # getty-programs for the normal runlevels # <id>:<runlevels>:<action>:<process> # The "id" field MUST be the same as the last # characters of the device (after "tty"). 1:2345:respawn:/sbin/mingetty --noclear tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 # #S0:12345:respawn:/sbin/agetty -L 9600 ttyS0 vt102 # # Note: Do not use tty7 in runlevel 3, this virtual line # is occupied by the programm xdm. # # This is for the package xdmsc, after installing and # and configuration you should remove the comment character # from the following line: #7:3:respawn:+/etc/init.d/rx tty7 # modem getty. # mo:235:respawn:/usr/sbin/mgetty -s 38400 modem # fax getty (hylafax) # mo:35:respawn:/usr/lib/fax/faxgetty /dev/modem # vbox (voice box) getty # I6:35:respawn:/usr/sbin/vboxgetty -d /dev/ttyI6 # I7:35:respawn:/usr/sbin/vboxgetty -d /dev/ttyI7 # end of /etc/inittab

Do you see anything amiss?

Thanks,

gtennant

Damn! I see that cutting and pasting my inittab into this posting is not ideal. Here's the salient line in my inittab:

# The default runlevel is defined here
id:5:initdefault:

Should do it, no?

As soon as I figure out an adequate way to include it in a more comprehensible manner, I'll push out my whole inittab. Ideas?

Thx,

gtennant

Do you get any error messages on the login screen (the text-based one), like failed services, etc?
What runlevel is indicated (Master Resource Control: runlevel x has been....reached)?

The last few lines of the startup log are:

Master Resource Control: runlevel 5 has been reached
Skipped services in runlevel 5: nfs acpid autofs splash smbfs
<notice>killproc: kill(2532,3)

Leads one to think that runlevel 5 should be okay. I question the skipping of splash service..........?

Thanks, abisko00

gtennant

What confuses me a little is that you get into the GUI with 'startx'. Otherwise I would have suggested to reconfigure your graphics card with 'sax2'.

Seems that xdm/kdm is not working properly. Have a look at /var/log/kdm.log for error messages.

abisk00!

You look to have something here... Log is as follows:

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: SuSE Linux [ELF] SuSE
Current Operating System: Linux linux 2.6.13-15.8-default #1 Tue Feb 7 11:07:24
UTC 2006 i686
Build Date: 07 October 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 18 06:53:52 2006
(==) Using config file: "/etc/X11/xorg.conf"
(EE) I810(0): No Video BIOS modes for chosen depth.
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

What to do?

Thanks,

gtennant

This confuses me even more. Please confirm that you get the x server running with startx.
Do you have two network cards on your system? Maybe you need to switch-off one in the bios, or configure both with sax2. To do the later, login as root, type 'init 3' to change in runlevel 3, then 'sax2 -p' to get all graphics cards listed. If you get onlöy one card listed, start the configuration with a simple 'sax2', test and save the settings. If more cards appear, start with e.g. 'sax2 -m 0=i810' (change "0" for the port at which the card is detected and "i810" for the driver).

I am pretty sure that this is caused by SuSE booting into the "Last boot" option.
IE it restores to the same level as you did last time you booted up.
In KDE Control Centre>Session Manager it shows an option: "Restore previous Session"
which is used as default.
Try to set it to: "Start with an empty session" and see if that will get you into the GUI right from the start.
then set it back to the old setting.