Using KDE and installed all recent updates. Have kernels 5.15, 6.6, and 6.11.
I’m having trouble getting the 3.0 USB ports (2 in front; 8 in back–none recognize flash drives) working on a desktop machine. I’ve had it for a couple years and am almost certain that I used at least the front to write to flash drives. They work for running the USB WIFI for internet and for the wireless mouse and wired keyboard; but only the two 2.0 recognize a flash drive when inserted.
I read this post and tried some of the items mentioned but without success.
Today first updated the BIOS and then ran the two commands:
hwinfo --usb-ctrl
and
sudo mkinitcpio -P
the output of which are below, except for removing most of the non-warning lines from the latter.
I noticed that in the 5.15 kernel, it shows
Driver: "xhci_hcd"
Driver Modules: "xhci_pci"
but for the 6.6 and 6.11
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
However, if boot with 5.15 the 3.0 ports still don’t recognize the flash drives.
Before updating the BIOS, I tried sudo modprobe ehci-hcd
and rebooted but that did not get them to recognize a flash drive. I haven’t tried that command again since the BIOS update.
Would you please point to what to try next? Thank you.
hwinfo --usb-ctrl ✔ 2m 8s
16: PCI 14.0: 0c03 USB Controller (XHCI)
[Created at pci.386]
Unique ID: MZfG.1yERtQdHuT6
SysFS ID: /devices/pci0000:00/0000:00:14.0
SysFS BusID: 0000:00:14.0
Hardware Class: usb controller
Model: "Intel 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xa2af "200 Series/Z370 Chipset Family USB 3.0 xHCI Controller"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x8299
Driver: "xhci_hcd"
Driver Modules: "xhci_pci"
Memory Range: 0xf0020000-0xf002ffff (rw,non-prefetchable)
IRQ: 121 (50426 events)
Module Alias: "pci:v00008086d0000A2AFsv0000103Csd00008299bc0Csc03i30"
Driver Info #0:
Driver Status: xhci_pci is active
Driver Activation Cmd: "modprobe xhci_pci"
Config Status: cfg=new, avail=yes, need=no, active=unknown
sudo mkinitcpio -P ✔
[sudo] password for gary:
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.167-1-MANJARO'
==> WARNING: consolefont: no font found in configuration
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: '5.15.167-1-MANJARO'
==> WARNING: Possibly missing firmware for module: 'ast'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: consolefont: no font found in configuration
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux611.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.11-x86_64 -g /boot/initramfs-6.11-x86_64.img
==> Starting build: '6.11.2-4-MANJARO'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
==> WARNING: consolefont: no font found in configuration
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.11-x86_64.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux611.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
==> Starting build: '6.11.2-4-MANJARO'
==> WARNING: Possibly missing firmware for module: 'ast'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
==> WARNING: consolefont: no font found in configuration
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.11-x86_64-fallback.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img
==> Starting build: '6.6.54-2-MANJARO'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
==> WARNING: consolefont: no font found in configuration
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect
==> Starting build: '6.6.54-2-MANJARO'
==> WARNING: Possibly missing firmware for module: 'ast'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
==> WARNING: consolefont: no font found in configuration
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
==> Initcpio image generation successful
ADDED:
I tried adding all the firmware through mkinitcpio-firmware
and added the usb3.conf file with the two setting listed in the mentioned post. It didn’t work. The hwinfo --usb-ctrl
appears to indicate that the driver is correct and active. I don’t know what the active
in Config Status
means. I ran the modprobe xhci_pci
and rebooted on several occasions throughout. I’ve had no more success than the post that I started from. The BIOS appears to show that every USB port on this machine is checked and all types are permitted. I do not see any BIOS options that distinguish between 2.0 and 3.0, only by port number and type C; and all are checked.
I thought the above was the case and then tried a new USB of the exact same type, size, and manufacturer; and it is recognized by the 3.0 ports. I’m using Samsung USB 3.1 Flash Drive BAR Plus 256 GB. One I’ve been using for several years and I think is about 1/2 full. It works fine in the 2.0 ports and I generally back up my code files every night on it. (I need to learn version control like Fossil or git.) But it is not recognized in the 3.0 port. The new drive not yet written to or re-formatted is almost immediately recognized.
What does that mean? The drive has the 3.1 engraved on the back of the metal cover; so, I shouldn’t be mistaken about it.
Thanks.