Thanks! What is the difference/benefit of your build with the latest snapshot? I am running the 6.6 kernel snapshot for a while now. It is pretty stable. The only thing i notice is high memory usage and transmit power limited to 5dbm.
Includes these two PR:
TX power is not limited.
2 Likes
thanks! I can already confirm that the TX power went from 5 to 16 dbm. I will report back on memory usage in the coming days.
This new build doesn't seem to work for my MX4200 V1. I did the sysupgrade, ran /lib/firmware/ath11k/IPQ8074/hw2.0/cal-ahb-c000000.wifi.bin and then rebooted. My radios seem to be stuck in a disabled state:
phy0-ap0 ESSID: "XXX"
Access Point: D8:EC:5E:XX:XX:XX
Mode: Master Channel: unknown (unknown) HT Mode: NOHT
Center Channel 1: unknown 2: unknown
Tx-Power: 0 dBm Link Quality: unknown/70
Signal: unknown Noise: unknown
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/ax/n
Hardware: embedded [Qualcomm Atheros IPQ8074]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
phy1-ap0 ESSID: "XXX"
Access Point: D8:EC:5E:XX:XX:XX
Mode: Master Channel: unknown (unknown) HT Mode: NOHT
Center Channel 1: unknown 2: unknown
Tx-Power: 0 dBm Link Quality: unknown/70
Signal: unknown Noise: unknown
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ax/b/g/n
Hardware: embedded [Qualcomm Atheros IPQ8074]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
phy2-ap0 ESSID: "XXX"
Access Point: D8:EC:5E:XX:XX:XX
Mode: Master Channel: unknown (unknown) HT Mode: NOHT
Center Channel 1: unknown 2: unknown
Tx-Power: 0 dBm Link Quality: unknown/70
Signal: unknown Noise: unknown
Bit Rate: unknown
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/ax/n
Hardware: embedded [Qualcomm Atheros IPQ8074]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy2
Ah, this is probably my issue. Need to work out what the correct option path config is.
Edit: actually these look like they did get updated to be kernel 6.6 compatible so don't think this is my issue.
Edit2: did a full wipe of config and that seems to have resolved the issue.
After 2 days, my 2 dumb AP's are running stable. Memory usage seems to fluctuate with a lowest of around 3% (based on what I have seen).
AP details
AP1:
AP2:
thanks.
Just put these on my 2 AP and will monitor.
@lytr - With https://github.com/openwrt/openwrt/pull/14512 merged there should not be power limitations in the snapshot ? Are there any significant differences left between custom builds and snapshots ?
Thanks again to everybody bringing life in those devices with good hardware and limited software!
Yes, there will be no more power limitations. There is no difference in builds.
1 Like
Any help reverting firmware is appreciated.
I Installed the latest openwrt snapshot to MX4200V1 on Partition 1 - from www.openwrt.org/toh/linksys/mx4200_v1_and_v2.
Partition 2 still has the Linksys retail firmware.
I can power cycle to switch between the two. ( www.linksys.com/support-article?articleNum=49557 )
Figured out I had to install LUCI from SSH to get 19.168.1.1 to work from browser as I installed a openwrt snapshot and not a stable version. ( www.openwrt.org/docs/guide-user/luci/luci.essentials)
Linksys MX4200V1 retail firmware = https://downloads.linksys.com/support/assets/firmware/FW_MX4200_1.0.12.209581_prod.img
Q1. Can I restore the Linksys retail firmware MX4200V1 from luci.
(luci/admin/system/flash--> Flash new firmware image)
Q2. What is the SSH commands to install this Linksys retail firmware back onto partition 1 ?
You can install the OEM image in the same way as the factory image:
mtd -r -e kernel -n write FW_MX4200_1.0.13.210200_prod.img kernel
or
mtd -r -e alt_kernel -n write FW_MX4200_1.0.13.210200_prod.img alt_kernel
depending on which partition you want to install.
1 Like
I think you could just boot the Linksys firmware and flash retail from it. That will flash the other partition where you have OpenWrt, not the one that you are using. That's precisely what dual boot is for. If the newly flashed partition doesn't boot, it would revert back to the partition where you flashed from which is working.
2 Likes
innovara booting from the Linksys firmware and flash retail from it
This is the method for me. I have done it twice and am now comfortable with this method.
Thank you innovara & lytr
1 Like
hey guys, i have a community fibre router and i need to keep isp firmware, is it possible to use openwrt and keep isp firmware on it too
The v2 model
Anyone know when the PR to officially support the mx4200 will be merged or is it still WIP? Talking about this: https://github.com/openwrt/openwrt/pull/14474
Well read the last 2-3 comments, it is pretty obvious.
It is, but you don't have any client connected to it
oh, also for this router should i enable packet steering?
and should i enable WLAN roaming?