Hello, I am using a Beelink GTR9 Pro AI Max+ 395 and have run into some USB issues that seem to be caused by the system firmware. Problem description: During boot, Linux reports repeated errors on usb 3-5 such as: usb 3-5: device descriptor read/64, error -110 usb 3-5: device not accepting address X, error -62 usb usb3-port5: unable to enumerate USB device This delays the initialization of my keyboard and mouse. Sometimes, the system becomes unstable and freezes, which I suspect is related to these USB controller issues. In the BIOS, the system reports 3 keyboards, 2 mice, and 2 docks connected, even though I only have one keyboard and one mouse attached (and a dock with a headset). I also tested with only keyboard + mouse connected; the issue persists. I disabled XHCI handover in BIOS; the issue persists. There is no option in BIOS to disable the individual phantom port (usb 3-5). My request: Could you please investigate if this is a firmware/ACPI bug that makes the controller report phantom USB devices? If so, could you provide a BIOS/firmware update to correct this behavior, or advise on a workaround?

Hi there, ①Please press delete key as soon as you turn on the PC, so that you can go to BIOS. Please send us a picture of the Main page. We will check if you need to update the BIOS. ② Please try to install the latest version of Ubuntu 25.04

I don’t use Ubuntu and I would like to keep my OS if possible. I run NixOS on Linux Kernel 6.16.8.

ipkakr Please check your private message of the latest BIOS. After we test, ubuntu 25.04 doesn’t have these issue.

Same issue here, with the error messages, using Arch 6.16.8, with BIOS GTRP 108. It just takes a while to boot, but it works. No freezes so far. My first guess its these error messages are related to Bluetooth, but that’s a shot in the dark…

GTR9 Pro AI Max+ 395 USB issues

Beelink CS-Bettie

tbocek
Thank you for your reply.
Is the machine functioning normally now?

tbocek

Yes, for me, the error “usb 3-5: device descriptor” is gone after full power-off (unplug completely).

So far, everything runs, I did not run my machine for a long time, and OP reported about freezes, but I have not observed this.

tbocek

Just had my first freeze: amdgpu 0000:c6:00.0: [drm] ERROR [CRTC:86:crtc-0] flip_done timed out - seems to be an AMD issue.

DrDre

@tbocek I had the same usb issues, I suspect these have to do with either ethernet / mediatek BT controller. These malfuncation and only get back up after a full unplug from power

jotapesse

@tbocek I had the same usb issues, I suspect these have to do with either ethernet / mediatek BT controller. These malfuncation and only get back up after a full unplug from power

Ok, just had it completely powered off, then on, and the error was gone….
Yes, for me, the error “usb 3-5: device descriptor” is gone after full power-off (unplug completely).

DrDre @tbocek Indeed! I resolved the issue in the exact same way. This odd USB Bus 003 Device 005 is in fact the Bluetooth controller on the Mediatek MT7925 Wi-Fi/Bluetooth card, which was not working or found on my Linux system. Now it is detected and working normally and I no longer have those USB errors:

$ lsusb
(...)
Bus 003 Device 005: ID 13d3:3604 IMC Networks Wireless_Device
(...)

👉 Simply power down the GTR 9 Pro and unplug the AC power cord. Let it rest for a minute to fully discharge the power supply caps. Plug the AC power cord and power it on again. Resolved! This seems to be a case of the Bluetooth controlled (USB device) getting into a locked/limbo state which isn’t cleared until all Power is removed, possibly following a driver or firmware update. Others have reported the exact same behaviour and resolution.

Reference: (ArchLinux Forum) [SOLVED] Mediatek MT7925 Bluetooth Controller Not Working

kx

I see the same USB errors on my GTR9 Pro.
System: BIOS 1.08, firmware 1.30, Fedora 43, kernel 6.17.0-63.fc43.x86_64

usb 3-5: device descriptor read/64, error -110  
usb 3-5: device not accepting address 7, error -62
usb 3-5: device not accepting address 7, error -62    
usb usb3-port5: unable to enumerate USB device

And just while writing this post, I also got another crash:

kernel: amdgpu 0000:c4:00.0: [drm] *ERROR* [CRTC:86:crtc-0] flip_done timed out

jotapesse

I also get the same USB related errors on my GTR 9 Pro, with BIOS P1.08 and NixOS Linux kernel 6.17.0:

[    7.375780] usb 3-5: device descriptor read/64, error -110
[   23.244901] usb 3-5: device descriptor read/64, error -110
[   23.663796] usb 3-5: new high-speed USB device number 6 using xhci_hcd
[   28.876862] usb 3-5: device descriptor read/64, error -110
[   44.748847] usb 3-5: device descriptor read/64, error -110
[   44.852914] usb usb3-port5: attempt power cycle
[   45.231797] usb 3-5: new high-speed USB device number 7 using xhci_hcd
[   56.109496] usb 3-5: device not accepting address 7, error -62
[   56.424783] usb 3-5: new high-speed USB device number 8 using xhci_hcd
[   67.373152] usb 3-5: device not accepting address 8, error -62
[   67.373462] usb usb3-port5: unable to enumerate USB device

ipkakr

The reboot with unplugging indeed solved my USB problems. The freezes amdgpu 0000:c6:00.0: [drm] ERROR [CRTC:86:crtc-0] flip_done timed out still occur, however.

jotapesse

ipkakr That’s because you weren’t looking at the proper thread for that issue. 😄 I found a workaround for it here: GTR9 Pro - Linux - System Freezes - amdgpu Pageflip so hopefully that will help you sort it.

userix

Hello,

I join this topic with the same complaint - the usb-3-5 problem appeared to me after several days using the GTR9 Pro.

[    3.614951] usb 3-5: new high-speed USB device number 6 using xhci_hcd
[    8.856026] usb 3-5: device descriptor read/64, error -110
[   24.728149] usb 3-5: device descriptor read/64, error -110
[   25.147107] usb 3-5: new high-speed USB device number 7 using xhci_hcd
[   30.360003] usb 3-5: device descriptor read/64, error -110
[   46.231972] usb 3-5: device descriptor read/64, error -110
[   46.336143] usb usb3-port5: attempt power cycle
[   46.714897] usb 3-5: new high-speed USB device number 8 using xhci_hcd
[   51.751997] xhci_hcd 0000:c9:00.0: Timeout while waiting for setup device command
[   57.383939] xhci_hcd 0000:c9:00.0: Timeout while waiting for setup device command
[   57.591874] usb 3-5: device not accepting address 8, error -62
[   57.906928] usb 3-5: new high-speed USB device number 9 using xhci_hcd
[   63.015961] xhci_hcd 0000:c9:00.0: Timeout while waiting for setup device command
[   63.575219] systemd-udevd[474]: worker [493] /devices/pci0000:00/0000:00:08.3/0000:c9:00.0/usb3 is taking a long time
[   68.647969] xhci_hcd 0000:c9:00.0: Timeout while waiting for setup device command
[   68.855884] usb 3-5: device not accepting address 9, error -62
[   68.856168] usb usb3-port5: unable to enumerate USB device

The proposed unplug method in this topic does not work as expected, unfortunately.
It remedies at the problem at first, but after each soft reboot the system boot becomes more sluggish and lengthier in freeze.
After 5-th, 6-th reboot the boot time is minutes in my case.

The problem manifests in both Linux kernels 6.16.12 & 6.17.5.
The port is not recognized in Windows 11 neither, however the boot process there ignores it and the boot is fast there.

I’ve narrowed down the faulty port physically in BIOS.
The USB port is XHCI0 2.0 Port 4 - just this one.
After disabling it the boot process again is split seconds no matter how many reboots are made.
But this solution disables Bluetooth too, unfortunately.
For the time being is an acceptable workaround for me.

But the questions is:
Can we expect and when a permanent fix by a future BIOS update?

jotapesse

I’ve narrowed down the faulty port physically in BIOS.
The port is XHCI0 2.0 Port 4 - just this one.

userix Are you sure? Because your system logs, like mine, point to the usb3-port5 which was the Bluetooth controller (IMC Networks Wireless_Device) on the Mediatek MT7925 Wi-Fi/Bluetooth card. Also, are you sure you did try to:

Power down the GTR9 Pro;
Fully unplug the AC power cord (disconnect it);
Let it rest for a minute (to fully discharge any residual capacitance);
Replug the AC power cord and power it on;

That worked to resolve it permanently to everyone of us here and the same behaviour and resolution is well known from several other PC brands/models using the same Mediatek MT7925 Wi-Fi/Bluetooth card. Never again the same issue reappeared and Bluetooth is working normally since then. No need to deactivate anything on the BIOS.

tbocek

userix Interesting, booting up my GTR9 Pro also seems to be sluggish (takes much longer than any machine I have), but I have not tried to disable the NIC nor the USB port, as I do not currently use the GTR9 (its used currently as an expensive paper weight :). But, I’ll give it a shot.

tbocek

userix My machine now boots fast as well, still hitting the GDM 10sec delay (https://gitlab.gnome.org/GNOME/gdm/-/issues/974), but this is not related to beelink, but a bug in GDM. I now also disabled the NIC, and I’ll check how reliable my machine now works.

Update: no crash so far, but hitting: amdgpu 0000:c4:00.0: [drm] ERROR [CRTC:90:crtc-1] flip_done timed out again.

jotapesse

Interesting, booting up my GTR9 Pro also seems to be sluggish (takes much longer than any machine I have)

Good point! I experience the same performance issue. Specifically, the KDE Plasma desktop load seems to lag significantly and the network connection lags as well to get started/established. Something is wrong with it for sure.

jotapesse

Update: no crash so far, but hitting: amdgpu 0000:c4:00.0: [drm] ERROR [CRTC:90:crtc-1] flip_done timed out again.

tbocek Have you tried the above workaround that I’m using (or equivalent solution for other window managers)? Or are you still using that amdgpu.dcdebugmask=0×10 kernel parameter? That’s known to not resolve for many.