You are not logged in.

#1 2026-01-15 18:17:43

Regular_World
Member
Registered: 2026-01-15
Posts: 8

[SOLVED] problem with boot, big delay in initrd (over 1 minute)

i bought a brand new motherboard because my old one was failing, this new one is an asus rog strix b850-f. but when booting it up it is taking way too long to get to arch. on the old one it was almost instant.

[HORTA@regularworld ~]$ systemd-analyze 
Startup finished in 28.396s (firmware) + 13.866s (loader) + 1.701s (kernel) + 1min 6.022s (initrd) + 2.792s (userspace) = 1min 52.778s 
graphical.target reached after 2.792s in userspace.[/quote]
i also ran systemd-analyze blame and this was the result
[quote]
[HORTA@regularworld ~]$ systemd-analyze blame 
1min 6.251s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
1min 6.251s dev-tpm0.device
1min 6.248s dev-ttyS0.device
1min 6.248s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
1min 6.248s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 6.248s dev-ttyS1.device
1min 6.246s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 6.246s dev-ttyS3.device
1min 6.246s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
1min 6.246s dev-tpmrm0.device
1min 6.246s dev-ttyS2.device
1min 6.246s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 6.243s sys-module-configfs.device
1min 6.243s sys-module-fuse.device
1min 6.158s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
1min 6.158s dev-disk-by\x2ddiskseq-2\x2dpart1.device
1min 6.158s sys-devices-pci0000:00-0000:00:01.2-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
1min 6.158s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
1min 6.158s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 6.158s dev-disk-by\x2dpartuuid-1cd31ef0\x2d63ce\x2d4dc4\x2dbffe\x2d1f9bbb64de68.device
1min 6.158s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZALQ512HBLU\x2d00BL2_S65DNE0R141551_1\x2dpart1.device
1min 6.158s dev-nvme0n1p1.device
1min 6.158s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
1min 6.158s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZALQ512HBLU\x2d00BL2_S65DNE0R141551\x2dpart1.device
1min 6.158s dev-disk-by\x2did-nvme\x2deui.002538d1110178cb\x2dpart1.device
1min 6.158s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-1cd31ef0\x2d63ce\x2d4dc4\x2dbffe\x2d1f9bbb64de68.device
1min 6.156s dev-disk-by\x2ddiskseq-2\x2dpart2.device
1min 6.156s sys-devices-pci0000:00-0000:00:01.2-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
1min 6.156s dev-nvme0n1p2.device
1min 6.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
1min 6.156s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZALQ512HBLU\x2d00BL2_S65DNE0R141551\x2dpart2.device
1min 6.156s dev-disk-by\x2duuid-E25A16155A15E757.device
1min 6.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-E25A16155A15E757.device
1min 6.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-1d4204e8\x2dda51\x2d422e\x2dadd9\x2dfcb9feef27dc.device
1min 6.156s dev-disk-by\x2did-nvme\x2deui.002538d1110178cb\x2dpart2.device
1min 6.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart2.device
1min 6.156s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
1min 6.156s dev-disk-by\x2dpartuuid-1d4204e8\x2dda51\x2d422e\x2dadd9\x2dfcb9feef27dc.device
1min 6.156s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZALQ512HBLU\x2d00BL2_S65DNE0R141551_1\x2dpart2.device
1min 6.156s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
1min 6.151s dev-disk-by\x2did-nvme\x2deui.002538d1110178cb\x2dpart3.device
1min 6.151s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZALQ512HBLU\x2d00BL2_S65DNE0R141551\x2dpart3.device
1min 6.151s dev-disk-by\x2duuid-A4FC3A9CFC3A6926.device
1min 6.151s dev-nvme0n1p3.device
1min 6.151s dev-disk-by\x2ddiskseq-2\x2dpart3.device
1min 6.151s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
1min 6.151s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-2585c175\x2dd817\x2d4784\x2d8b9a\x2dd01526e8b564.device
1min 6.151s dev-disk-by\x2dpartuuid-2585c175\x2dd817\x2d4784\x2d8b9a\x2dd01526e8b564.device
1min 6.151s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZALQ512HBLU\x2d00BL2_S65DNE0R141551_1\x2dpart3.device
1min 6.151s sys-devices-pci0000:00-0000:00:01.2-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
1min 6.151s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-A4FC3A9CFC3A6926.device
1min 6.151s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart3.device
1min 6.146s dev-disk-by\x2did-nvme\x2deui.002538d1110178cb.device
1min 6.146s sys-devices-pci0000:00-0000:00:01.2-0000:01:00.0-nvme-nvme0-nvme0n1.device
1min 6.146s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZALQ512HBLU\x2d00BL2_S65DNE0R141551_1.device
1min 6.146s dev-disk-by\x2ddiskseq-2.device
1min 6.146s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
1min 6.146s dev-disk-by\x2did-nvme\x2dSAMSUNG_MZALQ512HBLU\x2d00BL2_S65DNE0R141551.device
1min 6.146s dev-nvme0n1.device
1min 6.143s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-18e66c66\x2df42c\x2d424b\x2dbf57\x2d764bf71ff719.device
1min 6.143s dev-nvme1n1p2.device
1min 6.143s dev-disk-by\x2ddesignator-swap.device
1min 6.143s sys-devices-pci0000:00-0000:00:02.2-0000:0a:00.0-nvme-nvme1-nvme1n1-nvme1n1p2.device
1min 6.143s dev-disk-by\x2dpartuuid-cfa87ac6\x2d53db\x2d4206\x2d98ba\x2dcb3cd6df987a.device
1min 6.143s dev-disk-by\x2duuid-18e66c66\x2df42c\x2d424b\x2dbf57\x2d764bf71ff719.device
1min 6.143s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart2.device
1min 6.143s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN850X_2000GB_24519A4A0R09_1\x2dpart2.device
1min 6.143s dev-disk-by\x2ddiskseq-1\x2dpart2.device
1min 6.143s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-cfa87ac6\x2d53db\x2d4206\x2d98ba\x2dcb3cd6df987a.device
1min 6.143s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
1min 6.143s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b444a41365017\x2dpart2.device
1min 6.143s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN850X_2000GB_24519A4A0R09\x2dpart2.device
1min 6.143s dev-disk-by\x2ddesignator-esp.device
1min 6.143s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b444a41365017\x2dpart1.device
1min 6.143s sys-devices-pci0000:00-0000:00:02.2-0000:0a:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
1min 6.143s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN850X_2000GB_24519A4A0R09\x2dpart1.device
1min 6.143s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN850X_2000GB_24519A4A0R09_1\x2dpart1.device
1min 6.143s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 6.143s dev-nvme1n1p1.device
1min 6.143s dev-disk-by\x2dpartuuid-0862225c\x2d2703\x2d4f05\x2d8512\x2de9b8f32eff1c.device
1min 6.143s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-2DF5\x2d7F71.device
1min 6.143s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-0862225c\x2d2703\x2d4f05\x2d8512\x2de9b8f32eff1c.device
1min 6.143s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart1.device
1min 6.143s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 6.143s dev-disk-by\x2duuid-2DF5\x2d7F71.device
1min 6.141s dev-nvme1n1.device
1min 6.141s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1.device
1min 6.141s sys-devices-pci0000:00-0000:00:02.2-0000:0a:00.0-nvme-nvme1-nvme1n1.device
1min 6.141s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN850X_2000GB_24519A4A0R09.device
1min 6.141s dev-disk-by\x2ddiskseq-1.device
1min 6.141s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b444a41365017.device
1min 6.141s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN850X_2000GB_24519A4A0R09_1.device
1min 6.127s sys-devices-pci0000:00-0000:00:02.2-0000:0a:00.0-nvme-nvme1-nvme1n1-nvme1n1p3.device
1min 6.127s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart3.device
1min 6.127s dev-gpt\x2dauto\x2droot.device
1min 6.127s dev-disk-by\x2duuid-4a1bb783\x2d12db\x2d4d2b\x2db64c\x2d0d5453338ef0.device
1min 6.127s dev-nvme1n1p3.device
1min 6.127s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-9dd0e418\x2d6024\x2d4459\x2da92a\x2d4e44c04f249a.device
1min 6.127s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-3.device
1min 6.127s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b444a41365017\x2dpart3.device
1min 6.127s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN850X_2000GB_24519A4A0R09_1\x2dpart3.device
1min 6.127s dev-disk-by\x2dpartuuid-9dd0e418\x2d6024\x2d4459\x2da92a\x2d4e44c04f249a.device
1min 6.127s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN850X_2000GB_24519A4A0R09\x2dpart3.device
1min 6.127s dev-disk-by\x2ddiskseq-1\x2dpart3.device
1min 6.127s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-4a1bb783\x2d12db\x2d4d2b\x2db64c\x2d0d5453338ef0.device
1min 6.127s dev-disk-by\x2ddesignator-root.device
      991ms dbus-broker.service
      360ms initrd-switch-root.service
      269ms docker.service
      154ms ckb-next.service
      135ms plymouth-start.service
      111ms user@1000.service
      111ms containerd.service
       94ms systemd-journal-flush.service
       93ms cups.service
       91ms systemd-udev-trigger.service
       86ms udisks2.service
       82ms NetworkManager.service
       80ms dev-disk-by\x2duuid-18e66c66\x2df42c\x2d424b\x2dbf57\x2d764bf71ff719.swap
       74ms ufw.service
       60ms upower.service
       37ms accounts-daemon.service
       36ms systemd-fsck-root.service
       32ms efi.mount
       31ms systemd-tmpfiles-setup-dev-early.service
       31ms systemd-tmpfiles-clean.service
       29ms systemd-udevd.service
       29ms systemd-journald.service
       25ms systemd-tmpfiles-setup.service
       23ms plymouth-quit-wait.service
       23ms plymouth-quit.service
       21ms systemd-rfkill.service
       20ms systemd-hostnamed.service
       20ms polkit.service
       20ms colord.service
       18ms systemd-logind.service
       17ms systemd-timesyncd.service
       17ms systemd-remount-fs.service
       17ms initrd-cleanup.service
       14ms user-runtime-dir@1000.service
       13ms initrd-udevadm-cleanup-db.service
       13ms systemd-userdbd.service
       12ms plymouth-read-write.service
       11ms tmp.mount
       10ms NetworkManager-wait-online.service
        9ms systemd-modules-load.service
        9ms dev-hugepages.mount
        8ms dev-mqueue.mount
        8ms systemd-tmpfiles-setup-dev.service
        8ms sys-kernel-debug.mount
        8ms sys-kernel-tracing.mount
        8ms kmod-static-nodes.service
        7ms sys-kernel-config.mount
        7ms systemd-binfmt.service
        7ms sys-fs-fuse-connections.mount
        5ms docker.socket
        5ms systemd-udev-load-credentials.service
        5ms systemd-vconsole-setup.service
        5ms systemd-random-seed.service
        5ms systemd-update-utmp.service
        4ms rtkit-daemon.service
        4ms systemd-sysctl.service
        3ms systemd-user-sessions.service
        3ms systemd-userdb-load-credentials.service
        2ms proc-sys-fs-binfmt_misc.mount
        2ms systemd-coredump.socket
        2ms initrd-parse-etc.service
      986us polkit-agent-helper.socket
      907us sshd-unix-local.socket
      622us systemd-bootctl.socket
      584us systemd-mute-console.socket
      475us systemd-ask-password.socket
      408us systemd-factory-reset.socket
      379us systemd-sysext.socket
      357us systemd-creds.socket
      344us systemd-repart.socket
      183us dirmngr@etc-pacman.d-gnupg.socket
       40us systemd-rfkill.socket
       32us systemd-importd.socket
       27us systemd-journald-dev-log.socket
       27us gpg-agent-browser@etc-pacman.d-gnupg.socket
       21us cups.socket
       14us dm-event.socket
       13us systemd-machined.socket
       12us gpg-agent-extra@etc-pacman.d-gnupg.socket
       12us systemd-journald.socket
       11us systemd-userdbd.socket
       11us gpg-agent-ssh@etc-pacman.d-gnupg.socket
       10us dbus.socket
       10us gpg-agent@etc-pacman.d-gnupg.socket
       10us keyboxd@etc-pacman.d-gnupg.socket
       10us systemd-udevd-varlink.socket
        7us systemd-hostnamed.socket
        7us systemd-udevd-control.socket
        5us systemd-udevd-kernel.socket
        5us systemd-logind-varlink.socket

i also changed /etc/fstab to make sure that it was using the correct UUID.

Is there anything i can do for this not to happen?

Last edited by Regular_World (2026-01-15 21:19:38)

Offline

#2 2026-01-15 18:31:59

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,723

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

fstab has no effect on the initramfs. Make sure your bootloader config is correct and rebuild the initramfs to make sure it has all of the correct drivers.

Offline

#3 2026-01-15 18:44:33

Regular_World
Member
Registered: 2026-01-15
Posts: 8

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

this is what is in grub

# GRUB boot loader configuration

GRUB_DEFAULT=0
GRUB_TIMEOUT=17
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `videoinfo'
GRUB_GFXMODE=2560x1440

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/home/HORTA/Pictures/grubWP"
GRUB_THEME="/boot/grub/themes/grubphemous/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
#GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Probing for other operating systems is disabled for security reasons. Read
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
# functionality install os-prober and uncomment to detect and include other
# operating systems.
GRUB_DISABLE_OS_PROBER=false

Last edited by Regular_World (2026-01-15 20:45:37)

Offline

#4 2026-01-15 18:47:56

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,723

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

Please, code tags, not quote tags.

That is not the grub config, that is the file to configure grub-mkconfig, which generates the config. If it's booting, it's unlikely that's where the problem is, though, I only brought it up because you mentioned fstab. It's probably missing driver in the initramfs for something that's not critical for booting.

Offline

#5 2026-01-15 18:59:59

Regular_World
Member
Registered: 2026-01-15
Posts: 8

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

sorry this is my first time posting here.
but since i ran

 grub-mkconfig -o /boot/grub/grub.cfg 

and

sudo mkinitcpio -P

that should be fine right?

Offline

#6 2026-01-15 19:17:48

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,723

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

If I'm right, that should do it. If I'm wrong, it shouldn't cause any harm.

Offline

#7 2026-01-15 19:26:27

Regular_World
Member
Registered: 2026-01-15
Posts: 8

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

i tried it and nothing changed.
i did notice though when i rebooted it said a "stop job is running for rule based manager for device events" and at 66seconds it finally gives up and boots to arch.
i was also reading another post similiar with my problem and it was something to do with tpm, i tried to mask it like they did in their post but either i didnt do it correctly or it didnt work.
this is the post: https://bbs.archlinux.org/viewtopic.php?id=296699

Last edited by Regular_World (2026-01-15 19:27:58)

Offline

#8 2026-01-15 20:43:03

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,043

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Offline

#9 2026-01-15 20:51:19

Regular_World
Member
Registered: 2026-01-15
Posts: 8

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

sudo journalctl -b | curl -F 'file=@-' 0x0.st

retuns this http://0x0.st/P8vE.txt

Offline

#10 2026-01-15 20:57:49

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,043

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

Jan 15 20:47:48 archlinux kernel: hub 1-8:1.0: 4 ports detected
Jan 15 20:47:48 archlinux kernel: usb 1-11: new high-speed USB device number 5 using xhci_hcd
Jan 15 20:47:54 archlinux kernel: usb 1-11: device descriptor read/64, error -110
Jan 15 20:48:10 archlinux kernel: usb 1-11: device descriptor read/64, error -110
Jan 15 20:48:10 archlinux kernel: usb 1-11: new high-speed USB device number 6 using xhci_hcd
Jan 15 20:48:15 archlinux kernel: usb 1-11: device descriptor read/64, error -110
Jan 15 20:48:31 archlinux kernel: usb 1-11: device descriptor read/64, error -110
Jan 15 20:48:31 archlinux kernel: usb usb1-port11: attempt power cycle
Jan 15 20:48:32 archlinux kernel: usb 1-11: new high-speed USB device number 7 using xhci_hcd
Jan 15 20:48:37 archlinux kernel: usb 1-11: Device not responding to setup address.
Jan 15 20:48:42 archlinux kernel: usb 1-11: Device not responding to setup address.

Some bogus USB device - since it's never responding I can't tell you what it is.
Best approach is to remove all external USB devices, see whether that fixes it, then re-attach half of them, then half of the half that must contain the troublemaker etc et pp. (ie. bisect the broken device wink)


Edit:

usb 1-7: Product: AURA LED Controller

Devices to an on-board usb connector count as "external" (but from what I can tell it's not the LED controller)

Last edited by seth (2026-01-15 20:59:32)

Offline

#11 2026-01-15 20:58:32

Regular_World
Member
Registered: 2026-01-15
Posts: 8

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

i will try that ty

Offline

#12 2026-01-15 21:17:50

Regular_World
Member
Registered: 2026-01-15
Posts: 8

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

ty so much. i guess i still have a lot more to learn about arch, even after using it for 6 months.

Startup finished in 12.860s (firmware) + 1.632s (loader) + 1.775s (kernel) + 4.489s (initrd) + 8.108s (userspace) = 28.866s 
graphical.target reached after 2.764s in userspace.

i disconnected everything from the pc and it still had that 60 secs of delaying, then i remembered to try and replug the usb connectors on the motherboard and that fixed it. thank you so much for pointing out the usb error smile

Offline

#13 2026-01-15 21:19:43

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,043

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

That's actually not an arch (or any OS) issue - loose or wedged connector?

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

F5ck lol

Last edited by seth (2026-01-15 21:20:02)

Offline

#14 2026-01-15 21:21:44

Regular_World
Member
Registered: 2026-01-15
Posts: 8

Re: [SOLVED] problem with boot, big delay in initrd (over 1 minute)

yeah i know but i still would not have checked journalctl -b if you hadn't said it. either way ty

Offline

Board footer

Powered by FluxBB