Skip to content

WAN Port does not work on Linksys MR7500 #21835

Open
#24055
Open
WAN Port does not work on Linksys MR7500#21835
#24055
Labels
Official ImageSupported Devicebugissue report with a confirmed bugrelease/25.12pull request/issue targeted (also) for OpenWrt 24.10 releasetarget/qualcommaxpull request/issue for qualcommax target

Description

@RobotRoss
RobotRoss
opened on Feb 2, 2026

Describe the bug

WAN port cannot be made to work under any circumstances.

OpenWrt version

r32534-12374d88b9

OpenWrt release

25.12.0-rc4

OpenWrt target/subtarget

qualcommax/ipq60xx

Device

Linksys MR7500

Image kind

Official downloaded image

Steps to reproduce

Flash OpenWRT on MR7500. Place AQR firmware file (extracted from factory image, "AQR114C.cld") in /lib/firmware/marvell/

Add required uboot variable to enable firmware load: fw_setenv bootcmd 'aq_load_fw; run bootusb; if test $auto_recovery = no; then bootipq; elif test $boot_part = 1; then run bootpart1; else run bootpart2; fi'

Restart.

Observe WAN port does not work.

Actual behaviour

WAN port does not work under any circumstances, despite firmware being present on filesystem in correct location.

Log:

[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x51af8014]
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    0.000000] Linux version 6.12.66 (builder@buildhost) (aarch64-openwrt-linux-musl-gcc (OpenWrt GCC 14.3.0 r32534-12374d88b9) 14.3.0, GNU ld (GNU Binutils) 2.44) #0 SMP Thu Jan 29 22:36:22 2026
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Machine model: Linksys MR7500
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] OF: reserved mem: 0x0000000000060000..0x0000000000065fff (24 KiB) nomap non-reusable memory@60000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] OF: reserved mem: 0x0000000040000000..0x0000000040ffffff (16384 KiB) nomap non-reusable memory@40000000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] OF: reserved mem: 0x000000004a100000..0x000000004a4fffff (4096 KiB) nomap non-reusable bootloader@4a100000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] OF: reserved mem: 0x000000004a600000..0x000000004a9fffff (4096 KiB) nomap non-reusable memory@4a600000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] OF: reserved mem: 0x000000004aa00000..0x000000004aafffff (1024 KiB) nomap non-reusable memory@4aa00000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] OF: reserved mem: 0x000000004ab00000..0x000000004fffffff (87040 KiB) nomap non-reusable memory@4ab00000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Zone ranges:
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   DMA      [mem 0x0000000040000000-0x000000005fffffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   DMA32    empty
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   Normal   empty
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Movable zone start for each node
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Early memory node ranges
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   node   0: [mem 0x0000000040000000-0x0000000040ffffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   node   0: [mem 0x0000000041000000-0x000000004a0fffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   node   0: [mem 0x000000004a100000-0x000000004a4fffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   node   0: [mem 0x000000004a500000-0x000000004a5fffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   node   0: [mem 0x000000004a600000-0x000000004fffffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000]   node   0: [mem 0x0000000050000000-0x000000005fffffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000005fffffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] psci: probing for conduit method from DT.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] psci: PSCIv1.0 detected in firmware.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] psci: Using standard PSCI v0.2 function IDs
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] psci: SMC Calling Convention v1.0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] percpu: Embedded 20 pages/cpu s43288 r8192 d30440 u81920
[29 Jan 2026, 22:37:17 UTC] kern.debug: [    0.000000] pcpu-alloc: s43288 r8192 d30440 u81920 alloc=20*4096
[29 Jan 2026, 22:37:17 UTC] kern.debug: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Detected VIPT I-cache on CPU0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] CPU features: detected: Spectre-v4
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] alternatives: applying boot alternatives
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    0.000000] Kernel command line: init=/sbin/init rootfstype=squashfs ubi.mtd=rootfs root=mtd:squashfs rootwait root=/dev/ubiblock0_0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 131072
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] software IO TLB: SWIOTLB bounce buffer size adjusted to 0MB
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] software IO TLB: area num 4.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] software IO TLB: SWIOTLB bounce buffer size roundup to 1MB
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] software IO TLB: mapped [mem 0x000000005f4c0000-0x000000005f5c0000] (1MB)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] rcu: Hierarchical RCU implementation.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] 	Tracing variant of Tasks RCU enabled.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=4.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] Root IRQ handler: 0xffffffc080010000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] GICv2m: range[mem 0x0b00a000-0x0b00affc], SPI[448:479]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] arch_timer: cp15 and mmio timer(s) running at 24.00MHz (virt/virt).
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000086] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.000099] pid_max: default: 32768 minimum: 301
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.005023] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.005036] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.009755] rcu: Hierarchical SRCU implementation.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.009763] rcu: 	Max phase no-delay instances is 1000.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.010101] Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.010497] smp: Bringing up secondary CPUs ...
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.011150] Detected VIPT I-cache on CPU1
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.011254] CPU1: Booted secondary processor 0x0000000001 [0x51af8014]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.011990] Detected VIPT I-cache on CPU2
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.012066] CPU2: Booted secondary processor 0x0000000002 [0x51af8014]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.012818] Detected VIPT I-cache on CPU3
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.012888] CPU3: Booted secondary processor 0x0000000003 [0x51af8014]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.012970] smp: Brought up 1 node, 4 CPUs
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.012979] SMP: Total of 4 processors activated.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.012983] CPU: All CPU(s) started at EL1
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.012986] CPU features: detected: 32-bit EL0 Support
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.012991] CPU features: detected: CRC32 instructions
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.013039] alternatives: applying system-wide alternatives
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.013235] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.013497] Memory: 384068K/524288K available (8896K kernel code, 900K rwdata, 1908K rodata, 960K init, 304K bss, 137260K reserved, 0K cma-reserved)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.021416] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.021441] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.021560] 29472 pages in range for non-PLT usage
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.021565] 520992 pages in range for PLT usage
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.023674] pinctrl core: initialized pinctrl subsystem
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.028008] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.028607] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.028646] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.028679] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.029051] thermal_sys: Registered thermal governor 'step_wise'
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.029111] cpuidle: using governor menu
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.029320] ASID allocator initialised with 65536 entries
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.036716] /soc@0/interrupt-controller@b000000: Fixed dependency cycle(s) with /soc@0/interrupt-controller@b000000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.077755] qcom,cpr4-apss-regulator b018000.cpr4-ctrl: CPR valid fuse count: 4
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    0.100682] SCSI subsystem initialized
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.100896] usbcore: registered new interface driver usbfs
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.100934] usbcore: registered new interface driver hub
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.100971] usbcore: registered new device driver usb
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.101262] qcom_scm: convention: smc arm 64
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.104030] clocksource: Switched to clocksource arch_sys_counter
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.104237] s2: Bringing 0uV into 725000-725000uV
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.105308] l2: Bringing 0uV into 1800000-1800000uV
[29 Jan 2026, 22:37:17 UTC] kern.err: [    0.105443] qcom_rpm_smd_regulator remoteproc:glink-edge:rpm-requests:regulators: Supply for l2 (l2) resolved to itself
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.107933] NET: Registered PF_INET protocol family
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.108071] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.110472] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.110491] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.110505] TCP established hash table entries: 4096 (order: 3, 32768 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.110553] TCP bind hash table entries: 4096 (order: 5, 131072 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.110691] TCP: Hash tables configured (established 4096 bind 4096)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.111132] MPTCP token hash table entries: 512 (order: 2, 12288 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.111290] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.111355] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.111649] NET: Registered PF_UNIX/PF_LOCAL protocol family
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.111684] PCI: CLS 0 bytes, default 64
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.113282] workingset: timestamp_bits=46 max_order=17 bucket_order=0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.113992] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.113999] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.116750] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[29 Jan 2026, 22:37:17 UTC] kern.warn: [    0.121538] qcom-qmp-usb-phy 78000.ssphy: supply vdda-phy not found, using dummy regulator
[29 Jan 2026, 22:37:17 UTC] kern.warn: [    0.121684] qcom-qmp-usb-phy 78000.ssphy: supply vdda-pll not found, using dummy regulator
[29 Jan 2026, 22:37:17 UTC] kern.warn: [    0.123222] qcom-qusb2-phy 79000.qusb: supply vdda-pll not found, using dummy regulator
[29 Jan 2026, 22:37:17 UTC] kern.warn: [    0.123354] qcom-qusb2-phy 79000.qusb: supply vdda-phy-dpdm not found, using dummy regulator
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.123529] qcom-qusb2-phy 79000.qusb: Registered Qcom-QUSB2 phy
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.125966] qcom-pcie 20000000.pcie: host bridge /soc@0/pcie@20000000 ranges:
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.126032] qcom-pcie 20000000.pcie:       IO 0x0020200000..0x002020ffff -> 0x0000000000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.126058] qcom-pcie 20000000.pcie:      MEM 0x0020220000..0x002fffffff -> 0x0020220000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.131691] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.135548] msm_serial 78b0000.serial: msm_serial: detected port #1
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.135660] msm_serial 78b0000.serial: uartclk = 24000000
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.136032] 78b0000.serial: ttyMSM1 at MMIO 0x78b0000 (irq = 22, base_baud = 1500000) is a MSM
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.136450] msm_serial 78b1000.serial: msm_serial: detected port #0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.136514] msm_serial 78b1000.serial: uartclk = 1843199
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.136845] 78b1000.serial: ttyMSM0 at MMIO 0x78b1000 (irq = 23, base_baud = 115199) is a MSM
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.136921] msm_serial: console setup on port #0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.136965] printk: legacy console [ttyMSM0] enabled
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.245801] qcom-pcie 20000000.pcie: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 1024G
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.248078] msm_serial: driver initialized
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.464035] qcom-pcie 20000000.pcie: PCIe Gen.3 x1 link up
[29 Jan 2026, 22:37:17 UTC] kern.info: [    0.999367] qcom-pcie 20000000.pcie: PCI host bridge to bus 0000:00
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.004477] pci_bus 0000:00: root bus resource [bus 00-ff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.010615] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.016181] pci_bus 0000:00: root bus resource [mem 0x20220000-0x2fffffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.022420] pci 0000:00:00.0: [17cb:1003] type 01 class 0x060400 PCIe Root Port
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.029214] pci 0000:00:00.0: BAR 0 [mem 0x00000000-0x00000fff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.036412] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.042301] pci 0000:00:00.0:   bridge window [io  0x0000-0x0fff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.047519] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.053764] pci 0000:00:00.0:   bridge window [mem 0x00000000-0x000fffff 64bit pref]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.060589] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.071401] pci 0000:01:00.0: [17cb:1104] type 00 class 0x028000 PCIe Endpoint
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.074430] pci 0000:01:00.0: BAR 0 [mem 0x00000000-0x001fffff 64bit]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.081980] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.088106] pci 0000:01:00.0: 7.876 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x1 link at 0000:00:00.0 (capable of 15.752 Gb/s with 8.0 GT/s PCIe x2 link)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.094503] pci 0000:00:00.0: bridge window [mem 0x20400000-0x205fffff]: assigned
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.108811] pci 0000:00:00.0: BAR 0 [mem 0x20220000-0x20220fff]: assigned
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.116449] pci 0000:01:00.0: BAR 0 [mem 0x20400000-0x205fffff 64bit]: assigned
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.123246] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.130337] pci 0000:00:00.0:   bridge window [mem 0x20400000-0x205fffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.135543] pci_bus 0000:00: resource 4 [io  0x0000-0xffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.142473] pci_bus 0000:00: resource 5 [mem 0x20220000-0x2fffffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.147864] pci_bus 0000:01: resource 1 [mem 0x20400000-0x205fffff]
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.156533] pcieport 0000:00:00.0: PME: Signaling with IRQ 26
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.160625] pcieport 0000:00:00.0: AER: enabled with IRQ 26
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.165039] loop: module loaded
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.172959] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xac
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.174846] nand: Hynix H27S4G8F2EDA-BC
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.181357] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.204814] i2c_dev: i2c /dev entries driver
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.210459] sdhci: Secure Digital Host Controller Interface driver
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.210503] sdhci: Copyright(c) Pierre Ossman
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.215573] sdhci-pltfm: SDHCI platform and OF driver helper
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.223951] remoteproc remoteproc0: releasing cd00000.remoteproc
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.228248] NET: Registered PF_INET6 protocol family
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.232956] Segment Routing with IPv6
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.236701] In-situ OAM (IOAM) with IPv6
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.240255] NET: Registered PF_PACKET protocol family
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.244218] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.249258] 8021q: 802.1Q VLAN Support v1.8
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.293716] qcom,cpr4-apss-regulator b018000.cpr4-ctrl: CPR valid fuse count: 4
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.294007] cpr4_ipq807x_apss_read_fuse_data: apc_corner: speed bin = 0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.299844] cpr4_ipq807x_apss_read_fuse_data: apc_corner: CPR fusing revision = 2
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.306457] cpr4_ipq807x_apss_read_fuse_data: apc_corner: CPR misc fuse value = 0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.314110] cpr4_ipq807x_apss_read_fuse_data: apc_corner: Voltage boost fuse config = 0 boost = disable
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.321599] cpr3_mem_acc_init: apc: not using memory accelerator regulator
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.330758] cpr4_ipq807x_apss_calculate_open_loop_voltages: apc_corner: fused      SVS: open-loop= 675000 uV
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.337705] cpr4_ipq807x_apss_calculate_open_loop_voltages: apc_corner: fused      NOM: open-loop= 787500 uV
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.347687] cpr4_ipq807x_apss_calculate_open_loop_voltages: apc_corner: fused    TURBO: open-loop= 850000 uV
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.357497] cpr4_ipq807x_apss_calculate_open_loop_voltages: apc_corner: fused   STURBO: open-loop= 900000 uV
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.367329] cpr4_ipq807x_apss_calculate_target_quotients: apc_corner: fused      SVS: quot[ 7]= 571, quot_offset[ 7]=   0
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.377117] cpr4_ipq807x_apss_calculate_target_quotients: apc_corner: fused      NOM: quot[ 7]= 755, quot_offset[ 7]= 180
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.387968] cpr4_ipq807x_apss_calculate_target_quotients: apc_corner: fused    TURBO: quot[ 7]= 851, quot_offset[ 7]=  95
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.398904] cpr4_ipq807x_apss_calculate_target_quotients: apc_corner: fused   STURBO: quot[ 7]= 919, quot_offset[ 7]=  65
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.410146] cpr3_regulator_init_ctrl: apc: Default CPR mode = closed-loop
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.413702] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xac
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.427696] nand: Hynix H27S4G8F2EDA-BC
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.433950] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.438327] 20 qcomsmem partitions found on MTD device qcom_nand.0
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.445220] Creating 20 MTD partitions on "qcom_nand.0":
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.451405] 0x000000000000-0x000000180000 : "0:sbl1"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.458849] 0x000000180000-0x000000280000 : "0:mibib"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.463198] 0x000000280000-0x000000600000 : "0:qsee"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.470454] 0x000000600000-0x000000680000 : "0:devcfg"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.472673] 0x000000680000-0x000000700000 : "0:rpm"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.477662] 0x000000700000-0x000000780000 : "0:cdt"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.482424] 0x000000780000-0x000000800000 : "0:appsblenv"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.487350] 0x000000800000-0x000000980000 : "0:appsbl"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.493735] 0x000000980000-0x000000a00000 : "0:art"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.497894] 0x000000a00000-0x000000a80000 : "0:ethphyfw"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.502660] 0x000000a80000-0x000000b00000 : "u_env"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.508266] 0x000000b00000-0x000000b40000 : "s_env"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.512576] 0x000000b40000-0x000000b80000 : "devinfo"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.558061] 0x000000b80000-0x000001380000 : "kernel"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.566147] 0x000001380000-0x000005d80000 : "rootfs"
[29 Jan 2026, 22:37:17 UTC] kern.info: [    1.636465] mtd: setting mtd14 (rootfs) as root device
[29 Jan 2026, 22:37:17 UTC] kern.alert: [    1.636830] mtdsplit: no squashfs found in "rootfs"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.640543] 0x000005d80000-0x000006580000 : "alt_kernel"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.653312] 0x000006580000-0x00000af80000 : "alt_rootfs"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.723513] 0x00000af80000-0x00000b380000 : "sysdiag"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    1.727838] 0x00000b380000-0x00001f080000 : "syscfg"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.026738] 0x00001f080000-0x00001f580000 : "app_data"
[29 Jan 2026, 22:37:17 UTC] kern.info: [    2.040636] cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 799999 KHz, changing to: 864000 KHz
[29 Jan 2026, 22:37:17 UTC] kern.info: [    2.043968] remoteproc remoteproc0: cd00000.remoteproc is available
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.050723] ubi0: attaching mtd14
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.484962] ubi0: scanning is finished
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.544489] ubi0: attached mtd14 (name "rootfs", size 74 MiB)
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.544530] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.549226] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.556012] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.562853] ubi0: good PEBs: 592, bad PEBs: 0, corrupted PEBs: 0
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.569630] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.575882] ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1769726182
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.582909] ubi0: available PEBs: 0, total reserved PEBs: 592, PEBs reserved for bad PEB handling: 80
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.592219] ubi0: background thread "ubi_bgt0d" started, PID 688
[29 Jan 2026, 22:37:17 UTC] kern.info: [    2.593055] block ubiblock0_0: created from ubi0:0(rootfs)
[29 Jan 2026, 22:37:17 UTC] kern.info: [    2.607493] clk: Disabling unused clocks
[29 Jan 2026, 22:37:17 UTC] kern.info: [    2.616178] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[29 Jan 2026, 22:37:17 UTC] kern.info: [    2.616464] Freeing unused kernel memory: 960K
[29 Jan 2026, 22:37:17 UTC] kern.info: [    2.622426] Run /sbin/init as init process
[29 Jan 2026, 22:37:17 UTC] kern.debug: [    2.626658]   with arguments:
[29 Jan 2026, 22:37:17 UTC] kern.debug: [    2.626661]     /sbin/init
[29 Jan 2026, 22:37:17 UTC] kern.debug: [    2.626664]   with environment:
[29 Jan 2026, 22:37:17 UTC] kern.debug: [    2.626666]     HOME=/
[29 Jan 2026, 22:37:17 UTC] kern.debug: [    2.626668]     TERM=linux
[29 Jan 2026, 22:37:17 UTC] kern.notice: [    2.754063] random: crng init done
[29 Jan 2026, 22:37:17 UTC] user.info: [    2.801824] init: Console is alive
[29 Jan 2026, 22:37:17 UTC] user.info: [    2.801966] init: - watchdog -
[29 Jan 2026, 22:37:17 UTC] user.info: [    3.304736] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[29 Jan 2026, 22:37:17 UTC] kern.warn: [    5.372664] Aquantia AQR114C 90000.mdio-1:08: Direct firmware load for marvell/AQR114C.cld failed with error -2
[29 Jan 2026, 22:37:17 UTC] kern.warn: [    5.372722] Aquantia AQR114C 90000.mdio-1:08: Falling back to sysfs fallback for: marvell/AQR114C.cld
[29 Jan 2026, 22:37:17 UTC] user.info: [   14.890638] init: - preinit -
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.720899] UBIFS (ubi0:1): Mounting in unauthenticated mode
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.721035] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 823
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.759051] UBIFS (ubi0:1): recovery needed
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.853205] UBIFS (ubi0:1): recovery completed
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.853333] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.856587] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.864474] UBIFS (ubi0:1): FS size: 53964800 bytes (51 MiB, 425 LEBs), max 435 LEBs, journal size 2666496 bytes (2 MiB, 21 LEBs)
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.874373] UBIFS (ubi0:1): reserved for root: 2548890 bytes (2489 KiB)
[29 Jan 2026, 22:37:17 UTC] kern.notice: [   19.885996] UBIFS (ubi0:1): media format: w5/r0 (latest is w5/r0), UUID 006912AE-BAD3-44D8-830A-6EE0A5EC0CD1, small LPT model
[29 Jan 2026, 22:37:17 UTC] user.info: [   19.897876] mount_root: switching to ubifs overlay
[29 Jan 2026, 22:37:17 UTC] kern.warn: [   19.911617] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[29 Jan 2026, 22:37:17 UTC] user.warn: [   19.916891] urandom-seed: Seeding with /etc/urandom.seed
[29 Jan 2026, 22:37:17 UTC] user.info: [   19.978212] procd: - early -
[29 Jan 2026, 22:37:17 UTC] user.info: [   19.978330] procd: - watchdog -
[29 Jan 2026, 22:37:17 UTC] user.info: [   20.545348] procd: - watchdog -
[29 Jan 2026, 22:37:17 UTC] user.info: [   20.617108] procd: - ubus -
[29 Jan 2026, 22:37:17 UTC] user.info: [   20.769860] procd: - init -
[29 Jan 2026, 22:37:17 UTC] user.info: [   21.157755] kmodloader: loading kernel modules from /etc/modules.d/*
[29 Jan 2026, 22:37:17 UTC] user.info: [   21.314452] urngd: v1.0.2 started.
[29 Jan 2026, 22:37:17 UTC] kern.warn: [   21.329430] gpio_button_hotplug: loading out-of-tree module taints kernel.
[29 Jan 2026, 22:37:17 UTC] kern.warn: [   21.404325] ssdk_dt_parse_interrupt[942]:INFO:intr-gpio does not exist
[29 Jan 2026, 22:37:17 UTC] kern.warn: [   21.445769] aquantia_phy_api_ops_init[1485]:INFO:qca probe aquantia phy driver succeeded!
[29 Jan 2026, 22:37:17 UTC] kern.warn: [   22.744093] regi_init[2525]:INFO:Initializing CPPE Done!!
[29 Jan 2026, 22:37:17 UTC] kern.warn: [   22.744219] regi_init[2574]:INFO:qca-ssdk module init succeeded!
[29 Jan 2026, 22:37:17 UTC] kern.info: [   22.750715] EDMA ver 1 hw init
[29 Jan 2026, 22:37:17 UTC] kern.info: [   22.754805] EDMA HW Reset completed succesfully
[29 Jan 2026, 22:37:17 UTC] kern.info: [   22.757449] Num rings - TxDesc:1 (23-23) TxCmpl:1 (23-23)
[29 Jan 2026, 22:37:17 UTC] kern.info: [   22.761849] RxDesc:1 (15-15) RxFill:1 (7-7)
[29 Jan 2026, 22:37:17 UTC] kern.info: [   22.934955] Qualcomm QCA8075 90000.mdio-1:00: attached PHY driver (mii_bus:phy_addr=90000.mdio-1:00, irq=POLL)
[29 Jan 2026, 22:37:17 UTC] kern.info: [   23.004622] Qualcomm QCA8075 90000.mdio-1:01: attached PHY driver (mii_bus:phy_addr=90000.mdio-1:01, irq=POLL)
[29 Jan 2026, 22:37:17 UTC] kern.info: [   23.074692] Qualcomm QCA8075 90000.mdio-1:02: attached PHY driver (mii_bus:phy_addr=90000.mdio-1:02, irq=POLL)
[29 Jan 2026, 22:37:17 UTC] kern.info: [   23.144466] Qualcomm QCA8075 90000.mdio-1:03: attached PHY driver (mii_bus:phy_addr=90000.mdio-1:03, irq=POLL)
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.156114] Aquantia AQR114C 90000.mdio-1:08: attached PHY driver (mii_bus:phy_addr=90000.mdio-1:08, irq=POLL)
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.157313] **********************************************************
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.165052] * NSS Data Plane driver
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.171525] **********************************************************
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.188662] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.188714] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.193944] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe65 hci version 0x110 quirks 0x0000808000000010
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.200681] xhci-hcd xhci-hcd.1.auto: irq 42, io mem 0x08a00000
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.210114] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.215890] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.221438] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.229354] hub 1-0:1.0: USB hub found
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.235640] hub 1-0:1.0: 1 port detected
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.239565] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.243658] hub 2-0:1.0: USB hub found
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.251656] hub 2-0:1.0: 1 port detected
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.262777] Loading modules backported from Linux version v6.18.7-0-g5dfbc5357
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.262821] Backport generated by backports.git c8a37ce
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.277887] NET: Registered PF_QIPCRTR protocol family
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.390664] PPP generic driver version 2.4.2
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.391484] NET: Registered PF_PPPOX protocol family
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.427705] ath11k c000000.wifi: ipq6018 hw1.0
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.427740] ath11k c000000.wifi: FW memory mode: 1
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.535952] remoteproc remoteproc0: powering up cd00000.remoteproc
[29 Jan 2026, 22:37:17 UTC] kern.info: [   25.553654] remoteproc remoteproc0: Booting fw image IPQ6018/q6_fw.mdt, size 7340
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.530812] remoteproc remoteproc0: remote processor cd00000.remoteproc is now up
[29 Jan 2026, 22:37:17 UTC] kern.warn: [   26.532176] ath11k c000000.wifi: qmi fail to get qcom,m3-dump-addr, ignore m3 dump mem req
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.537908] ath11k c000000.wifi: chip_id 0x0 chip_family 0x4 board_id 0xff soc_id 0xffffffff
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.537944] ath11k_pci 0000:01:00.0: BAR 0 [mem 0x20400000-0x205fffff 64bit]: assigned
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.545489] ath11k c000000.wifi: fw_version 0x25008f8e fw_build_timestamp 2024-03-01 03:54 fw_build_id WLAN.HK.2.5.0.1-03982-QCAHKSWPL_SILICONZ-3
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.554110] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.576022] ath11k_pci 0000:01:00.0: MSI vectors: 16
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.580970] ath11k_pci 0000:01:00.0: qcn9074 hw1.0
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.586177] ath11k_pci 0000:01:00.0: FW memory mode: 2
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.778263] mhi mhi0: Requested to power ON
[29 Jan 2026, 22:37:17 UTC] kern.info: [   26.778316] mhi mhi0: Power on setup success
[29 Jan 2026, 22:37:17 UTC] kern.info: [   27.494099] mhi mhi0: Wait for device to enter SBL or Mission mode
[29 Jan 2026, 22:37:17 UTC] user.info: [   27.547668] kmodloader: done loading kernel modules from /etc/modules.d/*
[29 Jan 2026, 22:37:17 UTC] kern.info: [   27.562182] ath11k_pci 0000:01:00.0: chip_id 0x0 chip_family 0x0 board_id 0xff soc_id 0xffffffff
[29 Jan 2026, 22:37:17 UTC] kern.info: [   27.562238] ath11k_pci 0000:01:00.0: fw_version 0x290b8862 fw_build_timestamp 2024-09-23 10:51 fw_build_id
[29 Jan 2026, 22:37:17 UTC] kern.warn: [   28.073184] ath11k_pci 0000:01:00.0: htt event 48 not handled
[29 Jan 2026, 22:37:17 UTC] user.notice: dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
[29 Jan 2026, 22:37:17 UTC] user.notice: dnsmasq: Allowing 127.0.0.0/8 responses
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: started, version 2.91 cachesize 1000
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: DNS service limited to local subnets
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: UBus support enabled: connected to system bus
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for test
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for onion
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for localhost
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for local
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for invalid
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for bind
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for lan
[29 Jan 2026, 22:37:17 UTC] daemon.warn: dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: read /etc/hosts - 12 names
[29 Jan 2026, 22:37:17 UTC] daemon.info: dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 0 names
[29 Jan 2026, 22:37:17 UTC] authpriv.info: dropbear[1968]: Not backgrounding
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: vrf
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: bonding
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: 8021ad
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: 8021q
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: macvlan
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: veth
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: bridge
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: Network device
[29 Jan 2026, 22:37:18 UTC] user.notice: : Added device handler type: tunnel
[29 Jan 2026, 22:37:18 UTC] daemon.notice: wpa_supplicant[2121]: Successfully initialized wpa_supplicant
[29 Jan 2026, 22:37:19 UTC] daemon.notice: procd: /etc/rc.d/S50uhttpd: 4+0 records in
[29 Jan 2026, 22:37:19 UTC] daemon.notice: procd: /etc/rc.d/S50uhttpd: 4+0 records out
[29 Jan 2026, 22:37:19 UTC] daemon.notice: hostapd: Set MLD config: [ ]
[29 Jan 2026, 22:37:19 UTC] daemon.notice: hostapd: Reload all interfaces
[29 Jan 2026, 22:37:19 UTC] daemon.notice: wpa_supplicant[2121]: Set MLD config: [ ]
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.100266] br-lan: port 1(lan1) entered blocking state
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.100311] br-lan: port 1(lan1) entered disabled state
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.104390] nss-dp 3a001000.dp1 lan1: entered allmulticast mode
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.109680] nss-dp 3a001000.dp1 lan1: entered promiscuous mode
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'lan' is enabled
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'lan' is setting up now
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'lan' is now up
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.130456] br-lan: port 2(lan2) entered blocking state
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.130500] br-lan: port 2(lan2) entered disabled state
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.134564] nss-dp 3a001200.dp2 lan2: entered allmulticast mode
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.139891] nss-dp 3a001200.dp2 lan2: entered promiscuous mode
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.148776] br-lan: port 3(lan3) entered blocking state
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.151512] br-lan: port 3(lan3) entered disabled state
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.156729] nss-dp 3a001400.dp3 lan3: entered allmulticast mode
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.162027] nss-dp 3a001400.dp3 lan3: entered promiscuous mode
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.171361] br-lan: port 4(lan4) entered blocking state
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.173649] br-lan: port 4(lan4) entered disabled state
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.178875] nss-dp 3a001600.dp4 lan4: entered allmulticast mode
[29 Jan 2026, 22:37:19 UTC] kern.info: [   30.184236] nss-dp 3a001600.dp4 lan4: entered promiscuous mode
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/luci-splash reload dependency on /etc/config/firewall
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'loopback' is enabled
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'loopback' is setting up now
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'loopback' is now up
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/qos reload dependency on /etc/config/firewall
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/miniupnpd reload dependency on /etc/config/firewall
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'wan' is enabled
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'wan6' is enabled
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Network device 'lo' link is up
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: Interface 'loopback' has link connectivity
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio0 (2491): wifi-scripts: Starting
[29 Jan 2026, 22:37:19 UTC] user.notice: firewall: Reloading firewall due to ifup of lan (br-lan)
[29 Jan 2026, 22:37:19 UTC] daemon.notice: hostapd: Set new config for phy phy0:
[29 Jan 2026, 22:37:19 UTC] daemon.notice: wpa_supplicant[2121]: Set new config for phy phy0
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/odhcpd reload dependency on /etc/config/dhcp
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio0 (2491): command failed: Not supported (-95)
[29 Jan 2026, 22:37:19 UTC] daemon.notice: wpa_supplicant[2121]: Set new config for phy phy0
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/dhcp reload dependency on /etc/config/network
[29 Jan 2026, 22:37:19 UTC] daemon.notice: hostapd: Set new config for phy phy0:
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio0 (2491): wifi-scripts: Configuring 'phy0' txantenna: 4294967295, rxantenna: 4294967295 distance: 0
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio1 (2547): wifi-scripts: Starting
[29 Jan 2026, 22:37:19 UTC] daemon.notice: hostapd: Set new config for phy phy1:
[29 Jan 2026, 22:37:19 UTC] daemon.notice: wpa_supplicant[2121]: Set new config for phy phy1
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/network reload dependency on /etc/config/wireless
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio1 (2547): command failed: Not supported (-95)
[29 Jan 2026, 22:37:19 UTC] daemon.notice: wpa_supplicant[2121]: Set new config for phy phy1
[29 Jan 2026, 22:37:19 UTC] daemon.notice: hostapd: Set new config for phy phy1:
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio1 (2547): wifi-scripts: Configuring 'phy1' txantenna: 4294967295, rxantenna: 4294967295 distance: 0
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up non-init /etc/config/fstab reload handler: /sbin/block mount
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio2 (2590): wifi-scripts: Starting
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/system reload trigger for non-procd /etc/init.d/led
[29 Jan 2026, 22:37:19 UTC] daemon.notice: hostapd: Set new config for phy phy2:
[29 Jan 2026, 22:37:19 UTC] daemon.notice: wpa_supplicant[2121]: Set new config for phy phy2
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio2 (2590): command failed: Not supported (-95)
[29 Jan 2026, 22:37:19 UTC] daemon.notice: wpa_supplicant[2121]: Set new config for phy phy2
[29 Jan 2026, 22:37:19 UTC] daemon.notice: hostapd: Set new config for phy phy2:
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/luci_statistics reload dependency on /etc/config/system
[29 Jan 2026, 22:37:19 UTC] daemon.notice: netifd: radio2 (2590): wifi-scripts: Configuring 'phy2' txantenna: 4294967295, rxantenna: 4294967295 distance: 0
[29 Jan 2026, 22:37:19 UTC] daemon.notice: wpa_supplicant[2121]: Start pending MLD interfaces
[29 Jan 2026, 22:37:19 UTC] user.notice: ucitrack: Setting up /etc/config/dhcp reload dependency on /etc/config/system
[29 Jan 2026, 22:37:19 UTC] daemon.notice: procd: /etc/rc.d/S96led: setting up led LAN1-PORT-LINK
[29 Jan 2026, 22:37:19 UTC] daemon.notice: procd: /etc/rc.d/S96led: setting up led LAN1-PORT-TRAFFIC
[29 Jan 2026, 22:37:19 UTC] daemon.notice: procd: /etc/rc.d/S96led: setting up led LAN2-PORT-LINK
[29 Jan 2026, 22:37:19 UTC] daemon.notice: procd: /etc/rc.d/S96led: setting up led LAN2-PORT-TRAFFIC
[29 Jan 2026, 22:37:20 UTC] daemon.notice: procd: /etc/rc.d/S96led: setting up led LAN3-PORT-LINK
[29 Jan 2026, 22:37:20 UTC] daemon.notice: procd: /etc/rc.d/S96led: setting up led LAN3-PORT-TRAFFIC
[29 Jan 2026, 22:37:20 UTC] daemon.notice: procd: /etc/rc.d/S96led: setting up led LAN4-PORT-LINK
[29 Jan 2026, 22:37:20 UTC] daemon.notice: procd: /etc/rc.d/S96led: setting up led LAN4-PORT-TRAFFIC
[29 Jan 2026, 22:37:20 UTC] daemon.notice: procd: /etc/rc.d/S99bootcount: Boot count sucessfully reset to zero.
[29 Jan 2026, 22:37:20 UTC] daemon.info: procd: - init complete -
[29 Jan 2026, 22:37:22 UTC] kern.info: [   33.284837] nss-dp 3a001600.dp4 lan4: PHY Link up speed: 1000
[29 Jan 2026, 22:37:22 UTC] kern.info: [   33.285368] br-lan: port 4(lan4) entered blocking state
[29 Jan 2026, 22:37:22 UTC] kern.info: [   33.289578] br-lan: port 4(lan4) entered forwarding state
[29 Jan 2026, 22:37:22 UTC] daemon.notice: netifd: Network device 'lan4' link is up
[29 Jan 2026, 22:37:22 UTC] daemon.notice: netifd: bridge 'br-lan' link is up
[29 Jan 2026, 22:37:22 UTC] daemon.notice: netifd: Interface 'lan' has link connectivity
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: exiting on receipt of SIGTERM
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: started, version 2.91 cachesize 1000
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: DNS service limited to local subnets
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: UBus support enabled: connected to system bus
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq-dhcp[1]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for test
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for onion
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for localhost
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for local
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for invalid
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for bind
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: using only locally-known addresses for lan
[29 Jan 2026, 22:37:23 UTC] daemon.warn: dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: read /etc/hosts - 12 names
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
[29 Jan 2026, 22:37:23 UTC] daemon.info: dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
[29 Jan 2026, 22:37:24 UTC] daemon.warn: odhcpd[2256]: No default route present, setting ra_lifetime to 0!
[29 Jan 2026, 22:37:24 UTC] daemon.warn: odhcpd[2256]: rfc9096: br-lan: piofile updated
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.1.184 48:65:ee:15:3f:37
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.184 48:65:ee:15:3f:37
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq[1]: read /etc/hosts - 12 names
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq[1]: read /tmp/hosts/odhcpd.hosts.lan - 2 names
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.1.184 48:65:ee:15:3f:37
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.184 48:65:ee:15:3f:37
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq[1]: read /etc/hosts - 12 names
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq[1]: read /tmp/hosts/odhcpd.hosts.lan - 2 names
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.184 48:65:ee:15:3f:37
[29 Jan 2026, 22:37:27 UTC] daemon.info: dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.184 48:65:ee:15:3f:37 trudeautop
[29 Jan 2026, 22:37:38 UTC] authpriv.info: dispatcher.uc: luci: accepted login on / for root from 192.168.1.184
[29 Jan 2026, 22:37:39 UTC] daemon.warn: odhcpd[2256]: No default route present, setting ra_lifetime to 0!
[29 Jan 2026, 22:37:55 UTC] daemon.warn: odhcpd[2256]: No default route present, setting ra_lifetime to 0!
[29 Jan 2026, 22:37:58 UTC] kern.err: [   69.604226] Aquantia AQR114C 90000.mdio-1:08: failed to find FW file marvell/AQR114C.cld (-110)
[29 Jan 2026, 22:37:58 UTC] kern.err: [   69.604288] Aquantia AQR114C 90000.mdio-1:08: probe with driver Aquantia AQR114C failed with error -110
[29 Jan 2026, 22:37:58 UTC] user.info: [   69.624523] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[29 Jan 2026, 22:42:02 UTC] authpriv.info: dropbear[3584]: Child connection from 192.168.1.184:38946
[29 Jan 2026, 22:42:02 UTC] authpriv.notice: dropbear[3584]: Auth succeeded with blank password for 'root' from 192.168.1.184:38946

Expected behaviour

WAN port should work when firmware is present and loaded.

Additional info

Seems to have been fixed in another fork, see: https://github.com/PIPIPIG233666/openwrt-ipq/

Diffconfig

Terms

  • I am reporting an issue for OpenWrt, not an unsupported fork.

Activity

  1. RobotRoss
    added
    bugissue report with a confirmed bug
    to-triage
    bug-report
    on Feb 2, 2026

  2. ben-temp commented on Feb 2, 2026

    @ben-temp
    ben-temp
    on Feb 2, 2026

    Can confirm experiencing the same issue

  3. testuser7 commented on Feb 2, 2026

    @testuser7
    testuser7
    on Feb 2, 2026
    Contributor

    @RobotRoss Do you have access to the serial console? It looks like the firmware was not loaded in the u-boot.

    What does the command return?

    hexdump -C -n 0x5330 /dev/mtd9

  4. RobotRoss commented on Feb 2, 2026

    @RobotRoss
    RobotRoss
    on Feb 2, 2026
    ContributorAuthor

    @RobotRoss Do you have access to the serial console? It looks like the firmware was not loaded in the u-boot.

    What does the command return?

    hexdump -C -n 0x5330 /dev/mtd9

    Do you mean the physical serial header on the motherboard or will the SSH console suffice?

  5. testuser7 commented on Feb 2, 2026

    @testuser7
    testuser7
    on Feb 2, 2026
    Contributor

    Do you mean the physical serial header on the motherboard or will the SSH console suffice?

    To find out why it's not working, you need a physical connection. But for the hexdump command, you use ssh.

  6. github-actions commented on Feb 2, 2026

    @github-actions
    github-actionsbot
    on Feb 2, 2026 – with GitHub Actions

    Invalid Version reported. Snapshot
    Is this from a clean repository?

  7. github-actions commented on Feb 2, 2026

    @github-actions
    github-actionsbot
    on Feb 2, 2026 – with GitHub Actions

    Invalid Release reported. Snapshot
    Is this from a clean repository?

  8. github-actions commented on Feb 2, 2026

    @github-actions
    github-actionsbot
    on Feb 2, 2026 – with GitHub Actions

    Invalid Target/Subtarget reported. ipq60xx/generic
    Is this from a supported device?

  9. github-actions
    added
    invalid
    and removed
    to-triage
    bug-report
    on Feb 2, 2026

  10. RobotRoss commented on Feb 3, 2026

    @RobotRoss
    RobotRoss
    on Feb 3, 2026
    ContributorAuthor

    @RobotRoss Do you have access to the serial console? It looks like the firmware was not loaded in the u-boot.

    What does the command return?

    hexdump -C -n 0x5330 /dev/mtd9

    Updated OP to fix GHA complaints.

    Log requested as follows:

    root@OpenWrt:~# hexdump -C -n 0x5330 /dev/mtd9
hexdump: invalid number '0x5330'

    Given the failure of the above, I ran the command past an AI (may or may not be helpful), it seemed to think that it had a problem with the hex number given, and gave me a decimal number to try instead:

    root@OpenWrt:~# hexdump -C -n 21296 /dev/mtd9
00000000  13 00 00 00 03 00 00 00  00 00 00 00 00 00 00 44  |...............D|
00000010  02 00 06 00 02 00 06 00  02 00 06 44 00 00 00 00  |...........D....|
00000020  02 00 06 44 00 00 00 00  00 00 00 00 00 00 00 00  |...D............|
00000030  05 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000040  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00004030  05 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00004040  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00005320  00 00 00 00 00 00 00 00  08 20 00 10 00 04 00 24  |......... .....$|
00005330

  11. RobotRoss commented on Feb 3, 2026

    @RobotRoss
    RobotRoss
    on Feb 3, 2026
    ContributorAuthor

    So, I've done some more bashing with an LLM (Claude in my case) and it's managed to come up with a workaround:

    cat > /etc/rc.local << 'EOF'
#!/bin/sh

# Wait for the initial probe to complete and fail
( sleep 75

  logger -t aquantia-fix "Starting Aquantia firmware fix"
  
  if [ -f /lib/firmware/marvell/AQR114C.cld ]; then
    logger -t aquantia-fix "Firmware found, binding device to driver"
    
    # Try to unbind first (will fail if not bound, that's OK)
    echo "90000.mdio-1:08" > /sys/bus/mdio_bus/drivers/Aquantia\ AQR114C/unbind 2>/dev/null || true
    sleep 1
    
    # Bind the device to trigger probe with firmware now available
    echo "90000.mdio-1:08" > /sys/bus/mdio_bus/drivers/Aquantia\ AQR114C/bind 2>&1 | logger -t aquantia-fix
    
    # Wait for firmware to fully load (takes ~30 seconds)
    sleep 35
    
    # Restart the WAN interface to attach the PHY
    logger -t aquantia-fix "Restarting WAN interface to attach PHY"
    ip link set wan down
    sleep 2
    ip link set wan up
    
    logger -t aquantia-fix "Fix complete - WAN should be operational"
  else
    logger -t aquantia-fix "ERROR: Firmware file not found!"
  fi
) &

exit 0
EOF

    chmod +x /etc/rc.local

    The problem seems to be that not all MR7500s come with working firmware in the chip's on board memory (hence the failure to load firmware at 2sec), and the Linksys firmware will always load from the filesystem.

    OpenWRT will try this, however it will always fail because the fallback load-from-filesystem happens before the filesystem is ready, leading to the -110 timeout error when trying to load the firmware from /lib/firmware/marvell/AQR114C.cld (See failure at 69 seconds)

    The workaround just rebinds the WAN after the filesystem is fully ready, meaning the firmware can load from the FS.

    Log:

    [29 Jan 2026, 23:03:32 UTC] kern.err: [   69.603860] Aquantia AQR114C 90000.mdio-1:08: failed to find FW file marvell/AQR114C.cld (-110)
[29 Jan 2026, 23:03:32 UTC] kern.err: [   69.603921] Aquantia AQR114C 90000.mdio-1:08: probe with driver Aquantia AQR114C failed with error -110
[29 Jan 2026, 23:03:32 UTC] user.info: [   69.624009] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[29 Jan 2026, 23:03:41 UTC] authpriv.info: dropbear[3522]: Child connection from 192.168.1.184:59946
[29 Jan 2026, 23:03:41 UTC] authpriv.notice: dropbear[3522]: Auth succeeded with blank password for 'root' from 192.168.1.184:59946
[29 Jan 2026, 23:04:08 UTC] user.notice: aquantia-fix: Starting Aquantia firmware fix
[29 Jan 2026, 23:04:08 UTC] user.notice: aquantia-fix: Firmware found, binding device to driver
[29 Jan 2026, 23:04:11 UTC] kern.info: [  108.567589] Aquantia AQR114C 90000.mdio-1:08: loading firmware version 'v5.6.5 Cybertan Divo 090221 14:43:44' from 'FS'
[29 Jan 2026, 23:04:24 UTC] kern.info: [  121.424286] hwmon hwmon10: temp1_input not attached to any thermal zone
[29 Jan 2026, 23:04:28 UTC] kern.warn: [  125.625675] uniphy autoneg time out!
[29 Jan 2026, 23:04:59 UTC] user.notice: aquantia-fix: Restarting WAN interface to attach PHY
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.431727] ------------[ cut here ]------------
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.431765] called from state READY
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.435470] WARNING: CPU: 2 PID: 3631 at drivers/net/phy/phy.c:1620 0xffffffc08057acd4
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.438632] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_inet ath11k_pci(O) ath11k_ahb(O) ath11k(O) pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211(O) cfg80211(O) slhc qrtr_smd qrtr_mhi qrtr qmi_helpers(O) nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 mhi libcrc32c crc_ccitt compat(O) leds_pwm leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom qca_nss_dp(O) qca_ssdk(O) gpio_button_hotplug(O) ext4 mbcache jbd2 sha512_generic sha512_arm64 seqiv sha3_generic jitterentropy_rng drbg michael_mic hmac geniv cmac aquantia crc_itu_t crc32c_generic
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.497212] CPU: 2 UID: 0 PID: 3631 Comm: ip Tainted: G           O       6.12.66 #0
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.519448] Tainted: [O]=OOT_MODULE
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.527339] Hardware name: Linksys MR7500 (DT)
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.530554] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.535070] pc : 0xffffffc08057acd4
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.541920] lr : 0xffffffc08057acd4
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.545393] sp : ffffffc088383af0
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.548866] x29: ffffffc088383af0 x28: ffffff8002940000 x27: ffffff8003af5600
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.552345] x26: 0000000000401002 x25: ffffff80036e0000 x24: ffffff8003af5610
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.559464] x23: 0000000000001003 x22: ffffff80036e0000 x21: ffffffc088383bc0
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.566581] x20: ffffff80036e0000 x19: ffffff80035b9000 x18: ffffffc080bbb600
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.573700] x17: ffffffbf9f3aa000 x16: ffffffc080cf8000 x15: 000000000000015b
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.580816] x14: 000000000000015b x13: 00000000ffffffea x12: ffffffc080c135a8
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.587936] x11: ffffffc080bbb600 x10: ffffffc080c13600 x9 : 0000000000000001
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.595054] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : 0000000000000001
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.602171] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.609290] x2 : ffffff801fece338 x1 : ffffffbf9f3aa000 x0 : 0000000000000017
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.616407] Call trace:
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.623517]  0xffffffc08057acd4
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.625776]  0xffffffc078ec424c [qca_nss_dp@0000000032e3d111+0x6000]
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.628906]  0xffffffc0806738f4
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.635498]  0xffffffc08067b410
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.638361]  0xffffffc08067b550
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.641487]  0xffffffc08075f754
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.644612]  0xffffffc080763250
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.647736]  0xffffffc080648ff4
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.650861]  0xffffffc08020b1a4
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.653986]  0xffffffc080020f5c
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.657111]  0xffffffc080021040
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.660237]  0xffffffc0808b2248
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.663361]  0xffffffc0808b27c0
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.666486]  0xffffffc080011558
[29 Jan 2026, 23:04:59 UTC] kern.warn: [  156.669612] ---[ end trace 0000000000000000 ]---
[29 Jan 2026, 23:05:01 UTC] user.notice: aquantia-fix: Fix complete - WAN should be operational
[29 Jan 2026, 23:05:06 UTC] kern.warn: [  163.545297] uniphy autoneg time out!
[29 Jan 2026, 23:05:06 UTC] daemon.notice: netifd: Network device 'wan' link is up
[29 Jan 2026, 23:05:06 UTC] daemon.notice: netifd: Interface 'wan' has link connectivity
[29 Jan 2026, 23:05:06 UTC] daemon.notice: netifd: Interface 'wan' is setting up now
[29 Jan 2026, 23:05:06 UTC] daemon.notice: netifd: Interface 'wan6' has link connectivity
[29 Jan 2026, 23:05:06 UTC] daemon.notice: netifd: Interface 'wan6' is setting up now
[29 Jan 2026, 23:05:06 UTC] kern.info: [  163.844197] nss-dp 3a003000.dp5-syn wan: PHY Link up speed: 1000

    This at least gets as far as getting the WAN interface running and link UP, however it doesn't pass traffic. (e.g. ping 8.8.8.8 returns

    root@OpenWrt:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: Network unreachable

    )

  12. 141 remaining items

  13. RobotRoss commented on Oct 1, 2026

    @RobotRoss
    RobotRoss
    on Oct 1, 2026
    ContributorAuthor

    That's in 25.12.5 then, yes? Combined with the instructions I've seen so far, is UART or even a snapshot image necessary at all then? Can OpenWrt 25.12.5 be installed from the OEM Web GUI, then the AQR114C driver be installed via OpenWrt SSH, and that's it?

    Stable can be installed from the OEM GUI, yes - although you're better off going for snapshot until the next stable release if you want a working WAN port.

  14. daigennki commented on Oct 1, 2026

    @daigennki
    daigennki
    on Oct 1, 2026

    Okay, and will I still need to use UART if I want to install snapshot with WAN port support?

  15. RobotRoss commented on Oct 1, 2026

    @RobotRoss
    RobotRoss
    on Oct 1, 2026
    ContributorAuthor

    Okay, and will I still need to use UART if I want to install snapshot with WAN port support?

    UART is not needed to flash the WAN port firmware. That can be done via scp and SSH.

  16. howels commented on Oct 1, 2026

    @howels
    howels
    on Oct 1, 2026

    Okay, and will I still need to use UART if I want to install snapshot with WAN port support?

    Yeah, you don't need UART, it's just a bit easier to see what's going on and fix a bad flash. The plastic clips are really tough to open on this one too.

  17. howels commented on Oct 5, 2026

    @howels
    howels
    on Oct 5, 2026

    While we are looking at this device, the Linksys product page states that the USB port:

    Supports up to 1100mA current draw

    Is there a U-Boot setting or GPIO we need to toggle to output power on the USB port? I can't light up an old USB2 flash drive currently, everything needs an external powered USB hub to function.

  18. RobotRoss commented on Oct 5, 2026

    @RobotRoss
    RobotRoss
    on Oct 5, 2026
    ContributorAuthor

    While we are looking at this device, the Linksys product page states that the USB port:

    Supports up to 1100mA current draw

    Is there a U-Boot setting or GPIO we need to toggle to output power on the USB port? I can't light up an old USB2 flash drive currently, everything needs an external powered USB hub to function.

    I've just tried on my end, and the port is outputting power. (I've plugged a battery charger into it, put a battery on charge and power has not been lost), and I have also tested a USB memory stick which also seems to be working.

    Worth noting that a lot of USB drive LEDs are activity based, so won't light up unless the drive is mounted and actively having read / writes being done.

    I did notice a bug with the device template though which caused the USB port LED on the router itself to not work due to a typo in the device definition, meaning the kmod was not being pulled in as it should. Fixed in #25634

  19. howels commented on Oct 5, 2026

    @howels
    howels
    on Oct 5, 2026

    While we are looking at this device, the Linksys product page states that the USB port:

    Supports up to 1100mA current draw

    Is there a U-Boot setting or GPIO we need to toggle to output power on the USB port? I can't light up an old USB2 flash drive currently, everything needs an external powered USB hub to function.

    I've just tried on my end, and the port is outputting power. (I've plugged a battery charger into it, put a battery on charge and power has not been lost), and I have also tested a USB memory stick which also seems to be working.

    Worth noting that a lot of USB drive LEDs are activity based, so won't light up unless the drive is mounted and actively having read / writes being done.

    I did notice a bug with the device template though which caused the USB port LED on the router itself to not work due to a typo in the device definition, meaning the kmod was not being pulled in as it should. Fixed in #25634

    I'm looking at lsusb output here - it doesn't seem to get power and init anything unless I use a USB3 hub. This is on OpenWrt SNAPSHOT, r36741-edd23eb01e

  20. RobotRoss commented on Oct 5, 2026

    @RobotRoss
    RobotRoss
    on Oct 5, 2026
    ContributorAuthor

    I'm looking at lsusb output here - it doesn't seem to get power and init anything unless I use a USB3 hub. This is on OpenWrt SNAPSHOT, r36741-edd23eb01e

    Unable to reproduce on my end. This is the output before, and after plugging a memory stick in:

    root@OpenWrt-Linksys:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
root@OpenWrt-Linksys:~# [ 1196.680327] usb 1-1: new high-speed USB device number 2 using xhci-hcd
root@OpenWrt-Linksys:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05dc:a81d Lexar Media, Inc. LJDTT16G [JumpDrive 16GB]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

    OpenWrt SNAPSHOT, r36661-061397968d

  21. howels commented on Oct 5, 2026

    @howels
    howels
    on Oct 5, 2026

    I'm looking at lsusb output here - it doesn't seem to get power and init anything unless I use a USB3 hub. This is on OpenWrt SNAPSHOT, r36741-edd23eb01e

    Unable to reproduce on my end. This is the output before, and after plugging a memory stick in:

    root@OpenWrt-Linksys:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
root@OpenWrt-Linksys:~# [ 1196.680327] usb 1-1: new high-speed USB device number 2 using xhci-hcd
root@OpenWrt-Linksys:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05dc:a81d Lexar Media, Inc. LJDTT16G [JumpDrive 16GB]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

    OpenWrt SNAPSHOT, r36661-061397968d

    Update to latest snapshot and problem has gone away, I can't explain why. It is working now.

  22. David-Grim commented on Oct 5, 2026

    @David-Grim
    David-Grim
    on Oct 5, 2026

    Not related to the topic at hand, but a word of caution for those flashing thinking there will be no issues with their router: I am experiencing some serious kernel level memory leaks probably stemming from the ath11k driver set. 6GHz wifi is just a no go. After setting up wifi I experienced frequent lockups needing to reboot my main router every 20-30 minutes. After turning 6GHz off there was still a crazy amount of ram being used starting off at about 80% available, then shooting up to 95% after about 15-20 minutes. I thought it could be the ath11k_pci driver, as rmmod'ing it took my usage from ~85% threshold to ~55% in an instant, but unfortunately usage still slowly crept up. I determined its not something in the userland after monitoring via top over several hours. Don't flash and expect stability. I'm being forced to return to OEM firmware until the issues can be resolved.

  23. daigennki commented on Oct 5, 2026

    @daigennki
    daigennki
    on Oct 5, 2026

    Not related to the topic at hand, but a word of caution for those flashing thinking there will be no issues with their router: I am experiencing some serious kernel level memory leaks probably stemming from the ath11k driver set. 6GHz wifi is just a no go. After setting up wifi I experienced frequent lockups needing to reboot my main router every 20-30 minutes. After turning 6GHz off there was still a crazy amount of ram being used starting off at about 80% available, then shooting up to 95% after about 15-20 minutes. I thought it could be the ath11k_pci driver, as rmmod'ing it took my usage from ~85% threshold to ~55% in an instant, but unfortunately usage still slowly crept up. I determined its not something in the userland after monitoring via top over several hours. Don't flash and expect stability. I'm being forced to return to OEM firmware until the issues can be resolved.

    I already mentioned this in the OpenWrt forum thread, but that would certainly explain the high memory usage. I'm not even using the Wifi features at the moment and it's using around 280 MiB (~75%), which seems like a lot for a device like this. I believe that may have caused an OOM crash/hang at one point when I was messing around with extra packages like Adblock.

  24. RobotRoss commented on Oct 5, 2026

    @RobotRoss
    RobotRoss
    on Oct 5, 2026
    ContributorAuthor

    Not related to the topic at hand, but a word of caution for those flashing thinking there will be no issues with their router: I am experiencing some serious kernel level memory leaks probably stemming from the ath11k driver set. 6GHz wifi is just a no go. After setting up wifi I experienced frequent lockups needing to reboot my main router every 20-30 minutes. After turning 6GHz off there was still a crazy amount of ram being used starting off at about 80% available, then shooting up to 95% after about 15-20 minutes. I thought it could be the ath11k_pci driver, as rmmod'ing it took my usage from ~85% threshold to ~55% in an instant, but unfortunately usage still slowly crept up. I determined its not something in the userland after monitoring via top over several hours. Don't flash and expect stability. I'm being forced to return to OEM firmware until the issues can be resolved.

    Likely caused by this or a similar issue: #24154 , with associated fix: #21495

    I believe the issue is that ath11k reserves 2 RAM regions on this router due to the twin chip design (on-SoC for 2.4/5GHz, separate chip for 6GHz), effectively doubling it's RAM footprint.

  25. RobotRoss commented on Oct 6, 2026

    @RobotRoss
    RobotRoss
    on Oct 6, 2026
    ContributorAuthor

    I have also found another cause for about 130MB RAM loss, due to an ath11k misconfiguration caused by a regression.

    I have submitted a PR which fixes the problem for this and other affected devices: https://github.com/openwrt/openwrt/pull/25659

  26. daigennki commented on Oct 9, 2026

    @daigennki
    daigennki
    on Oct 9, 2026

    Back to the main topic: Where do we now stand regarding making the WAN port work out of the box? Do we know yet if the "CRC skip" fix is upstreamable?

  27. howels commented on Oct 9, 2026

    @howels
    howels
    on Oct 9, 2026

    27. Back to the main topic: Where do we now stand regarding making the WAN port work out of the box? Do we know yet if the "CRC skip" fix is upstreamable?

    Process for acq114 firmware extraction, header rewrite and nvmem flash is documented now. That is enough to bring up the device with 2.5Gb port.
    Full fix requires someone to upstream the file to linux-firmware with relevant licenses attached.
    Perhaps the nvmem process could be improved with an initramfs tool to scan fw partition and fix missing headers in-place?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Official ImageSupported Devicebugissue report with a confirmed bugrelease/25.12pull request/issue targeted (also) for OpenWrt 24.10 releasetarget/qualcommaxpull request/issue for qualcommax target

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions