Can't get USB 3.0 port to work on Flint 3, stuck at 2.0

Routers
1

I’ve been messing around with this for hours, but can’t seem to get this to work at all…When I plug in any of my external harddrives, I can only get them to show up when USB2.0 is selected. After hours of AI assisted troubleshooting, we came up with this conclusion. I’d love to figure this out, but need help from humans who are smarter than me and googling.

Device: GL-BE9300 (Flint 3) Firmware Version: OpenWrt 23.05-SNAPSHOT] Kernel Version: 5.4.213

Issue Description: The USB 3.0 controller (dwc3-qcom) fails to initialize SuperSpeed (5Gbps) mode because the kernel cannot locate the GPIO pin required to toggle the device power rail. This forces all connected USB 3.0 devices (including SSDs and powered HDDs) to fallback to USB 2.0 (High-Speed) or fail enumeration entirely.

Steps to Reproduce:

Connect a known-good USB 3.0 drive (Seagate Expansion HDD or Samsung T5 SSD).

Set USB mode to "3.0" in the web GUI.

Observe lsusb -t showing the device on Bus 01 (480M) instead of Bus 02 (5000M).

Attempting to manually unbind/bind the driver via /sys/bus/platform/drivers/dwc3-qcom/ results in the port powering down and failing to power back up.

Kernel Log Evidence (dmesg): The kernel ring buffer shows a critical failure in the dwc3-qcom driver initialization. The Device Tree seems to be missing the device-power-gpios definition for the 8af8800.usb3 node.

[ 12.769552] dwc3-qcom 8af8800.usb3: GPIO lookup for consumer device-power
[ 12.769560] dwc3-qcom 8af8800.usb3: using device tree for GPIO lookup
[ 12.769577] of_get_named_gpiod_flags: can't parse 'device-power-gpios' property of node '/soc/usb3@8A00000[0]'
[ 12.769597] dwc3-qcom 8af8800.usb3: No GPIO consumer device-power found

Additionally, when the driver attempts to re-initialize (after a bind/unbind), the PHY fails to reach the correct power state:

[ 1214.663254] dwc3-qcom 8af8800.usb3: HS-PHY not in L2

Conclusion: The USB 3.0 PHY is active (Bus 02 exists), but the driver cannot toggle the power rail required for SuperSpeed negotiation due to the missing GPIO mapping in the DTB (Device Tree Blob). This appears to be a firmware regression or a missing definition for this hardware revision.

Please advise on a firmware patch or a workaround to manually define the GPIO pin.

3

Hi

Could you please help us check the following:

  1. Do other type of USB 3.0 devices (for example, a USB flash drive) work correctly on this device?

  2. Please restore the device to its factory settings to rule out configuration-related issues.

  3. Let us know the GL firmware version currently installed. You can find this in the top-left corner of the Admin Panel or under System → Upgrade.

    image
    image1135×595 23.9 KB

  4. Please export the device logs and send them to us via private message so we can review them further.

    How to export the logs:

    image
    image1430×911 87 KB

    How to send private message:

    image
    image632×233 19.1 KB

4

firmware is the latest, 4.8.3. I have previously tried factory resetting, not change. Ill pm the logs in a few minutes.

I have tried 3 separate devices:

Lexar Dual Drive USB-C & USB-A 128GB (usb 3.2 jumpdrive)

Seagate Expansion 22TB HDD

Samsung T5 1TB SSD

They all only show up when I select USB 2.0 in the System→Overview page of the GUI.

From a terminal, here is what is currently setup:

root@GL-BE9300:~# lsusb -t

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

|\_\_ Port 1: Dev 2, If 0, Class=, Driver=uas, 480M

root@GL-BE9300:~# lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux 5.4.213 xhci-hcd xHCI Host Controller

Bus 001 Device 002: ID 0bc2:2038 Seagate Expansion HDD

Bus 001 Device 001: ID 1d6b:0002 Linux 5.4.213 xhci-hcd xHCI Host Controller

root@GL-BE9300:~#

5

Thanks for the update. Looking forward to your log.

6

Sent you a new PM with logs etc…

7

Thank you for the update. We have asked the R&D team to review the logs.

8

In case anybody else has this issue please let me know!

Was unable to find the solution and was instructed to reach out to the official support email as they suspect a hardware issue.