@pepermint I still have that file provided by @georgem83 - build 31582+8 (kernel 6.12.54), I’ve sent you a link where you can download it in a PM.
LuCI Master (25.280.81600~6c5f78f) / OpenWrt SNAPSHOT (r31363+2-b64fdedeaca3)
with apk add usbutils
USB 2.0 log - USB Flash Drive
root@MR5500_george:~#
root@MR5500_george:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.12.50 xhci-hcd xHCI Host Controller
Bus 002 Device 001: ID 1d6b:0003 Linux 6.12.50 xhci-hcd xHCI Host Controller
root@MR5500_george:~# [ 98.944782] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[ 99.099319] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 99.101156] scsi host0: usb-storage 1-1:1.0
[ 100.155837] scsi 0:0:0:0: Direct-Access VendorCo ProductCode 2.00 PQ: 0 ANSI: 4
[ 100.160571] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[ 100.163290] sd 0:0:0:0: [sda] Write Protect is off
[ 100.170528] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 100.175540] sd 0:0:0:0: [sda] No Caching mode page found
[ 100.180289] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 100.246601] sda: sda1 sda2
[ 100.247335] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 100.282019] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[ 100.508866] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[ 100.739785] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[ 104.834277] usb 1-1: USB disconnect, device number 2
[ 107.344895] usb 1-1: new high-speed USB device number 3 using xhci-hcd
[ 107.499317] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 107.501146] scsi host0: usb-storage 1-1:1.0
[ 108.565782] scsi 0:0:0:0: Direct-Access VendorCo ProductCode 2.00 PQ: 0 ANSI: 4
[ 108.569943] sd 0:0:0:0: [sda] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[ 108.573243] sd 0:0:0:0: [sda] Write Protect is off
[ 108.582284] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 108.586576] sd 0:0:0:0: [sda] No Caching mode page found
[ 108.590330] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 108.657301] sda: sda1 sda2
[ 108.658181] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 108.694315] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[ 108.919210] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[ 109.146425] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.USB 3.0 log - USB Flash Drive
root@MR5500_george:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.12.50 xhci-hcd xHCI Host Controller
Bus 002 Device 001: ID 1d6b:0003 Linux 6.12.50 xhci-hcd xHCI Host Controller
root@MR5500_george:~# [ 127.134899] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 128.754878] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 128.755211] usb usb1-port1: attempt power cycle
[ 130.444884] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 132.054908] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
[ 132.055255] usb usb1-port1: unable to enumerate USB device
USB 3.0 log - External SSD
root@MR5500_george:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.12.50 xhci-hcd xHCI Host Controller
Bus 002 Device 001: ID 1d6b:0003 Linux 6.12.50 xhci-hcd xHCI Host Controller
root@MR5500_george:~# [ 184.475454] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 188.585327] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 192.695379] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 196.815469] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 200.925433] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 205.035552] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 209.155558] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?Others error after USB 3.0 External SSD connected
root@MR5500_george:~# [ 324.804703] pcieport 0000:00:00.0: AER: Correctable error message received from 0000:01:00.0
[ 324.804833] ath11k_pci 0000:01:00.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[ 324.812261] ath11k_pci 0000:01:00.0: device [17cb:1104] error status/mask=00000001/0000e000
[ 324.822156] ath11k_pci 0000:01:00.0: [ 0] RxErr (First)@podtor May I ask why are you testing the older version 31363+2, when @georgem83 has since provided a newer test image 31582+8 ? As far as I see, neither of them has functional USB 3.0 (not attacking or anything, just trying to understand).
link please
@podtor PM sent… even though it seems you have already tested it (build 31582+8), you have a report for it here: Adding support for Linksys MR5500 - #242 by podtor
Am I missing something?
@pepermint @podtor Any feedback on testing USB 3.0 with build 31582+8 from @georgem83 that I re-shared with you guys ?
Issues with all the insanity going on here. I just downloaded the link you said and have it installed. i could use some help.
Note: Give me commands to run. i am not sure how to tell what USB is detected. I am more used to (on routers) Merlin and DDWRT….. or Debian. I have never used a USB on openwrt so definitely assume I have no clue.
(A) I just piggy backed the router off my main GL MT6000 router. Simple and dumb plugged into the MR5500 WAN port. Any settings I should set up or just leave as is for testing
(B) how did @podtor make the print compacted if I am to post my boot logs here
(C) Treat me like I am stupid - give me commands to test as I am learning. Yup, I am blunt to everyone including myself. Sorta happens being X Military. Hopefully if I am blunt you will not be offended, throw it back, lol.
system is Cable modem > GL.Inet Gl MT6000 openwrt 24.10.4 > Linksys MR5500 George’s test snapshot for anyone wondering if there are settings I should have on the MR5500
EDIT: I PM’d george the boot logs since I was unable to figure out how to post that much info here in the forums… I tried the quotes and the preformatted text. pretty sure I am missing something.
EDIT2: apk add usbutils… got it and installed. Tel me what commands you want to see now please. USB for testing is an amazon basics usb3 drive currently formatted in exfat (checked with gparted on LMDE 7)
*****************************************************************************************************************
root@OpenWrt-MR5500:/rom# lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 001: Dev 002, If 0, Class=[unknown], Driver=usb-storage, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M
root@OpenWrt-MR5500:/rom# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.12.54 xhci-hcd xHCI Host Controller
Bus 001 Device 002: ID 346d:3281 General USB Flash Disk
Bus 002 Device 001: ID 1d6b:0003 Linux 6.12.54 xhci-hcd xHCI Host Controller
******************************************************************************************************************
[Nov 15, 2025, 5:14:16 PM EST] kern.info: [ 1919.905299] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[Nov 15, 2025, 5:14:16 PM EST] kern.info: [ 1920.058858] usb-storage 1-1:1.0: USB Mass Storage device detected
[Nov 15, 2025, 5:14:16 PM EST] kern.info: [ 1920.061148] scsi host0: usb-storage 1-1:1.0
[Nov 15, 2025, 5:14:17 PM EST] kern.notice: [ 1921.106251] scsi 0:0:0:0: Direct-Access General USB Flash Disk 3.00 PQ: 0 ANSI: 4
[Nov 15, 2025, 5:14:17 PM EST] kern.notice: [ 1921.110984] sd 0:0:0:0: [sda] 243404800 512-byte logical blocks: (125 GB/116 GiB)
[Nov 15, 2025, 5:14:17 PM EST] kern.notice: [ 1921.113690] sd 0:0:0:0: [sda] Write Protect is off
[Nov 15, 2025, 5:14:17 PM EST] kern.debug: [ 1921.120897] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[Nov 15, 2025, 5:14:17 PM EST] kern.warn: [ 1921.125912] sd 0:0:0:0: [sda] No Caching mode page found
[Nov 15, 2025, 5:14:17 PM EST] kern.warn: [ 1921.130612] sd 0:0:0:0: [sda] Assuming drive cache: write through
[Nov 15, 2025, 5:14:17 PM EST] kern.info: [ 1921.186638] sda: sda1
[Nov 15, 2025, 5:14:17 PM EST] kern.notice: [ 1921.187195] sd 0:0:0:0: [sda] Attached SCSI removable disk
[Nov 15, 2025, 5:14:17 PM EST] kern.warn: [ 1921.221934] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[Nov 15, 2025, 5:14:18 PM EST] kern.warn: [ 1921.442927] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[Nov 15, 2025, 5:14:23 PM EST] kern.warn: [ 1926.852093] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[Nov 15, 2025, 5:16:24 PM EST] kern.warn: [ 2047.611686] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[Nov 15, 2025, 5:16:48 PM EST] user.notice: advanced-reboot: attempting to mount alternative partition (mtd13)
[Nov 15, 2025, 5:16:48 PM EST] kern.notice: [ 2071.854486] ubi1: attaching mtd13
[Nov 15, 2025, 5:16:49 PM EST] kern.notice: [ 2072.417054] ubi1: scanning is finished
@pepermint I get the same results as you do. @podtor and @georgem83 can you please give us more details on what and how to test exactly?
Hi @georgem83, hope everything’s going well on your side.
I wanted to ask whether you’ve managed to diagnose the USB 3.0 handling issue on the Linksys MR500, or if you’re planning to release any new test builds. If so, feel free to let me know — I’d be happy to test them.
@georgem83 Same question here as well.
I'm currently writing drivers to enable bluetooth from scratch, at least, trying to.. When I'm done with that, I'll direct my attention to USB3 again. Definitely still on my to-do.. (next to my full-time job i.e. 
)
Do you need to do something similar: https://github.com/sinancetinkaya/nbg7815_ble_init ?
nah, I've written the remoteproc driver and it loads the firmware (finally).
I'm now implementing a custom HCI driver based on IPC doorbell & interrupt with data exchange over shared memory
Installed 25.12.2 and so far so good. Just checking in for any potential new testing for MR5500.
Hi,
I'm trying to figure out if everything is now working on USB 3.0.
It's not, unless @georgem83 figures out how to fix it.
@georgem83 heads-up before anyone tries this on an MR5500: the branch as published cannot build the MR5500 DTB on 6.18.
0825-arm64-dts-qcom-ipq5018-Flatten-usb-controller-node.patch removes the usb_dwc child node from ipq5018.dtsi, but target/linux/qualcommax/dts/ipq5018-mr5500.dts still has:
&usb_dwc {
#address-cells = <1>;
#size-cells = <0>;
dr_mode = "host";
usb_port1: port@1 { ... };
};
so dtc stops with:
Error: ../dts/ipq5018-mr5500.dts:283.1-9 Label or path usb_dwc not found
FATAL ERROR: Syntax error parsing input tree
The fix is to fold those properties into the now-flattened &usb node (that is what I did locally to get a build):
&usb {
status = "okay";
vbus-supply = <®ulator_fixed_5p0>;
#address-cells = <1>;
#size-cells = <0>;
dr_mode = "host";
usb_port1: port@1 {
reg = <1>;
#trigger-source-cells = <0>;
};
};
It does not show up in a default build because the branch keeps KERNEL_PATCHVER=6.12 while the USB3 series lives in patches-6.18 - so a plain build never applies 0825, and a CONFIG_TESTING_KERNEL=y build fails at the DTB step. Worth flagging, because it means a tester on the default kernel would be testing nothing at all.
One more thing while porting: the new PHY_QCOM_UNIPHY_USB_22ULL symbol is only answered in ipq50xx/config-default. Since the patch adds it for the whole qualcommax target, ipq60xx/ipq807x will meet an unanswered visible symbol, syncconfig turns interactive and the build dies on EOF. Adding # CONFIG_PHY_QCOM_UNIPHY_USB_22ULL is not set to the shared config-6.18 avoids that (same thing bit the DWMAC symbol recently).
Otherwise the series ports cleanly - I have it applied on an Archer AX55 v1 (IPQ5018) with our board DTS adapted to the flattened node, and all 11 patches apply without fuzz. Hardware results to follow.
for anyone who's like to test USB3, I've uploaded new build to: https://filebin.net/hor2duzsor5kw6k3
kindly upload your logs and test results
I've uploaded two versions (one ends with -mod) which will help determine which patch set to send upstream for linux support. Can anyone (ping @KrypteX, @ikap60, @pepermint, @podtor) test and let me know which (perhaps both) work in USB3 / Super-speed mode?