OpenWrt support for Linksys MX4200

kyogithub · 2024-11-19T05:28:02.648Z

@arix I'm stuck in building a custom image since APK was implemented, I included some extra packages but the image generation fails at:

image1856×354 12 KB

Do you have any hints? With the old opkg I used to build this same extra packages and other image with even more.

BabaBlackship-Da · 2024-11-19T18:55:11.819Z

I am intrigued…. You gave me my next project

kyogithub · 2024-11-20T03:03:04.322Z

We're going to stable?

image980×536 30.5 KB

MysteriousApple35 · 2024-11-20T17:41:44.005Z

Hey friends,

I installed @lytr's MX4300 build a couple months ago. I installed this version here: https://github.com/testuser7/openwrt/releases/tag/qualcommax-2540ea6
I installed it only on one partition.

Everything has been great so far, especially after enabling some of the additional settings that people have mentioned here. However, I am looking to update to the latest version provided by Lytr, which I believe is this one.

I've seen conflicting answers, so I decided to ask here and hope I can get the right answers:

I only installed OpenWRT on one partition, how can I fix this so that I can do a sysupgrade to the latest version provided by Lytr? I already tried doing a sysupgrade, but it failed and reverted back, so I'm guessing I need to install OpenWRT on the other partition. Which version do I install?
If I sysupgrade with this snapshot, I know the config will be wiped, but will IP addresses of devices change? Only asking because I have some devices on the network where if the IP changes it's a pain to setup correctly again.
If I decided to try a different build, say from Arix, would #2 also happen?
How can I update packages so that I make sure I'm staying up-to-date with security patches and features?

Thank you all for very much for your help, especially those of you who are creating these builds!

kyogithub · 2024-11-21T01:14:24.204Z

well, it seems that I was to eager to test, days later and fork updated it compiles just fine

FanOfOpenWRT · 2024-11-21T01:23:19.933Z

I suspect this is related somehow to the OPK vs APK package manager change...

luci-app-statistics and collectd stopped working, and I can't figure out what's wrong.

Screenshot 2024-11-20 202038947×360 21.5 KB

When I open the Graphs page in Luci, all I see is:

Screenshot 2024-11-20 2022491411×359 20.4 KB

The only log entry that mentions collectd:

Wed Nov 20 20:17:48 2024 daemon.err collectd[2432]: Initialization complete, entering read-loop.

kyogithub · 2024-11-21T01:47:13.764Z

AFIK you can sysupgrade any boot partition, even with different versions, so your case could be another issue, maybe the other partition is still on Linksys ver, in that case you need first install factory then sysupgrade it
The config should not be erased, there is a checkbox for that. some additional packages or configs may be erased if they are not in the image and in the retain list.
Maybe, but even if not, they recommend start from zero when you change from NSS to FOSS and vice versa
As for now, this images are from snapshot so... we can update the whole image for now or just wait a while, as far I saw this router is near to become part of the stable branch, and when that happens there are tools to upgrade base, auc, or just apps, with apk.

vochong · 2024-11-21T01:48:46.309Z

You may want to report APK-related issues in the following thread.
Otherwise, they may not get proper attention from devs:

The future is now: opkg vs apk Talk about Documentation

apk has replaced opkg in main branch SNAPSHOT builds The apk switchover is an ongoing process, and still has several issues to resolve. If you do not wish to deal with the issues inherent in bleeding edge snapshots, then it is strongly suggested that you move to 24.10-SNAPHOT (https://downloads.openwrt.org/releases/24.10-SNAPSHOT/targets/). With @slh's posting of @aparcar's status report on the APK project (How can I tell opkg to prioritize a repo when a package if found in multiple repos?…

HypervisorX · 2024-11-21T11:36:50.096Z

I'm pretty desperate to get some more flash storage available to use on the mx4300.
Does anyone know what else is required besides this modification mentioned by qosmio to gain access to access the ubi_concat partition?

I compiled a firmware after applying the git diff mentioned by qosmio, and then flashed the resulting sysupgrade.bin image via the standard luci firmware upgrade ui. I don't see a new ubi_concat partition anywhere. Is there something I'm missing, perhaps a different flash method required, or am I just looking in the wrong place?
ubinfo just shows the usual single ubi device with 2 ubi volumes for rootfs and rootfs_data, with 0 available erase blocks and total available eraseblocks of roughly 150MiB so it definitely isn't including that extra roughly 500MiB to be gained from app2/app2_data. I was assuming id find a second ubi device with the ubi_concat partition but no such luck.

After backing them up, I even tried erasing the app2 and app2_data mtd partitions and rebooting in case the useless data in them was causing an issue but it didn't seem to change anything.

I also tried doing a make distclean and recompiling just to be sure some leftover compilation artifacts weren't what was giving me issues.

If anyone could point me in the right direction id be grateful. Thanks

private · 2024-11-21T11:59:23.085Z

I'm having an issue with a custom build on the homeWrk version of this router and was wondering if its only me. I'm completely new to this so I might be my fault. I made the custom build so I could get access to the apk package manager.

The issue is that after installing any package, all other attempts to install anything fails with the below error. If I uninstall the first package, I'm allowed to install another.

root@OpenWrt:~# apk add docker-compose
ERROR: unable to select packages:
  adblock-fast-1.1.2-r10:
    error: uninstallable
    arch: all
    satisfies: luci-app-adblock-fast-1.1.2-r10[adblock-fast]
  luci-app-adblock-fast-1.1.2-r10:
    error: uninstallable
    arch: all
    satisfies: world[luci-app-adblock-fast]
root@OpenWrt:~# apk add adb
ERROR: unable to select packages:
  adblock-fast-1.1.2-r10:
    error: uninstallable
    arch: all
    satisfies: luci-app-adblock-fast-1.1.2-r10[adblock-fast]
  luci-app-adblock-fast-1.1.2-r10:
    error: uninstallable
    arch: all
    satisfies: world[luci-app-adblock-fast]

I just used random packages for the test.

The other interesting thing is that if I do multiple packages at once, that works.

root@OpenWrt:~# apk add adblock-fast
(1/1) Installing adblock-fast (1.1.2-r10)
Executing adblock-fast-1.1.2-r10.post-install
OK: 36 MiB in 183 packages
root@OpenWrt:~# apk add luci-theme-openwrt-2020
ERROR: unable to select packages:
  adblock-fast-1.1.2-r10:
    error: uninstallable
    arch: all
    satisfies: world[adblock-fast]
root@OpenWrt:~# apk del adblock-fast
(1/1) Purging adblock-fast (1.1.2-r10)
Executing adblock-fast-1.1.2-r10.pre-deinstall
Stopping adblock-fast service... OK
Removing rc.d symlink for adblock-fast... OK
OK: 36 MiB in 182 packages
root@OpenWrt:~# apk add luci-theme-openwrt-2020
(1/1) Installing luci-theme-openwrt-2020 (24.322.80622~a403707)
Executing luci-theme-openwrt-2020-24.322.80622~a403707.post-install
OK: 36 MiB in 183 packages
root@OpenWrt:~# apk add adblock-fast
ERROR: unable to select packages:
  luci-theme-openwrt-2020-24.322.80622~a403707:
    error: uninstallable
    arch: all
    satisfies: world[luci-theme-openwrt-2020]
root@OpenWrt:~# apk del luci-theme-openwrt-2020
(1/1) Purging luci-theme-openwrt-2020 (24.322.80622~a403707)
Executing luci-theme-openwrt-2020-24.322.80622~a403707.pre-deinstall
OK: 36 MiB in 182 packages
root@OpenWrt:~# apk del luci-theme-openwrt-2020 adblock-fast
OK: 36 MiB in 182 packages
root@OpenWrt:~# apk add luci-theme-openwrt-2020 adblock-fast
(1/2) Installing adblock-fast (1.1.2-r10)
Executing adblock-fast-1.1.2-r10.post-install
(2/2) Installing luci-theme-openwrt-2020 (24.322.80622~a403707)
Executing luci-theme-openwrt-2020-24.322.80622~a403707.post-install
OK: 36 MiB in 184 packages
root@OpenWrt:~#

sppmaster · 2024-11-21T12:12:06.393Z

Better ask for help here

The future is now: opkg vs apk Talk about Documentation

apk has replaced opkg in main branch SNAPSHOT builds The apk switchover is an ongoing process, and still has several issues to resolve. If you do not wish to deal with the issues inherent in bleeding edge snapshots, then it is strongly suggested that you move to 24.10-SNAPHOT (https://downloads.openwrt.org/releases/24.10-SNAPSHOT/targets/). With @slh's posting of @aparcar's status report on the APK project (How can I tell opkg to prioritize a repo when a package if found in multiple repos?…

Sheik · 2024-11-21T21:57:41.536Z

I am trying to see where you see that this PR got merged into the main openwrt...

The PR here:

github.com/openwrt/openwrt

qualcommax: ipq807x: add support for Linksys MX4300 (LN1301)

openwrt:main ← testuser7:mx4300

opened 09:42PM - 04 Aug 24 UTC

testuser7

+651 -213

Hardware specification: ======== SoC: Qualcomm IPQ8174 Flash: 1GB (Micron MT2…9F8G08ABBCAH4 or AMD/Spansion S34MS08G2) RAM: 2GB (2x Kingston B5116ECMDXGJD or ESMT M15T2G16128A DDR3L) Ethernet: 4x 10/100/1000Mbps (Qualcomm QCA8075) WiFi1: 5GHz ax 2x2 (Qualcomm QCN5054 + Skyworks SKY85755-11) - channels 36-64 (low band) WiFi2: 2.4GHz ax 2x2 (Qualcomm QCN5024 + Skyworks SKY85340-11) WiFi3: 5GHz ax 4x4 (Qualcomm QCN5054 + Skyworks SKY85755-11) - channels 100-177 (high band) LED: 1x RGB status (NXP PCA9633) USB: 1x USB 3.0 Button: WPS, Reset Flash instructions: ======== 1. Manually upgrade firmware using openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin image. More details can be found here: https://support.linksys.com/kb/article/6564-en/ After first boot check actual partition: - `fw_printenv -n boot_part` and install firmware on second partition using command in case of 2: - `mtd -r -e kernel -n write openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin kernel` and in case of 1: - `mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin alt_kernel` 2. Installation using serial connection from OEM firmware (default login: root, password: admin): - `fw_printenv -n boot_part` In case of 2: - `flash_erase /dev/mtd21 0 0` - `nandwrite -p /dev/mtd21 openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin` or in case of 1: - `flash_erase /dev/mtd23 0 0` - `nandwrite -p /dev/mtd23 openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin` After first boot install firmware on second partition: - `mtd -r -e kernel -n write openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin kernel` or: - `mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin alt_kernel` 3. Installation from initramfs image using USB drive: Put the initramfs image on the USB drive: - `dd bs=1M if=openwrt-qualcommax-ipq807x-linksys_mx4300-initramfs-uImage.itb of=/dev/sdX` Stop u-boot and run: - `usb start && usbboot $loadaddr 0 && bootm $loadaddr` Write firmware to the flash from initramfs: - `mtd -e kernel -n write openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin kernel` and: - `mtd -r -e alt_kernel -n write openwrt-qualcommax-ipq807x-linksys_mx4300-squashfs-factory.bin alt_kernel` 4. Back to the OEM firmware: - `mtd -e kernel -n write FW_MX4300_1.0.4.215382_prod.img kernel` and: - `mtd -r -e alt_kernel -n write FW_MX4300_1.0.4.215382_prod.img alt_kernel` 5. USB recovery: Put the initramfs image on the USB: - `dd bs=1M if=openwrt-qualcommax-ipq807x-linksys_mx4300-initramfs-uImage.itb of=/dev/sdX` Set u-boot env: - `fw_setenv bootusb 'usb start && usbboot $loadaddr 0 && bootm $loadaddr'` - `fw_setenv bootcmd 'run bootusb; if test $auto_recovery = no; then bootipq; elif test $boot_part = 1; then run bootpart1; else run bootpart2; fi'`

Remains Open and unmerged...

It looks like it got stuck about the time you mention (Oct 6), with robimarko's comment here:

github.com/openwrt/openwrt

Comment by robimarko - qualcommax: ipq807x: add support for Linksys MX4300 (LN1301)

openwrt:main ← testuser7:mx4300

@testuser7 Is there any way to avoid adding yet another `cmdline` hack that we t…hen have to carry essentially forever?

Which corresponds to the "Call to arms" here for this patch by asd111333:

OpenWrt support for Linksys MX4200 For Developers

I will say that the crux is the kernel patch I wrote to dynamically patch the bootargs at boot time. We can replace the patch with bootstrapping. There is already a script I posted above that can do this. We just need someone to refine it, put it in the right place, and test it.

armadiLL0 · 2024-11-21T22:45:02.150Z

Thanks for the response, I been playing around with it, still trying to figure this out. But I believe this is mostly me and not doing it properly.

kyogithub · 2024-11-22T01:36:21.665Z

You're right. I'm not that into Git, so I thought that as soon as they pushed the PR, it was already approved. My mistake

Sheik · 2024-11-22T01:51:35.801Z

Oh, no problem! I was excited that I missed something, and they had it merged!
I still have hopes that it will eventually get merged.

FanOfOpenWRT · 2024-11-23T09:40:06.147Z

Should I be concerned that all of @arix's OSS builds for MX4300 have been retroactively deleted?

Previously, there were OSS and NSS builds here, now there appear to be only NSS builds, and all previous OSS builds are also gone:

GitHub

Releases · arix00/openwrt-mx4300

This repository is a mirror of https://git.openwrt.org/openwrt/openwrt.git It is for reference only and is not active for check-ins. We will continue to accept Pull Requests here. They will be mer...

HypervisorX · 2024-11-23T11:32:26.327Z

looks like maybe they were just cleaning up the old releases or something and the github actions for generating the release files hadn't finished running yet. Never used any of arix's builds myself but this appears to be what you were looking for if you want OSS from that repo.

moh1t · 2024-11-23T12:43:49.230Z

I have mx4300 variant of LN1301 and I’m on arix’s foss build (qualcommax-foss-3d852fb kernel 6.6.59) released around November 8th.

5Ghz wifi iperf performance is not that great around 300-400 mbps on 2x2 802.11ax 80Mhz width ipad or iphone with 1100 mbps+ link speed, even 5 feet away from the router. Have tried all channels (DFS and non-DFS), channel widths and tx power combinations. I have 4 units and it’s the same with all of them. Is there something else I can do to improve throughput? Does NSS build provide higher wifi throughput?

mag2352 · 2024-11-23T13:11:26.835Z

On FOSS, I was experiencing device disconnects repeatedly, this was on one of arix’s FOSS builds that were deleted on GitHub. So in my use case, NSS was actually more stable than the FOSS build (keep in mind this very well could have been user error, but I figured it was not worth my time staying on FOSS). On NSS with iperf, I can hit 800-900 mbps on my iPhone when in the same room as the router. On my laptop, I can get damn near Ethernet speeds on a file transfer to my media server (around 930 mbps).

HypervisorX · 2024-11-23T14:21:14.604Z

got the issue I was having figured out, so I've got all that extra space available. Turns out my issue was just that I was missing a required kernel patch.