Very slow boot: firmware

The boot is extremely slow and this is due to the firmware: 47 seconds

How can I reduce it?

$ systemd-analyze

Startup finished in 46.907s (firmware) + 2.527s (loader) + 495ms (kernel) + 3.901s (initrd) + 4.892s (userspace) = 58.724s 
graphical.target reached after 4.892s in userspace.

$ systemd-analyze blame

5.171s sys-devices-platform-serial8250-tty-ttyS3.device
5.171s dev-ttyS3.device
5.171s dev-ttyS2.device
5.171s sys-devices-platform-serial8250-tty-ttyS2.device
5.170s dev-ttyS1.device
5.170s sys-devices-platform-serial8250-tty-ttyS1.device
5.169s dev-ttyS0.device
5.169s sys-devices-platform-serial8250-tty-ttyS0.device
5.161s dev-nvme0n1p3.device
5.161s dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dnvme\x2d1\x2dpart3.device
5.161s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066_1\x2dpart3.device
5.161s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066\x2dpart3.device
5.161s dev-disk-by\x2dlabel-home.device
5.161s dev-disk-by\x2did-nvme\x2deui.0025388c01b799f0\x2dpart3.device
5.161s dev-disk-by\x2ddiskseq-1\x2dpart3.device
5.161s sys-devices-pci0000:00-0000:00:02.4-0000:03:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
5.161s dev-disk-by\x2duuid-1fcf4752\x2d1dfa\x2d4845\x2d9fce\x2d1621a9049b2f.device
5.161s dev-disk-by\x2dpartuuid-97ce1a5b\x2df0a5\x2d4816\x2da8f1\x2d26a157c6a118.device
5.161s dev-disk-by\x2dpartlabel-home.device
5.132s dev-disk-by\x2duuid-d8377773\x2d4f68\x2d4598\x2dacf8\x2d843b0fbe319b.device
5.132s dev-disk-by\x2dpartlabel-root.device
5.132s dev-disk-by\x2dlabel-root.device
5.132s dev-disk-by\x2dpartuuid-47b18e10\x2dda57\x2d448c\x2d8ae6\x2d9ee868c1577f.device
5.132s sys-devices-pci0000:00-0000:00:02.4-0000:03:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
5.131s dev-nvme0n1p2.device
5.131s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066_1\x2dpart2.device
5.131s dev-disk-by\x2ddiskseq-1\x2dpart2.device
5.131s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066\x2dpart2.device
5.131s dev-disk-by\x2did-nvme\x2deui.0025388c01b799f0\x2dpart2.device
5.131s dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dnvme\x2d1\x2dpart2.device
5.127s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066_1\x2dpart4.device
5.127s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066\x2dpart4.device
5.127s dev-disk-by\x2dlabel-swap.device
5.127s dev-disk-by\x2dpartlabel-swap.device
5.127s dev-nvme0n1p4.device
5.127s dev-disk-by\x2duuid-c74f375d\x2d8657\x2d4fa9\x2d9340\x2d39d618e4c544.device
5.127s dev-disk-by\x2ddiskseq-1\x2dpart4.device
5.127s dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dnvme\x2d1\x2dpart4.device
5.127s dev-disk-by\x2did-nvme\x2deui.0025388c01b799f0\x2dpart4.device
5.127s dev-disk-by\x2dpartuuid-c8b54684\x2d038d\x2d4418\x2dafa5\x2d60f2002316ce.device
5.127s sys-devices-pci0000:00-0000:00:02.4-0000:03:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
5.124s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066\x2dpart1.device
5.123s dev-disk-by\x2dpartuuid-8c25c520\x2dc5b5\x2d4288\x2da47e\x2d82d52454098d.device
5.123s dev-disk-by\x2duuid-A19E\x2d1DC2.device
5.123s dev-disk-by\x2ddiskseq-1\x2dpart1.device
5.123s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066_1\x2dpart1.device
5.123s dev-disk-by\x2did-nvme\x2deui.0025388c01b799f0\x2dpart1.device
5.123s dev-disk-by\x2dpartlabel-boot.device
5.123s dev-nvme0n1p1.device
5.123s sys-devices-pci0000:00-0000:00:02.4-0000:03:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
5.123s dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dnvme\x2d1\x2dpart1.device
5.078s dev-disk-by\x2ddiskseq-1.device
5.078s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066.device
5.078s dev-disk-by\x2did-nvme\x2deui.0025388c01b799f0.device
5.078s dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dnvme\x2d1.device
5.078s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZVLB512HBJQ\x2d000L2_S4DYNX0NC97066_1.device
5.078s dev-nvme0n1.device
5.078s sys-devices-pci0000:00-0000:00:02.4-0000:03:00.0-nvme-nvme0-nvme0n1.device
3.223s dracut-initqueue.service
2.034s sys-devices-pci0000:00-0000:00:08.1-0000:04:00.0-drm-card0-card0\x2deDP\x2d1-amdgpu_bl0.device
1.278s NetworkManager.service
 852ms initrd-switch-root.service
 745ms display-manager.service
 608ms systemd-journald.service
 393ms systemd-udev-trigger.service
 354ms systemd-remount-fs.service
 338ms modprobe@nvme_fabrics.service
 326ms boot-sysctl.service
 306ms modprobe@fuse.service
 305ms avahi-daemon.service
 290ms polkit.service
 286ms mcelog.service
 285ms apparmor.service
 280ms nscd.service
 211ms modprobe@drm.service
 205ms cpupower.service
 203ms plymouth-quit-wait.service
 201ms firewalld.service
 196ms kbdsettings.service
 177ms kmod-static-nodes.service
 177ms modprobe@configfs.service
 141ms dracut-shutdown.service
 138ms issue-generator.service
 137ms klog.service
 133ms dev-mqueue.mount
 133ms sys-kernel-debug.mount
 132ms sys-kernel-tracing.mount
 132ms dev-hugepages.mount
 123ms plymouth-start.service
 107ms systemd-fsck@dev-disk-by\x2duuid-A19E\x2d1DC2.service
 106ms systemd-tmpfiles-setup-dev-early.service
 105ms user@1000.service
  98ms systemd-vconsole-setup.service
  91ms augenrules.service
  88ms systemd-fsck@dev-disk-by\x2duuid-1fcf4752\x2d1dfa\x2d4845\x2d9fce\x2d1621a9049b2f.service
  80ms systemd-random-seed.service
  78ms systemd-tmpfiles-setup.service
  75ms systemd-journal-flush.service
  67ms chronyd.service
  60ms alsa-restore.service
  58ms ModemManager.service
  58ms rsyslog.service
  58ms systemd-logind.service
  54ms boot-efi.mount
  54ms systemd-backlight@backlight:amdgpu_bl0.service
  53ms auditd.service
  52ms plymouth-read-write.service
  51ms systemd-udevd.service
  50ms wpa_supplicant.service
  49ms logrotate.service
  48ms systemd-user-sessions.service
  48ms systemd-backlight@leds:platform::kbd_backlight.service
  47ms systemd-sysctl.service
  43ms user-runtime-dir@1000.service
  43ms upower.service
  42ms smartd.service
  42ms dracut-cmdline.service
  38ms systemd-tmpfiles-setup-dev.service
  36ms udisks2.service
  31ms colord.service
  30ms systemd-update-utmp.service
  28ms accounts-daemon.service
  26ms systemd-hostnamed.service
  24ms rtkit-daemon.service
  24ms modprobe@efi_pstore.service
  20ms systemd-fsck-root.service
  20ms sound-extra.service
  16ms plymouth-switch-root.service
  16ms dracut-pre-udev.service
  13ms sys-fs-fuse-connections.mount
  12ms sys-kernel-config.mount
  11ms dev-disk-by\x2duuid-c74f375d\x2d8657\x2d4fa9\x2d9340\x2d39d618e4c544.swap
  10ms initrd-cleanup.service
   8ms initrd-parse-etc.service
   8ms home.mount
   3ms initrd-udevadm-cleanup-db.service

and

$ systemd-analyze critical-chain

The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @4.892s
└─display-manager.service @4.147s +745ms
  └─time-sync.target @4.143s
    └─chronyd.service @4.075s +67ms
      └─network.target @4.046s
        └─NetworkManager.service @2.768s +1.278s
          └─network-pre.target @2.746s
            └─wpa_supplicant.service @4.080s +50ms
              └─dbus.service @2.238s
                └─basic.target @2.233s
                  └─sockets.target @2.233s
                    └─pcscd.socket @2.233s
                      └─sysinit.target @2.229s
                        └─systemd-update-utmp.service @2.197s +30ms
                          └─auditd.service @2.103s +53ms
                            └─systemd-tmpfiles-setup.service @1.993s +78ms
                              └─local-fs.target @1.989s
                                └─boot-efi.mount @1.928s +54ms
                                  └─systemd-fsck@dev-disk-by\x2duuid-A19E\x2d1DC2.service @1.788s +107ms
                                    └─dev-disk-by\x2duuid-A19E\x2d1DC2.device @584542y 2w 2d 20h 1min 46.129s +5.123s

$ inxi -Fxxx

System:
  Host: frogguski Kernel: 6.4.0-150600.23.17-default arch: x86_64 bits: 64
    compiler: gcc v: 7.5.0 Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.39
    info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0
    Distro: openSUSE Leap 15.6
Machine:
  Type: Convertible System: LENOVO product: 81X2 v: IdeaPad Flex 5 14ARE05
    serial: <superuser required> Chassis: type: 31 v: IdeaPad Flex 5 14ARE05
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN
    serial: <superuser required> UEFI: LENOVO v: EECN40WW date: 09/21/2022
Battery:
  ID-1: BAT0 charge: 31.2 Wh (59.4%) condition: 52.5/52.5 Wh (100.0%)
    volts: 11.1 min: 11.5 model: Celxpert L19C3PD6 type: Li-poly serial: 3876
    status: not charging cycles: 9
CPU:
  Info: 8-core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64
    type: MCP smt: <unsupported> arch: Zen 2 rev: 1 cache: L1: 512 KiB L2: 4 MiB
    L3: 8 MiB
  Speed (MHz): avg: 1849 high: 2000 min/max: 1400/2000 boost: enabled cores:
    1: 2000 2: 2000 3: 2000 4: 1397 5: 1397 6: 2000 7: 2000 8: 2000
    bogomips: 31941
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Renoir [Radeon RX Vega 6 ] vendor: Lenovo driver: amdgpu
    v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1
    off: eDP-1 empty: none bus-ID: 04:00.0 chip-ID: 1002:1636 class-ID: 0300
    temp: 39.0 C
  Device-2: Syntek Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-4:4 chip-ID: 174f:243f class-ID: 0e02
    serial: 200901010001
  Display: x11 server: X.org v: 1.21.1.11 compositor: xfwm v: 4.18.0 driver:
    X: loaded: modesetting unloaded: fbdev,vesa dri: radeonsi gpu: amdgpu
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-size: <missing: xdpyinfo>
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary model: BenQ GW2765
    serial: B3F01079019 res: 2560x1440 hz: 60 dpi: 109
    size: 597x336mm (23.5x13.23") diag: 686mm (27") modes: max: 2560x1440
    min: 720x400
  Monitor-2: eDP-1 note: disabled model: LG Display 0x40a9 res: 2560x1440
    dpi: 158 size: 309x174mm (12.17x6.85") diag: 355mm (14") modes:
    max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.3.4 renderer: AMD Radeon Graphics (radeonsi
    renoir LLVM 17.0.6 DRM 3.57 6.4.0-150600.23.17-default) direct-render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
    pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.5 chip-ID: 1022:15e2
    class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  API: ALSA v: k6.4.0-150600.23.17-default status: kernel-api with: aoss
    type: oss-emulator
  Server-1: PipeWire v: 1.0.5 status: off with: wireplumber status: active
  Server-2: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
    type: plugin
Network:
  Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
    vendor: Lenovo driver: rtw_8822ce v: N/A pcie: speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:c822 class-ID: 0280
  IF: wlan0 state: up mac: dc:e9:94:8b:d2:cf
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
    rev: 3.0 speed: 5 Gb/s lanes: 1 bus-ID: 2-1.4:3 chip-ID: 0bda:8153
    class-ID: 0000 serial: 000001
  IF: eth0 state: down mac: 00:24:32:50:06:15
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 bus-ID: 3-4:4 chip-ID: 0bda:c123 class-ID: e001
    serial: 00e04c000001
  Report: rfkill ID: hci0 rfk-id: 3 state: down bt-service: not found
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 82.77 GiB (17.4%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L2
    size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial: S4DYNX0NC97066
    fw-rev: 3L1QEXF7 temp: 33.9 C scheme: GPT
Partition:
  ID-1: / size: 58.37 GiB used: 10.26 GiB (17.6%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 488 MiB used: 5.8 MiB (1.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 394.03 GiB used: 72.5 GiB (18.4%) fs: ext4
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: partition size: 15.46 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p4
Sensors:
  System Temperatures: cpu: 47.9 C mobo: N/A gpu: amdgpu temp: 38.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 290 Uptime: 0h 3m wakeups: 4 Memory: available: 15 GiB
  used: 2.8 GiB (18.7%) Init: systemd v: 254 default: graphical Compilers:
  gcc: 7.5.0 alt: 7 Packages: pm: rpm pkgs: N/A note: see --rpm Shell: Bash
  v: 4.4.23 running-in: xfce4-terminal inxi: 3.3.27

@elfroggio Firmware = BIOS, talk the the product manufacturer, see what your BIOS settings are you may be able to tweak things, like waiting for a key press to enter the likes of a boot or setup menu etc. Disable things your not using.

Sorry, but I don’t think so.

Before Leap 15.6, I had 15.5 installed and the boot firmware load was in the 8second range.

I did not upgrade with 15.5 to 15.6 but did a fresh install.

Thanks

You’re lucky it boots slowly :slight_smile: After the most recent kernel upgrade, my laptop won’t boot at all - it freezes after about two minutes - then I have to hold down the Power button for 12 seconds to shut the laptop down.

If I boot to the previous kernel (Grub boot menu), all is fine - I’m actually typing this while logged into that previous kernel. Here’s a snippet from the end of the update output (which booting it does not work):

The following package requires a system reboot:
  kernel-default
    6.4.0-150600.23.17.1  x86_64

When I run a zypper up for my 15.6 installs, I always copy the update output to a text file (actually, I append to that file, so I can see all the historical updates).

I have also noticed recent updates to “nvme” software - the laptop does use an NVME drive, so I can’t rule that out.

If you have the option to boot to a previous kernel, try it and see if it works.

@elfroggio perhaps the newer 6.4.0 kernel and systemd are less tolerant to the BIOS part of your system. Are you using secure boot, can you disable the system hardware logo? If you google “sytemd-analyze+slow firmware” you will see lot’s of hits…

No, I have disabled it when I first installed 15.4 and it’s the same laptop.

The splash is already removed from the GRUB_CMDLINE_LINUX_DEFAULT and I use the plymouth_tribar.

What else can I do?

Thanks

I believe what malcolmlewis meant was in BIOS setup, disable showing the BIOS boot logo, so that POST is entirely in text mode, before Grub is loaded.

I just checked, there is no BIOS boot logo during the boot and there is no logo item in the BIOS setup accessed through the F2 during the boot.

Thanks

I have the same problem and it’s very hard if not impossible to fix. In my case the firmware time goes up each time I add a new USB drive. I believe the UEFI BIOS is checking for the existence of the drive for boot media. But resetting/updating the BIOS, disabling checking USB drive for boot media, none of it helped.

Now I use kexec for reboot and skip the whole firmware+grub portion. This works as I don’t poweroff my machine, it’s either running or in sleep. If you shutdown/hibernate this won’t work.

Docs for setting it up:

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