Arch Linux

LaserBeam

Member

Registered: 2023-09-29

Posts: 1

tty at boot

Hello everyone. I am trying to speed up the boot process, and following the wiki I started with:

systemd-analyze

Startup finished in 3.822s (firmware) + 4.915s (loader) + 616ms (kernel) + 40.743s (initrd) + 3.440s (userspace) = 53.539s 
graphical.target reached after 3.354s in userspace.

Then I did:

systemd-analyze blame

41.594s sys-devices-platform-serial8250-tty-ttyS1.device
41.594s dev-ttyS1.device
41.593s dev-ttyS0.device
41.593s sys-devices-platform-serial8250-tty-ttyS0.device
41.593s sys-devices-platform-serial8250-tty-ttyS11.device
41.593s dev-ttyS11.device
41.591s sys-devices-platform-serial8250-tty-ttyS10.device
41.591s dev-ttyS10.device
41.591s sys-devices-platform-serial8250-tty-ttyS12.device
41.591s dev-ttyS12.device
41.591s dev-ttyS13.device
41.591s sys-devices-platform-serial8250-tty-ttyS13.device
41.590s sys-devices-platform-serial8250-tty-ttyS14.device
41.590s dev-ttyS14.device
41.590s dev-ttyS15.device
41.590s sys-devices-platform-serial8250-tty-ttyS15.device
41.589s sys-devices-platform-serial8250-tty-ttyS16.device
41.589s dev-ttyS16.device
41.589s sys-devices-platform-serial8250-tty-ttyS17.device
41.589s dev-ttyS17.device
41.589s sys-devices-platform-serial8250-tty-ttyS18.device
41.589s dev-ttyS18.device
41.588s dev-ttyS19.device
41.588s sys-devices-platform-serial8250-tty-ttyS19.device
41.588s sys-devices-platform-serial8250-tty-ttyS2.device
41.588s dev-ttyS2.device
41.587s dev-ttyS21.device
41.587s sys-devices-platform-serial8250-tty-ttyS21.device
41.587s sys-devices-platform-serial8250-tty-ttyS22.device
41.587s dev-ttyS22.device
41.587s sys-devices-platform-serial8250-tty-ttyS23.device
41.587s dev-ttyS23.device
41.586s dev-ttyS20.device
41.586s sys-devices-platform-serial8250-tty-ttyS20.device
41.586s dev-ttyS24.device
41.586s sys-devices-platform-serial8250-tty-ttyS24.device
41.586s sys-devices-platform-serial8250-tty-ttyS26.device
41.586s dev-ttyS26.device
41.585s dev-ttyS27.device
41.585s sys-devices-platform-serial8250-tty-ttyS27.device
41.585s dev-ttyS28.device
41.585s sys-devices-platform-serial8250-tty-ttyS28.device
41.584s sys-devices-platform-serial8250-tty-ttyS25.device
41.584s dev-ttyS25.device
41.583s sys-devices-platform-serial8250-tty-ttyS29.device
41.583s dev-ttyS29.device
41.583s dev-ttyS3.device
41.583s sys-devices-platform-serial8250-tty-ttyS3.device
41.583s dev-ttyS30.device
41.583s sys-devices-platform-serial8250-tty-ttyS30.device
41.582s dev-ttyS31.device
41.582s sys-devices-platform-serial8250-tty-ttyS31.device
41.582s dev-ttyS4.device
41.582s sys-devices-platform-serial8250-tty-ttyS4.device
41.582s dev-ttyS7.device
41.582s sys-devices-platform-serial8250-tty-ttyS7.device
41.581s sys-devices-platform-serial8250-tty-ttyS5.device
41.581s dev-ttyS5.device
41.581s dev-ttyS6.device
41.581s sys-devices-platform-serial8250-tty-ttyS6.device
41.581s dev-ttyS8.device
41.581s sys-devices-platform-serial8250-tty-ttyS8.device
41.580s dev-ttyS9.device
41.580s sys-devices-platform-serial8250-tty-ttyS9.device
41.559s sys-module-configfs.device
41.421s sys-devices-pci0000:00-0000:00:1d.0-0000:2f:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
41.421s dev-disk-by\x2dpartuuid-1421c3c3\x2d60cb\x2d401b\x2d9b91\x2dcf85b11ec198.device
41.421s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKNU512GZ_BTKA13600B2P512A_1\x2dpart3.device
41.421s dev-disk-by\x2duuid-2478da9f\x2d2a44\x2d4497\x2d9caf\x2d3b285083a74a.device
41.421s dev-disk-by\x2dpath-pci\x2d0000:2f:00.0\x2dnvme\x2d1\x2dpart3.device
41.421s dev-disk-by\x2did-nvme\x2deui.0000000001000000e4d25caa989d5401\x2dpart3.device
41.421s dev-nvme0n1p3.device
41.421s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKNU512GZ_BTKA13600B2P512A\x2dpart3.device
41.421s dev-disk-by\x2did-nvme\x2deui.0000000001000000e4d25caa989d5401.device
41.421s dev-nvme0n1.device
41.421s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKNU512GZ_BTKA13600B2P512A.device
41.421s dev-disk-by\x2ddiskseq-1.device
41.421s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKNU512GZ_BTKA13600B2P512A_1.device
41.421s sys-devices-pci0000:00-0000:00:1d.0-0000:2f:00.0-nvme-nvme0-nvme0n1.device
41.421s dev-disk-by\x2dpath-pci\x2d0000:2f:00.0\x2dnvme\x2d1.device
41.421s dev-disk-by\x2ddiskseq-1\x2dpart3.device
41.416s dev-disk-by\x2duuid-e4590b81\x2d0393\x2d49b5\x2dbd36\x2d330b7652b2f9.device
41.415s dev-disk-by\x2dpartuuid-0be486ac\x2d013f\x2d4151\x2d9552\x2d3977cf594c9e.device
41.415s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKNU512GZ_BTKA13600B2P512A\x2dpart2.device
41.415s dev-disk-by\x2did-nvme\x2deui.0000000001000000e4d25caa989d5401\x2dpart2.device
41.415s sys-devices-pci0000:00-0000:00:1d.0-0000:2f:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
41.415s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKNU512GZ_BTKA13600B2P512A_1\x2dpart2.device
41.415s dev-disk-by\x2dpartlabel-endeavouros.device
41.415s dev-disk-by\x2ddiskseq-1\x2dpart2.device
41.415s dev-disk-by\x2dpath-pci\x2d0000:2f:00.0\x2dnvme\x2d1\x2dpart2.device
41.415s dev-nvme0n1p2.device
41.414s dev-nvme0n1p1.device
41.414s dev-disk-by\x2ddiskseq-1\x2dpart1.device
41.414s dev-disk-by\x2did-nvme\x2deui.0000000001000000e4d25caa989d5401\x2dpart1.device
41.414s dev-disk-by\x2duuid-DA39\x2d346E.device
41.414s dev-disk-by\x2dpartuuid-4c8ce2fc\x2d318f\x2d4b3b\x2da416\x2d374e6f5e413f.device
41.414s sys-devices-pci0000:00-0000:00:1d.0-0000:2f:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
41.414s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKNU512GZ_BTKA13600B2P512A_1\x2dpart1.device
41.414s dev-disk-by\x2did-nvme\x2dINTEL_SSDPEKNU512GZ_BTKA13600B2P512A\x2dpart1.device
41.414s dev-disk-by\x2dpath-pci\x2d0000:2f:00.0\x2dnvme\x2d1\x2dpart1.device

I am wondering if it is normal that I have some many tty services and services that takes so much time. They sometimes takes a minute. This is also the output of:

systemd-analyze critical-chain

graphical.target @3.354s
└─sddm.service @3.353s
  └─systemd-user-sessions.service @3.314s +36ms
    └─network.target @3.313s
      └─wpa_supplicant.service @3.306s +6ms
        └─dbus.service @2.305s +34ms
          └─basic.target @2.304s
            └─sockets.target @2.304s
              └─dbus.socket @2.304s
                └─sysinit.target @2.303s
                  └─systemd-backlight@backlight:intel_backlight.service @3.043s +60ms
                    └─system-systemd\x2dbacklight.slice @1.894s
                      └─system.slice
                        └─-.slice

Do you think it is normal? If not, what could I try to improve the situation. Thank you

Last edited by LaserBeam (2023-09-29 22:35:29)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: tty at boot

The systemd-analyze output makes it very clear the issue is in the initrd, not in later userspace. Using encryption?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,089

Re: tty at boot

what could I try to improve the situation

41.415s dev-disk-by\x2dpartlabel-endeavouros.device

Also not use EndeavourOS

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc