You are not logged in.
Pages: 1
Hello, noob arch user here.
I start arch some weeks ago, familiarizing myself. Before that i was trying fedora for some month and i was a win11 user before. I left win11 for obvious reason, and then fedora because friend keep telling me to try arch because i was always in a console. Right now, I love my Arch and i really want to make it the best i could ever have.
I have a problem tho (that's why I'm here haha)
My arch take a very looong time to boot. between 1 min 30s and 3 min to boot, depending of the day.
With the same computer, Fedora was taking something like 28-35 seconds, and win11 was taking approximately 32-38s.
I've tried to search where the problem is from, but i can't find it. I've looked at the systemd-analyze time and blame but i don't really understand what take so much time and how to read it correctly. Can someone help me ?
here are the systemd-analyze :
systemd-analyze time :
Startup finished in 26.787s (firmware) + 3.872s (loader) + 3.428s (kernel) + 1min 6.891s (initrd) + 4.225s (userspace) = 1min 45.204s
graphical.target reached after 4.225s in userspace.systemd-analyze blame :
1min 7.359s dev-sda.device
1min 7.359s dev-disk-by\x2did-wwn\x2d0x5000c500a29c8882.device
1min 7.359s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.device
1min 7.359s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0.device
1min 7.359s dev-disk-by\x2did-ata\x2dST2000DM006\x2d2DM164_Z4Z7XCYW.device
1min 7.359s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-0000:03:0a.0-0000:0a:00.0-ata5-host4-target4:0:0-4:0:0:0-block-sda.device
1min 7.359s dev-disk-by\x2ddiskseq-1.device
1min 7.316s dev-disk-by\x2dpartuuid-5d35bbab\x2db411\x2d4540\x2dbf80\x2d686e6ac0ab23.device
1min 7.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart-by\x2duuid-b0d5cd35\x2d80eb\x2d4837\x2da1ab\x2d2c80f42740bf.device
1min 7.316s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-0000:03:0a.0-0000:0a:00.0-ata5-host4-target4:0:0-4:0:0:0-block-sda-sda1.device
1min 7.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart-by\x2dlabel-HDD\x5cx20Barracuda.device
1min 7.316s dev-disk-by\x2dlabel-HDD\x5cx20Barracuda.device
1min 7.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart-by\x2dpartuuid-5d35bbab\x2db411\x2d4540\x2dbf80\x2d686e6ac0ab23.device
1min 7.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1\x2dpart1.device
1min 7.316s dev-sda1.device
1min 7.316s dev-disk-by\x2did-wwn\x2d0x5000c500a29c8882\x2dpart1.device
1min 7.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart1.device
1min 7.316s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 7.316s dev-disk-by\x2duuid-b0d5cd35\x2d80eb\x2d4837\x2da1ab\x2d2c80f42740bf.device
1min 7.316s dev-disk-by\x2did-ata\x2dST2000DM006\x2d2DM164_Z4Z7XCYW\x2dpart1.device
1min 7.316s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d1.0\x2dpart-by\x2dpartnum-1.device
1min 7.311s dev-tpm0.device
1min 7.311s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
1min 7.310s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
1min 7.310s dev-tpmrm0.device
1min 7.310s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
1min 7.310s dev-ttyS0.device
1min 7.309s dev-ttyS3.device
1min 7.309s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 7.308s dev-ttyS1.device
1min 7.308s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 7.308s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 7.308s dev-ttyS2.device
1min 7.305s sys-module-fuse.device
1min 7.304s sys-module-configfs.device
1min 7.247s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-0000:03:00.0-0000:04:00.0-nvme-nvme1-nvme1n1-nvme1n1p1.device
1min 7.247s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X115246P_1\x2dpart1.device
1min 7.247s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 7.247s dev-nvme1n1p1.device
1min 7.247s dev-disk-by\x2ddiskseq-3\x2dpart1.device
1min 7.247s dev-disk-by\x2duuid-0D4D\x2dA247.device
1min 7.247s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-BOOT.device
1min 7.247s dev-disk-by\x2ddesignator-esp.device
1min 7.247s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X115246P\x2dpart1.device
1min 7.247s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-15671dee\x2d1ac6\x2d4d3d\x2d8f20\x2dd15dddfae13b.device
1min 7.247s dev-disk-by\x2dlabel-BOOT.device
1min 7.247s dev-disk-by\x2dpartuuid-15671dee\x2d1ac6\x2d4d3d\x2d8f20\x2dd15dddfae13b.device
1min 7.247s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-0D4D\x2dA247.device
1min 7.247s dev-disk-by\x2did-nvme\x2deui.0025384141432d00\x2dpart1.device
1min 7.247s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
1min 7.244s dev-nvme1n1p2.device
1min 7.244s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X115246P\x2dpart2.device
1min 7.244s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-ARCH.device
1min 7.244s dev-disk-by\x2dpartuuid-450ad6eb\x2d1385\x2d4bc3\x2d987c\x2d97e3369b8d2e.device
1min 7.244s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-159e541f\x2dd8fb\x2d450c\x2da130\x2d1bcab19f926d.device
1min 7.244s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-450ad6eb\x2d1385\x2d4bc3\x2d987c\x2d97e3369b8d2e.device
1min 7.244s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X115246P_1\x2dpart2.device
1min 7.244s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
1min 7.244s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-450ad6eb\x2d1385\x2d4bc3\x2d987c\x2d97e3369b8d2e.device
1min 7.244s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X115246P_1\x2dpart2.device
1min 7.244s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
1min 7.244s dev-disk-by\x2ddiskseq-3\x2dpart2.device
1min 7.244s dev-disk-by\x2dlabel-ARCH.device
1min 7.244s dev-disk-by\x2did-nvme\x2deui.0025384141432d00\x2dpart2.device
1min 7.244s dev-disk-by\x2duuid-159e541f\x2dd8fb\x2d450c\x2da130\x2d1bcab19f926d.device
1min 7.244s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-2.device
1min 7.238s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X115246P.device
1min 7.238s dev-disk-by\x2did-nvme\x2deui.0025384141432d00.device
1min 7.238s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
1min 7.238s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-0000:03:00.0-0000:04:00.0-nvme-nvme1-nvme1n1.device
1min 7.238s dev-disk-by\x2ddiskseq-3.device
1min 7.238s dev-disk-by\x2did-nvme\x2dSamsung_SSD_990_PRO_with_Heatsink_2TB_S7DRNJ0X115246P_1.device
1min 7.238s dev-nvme1n1.device
1min 7.227s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.device
1min 7.227s dev-disk-by\x2did-ata\x2dST8000DX001\x2d3GK101_WWZ0LSZD.device
1min 7.227s dev-disk-by\x2ddiskseq-2.device
1min 7.227s dev-sdb.device
1min 7.227s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-0000:03:0a.0-0000:0a:00.0-ata6-host5-target5:0:0-5:0:0:0-block-sdb.device
1min 7.227s dev-disk-by\x2did-wwn\x2d0x5000c500e55e446f.device
1min 7.227s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0.device
1min 7.214s dev-nvme0n1p1.device
1min 7.214s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
1min 7.214s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2duuid-8b3e07c2\x2d9db0\x2d48b6\x2db890\x2dbcd1644e6d39.device
1min 7.214s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0T940025D_1\x2dpart1.device
1min 7.214s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0T940025D\x2dpart1.device
1min 7.214s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart1.device
1min 7.214s dev-disk-by\x2dpartuuid-0db91075\x2d925f\x2d4e25\x2da2c2\x2deab79d4dcd95.device
1min 7.214s dev-disk-by\x2dlabel-nvme\x5cx20slowbro.device
1min 7.214s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dlabel-nvme\x5cx20slowbro.device
1min 7.214s dev-disk-by\x2did-nvme\x2deui.002538d921a144db\x2dpart1.device
1min 7.214s dev-disk-by\x2duuid-8b3e07c2\x2d9db0\x2d48b6\x2db890\x2dbcd1644e6d39.device
1min 7.214s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartuuid-0db91075\x2d925f\x2d4e25\x2da2c2\x2deab79d4dcd95.device
1min 7.214s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1\x2dpart-by\x2dpartnum-1.device
1min 7.214s dev-disk-by\x2ddiskseq-4\x2dpart1.device
1min 7.213s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart1.device
1min 7.213s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartnum-1.device
1min 7.213s dev-sdb1.device
1min 7.213s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
1min 7.213s dev-disk-by\x2did-wwn\x2d0x5000c500e55e446f\x2dpart1.device
1min 7.213s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-0000:03:0a.0-0000:0a:00.0-ata6-host5-target5:0:0-5:0:0:0-block-sdb-sdb1.device
1min 7.213s dev-disk-by\x2ddiskseq-2\x2dpart1.device
1min 7.213s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2\x2dpart1.device
1min 7.213s dev-disk-by\x2did-ata\x2dST8000DX001\x2d3GK101_WWZ0LSZD\x2dpart1.device
1min 7.213s dev-disk-by\x2dpartuuid-b68b3aff\x2dad24\x2d44dc\x2d832e\x2dd6cba609bb71.device
1min 7.213s dev-disk-by\x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device
1min 7.213s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartuuid-b68b3aff\x2dad24\x2d44dc\x2d832e\x2dd6cba609bb71.device
1min 7.199s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0T940025D.device
1min 7.199s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NL0T940025D_1.device
1min 7.199s dev-disk-by\x2dpath-pci\x2d0000:01:00.0\x2dnvme\x2d1.device
1min 7.199s dev-disk-by\x2ddiskseq-4.device
1min 7.199s dev-disk-by\x2did-nvme\x2deui.002538d921a144db.device
1min 7.199s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.0-nvme-nvme0-nvme0n1.device
1min 7.199s dev-nvme0n1.device
1min 7.123s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartnum-2.device
1min 7.123s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2duuid-78EEF443EEF3F76A.device
1min 7.123s dev-disk-by\x2did-ata\x2dST8000DX001\x2d3GK101_WWZ0LSZD\x2dpart2.device
1min 7.123s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dpartuuid-5338198b\x2db1bc\x2d4a1c\x2db86c\x2d9172da150102.device
1min 7.123s dev-sdb2.device
1min 7.123s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart2.device
1min 7.123s dev-disk-by\x2ddiskseq-2\x2dpart2.device
1min 7.123s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2\x2dpart2.device
1min 7.123s dev-disk-by\x2did-wwn\x2d0x5000c500e55e446f\x2dpart2.device
1min 7.123s dev-disk-by\x2dpartuuid-5338198b\x2db1bc\x2d4a1c\x2db86c\x2d9172da150102.device
1min 7.123s dev-disk-by\x2dlabel-Fireduck.device
1min 7.123s dev-disk-by\x2dpath-pci\x2d0000:0a:00.0\x2data\x2d2.0\x2dpart-by\x2dlabel-Fireduck.device
1min 7.123s sys-devices-pci0000:00-0000:00:01.2-0000:02:00.0-0000:03:0a.0-0000:0a:00.0-ata6-host5-target5:0:0-5:0:0:0-block-sdb-sdb2.device
1min 7.123s dev-disk-by\x2duuid-78EEF443EEF3F76A.device
1.497s mnt-fireduck.mount
1.218s mnt-barracuda.mount
1.201s boot.mount
1.192s home.mount
1.191s var-log.mount
783ms NetworkManager.service
578ms initrd-switch-root.service
565ms firewalld.service
322ms systemd-udev-trigger.service
285ms systemd-modules-load.service
279ms apparmor.service
222ms user@1000.service
182ms upower.service
106ms udisks2.service
98ms systemd-tmpfiles-setup-dev-early.service
94ms systemd-journal-flush.service
83ms systemd-tmpfiles-setup-dev.service
66ms systemd-udevd.service
64ms mnt-slowbro.mount
61ms systemd-tmpfiles-setup.service
54ms polkit.service
50ms systemd-hostnamed.service
50ms bluetooth.service
50ms systemd-userdbd.service
49ms systemd-random-seed.service
48ms systemd-localed.service
47ms systemd-journald.service
45ms systemd-fsck@dev-disk-by\x2duuid-0D4D\x2dA247.service
43ms accounts-daemon.service
38ms initrd-cleanup.service
36ms systemd-logind.service
29ms systemd-fsck-root.service
28ms wpa_supplicant.service
26ms systemd-update-utmp.service
26ms initrd-parse-etc.service
25ms systemd-rfkill.service
23ms systemd-sysctl.service
23ms dev-hugepages.mount
22ms dev-mqueue.mount
22ms sys-kernel-debug.mount
21ms sys-kernel-tracing.mount
20ms tmp.mount
19ms user-runtime-dir@1000.service
18ms systemd-vconsole-setup.service
17ms systemd-user-sessions.service
17ms dbus-broker.service
16ms initrd-udevadm-cleanup-db.service
12ms systemd-binfmt.service
10ms rtkit-daemon.service
9ms kmod-static-nodes.service
8ms systemd-remount-fs.service
8ms sys-kernel-config.mount
7ms sys-fs-fuse-connections.mount
7ms systemd-udev-load-credentials.service
6ms systemd-userdb-load-credentials.service
5ms proc-sys-fs-binfmt_misc.mount
1ms systemd-coredump.socket
873us polkit-agent-helper.socket
762us sshd-unix-local.socket
531us systemd-mute-console.socket
476us systemd-factory-reset.socket
450us systemd-bootctl.socket
444us systemd-ask-password.socket
397us systemd-sysext.socket
384us systemd-creds.socket
357us systemd-repart.socket
140us dirmngr@etc-pacman.d-gnupg.socket
57us gpg-agent-browser@etc-pacman.d-gnupg.socket
53us gpg-agent-extra@etc-pacman.d-gnupg.socket
52us systemd-journald-dev-log.socket
51us keyboxd@etc-pacman.d-gnupg.socket
51us gpg-agent@etc-pacman.d-gnupg.socket
50us gpg-agent-ssh@etc-pacman.d-gnupg.socket
44us systemd-machined.socket
41us dbus.socket
38us systemd-journald.socket
34us systemd-importd.socket
33us systemd-rfkill.socket
29us systemd-userdbd.socket
23us dm-event.socket
23us systemd-udevd-varlink.socket
20us systemd-hostnamed.socket
20us systemd-udevd-control.socket
17us systemd-logind-varlink.socket
11us systemd-udevd-kernel.socketand the systemd-analyze critical-chain if needed too :
graphical.target @4.225s
└─sddm.service @4.224s
└─systemd-user-sessions.service @4.206s +17ms
└─network.target @4.205s
└─wpa_supplicant.service @4.176s +28ms
└─basic.target @2.821s
└─dbus-broker.service @2.794s +17ms
└─dbus.socket @2.790s +41us
└─sysinit.target @2.789s
└─systemd-update-utmp.service @2.762s +26ms
└─systemd-tmpfiles-setup.service @2.699s +61ms
└─systemd-journal-flush.service @2.602s +94ms
└─var-log.mount @1.409s +1.191s
└─dev-nvme1n1p2.deviceI'm sure my problem isn't something complicated but i'm too noob to find anything in the documentation that can help me
I can provfide the fstab if needed too
Last edited by Silaex (2026-01-24 14:56:47)
Offline
1min 7.123s dev-disk-by\x2duuid-78EEF443EEF3F76A.device
1.497s mnt-fireduck.mountYou're apparently waiting for the disk w/ the UUID 78EEF443EEF3F76A to show up
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stOffline
Here is the file
http://0x0.st/PZXL.txt
I tryed to limit to 10 minute journalctl + anonymise thing other than the UUID.
i think it could be that my disk timeout at a moment, i can't see it in the logs which is strange because it's mounted correctly.
I've grep all my boots with the UUID and in some boots nothing appear, and in other i have this:
janv. 23 17:42:02 hostname systemd[1]: Expecting device /dev/disk/by-uuid/78EEF443EEF3F76A...there are never other mentions about this disk in all my boots
Last edited by Silaex (2026-01-24 01:36:34)
Offline
janv. 23 18:08:30 archlinux kernel: usb 1-3: Product: AS2107
janv. 23 18:08:30 archlinux kernel: usb 1-3: Manufacturer: ASMedia
janv. 23 18:08:30 archlinux kernel: usb 1-3: SerialNumber: USB2.0 Hub
janv. 23 18:08:30 archlinux kernel: hub 1-3:1.0: USB hub found
janv. 23 18:08:30 archlinux kernel: hub 1-3:1.0: 4 ports detected
…
janv. 23 18:08:36 archlinux kernel: usb 1-3.3: device descriptor read/64, error -110
janv. 23 18:08:52 archlinux kernel: usb 1-3.3: device descriptor read/64, error -110
janv. 23 18:08:52 archlinux kernel: usb 1-3.3: new high-speed USB device number 6 using xhci_hcd
janv. 23 18:08:57 archlinux kernel: usb 1-3.3: device descriptor read/64, error -110
janv. 23 18:09:13 archlinux kernel: usb 1-3.3: device descriptor read/64, error -110
janv. 23 18:09:13 archlinux kernel: usb 1-3-port3: attempt power cycle
janv. 23 18:09:13 archlinux kernel: usb 1-4.3: new full-speed USB device number 7 using xhci_hcd
janv. 23 18:09:14 archlinux kernel: usb 1-4.3: New USB device found, idVendor=07ca, idProduct=d553, bcdDevice= 1.01
janv. 23 18:09:14 archlinux kernel: usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
janv. 23 18:09:14 archlinux kernel: usb 1-4.3: Product: Live Gamer Ultra 2.1-RGB
janv. 23 18:09:14 archlinux kernel: usb 1-4.3: Manufacturer: AVerMedia Computer Inc.
janv. 23 18:09:14 archlinux kernel: usb 1-4.3: SerialNumber: 5313706800713
janv. 23 18:09:14 archlinux kernel: hid-generic 0003:07CA:D553.000D: hiddev100,hidraw12: USB HID v1.11 Device [AVerMedia Computer Inc. Live Gamer Ultra 2.1-RGB] on usb-0000:08:00.1-4.3/input1
janv. 23 18:09:14 archlinux kernel: usb 1-3.3: new high-speed USB device number 8 using xhci_hcd
janv. 23 18:09:19 archlinux kernel: xhci_hcd 0000:08:00.1: Timeout while waiting for setup device command
janv. 23 18:09:25 archlinux kernel: xhci_hcd 0000:08:00.1: Timeout while waiting for setup device command
janv. 23 18:09:25 archlinux kernel: usb 1-3.3: device not accepting address 8, error -62
janv. 23 18:09:25 archlinux kernel: usb 1-3.3: new high-speed USB device number 9 using xhci_hcd
janv. 23 18:09:31 archlinux kernel: xhci_hcd 0000:08:00.1: Timeout while waiting for setup device command
janv. 23 18:09:31 archlinux systemd-udevd[396]: 1-3: Worker [449] processing SEQNUM=2622 is taking a long time.
janv. 23 18:09:36 archlinux kernel: xhci_hcd 0000:08:00.1: Timeout while waiting for setup device command
janv. 23 18:09:36 archlinux kernel: usb 1-3.3: device not accepting address 9, error -62
janv. 23 18:09:36 archlinux kernel: usb 1-3-port3: unable to enumerate USB deviceThere's some external hub and some broken/lose device attached to it (or the hub itself is the problem)
Offline
I see. so the problem is from this one ?
If my understanding is correct, the problem is from the AS2107 hub ? maybe port 0003 of this hub, or do I miss something ?
i've found the hub and the port003. my webcam is in it (it's the only device attached to it so it was not really difficult to find). i'm not sure if it resolve the problem because today, my computer seems to boot in ~30s wether the cam and usb hub are plugged in or not (it was also happening before but not most of the time).
Thanks for the help, i've changed my webcam from the usb hub to a 3.0 port in my mb. i'm going to continue to keep looking at my boot time to see if the problem reappears or if it was only this. the hub is useless right now so i've just unplugged it
I'm a little sad because i just discovered that this USB is 2.0 while the seller sells it as 3.0
Offline
In case and 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.
Offline
ok ! I do it !
Offline
Pages: 1