I have a Radxa O6 with 64GB of memory.
I followed the guide provided here. After rebooting into the 7.0.0-generic kernel, no USB devices are detected, though I can access the system over the network to interrogate it (I assume the TTL console is available too though it's not connected currently). If I reboot and select the 6.12.x kernel from Debian via GRUB USB works as expected, so this seems to be an interaction with the newer kernel.
Current kernel:
blood@orion:~$ uname -a
Linux orion 7.0.0-generic #1 SMP PREEMPT Tue Apr 21 05:59:24 EDT 2026 aarch64 GNU/Linux
EDK2 BIOS is the latest from github:
[ 0.144358] DMI: Radxa Computer (Shenzhen) Co., Ltd. Radxa Orion O6/Radxa Orion O6, BIOS 1.2.3 2026-06-15T03:35:10+00:00
Output of lsusb and its exit code:
blood@orion:~$ lsusb
blood@orion:~$ echo $?
1
That return code indicates that lsusb did not find any devices which matches the empty output.
Here are all of the messages containing USB during startup:
blood@orion:~$ sudo dmesg | grep -i usb
[ 0.148092] Sky1 USB: registering PNP0D10 scan handler
[ 0.249042] acpi PNP0D10:00: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249086] acpi PNP0D10:01: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249126] acpi PNP0D10:02: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249169] acpi PNP0D10:03: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249271] acpi PNP0D10:04: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249346] acpi PNP0D10:05: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249386] acpi PNP0D10:06: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249426] acpi PNP0D10:07: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249465] acpi PNP0D10:08: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.249505] acpi PNP0D10:09: Sky1: blocking PNP0D10, CIXH2030/CIXH2031 will handle USB
[ 0.268547] ACPI: bus type USB registered
[ 0.268571] usbcore: registered new interface driver usbfs
[ 0.268584] usbcore: registered new interface driver hub
[ 0.268594] usbcore: registered new device driver usb
A few other commands you might find interesting:
blood@orion:~$ dpkg -l | grep firmware-misc-nonfree
ii firmware-misc-nonfree 20260519-1~bpo13+1 all Binary firmware for various drivers in the Linux kernel
blood@orion:~$ dpkg -l | grep cix
ii cix-debian13-k7.0-driver-opensource 1.0.2 arm64 cix-debian13-k7.0-driver-opensource package
ii cix-grub-config 1.1.4 arm64 CIX GRUB boot configuration package
ii cix-npu-driver-dkms 6.1.1-2 all dkms source for CIX NPU driver
ii cix-vpu-driver-dkms 1.0.1-3 all dkms source for CIX VPU driver
ii cix-vpu-firmware 1.0.1-3 all firmware binaries for CIX VPU driver
The only USB cable I typically have directly connected is to my monitor which contains a hub with my keyboard, mouse, webcam, etc connected to it. I did try plugging the keyboard and mouse directly to the O6 and removing the cable to the hub but that did not make any noticeable difference.
I'm happy to provide any further details that you may need, though reproducing this can't be too hard.
I have a Radxa O6 with 64GB of memory.
I followed the guide provided here. After rebooting into the 7.0.0-generic kernel, no USB devices are detected, though I can access the system over the network to interrogate it (I assume the TTL console is available too though it's not connected currently). If I reboot and select the 6.12.x kernel from Debian via GRUB USB works as expected, so this seems to be an interaction with the newer kernel.
Current kernel:
EDK2 BIOS is the latest from github:
Output of lsusb and its exit code:
That return code indicates that
lsusbdid not find any devices which matches the empty output.Here are all of the messages containing USB during startup:
A few other commands you might find interesting:
The only USB cable I typically have directly connected is to my monitor which contains a hub with my keyboard, mouse, webcam, etc connected to it. I did try plugging the keyboard and mouse directly to the O6 and removing the cable to the hub but that did not make any noticeable difference.
I'm happy to provide any further details that you may need, though reproducing this can't be too hard.