You are not logged in.

#1 2024-03-31 19:50:45

aljustiet
Member
Registered: 2024-02-09
Posts: 12

[SOLVED] Devices connected to the USB4 port aren't detected.

I accidentally ran the `sudo reboot` while the `sudo pacman -Syu` process was running, after that I couldn't reboot because I guess the mkinitcpio wasn't finished yet, and initramfs wasn't yet created. After that I chrooted on arch and run the 'mkinitcpio -p linux' command, and reinstalled the bootloader. Now I can't connect devices to the USB4 port.

Last edited by aljustiet (2024-03-31 23:43:57)

Offline

#2 2024-03-31 22:14:21

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,619

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

uname -a
pacman -Qkk linux

chances are your kernel modules are corrupt/incorrectly written, you're strongly advised to explicitly reinstall all packages that were part of that update, check your /var/log/pacman.log

Online

#3 2024-03-31 22:36:03

aljustiet
Member
Registered: 2024-02-09
Posts: 12

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

V1del wrote:
uname -a
pacman -Qkk linux

chances are your kernel modules are corrupt/incorrectly written, you're strongly advised to explicitly reinstall all packages that were part of that update, check your /var/log/pacman.log

~ uname -a
pacman -Qkk linux
Linux arch 6.8.2-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 28 Mar 2024 17:06:35 +0000 x86_64 GNU/Linux
linux: 7244 total files, 0 altered files

Offline

#4 2024-03-31 22:42:04

aljustiet
Member
Registered: 2024-02-09
Posts: 12

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

V1del wrote:
uname -a
pacman -Qkk linux

chances are your kernel modules are corrupt/incorrectly written, you're strongly advised to explicitly reinstall all packages that were part of that update, check your /var/log/pacman.log

[2024-03-29T21:42:01+0500] [PACMAN] Running 'pacman -S linux linux-headers'
[2024-03-29T21:42:04+0500] [ALPM] running '70-dkms-upgrade.hook'...
[2024-03-29T21:42:04+0500] [ALPM-SCRIPTLET] ==> dkms remove --no-depmod vboxhost/7.0.14_non_OSE -k 6.8.2-arch2-1
[2024-03-29T21:42:04+0500] [ALPM] transaction started
[2024-03-29T21:42:05+0500] [ALPM] reinstalled linux (6.8.2.arch2-1)
[2024-03-29T21:42:06+0500] [ALPM] reinstalled linux-headers (6.8.2.arch2-1)
[2024-03-29T21:42:06+0500] [ALPM] transaction completed
[2024-03-29T21:42:07+0500] [ALPM] running '30-systemd-update.hook'...
[2024-03-29T21:42:07+0500] [ALPM] running '60-depmod.hook'...
[2024-03-29T21:42:08+0500] [ALPM] running '70-dkms-install.hook'...
[2024-03-29T21:42:08+0500] [ALPM-SCRIPTLET] ==> dkms install --no-depmod vboxhost/7.0.14_non_OSE -k 6.8.2-arch2-1
[2024-03-29T21:42:12+0500] [ALPM-SCRIPTLET] ==> depmod 6.8.2-arch2-1
[2024-03-29T21:42:13+0500] [ALPM] running '90-mkinitcpio-install.hook'...
[2024-03-29T21:42:14+0500] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2024-03-29T21:42:14+0500] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-03-29T21:42:14+0500] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
[2024-03-29T21:42:14+0500] [ALPM-SCRIPTLET] ==> Starting build: '6.8.2-arch2-1'
[2024-03-29T21:42:14+0500] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2024-03-29T21:42:14+0500] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2024-03-29T21:42:15+0500] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2024-03-29T21:42:15+0500] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2024-03-29T21:42:15+0500] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2024-03-29T21:42:18+0500] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2024-03-29T21:42:18+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-03-29T21:42:18+0500] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2024-03-29T21:42:18+0500] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2024-03-29T21:42:18+0500] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2024-03-29T21:42:18+0500] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2024-03-29T21:42:18+0500] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2024-03-29T21:42:19+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qat_420xx'
[2024-03-29T21:42:19+0500] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2024-03-29T21:42:20+0500] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2024-03-29T21:42:20+0500] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2024-03-29T21:42:20+0500] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-03-29T21:42:20+0500] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
[2024-03-29T21:42:21+0500] [ALPM-SCRIPTLET] ==> Initcpio image generation successful
[2024-03-29T21:42:21+0500] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2024-03-29T21:42:21+0500] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-03-29T21:42:21+0500] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
[2024-03-29T21:42:21+0500] [ALPM-SCRIPTLET] ==> Starting build: '6.8.2-arch2-1'
[2024-03-29T21:42:21+0500] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2024-03-29T21:42:21+0500] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2024-03-29T21:42:22+0500] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2024-03-29T21:42:22+0500] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2024-03-29T21:42:22+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'ast'
[2024-03-29T21:42:28+0500] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2024-03-29T21:42:29+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-03-29T21:42:29+0500] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2024-03-29T21:42:29+0500] [ALPM-SCRIPTLET]   -> Running build hook: [consolefont]
[2024-03-29T21:42:29+0500] [ALPM-SCRIPTLET] ==> WARNING: consolefont: no font found in configuration
[2024-03-29T21:42:29+0500] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2024-03-29T21:42:30+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'wd719x'
[2024-03-29T21:42:30+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla1280'
[2024-03-29T21:42:30+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'aic94xx'
[2024-03-29T21:42:30+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'bfa'
[2024-03-29T21:42:30+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qed'
[2024-03-29T21:42:30+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla2xxx'
[2024-03-29T21:42:32+0500] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2024-03-29T21:42:32+0500] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qat_420xx'
[2024-03-29T21:42:33+0500] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2024-03-29T21:42:33+0500] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2024-03-29T21:42:34+0500] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2024-03-29T21:42:36+0500] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-03-29T21:42:36+0500] [ALPM-SCRIPTLET] ==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
[2024-03-29T21:42:39+0500] [ALPM-SCRIPTLET] ==> Initcpio image generation successful

Last edited by aljustiet (2024-03-31 22:47:16)

Offline

#5 2024-03-31 23:10:47

seth
Member
Registered: 2012-09-03
Posts: 50,924

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

Run "dmesg -w" and plug a device into the slot. Does it produce *any* output?
Can you boot from devices plugged into a USB4 slot?

What kind of hardware is this (model/vendor)?
There recently was a lenovo (I think) thread that required pushing the power button for 30s or so to revive one of the USBs

Last edited by seth (2024-03-31 23:10:59)

Offline

#6 2024-03-31 23:13:57

aljustiet
Member
Registered: 2024-02-09
Posts: 12

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

$ sudo dmesg | grep usb4
[    1.348069] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.348106] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.08
[    1.348111] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.348114] usb usb4: Product: xHCI Host Controller
[    1.348117] usb usb4: Manufacturer: Linux 6.8.2-arch2-1 xhci-hcd
[    1.348120] usb usb4: SerialNumber: 0000:33:00.4

Offline

#7 2024-03-31 23:15:15

aljustiet
Member
Registered: 2024-02-09
Posts: 12

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

seth wrote:

Run "dmesg -w" and plug a device into the slot. Does it produce *any* output?
Can you boot from devices plugged into a USB4 slot?

What kind of hardware is this (model/vendor)?
There recently was a lenovo (I think) thread that required pushing the power button for 30s or so to revive one of the USBs

When I run the `sudo dmesg -w`, I don't have any reaction.
Device model: Thinkpad T14s gen 3 AMD 6850U

Last edited by aljustiet (2024-03-31 23:15:49)

Offline

#8 2024-03-31 23:16:39

aljustiet
Member
Registered: 2024-02-09
Posts: 12

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

Should I hold the power button when booting or shutting down?

Last edited by aljustiet (2024-03-31 23:17:17)

Offline

#9 2024-03-31 23:18:30

seth
Member
Registered: 2012-09-03
Posts: 50,924

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

https://bbs.archlinux.org/viewtopic.php … 6#p2158166
Edit: is for Legions, though

Last edited by seth (2024-03-31 23:19:52)

Offline

#10 2024-03-31 23:38:58

aljustiet
Member
Registered: 2024-02-09
Posts: 12

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

seth wrote:

Helped. What does holding the power button for 30 seconds do?

Offline

#11 2024-03-31 23:41:12

seth
Member
Registered: 2012-09-03
Posts: 50,924

Re: [SOLVED] Devices connected to the USB4 port aren't detected.

It's gonna be some firmware/cmos reset, check the UEFI settings whether anything has changed you want to change back.

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

Board footer

Powered by FluxBB