MT6000 custom build with LuCi and some optimization - kernel 6.6.x

I would dearly like the fq-codel related improvements here to make it back to openwrt and linux mainline. regrettably I don't do much dev anymore....

3 Likes

I agree, but @pesa1234 is the dev in this context. I would also love to see a lot of this great work make it back into mainline OpenWrt and Linux! :slight_smile:

1 Like

Ok, I will try to send a pr on fq_codel tuning but I don't think will be applied.

5 Likes

BTW any ideas why various Mediatek patches that you’re using weren’t accepted into the mainline kernel/hostapd/… or are they only backported by you?

1 Like

@pesa1234 @dtaht, I have been running stock 23.05.5 firmware on my GL-MT6000. Wi-fi performance is rather mediocre, verging on crummy in my production environment. (Testing with Crusader was pretty good in a test setup, 3 ft from the router.)

But sitting in my usual chairs in my home, the 5GHz is not so bad, but the 2.4GHz is worse.

Is it likely that the newest custom build would work better? What are the differences?

And what's a link to the latest? Any tricks I should know about installing it? Many thanks.

just pull his latest build and sysupgrade -n

1 Like

That's harder work (the -n) - the MT6000 is now my production router... I'll get around to it soon-ish, when I can afford to risk being off the air for a bit. Thanks.

I kept my previous configuration in tact when I switched over to Pesa's builds. Dave's suggestion of the -n approach is probably the safest, in general, but was not needed from my experience.

Just keep around your latest 23.05.5 image and a current sys-backup. Then, upgrade to Pesa's build. If anything doesn't look or feel right, just revert back to 23.05.5. This device is extremely forgiving.

1 Like

Release 24.10 is being finalized.
Is it easy to get a list of patches or commits in this build that did not make it to 24.10?
Or are they different builds altogether (different kernel)?

I have to ask - which changes those would be?

subjectively saying - If one looks at the Filogic 830/MT6000 building off Master, it's quite nice as-is - if one turns off the SW/HW offloads, Cake SQM is very effective - there's plenty of horsepower on the SoC even for a 1Gb symmetric connection on the WAN side...

2 Likes

And why is that?

The SW/HW offloads bypass any kernel level AQM/SQM...

3 Likes

I don't want to upgrade to the new kernel yet, since I have software that might not work and I don't want to take the risk. I want to stay on 23.05.5, but can I take advantage of the newer mt76 updates? And if so, does someone have clear instructions on how? I'm a relative newbie compiling things for OpenWrt but I've done it once or twice.

Just follow Failsafe instructions, and choose stable branch

@pesa1234 - where does your patchest live? I will try to get them into linux mainline

1 Like

Thanks -- I thought I'd use Failsafe's build container (https://github.com/Fail-Safe/openwrt-pesa1234-build), but I don't see where to select the stable branch in that process.

edit: Oh, I think I get it. It's git checkout v23.05.5 as I get to the later steps, right?

Perhaps I'm misunderstanding your goal, so feel free to correct any assumptions I have gotten wrong.

You're trying to use Pesa's build on your MT6000, but you want to be running the OpenWrt "stable" build. So you're trying to build using the container image I put together, but within the container your hope is to switch away from one of Pesa's "next-r4.x.x.mtk" branches to "v23.05.5" and build from that.

If I have all that right, you're not going to end up where you think you're headed. Pesa's build is very intentionally using the latest kernel and is kept in sync with OpenWrt SNAPSHOT. A lot, if not all, of the patches that @pesa1234 incorporates into the build are reliant on Kernel 6.6 and aren't necessarily backported to prior Kernel versions.

All that said, you can always follow the guidance I gave to @richb-hanover-priv here:

If something doesn't work as expected on Pesa's build, just revert back to 23.05.5 and restore your configuration there.

1 Like

Ah, ok, yes that's exactly what I was trying to do. If I can get your build container working, I might try that but otherwise will sit tight. I don't want to be tied to pesa1234's build and the fixed selection of packages. If I can build them myself, though, that's different.

2 Likes
https://github.com/pesa1234/openwrt.git

There my repo.

next-rx.x.x.mtk have my and mtk patches for MT6000.

Other repo are for testing on archerC6 or raspberry or WRT1900ACS
Main - 23.05 etc.. are forked from and are equal to std openwrt.