All, There are a couple of tweaks you can make to have kdm/kde3 boot like a rocket ship. kde-kdebase does not include a kdm3.service file. This causes systemd to flail around looking for one. I have one from the TDE builds I did for Arch that I installed on 42.3 -- works perfect! $ cat /usr/lib/systemd/system/kdm3.service [Unit] Description=KDE3 Display Manager After=systemd-user-sessions.service [Service] ExecStart=/opt/kde3/bin/kdm [Install] Alias=display-manager.service Just create the file and save it as /usr/lib/systemd/system/kdm3.service. Then do # systemctl daemon reload (to have systemd re-read its services files) Then just enable the service: # systemctl enable kdm3 That's it, the next boot, systemd will enable kdm3.service and the 90 sec timeout looking for a display manager is gone, e.g. 17:29 wizard:~/cnf/kde> sc -l status kdm3 ● kdm3.service - KDE3 Display Manager Loaded: loaded (/usr/lib/systemd/system/kdm3.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2018-04-21 17:00:28 CDT; 29min ago Main PID: 1351 (kdm) Tasks: 2 (limit: 512) CGroup: /system.slice/kdm3.service ├─1351 /opt/kde3/bin/kdm └─1451 /usr/bin/Xorg -br -nolisten tcp :0 vt8 -auth /var/lib/xdm/authdir/authfiles/A:0-5uunkE Apr 21 17:00:28 wizard systemd[1]: Started KDE3 Display Manager. === We need to add this to the kdebase package === Next, wicked has an incredibly long global timeout of 30 seconds set (it doesn't require any, but I set it at 1 second just to be on the safe side). This doesn't effect all systems, but caused my system with Intel eth0 to hang (even though no cable is plugged in) for the full 30 sec timeout causing my boot time to balloon to nearly 1 minute. You fix the problem by editing /etc/sysconfig/network/config and setting: WAIT_FOR_INTERFACES="1" After reducing the wait time from 30 to 1 second, I can now boot from OFF/cold to full KDE3 (with my custom kdm moodin splash theme) in 12.1 seconds, e.g. $ systemd-analyze Startup finished in 5.455s (kernel) + 3.466s (initrd) + 3.193s (userspace) = 12.115s That is the entire boot to my killer login in a total of 12.115 seconds. That's the way Linux with SSD should work. I can even drop another second by leaving WAIT_FOR_INTERFACES="" (empty). Give it a try if you have a boot delay based on wicked. To see all your services and their boot activation times, systemd plot with create a handy .svg graphic showing all service activation and the time it takes, just use: $ systemd-analyze plot > yourfile.svg The just look at it in a browser to determine if you have any delays you can fix -- and exactly what they are. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org