New Install Boot Times

Hi All, I’ve recently bought a new laptop (X13 gen1 AMD Ryzen Pro 3) and installed EOS onto it but I am facing an issue, not a show stopper but something I want to understand and try to fix. My current boot times are as follows:

Startup finished in 8.976s (firmware) + 1.820s (loader) + 6.859s (kernel) + 28.197s (initrd) + 7.394s (userspace) = 53.249s 
graphical.target reached after 7.394s in userspace.

As per the image below, I don’t understand why the system is running stopping those Daemons and running the job at the very end. This is slowing the boot time down.

I’ve run systemd-analyze blame and it shows the following:

29.241s sys-devices-pci0000:00-0000:00:02.2-0000:02:00.1-0000:02:00.1:0-0000:02:00.1:0.0-tty-ttyS4.device
29.241s dev-ttyS4.device
29.211s sys-devices-platform-STM0125:00-tpmrm-tpmrm0.device
29.211s dev-tpmrm0.device
29.205s dev-ttyS5.device
29.205s sys-devices-pci0000:00-0000:00:02.2-0000:02:00.2-0000:02:00.2:0-0000:02:00.2:0.0-tty-ttyS5.device
29.204s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
29.204s dev-ttyS1.device
29.184s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
29.184s dev-ttyS0.device
29.181s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
29.181s dev-ttyS2.device
29.178s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
29.178s dev-ttyS3.device
29.171s sys-module-fuse.device
29.164s sys-module-configfs.device
29.057s dev-disk-by\x2ddiskseq-1.device
29.057s dev-nvme0n1.device
29.057s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075212ebc70d7.device
29.057s sys-devices-pci0000:00-0000:00:02.1-0000:01:00.0-nvme-nvme0-nvme0n1.device
29.057s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
29.057s dev-disk-by\x2did-nvme\x2dMicron_MTFDHBA256TDV_21172EBC70D7.device
29.057s dev-disk-by\x2did-nvme\x2dMicron_MTFDHBA256TDV_21172EBC70D7_1.device
29.046s dev-disk-by\x2duuid-5dfd25c5\x2dfb3d\x2d4b91\x2db0ba\x2d217d31bc4e04.device
29.046s dev-disk-by\x2did-nvme\x2dMicron_MTFDHBA256TDV_21172EBC70D7_1\x2dpart2.device
29.046s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart2.device
29.046s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075212ebc70d7\x2dpart2.device
29.046s dev-disk-by\x2dpartuuid-7a951ec1\x2d3c76\x2d4428\x2d91dd\x2d1dbc61db21ff.device
29.046s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-endeavouros.device
29.046s dev-disk-by\x2did-nvme\x2dMicron_MTFDHBA256TDV_21172EBC70D7\x2dpart2.device
29.046s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-endeavouros.device
29.046s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-5dfd25c5\x2dfb3d\x2d4b91\x2db0ba\x2d2>
29.046s dev-disk-by\x2dlabel-endeavouros.device
29.046s dev-disk-by\x2dpartlabel-endeavouros.device
29.046s sys-devices-pci0000:00-0000:00:02.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
29.046s dev-nvme0n1p2.device
29.046s dev-disk-by\x2ddiskseq-1\x2dpart2.device
29.046s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
29.046s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-7a951ec1\x2d3c76\x2d4428\x2d91dd\>
29.040s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
29.040s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-5db4c19f\x2d3dd5\x2d4502\x2d94b7\>
29.040s dev-disk-by\x2duuid-FCBB\x2d7AF5.device
29.040s dev-disk-by\x2did-nvme\x2deui.000000000000000100a075212ebc70d7\x2dpart1.device
29.040s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-FCBB\x2d7AF5.device
29.040s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-EFI.device
29.039s dev-disk-by\x2ddiskseq-1\x2dpart1.device
29.039s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
29.039s dev-nvme0n1p1.device
29.039s dev-disk-by\x2dpartlabel-EFI.device
29.039s sys-devices-pci0000:00-0000:00:02.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
29.039s dev-disk-by\x2did-nvme\x2dMicron_MTFDHBA256TDV_21172EBC70D7_1\x2dpart1.device
29.039s dev-disk-by\x2dpartuuid-5db4c19f\x2d3dd5\x2d4502\x2d94b7\x2d89da77e5f471.device
29.039s dev-disk-by\x2did-nvme\x2dMicron_MTFDHBA256TDV_21172EBC70D7\x2dpart1.device

For journalctl -p 3 -xb i get the following output:

lip 03 13:58:30 arch-nomad kernel: xhci_hcd 0000:05:00.0: can't setup: -110
lip 03 13:58:30 arch-nomad kernel: xhci_hcd 0000:05:00.0: init 0000:05:00.0 fail, -110
lip 03 13:58:30 arch-nomad kernel: xhci_hcd 0000:05:00.0: probe with driver xhci_hcd failed with error -110
lip 03 13:58:32 arch-nomad kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ in>
lip 03 13:58:32 arch-nomad kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: Error >
lip 03 13:58:38 arch-nomad kernel: amdgpu 0000:06:00.0: amdgpu: Secure display: Generic Failure.
lip 03 13:58:38 arch-nomad kernel: amdgpu 0000:06:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
lip 03 13:58:38 arch-nomad gdm[641]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
lip 03 13:58:41 arch-nomad wpa_supplicant[638]: bgscan simple: Failed to enable signal strength monitoring
lip 03 13:58:53 arch-nomad gdm-password][1150]: gkr-pam: unable to locate daemon control file
lip 03 13:58:54 arch-nomad gdm[641]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
lip 03 13:58:54 arch-nomad systemd[1164]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 152 and the job result is failed.
lip 03 13:58:54 arch-nomad systemd[1164]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 148 and the job result is failed.
lip 03 13:58:57 arch-nomad gdm[641]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
lines 1-28/28 (END)

I am trying to understand how to fix this error please. On my desktop boot times are great but on the laptop not show much.

The other issue I have with made me stop using arch was that this error would make the system hang:

lip 03 13:58:38 arch-nomad kernel: amdgpu 0000:06:00.0: amdgpu: Secure display: Generic Failure.
lip 03 13:58:38 arch-nomad kernel: amdgpu 0000:06:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0

I tried adding AMDGPU to the modules in mkinitcpio.conf but that didn’t fix the error above in a different install. I keen to learn and understand how to fix these issues to get a better boot time but more so understand and have new knowledge.

Please let me know if you need any other information and thank you for the help in advance.

Can you run systemd-analyze critical-chain

As a side note, you should use code blocks instead of quote blocks.

As it may be hardware related, I suggest ensuring your BIOS is up-to-date, in case it’s something simple like that. Just starting with a clean slate and such.

You might also consider disabling any peripherals in the BIOS, you won’t need. For example, some might disable SATA, BlueTooth/WiFi, PXE boot, webcam etc, but only if you’re not using them!.

I will do as advised and report back. Thank you.

Bios is up-to-date and other items are good to go. If this is hardware related, could it be something failing?

I thought its something to do with the initrd. As per the image below, once its hits that, it starts a job stopping daemons:

Again, I am not sure if the issue is software or hardware related. When I had Arch installed, the gpu error was the reason of the hang up but EOS it seems to be this.

Thank you for your help.

Please find the requested below and thank you for letting me know about code blocks!

graphical.target @5.697s
└─gdm.service @5.685s +11ms
  └─systemd-user-sessions.service @5.670s +11ms
    └─network.target @5.666s
      └─wpa_supplicant.service @5.630s +35ms
        └─basic.target @4.444s
          └─dbus-broker.service @4.401s +40ms
            └─dbus.socket @4.398s
              └─sysinit.target @4.395s
                └─systemd-backlight@backlight:amdgpu_bl1.service @5.401s +57ms
                  └─system-systemd\x2dbacklight.slice @1.610s
                    └─system.slice
                      └─-.slice

Please let me know if you need anything else.

I am closing the topic as I installed arch. Different issues persist but I will hunt them down.

Sorry for wasting your time but thank you for the help and guidance.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.