Hallo I had the same problem here, but after some tracking, I found that the problem seems to be on the init.d script "earlykdm", if you start this script, the system will "hang" somehow. What I did to solve this was the following: 1.- Backup scripts "earlykdm" and "xdm" (found under /etc/init.d) 2.- Edit the script "xdm" removing "earlykdm" from: # Should-Start: ypbind $syslog gpm firstboot kbd resmgr earlykdm so now it will look like: # Should-Start: ypbind $syslog gpm firstboot kbd resmgr 3.- Open YaST on the shell and go to System->System Services (Runlevel) Once open, look for service "earlykdm" and disable it, save changes and exit YaST 4.- Now reboot your laptop and the system should start again Hope this helps you as it helped me, jeje Azael -- -- El mundo apesta y vosotros apestais tambien --

On Wednesday 01 March 2006 00:23, Linux Juggler wrote:

hi : i have update kde using yast in my labtop , but after updating the system stop at some point when it boot .

now i can start suse using the filesafe mode ...

any idea ?

Hi LJ, There have been quite a few threads recently in SLE on this exact problem... apparently there was a mixup causing a 10.1 component to be inadvertently installed during the update. From one of those threads:

"... It has to do with the file /etc/init.d/earlykdm, installed by the new kdebase3 rpms, build -27. You can edit that file with the changes I'll indicate below to put things right using the -27 build rpms.

Replace this:

if test -z "$DISPLAYMANAGER_AUTOLOGIN"; then /sbin/preload /etc/preload.d/kdm else /usr/bin/ionice -n2 /sbin/preload /etc/preload.d/kdm.auto /usr/bin/ionice -n6 /sbin/preload /etc/preload.d/kde & echo $! > /var/run/preload-session.pid fi

With this:

if test -z "$DISPLAYMANAGER_AUTOLOGIN"; then /sbin/preload < /var/cache/preload/kdm.preload else /usr/bin/ionice -n2 /sbin/preload < /var/cache/preload/kdm.auto.preload /usr/bin/ionice -n6 /sbin/preload < /var/cache/preload/kde.preload & echo $! > /var/run/preload-session.pid fi

And later, in the same thread:

At the Loader (Grub) screen, press F2 to get options. Type "init 3", at the prompt. That will boot the computer to the tty1 screen safely. Type in your root name and password, then type "rcxdm start" at the prompt. That will take you into KDE once again. From there, correct the file [as] mentioned [above] and your booting problems should go away.

hth & regards, Carl