You are not logged in.
Pages: 1
Topic closed
Hello,
Since I upgraded my system I experience problems with the USB3 interface.
I never had this warning message before.
xhci_pci firmware is missing when I do mkinitcpio -p linux.
Also my virtual machines don't start anymore when I enable XHCI in the settings.
$ sudo mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.8.3-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [lvm2]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.8.3-arch1-1
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [lvm2]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
$ uname -a
Linux somebody 5.8.3-arch1-1 #1 SMP PREEMPT Fri, 21 Aug 2020 16:54:16 +0000 x86_64 GNU/Linux
What can I do to solve this problem? Downgrade?
Offline
I downgraded Linux and VirtualBox and it is working for now.
Offline
See https://bbs.archlinux.org/viewtopic.php?id=257937 for a bit more background information. This particular issue should only actively affect you if you do have the rensas USB controller. If that isn't the case you likely have a different issue
Virtualbox does have issues with the kernel but it should not have a direct correlation to the issue shown here: https://bbs.archlinux.org/viewtopic.php?id=258217
FWIW this is the mkinitcpio stage, it's not going to be relevant to the booted up system. But yes if you have a rensas controller there's currently a known issue, see my first link
Offline
Hello V1del,
How to check if it is a rensas controller? Where can I find this kind of information?
And should I update my kernel with the corresponding file from Github, given from your first link?
How do I apply this patch to my system?
My virtual machine is working for now, since I downgraded Linux and VirtualBox.
Offline
Hello,
I did this
find / -iname "*RENSAS*" 2> /dev/null
but I did not find any filename specifying being a rensas controller.
Offline
That information would be in your lsusb/lspci output rather than a file.
Offline
$ lspci | grep -i usb
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
No text containing renesas in output of lsusb.
Offline
Please do what V1del suggests, a simple lspci/lsusb. And it's renesas, not rensas. Don't do grep.
I encountered the mssing firmware issue myself which left me without a working external wifi adapter. One can install the mentioned AUR package, or indeed just use an older kernel (lts) until things are fixed.
You might experience an other issue though.
Offline
Output of lspci (seems to be everything Intel):
$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation H110 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
And full output of lsusb:
$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05e3:0716 Genesys Logic, Inc. Multislot Card Reader/Writer
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 005: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 004: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Offline
lspci -v for output of usb:
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Device 8694
Flags: bus master, medium devsel, latency 0, IRQ 123
Memory at f7030000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
Offline
The only USB controller in the system is produced by Intel not Renesas so that will not be related to the VM issue.
Offline
The only USB controller in the system is produced by Intel not Renesas so that will not be related to the VM issue.
Why it is not related to the VM issue? I just updated my system, then mkinitcpio states xhci_pci is missing and VirtualBox cannot start the VM because of xHCI problems.
Doing a downgrade for linux and virtualbox package worked.
Offline
Read through https://bbs.archlinux.org/viewtopic.php?id=258217 and https://bbs.archlinux.org/viewtopic.php … 9#p1922549
Under 5.8 is there a kernel message indicating a failure to load renesas_usb_fw.mem? If not the kernel did not attempt to load the firmware because the system did not need it.
See Linux_5.8#Universal_Serial_Bus for other USB changes in 5.8. There were 14,206 non-merge commits in linux 5.8, I am suggesting one of the others caused the issue.
Edit:
If you are not convinced revert https://github.com/torvalds/linux/commi … 11094b6f09 and test if that solves the issue see https://bbs.archlinux.org/viewtopic.php … 8#p1921758.
Last edited by loqs (2020-08-30 15:14:22)
Offline
I have this message but it doesn't cause me any issues. I was just curious so I searched it today. Anyway for anyone looking it doesn't necessarily mean anything is broken.
Offline
Closing this old topic.
Offline
Pages: 1
Topic closed