OpenWRT repositories

Hi, I would like to update adblock to the last version, but in the gl.inet repositories there is an old version.
Which architecture should I choose from Index of /releases/packages-18.06/ for the model GL-MT300N-V2 and for the other models to have a more updated repository from OpenWRT? I’m interested to update only the packages repositories.



Thanks. After a bit of research I found the answer. We need to add this repository to get more updated packages from OpenWrt that the ones from gl.inet.
That way we can get adblock and may other updates for our packages.

While the OpenWrt package repos are usually compatible, anything that requires kernel modules will require retrieval of the “kmod” packages from the matching GL.iNet repo. There is also the possibility that the libraries that the package call do not have the same version (“ABI”) and they won’t work.

When working with GL-Inet’s OpenWRT, be mindful of which branch one is working on.

  • develop is not current - and if you clone to their OpenWRT, this is the default release is also a bit stale
  • 18.06-S1300 is specific to convexa-S
  • 18.06 - again, a bit stale, but supports products up to a certain point
  • 19.07 - current thru Brume, seems to be the most active… sometimes doesn’t build.
  • release - not current

So how to sync to GL-iNet’s git?

git clone
cd openwrt/
git checkout openwrt-19.07
make distclean
git pull && ./scripts/feeds update -a && ./scripts/feeds install -a && make menuconfig
make defconfig
make download
make V=s

Brume doesn’t build just yet - seeing errors below

Applying /home/sfx/builds/glinet/openwrt/target/linux/mvebu/patches-4.14/533-arm64-add-leds-configure-for-mv1000.patch using plaintext: 
patching file drivers/pinctrl/mvebu/pinctrl-armada-37xx.c
Hunk #1 FAILED at 170.
1 out of 1 hunk FAILED -- saving rejects to file drivers/pinctrl/mvebu/pinctrl-armada-37xx.c.rej
patching file drivers/leds/leds-glmv1000.c
patching file drivers/leds/Makefile
patching file drivers/leds/Kconfig
Patch failed! Please fix /home/sfx/builds/glinet/openwrt/target/linux/mvebu/patches-4.14/533-arm64-add-leds-configure-for-mv1000.patch!
Makefile:21: recipe for target '/home/sfx/builds/glinet/openwrt/build_dir/target-aarch64_cortex-a53_musl/linux-mvebu_cortexa53/linux-4.14.151/.prepared_6c1ccc56de1dbb7417e059aad24d397d' failed
make[4]: *** [/home/sfx/builds/glinet/openwrt/build_dir/target-aarch64_cortex-a53_musl/linux-mvebu_cortexa53/linux-4.14.151/.prepared_6c1ccc56de1dbb7417e059aad24d397d] Error 1
make[4]: Leaving directory '/home/sfx/builds/glinet/openwrt/target/linux/mvebu'
Makefile:13: recipe for target 'compile' failed
make[3]: *** [compile] Error 2
make[3]: Leaving directory '/home/sfx/builds/glinet/openwrt/target/linux'
time: target/linux/compile#7.96#2.85#8.91
target/Makefile:23: recipe for target 'target/linux/compile' failed
make[2]: *** [target/linux/compile] Error 2
make[2]: Leaving directory '/home/sfx/builds/glinet/openwrt'
target/Makefile:18: recipe for target '/home/sfx/builds/glinet/openwrt/staging_dir/target-aarch64_cortex-a53_musl/stamp/.target_compile' failed
make[1]: *** [/home/sfx/builds/glinet/openwrt/staging_dir/target-aarch64_cortex-a53_musl/stamp/.target_compile] Error 2
make[1]: Leaving directory '/home/sfx/builds/glinet/openwrt'
/home/sfx/builds/glinet/openwrt/include/ recipe for target 'world' failed
make: *** [world] Error 2

Not urgent for me at the moment, other things I have to do next week…

1 Like

BTW - there are warnings building against 19.07

WARNING: Makefile 'package/feeds/gli_pub/luci-app-chinadns/Makefile' has a dependency on 'redsocks2', which does not exist
WARNING: Makefile 'package/feeds/gli_pub/luci-app-chinadns/Makefile' has a dependency on 'ShadowVPN', which does not exist
WARNING: Makefile 'package/feeds/luci/luci-app-cifsd/Makefile' has a dependency on 'cifsd-tools', which does not exist
WARNING: Makefile 'package/feeds/luci/luci-proto-modemmanager/Makefile' has a dependency on 'modemmanager', which does not exist
WARNING: Makefile 'package/feeds/gli_pub/shadowsocks-libev/Makefile' has a build dependency on 'libpcre', which does not exist
WARNING: Makefile 'package/feeds/gli_pub/shadowsocks-libev/Makefile' has a build dependency on 'libmbedtls', which does not exist

Just as an FYI.

@alzhao - asking someone to clean things up (prune/merge) on the GL-Inet Github openwrt would be very helpful.

1 Like

Confirming that target/linux/mvebu/patches-4.14/533-arm64-add-leds-configure-for-mv1000.patch does not apply cleanly.

--- drivers/pinctrl/mvebu/pinctrl-armada-37xx.c	2019-06-05 20:11:44.098047406 -0700
+++ drivers/pinctrl/mvebu/pinctrl-armada-37xx.c	2019-06-05 20:14:39.122050335 -0700
@@ -170,10 +170,10 @@
 	PIN_GRP_EXTRA("uart2", 9, 2, BIT(1) | BIT(13) | BIT(14) | BIT(19),
 		      BIT(1) | BIT(13) | BIT(14), BIT(1) | BIT(19),
 		      18, 2, "gpio", "uart"),
-	PIN_GRP_GPIO("led0_od", 11, 1, BIT(20), "led"),
-	PIN_GRP_GPIO("led1_od", 12, 1, BIT(21), "led"),
-	PIN_GRP_GPIO("led2_od", 13, 1, BIT(22), "led"),
-	PIN_GRP_GPIO("led3_od", 14, 1, BIT(23), "led"),
+	//PIN_GRP_GPIO("led0_od", 11, 1, BIT(20), "led"),
+	//PIN_GRP_GPIO("led1_od", 12, 1, BIT(21), "led"),
+	//PIN_GRP_GPIO("led2_od", 13, 1, BIT(22), "led"),
+	//PIN_GRP_GPIO("led3_od", 14, 1, BIT(23), "led"),

Now on PIN_GRP_GPIO2, so there is the possibility that there is more needed than just a re-reference to the removal, although the introduction of drivers/leds/leds-glmv1000.c may be independent of the default pin controller.

1 Like

Will check and clean ASAP.