I understand that you shouldn't use an outdated version of OpenWRT, but I recently purchased a Gli.net MT-6000 router and it comes with version OpenWRT 21.02.
Until a stable version of OpenWRT is released for the router, I will need to continue with the factory firmware because my family members use the internet and the current snapshot versions of OpenWRT for my device have a bug caused by the MT76 drive that makes the 2.4GHz connection quite unstable.
Would there be any possibility of using the luci-app-sqm package in this version?
When I try to install it, this error appears:
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.4.238-1-2807c6c1a8b577598c79e9d34e93071d) for kmod-ipt-ipopt
* pkg_hash_fetch_best_installation_candidate: Packages for kmod-ipt-ipopt found, but incompatible with the architectures configured
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.4.238-1-2807c6c1a8b577598c79e9d34e93071d) for kmod-ipt-conntrack-extra
* pkg_hash_fetch_best_installation_candidate: Packages for kmod-ipt-conntrack-extra found, but incompatible with the architectures configured
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.4.238-1-2807c6c1a8b577598c79e9d34e93071d) for kmod-ipt-raw
* pkg_hash_fetch_best_installation_candidate: Packages for kmod-ipt-raw found, but incompatible with the architectures configured
* pkg_hash_check_unresolved: cannot find dependency kernel (= 5.4.238-1-2807c6c1a8b577598c79e9d34e93071d) for kmod-sched-cake
* pkg_hash_fetch_best_installation_candidate: Packages for kmod-sched-cake found, but incompatible with the architectures configured
* satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-sqm:
* kernel (= 5.4.238-1-2807c6c1a8b577598c79e9d34e93071d)
* opkg_install_cmd: Cannot install package luci-app-sqm.
The OEM version is not a normal OpenWrt, but gl.inet's own fork of OpenWrt with some underlying modifications. You need to download kernel related packages directly from gi.inet.
The MT6000 comes with a very recent fork of 23.05 and they can certainly use SQM from that factory firmware they have their own repo. Source: I have one.
Also the OpenWrt snapshots work fantastic. First thing I did was sysupgrade to one and haven’t looked back.
The log file I put in the post was because I tried to install the packages on the glinet system itself.
The latest beta version (v4.5.7) uses the old version of OpenWRT because they are using proprietary drivers in it due to the 2.4 GHz compatibility issue with the MT76 driver. You can follow the full discussion here: https://forum.gl-inet.com/t/flint-2-gl-mt6000-bug-reports-collective-thread/35608
Regarding the latest version of OpenWRT, I have a problem with the 2.4 GHz network involving constant disconnections and the impossibility of reaching more than 100 mbps on the devices connected to it.
Wow there are people with some strange issues with this device. It's been perfect for me, had a 30-day uptime before flashing a new snapshot last week for the new mt76 drivers. Odd they went back to the 21.02 build but good to know. This person said theirs keeps rebooting can't imagine how that's possible it's been rock solid with so many added packages running for me.
It appears you are using firmware that is not from the official OpenWrt project.
For the OEM firmware, gl-inet would be your contact, we don't know about it, nor what kind of features they provide (offer to install).
Once you install vanillar OpenWrt, we could help you.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
You may find that the best options are:
- Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
- Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
- Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
This topic was automatically closed after 27 hours. New replies are no longer allowed.