What is the output of:

systemctl status dhcpcd@eth0.service

journal shows systemd timing out on that service (that would explain the delay, timeout usually take 90 - 120 seconds).

    Do you have any welcome screen enabled? Try disabling from preferences, boot, welcome screen, none

    • demm replied to this.

      jomada This is before sddm or X loading, Systemd boot messages are still displaying, so disabling KSplash will not stop this hang (ofc will speed up boot proces after sddm).

        demm
        Hi demm, posted below: The hang is the same if I have no eth cable. I will remove the ethernet cable and use just wifi, but it take also very long

        systemctl status dhcpcd@eth0.service
        ● dhcpcd@eth0.service - dhcpcd on eth0
        Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled; vendor preset: enabled)
        Active: inactive (dead)

        Oct 28 08:55:33 acer1410 systemd[1]: Dependency failed for dhcpcd on eth0.
        Oct 28 08:55:33 acer1410 systemd[1]: dhcpcd@eth0.service: Job dhcpcd@eth0.service/start failed with result 'dependency'.

          Demm, I removed the eth cable and did a boot on wifi. If it will help, everything is the same (long period of black screen), but I noticed as the desktop was loading the wifi icon in the sidebar was spinning. Does this mean the driver only load when the desktop load up?

          christo    systemctl status dhcpcd@wlp2s0.service
          ● dhcpcd@wlp2s0.service - dhcpcd on wlp2s0
          Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled; vendor preset: enabled)
          Active: inactive (dead)

          Issue is:

          Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled

          for eth0. It is missing some dependency on your system, plus default in KaOS is not to have it enabled. Any reason why this service is enabled (changed some network settings?) What is the output if you manually start it, does it list the missing depend?

          sudo systemctl start dhcpcd@eth0.service

            demm Normally I just use wifi, but here is the output

            sudo systemctl start dhcpcd@eth0.service
Password: 
A dependency job for dhcpcd@eth0.service failed. See 'journalctl -xe' for details.
 christo  ~  ^C
 christo  ~  journalctl -xe
Oct 28 15:33:50 acer1410 systemd[1]: Dependency failed for dhcpcd on eth0.
-- Subject: A start job for unit dhcpcd@eth0.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit dhcpcd@eth0.service has finished with a failure.
-- 
-- The job identifier is 953 and the job result is dependency.
Oct 28 15:33:50 acer1410 systemd[1]: dhcpcd@eth0.service: Job dhcpcd@eth0.service/start failed with result 'dependency'.
Oct 28 15:33:50 acer1410 systemd[1]: sys-subsystem-net-devices-eth0.device: Job sys-subsystem-net-devices-eth0.device/start fail>
Oct 28 15:33:50 acer1410 sudo[2414]: pam_unix(sudo:session): session closed for user root
Oct 28 15:33:52 acer1410 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.

              @Christo61 default in KaOS is not to have it enabled. Any reason why this service is enabled (changed some network settings?)

              No answer for that one? Tried disabling that service? sudo systemctl disable dhcpcd@eth0.service

              Note:
              For cli output enclose your paste with 3 backticks ```, done for you this time, makes the output readable.

                demm
                I disabled the service as per your advice and rebooted twice. Once with ethernet and once ethernet cable removed, just wifi. It is still the same for eth and wifi, but feels a little bit faster - I did not time it. Actually I don't mess much with settings, so I don't know how it became "enabled", and the system is pretty much how I installed it a year ago. Everything was fine until version 242, when the 3-4 min blackscreen came along. Otherwize I enjoy Kaos alot
                Do you know how to find the missing dependency so I can install it?
                Thanks

                  demm
                  I have searched other forums as well for this blackscreen issue. Mostly it was multiple Swap files or Nvdia drivers that caused the same blackscreen. Some post I followed up on was this line of etc/default/grub
                  GRUB_CMDLINE_LINUX_DEFAULT. My one is completely to all I have seen. I will post mine and can you check if it is normal

                  GRUB_DISTRIBUTOR="KaOS"
                  GRUB_DISABLE_RECOVERY=true
                  GRUB_TERMINAL_INPUT=console
                  GRUB_DEFAULT=saved
                  GRUB_TIMEOUT=1
                  GRUB_PRELOAD_MODULES="part_gpt part_msdos"
                  GRUB_CMDLINE_LINUX=""
                  GRUB_GFXPAYLOAD_LINUX=keep
                  GRUB_DISABLE_OS_PROBER=true
                  GRUB_THEME="/usr/share/grub/themes/midna/theme.txt"
                  GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=e0e713a1-40d0-4056-b39e-cc644cec2d31 quiet systemd.show_status=0 "
                  GRUB_GFXMODE=1024x768

                  Thanks

                    This has nothing to do with systemd version (and not really systemd either), you did not update for a year (which in itself is not supported in KaOS), once you did update, you replaced/updated 830 packages one of those was systemd, so makes no sense to state

                    Everything was fine until version 242

                    Not a dependency to install either, your network names have changed, thus eth0 is failing, since it looks like it is no longer available, probably inxi -N or hwinfo --network will show the new name.

                    @demm

                    Network:   Device-1: Qualcomm Atheros AR8131 Gigabit Ethernet driver: atl1c 
                 Device-2: Intel WiFi Link 5100 driver: iwlwifi ```

                    I disabled eth0 and is gone now. Sorry for the Arch wiki and I removed the package intel-ucode anyway. Since eth0 is gone the system boot from the pressing of the button to the DE loaded 1 min 27s. This is a massive improvement to what it was. I can live with it like this, so I say it is solved

                    Thank You for your help

                    Now try and disable KSplash (systemsettings > startup & shutdown > splash screen, set to None), that should save another 30-40 seconds on this (older) hardware.

                    PS:
                    For code enclose with 3 backticks, so beginning and end, done for you this time.

                    demm, yes I did that and now down to 1m 3 sec

                    Thank You very much and problem is Solved