On 2012/01/04 00:37 (GMT-0500) Bob S composed:
service smartd done done Master Resource Control: Running /etc/init.d/after.local doneMaster Resource Control: runlevel 5 has been reached Skipped services in runlevel 5: cpufreq killproc: kill(398,3) Boot logging started on /dev/tty1(/dev/console) at Tue Jan 3 23:55:23 2012 Master Resource Control: previous runlevel: 5, switching to runlevel: 3 Master Resource Control: Running /etc/init.d/before.local done
service xdm stop Shutting down service kdm killproc: kill(2443,15) done service xdm done Master Resource Control: Running /etc/init.d/after.local doneMaster Resource Control: runlevel 3 has been reached killproc: kill(2790,3) Boot logging started on /dev/tty1(/dev/console) at Tue Jan 3 23:55:45 2012 Master Resource Control: previous runlevel: 3, switching to runlevel: 5 Master Resource Control: Running /etc/init.d/before.local done
service xdm start Starting service kdm startproc: execve (/opt/kde3/bin/kdm) [ /opt/kde3/bin/kdm ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=ext3 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 INIT_VERSION=sysvinit-2.89 KDEROOTHOME=/root/.kdm REDIRECT=/dev/tty1 COLUMNS=80 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=normal RUNLEVEL=5 PWD=/ SPLASHCFG= LANG=en_US.UTF-8 PREVLEVEL=3 LINES=25 QT_SYSTEM_DIR=/usr/share/desktop-data HOME=/ SHLVL=2 XCURSOR_THEME=DMZ WINDOWMANAGER=/opt/kde3/bin/startkde splash=verbose SPLASH=no ROOTFS_BLKDEV=/dev/root _=/sbin/startproc DAEMON=/opt/kde3/bin/kdm ] done service xdm done Master Resource Control: Running /etc/init.d/after.local doneMaster Resource Control: runlevel 5 has been reached killproc: kill(2829,3)
Above section shows it's going into runlevel 5, then back to runlevel 3, and again into runlevel 5. Obviously it isn't finishing the second time, but there shouldn't be a second time and I have no idea why this is happening. The two 12.1 systems and 11.4 system I checked here only go into it once, as I'm sure is the way it's supposed to be. Until then try making a change in /etc/sysconfing/boot. Find RUN_PARALLEL="yes" and change the "yes" to "no", and reboot to see if it avoids the problem. It will slow boot slightly (so slight you probably won't notice), but I'm sure you'd rather wait a few seconds extra instead of suffering what you must now. If it doesn't help, revert the change, and try the other suggestions in my previous thread reply. Since you're using KDM3, follow-up may soon need to be refocused onto that mailing list, unless you want (which I suspect too much bother for you) to try switching temporarily to KDM4 or GDM as a diagnostic. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org