Latest arm_cortex-a7_neon-vfpv4 packages seem broken

Hello psherman,
thank you for the answer, which unfortunately does not solve my problem. So far I was able to install updates without problems and adapt my system to my needs. This and Open Source are the reason why I use OpenWRT. Since yesterday this is no longer possible. Updates are offered for almost all installed packages, some of which end in non-resolvable dependencies (e.g. libiwinfo20200105). After resetting to default values it works for the basics.

Thank you and best regards
Brummbeere

@brummbeere - I think it might be good to clarify a few points

If you look through some of the links provided and search through the forums, you will see that OpenWrt's opkg package manager does not have the mechanisms in place to ensure that the upgrade will succeed. There are people working on improving the robustness of the upgrade system, but it was never designed for blindly updating all packages, and it also cannot update certain core packages without causing the system to fail. This has always been the case, but you are lucky that you have not experienced problems until this point.

Maybe you could explain exactly what you actually need to update using this method and why? In many cases, people believe that they should update just because an updated package is available. This is usually not necessary unless there is a specific feature addition, bug fix, or security patch that is critical for the continued operation of the system -- and like I said, this is rarely actually necessary. Beyond that, blindly updating all packages is the main issue here. If you have a few specific packages that you wish to upgrade, it may be okay to do so.

Yes, OpenWrt is open source. Nothing has changed in this regard.

Actually, the risk of upgraded packages causing major system issues has been around for a very long time -- this is just the first time you have encountered such issues. Again, just because there are updates does not mean that it is necessary or wise to install them, unless you know exactly what the update does and why you need it.

Yes. Because the reset to defaults removes the updated packages and all of the core packages are self-consistent. You can still install new packages to add functionality, but upgrading is usually not recommended.

The recommendation for upgrades has always been to wait for a maintenance release (for example 19.07.1 > 19.07.2) and flash a complete image. If there is a critical patch that must be applied before a new stable release can be built, you will see it here. If you must have the latest updates and be on the bleeding edge at all times, you should consider using snapshots (linked above by @lleachii), and to update your snapshot build regularly by flashing the newest snapshot (not upgrading packages) -- but understand that snapshots are not always stable and also make installing packages more difficult over time (snapshots are, by definition, a moving target). Or you can continue to upgrade specific/selected packages on a given build, but you need to understand that there is a risk involved, especially if you upgrade all packages.

1 Like

Nice idea but the reality is if I need to install dnsmasq-full onto a vanilla build, the problem occurs.

1 Like

If you're using a stable release build (without having performed any package upgrades) followed by using opkg update and opkg install and you experience this problem, that suggests that your problem may be different. I'd recommend opening a separate thread (if you haven't already done so) to try to address this problem.

EDIT: added opkg update to be consistent with @lleachii's comment below -- the package lists must be updated before the opkg system can install anything.

1 Like

Just to be clear:

  • release build reset to default
  • opkg update
  • then opkg install

I do this all the time to "upgrade"packages (since I flash snapshots - and use all packages bundled at the time, which is sightly different from the update methods y'all seek on stable builds.)

1 Like

I have the same problem with GL-B1300, bricked after upgrade. uboot recovered with
http://downloads.openwrt.org/releases/19.07.2/targets/ipq40xx/generic/openwrt-19.07.2-ipq40xx-generic-glinet_gl-b1300-squashfs-sysupgrade.bin
But now ALL packages in opkg repository are from new build 11 May.
https://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/
How i can install additonal luci modules, wireguard, upnp without risk of bricking device again?

I even tried to find package causing a problem.... Install one package and reboot....

Regards
Weasel

Correct. If they weren't you'd have mismatched kmods, packages, kernels, etc...likely causing the identical issue of a soft-bricked router.

:confused:

I literally just upgraded my router an hour ago and installed Wireguard...

  • Sysupgrade new snapshot
  • opkg update
  • opkg install mod-udptunnel4 kmod-udptunnel6 kmod-wireguard wireguard-tools wireguard luci-proto-wireguard luci-app-wireguard

What's the big problem?

1 Like

@ElectricWeasel -
From a fresh install (or reset to defaults)

opkg update
then
opkg install <package 1> <package 2> etc

just don't use opkg upgrade and you should be fine

1 Like

I did exacly as you typed, rebooted, no wireguard status on overview - was available before. Also I need DDNS so typed
opkg install ddns-scripts ddns-scripts_nsupdate luci-app-ddns
Now Overview stopped to work at all.


no single opkg upgrade command

Regards
Weasel

Can you show the output?

What does this mean???

If I understand this, it means you didn't type what I said.

Explain this. How do you make it appear on a fresh install?

:bulb:
Whoa...and I just realized your original problem causing a brick.

Router configuration was restored from backup.
opkg install kmod-udptunnel4 kmod-udptunnel6 kmod-wireguard wireguard-tools wireguard
then
opkg install luci-proto-wireguard luci-app-wireguard
reboot, no wireguard status on Overwiew
anyway to make this sense i need DDNS
opkg install ddns-scripts ddns-scripts_nsupdate luci-app-ddns
reboot, Overview broken as on picture above

I'm not suprized because now part of luci is in different version - is updated frequentely as i observed.
By "was" i mean in the morning with couple of other services like miniupnpd, WakeOnLan, collectd, fwknopd

Regards
Weasel

I just tested the install of the 3 items you mentioned, everything is working just fine on my installation.

Maybe Wireguard is not there because you didn't reinstall it.

To be clear, rebooting is not the same as resetting to defaults. Please try that first. (System > Backup / Flash Firmware > Reset to Defaults). Then configure the very basics, and try installing the packages you just said caused problems.

1 Like

If you have any misconfigured items in the backup, that could potentially cause issues.

Did you first run opkg update?

What do you mean by this?

Yup, basically you have no DNS resolution.
If you go to an SSH session, you can ping 8.8.8.8, but not google.com.

@ psherman
Thank you for the update instructions. I have indeed installed the updates because they were offered. Surely the belief in important security patches as with Linux distributions plays a role for me. I will probably wait for the next maintenance release.

1 Like

Nope, backup was taken from configuration that was solid for a weeks
If you want whole output:

|       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 19.07.2, r10947-65030d81f3
 -----------------------------------------------------
root@OpenWrt:~# opkg install mod-udptunnel4 kmod-udptunnel6 kmod-wireguard wireguard-tools wireguard
Unknown package 'mod-udptunnel4'.
Installing kmod-udptunnel6 (4.14.171-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/targets/ipq40xx/generic/kmods/4.14.171-1-fa00c1231ac7d7840ec6ffe62dcad926/kmod-udptunnel6_4.14.171-1_arm_cortex-a7_neon-vfpv4.ipk
Installing kmod-wireguard (4.14.171+0.0.20190702-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/targets/ipq40xx/generic/kmods/4.14.171-1-fa00c1231ac7d7840ec6ffe62dcad926/kmod-wireguard_4.14.171%2b0.0.20190702-1_arm_cortex-a7_neon-vfpv4.ipk
Installing kmod-udptunnel4 (4.14.171-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/targets/ipq40xx/generic/kmods/4.14.171-1-fa00c1231ac7d7840ec6ffe62dcad926/kmod-udptunnel4_4.14.171-1_arm_cortex-a7_neon-vfpv4.ipk
Installing wireguard-tools (1.0.20200319-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/base/wireguard-tools_1.0.20200319-1_arm_cortex-a7_neon-vfpv4.ipk
Installing libmnl0 (1.0.4-2) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/base/libmnl0_1.0.4-2_arm_cortex-a7_neon-vfpv4.ipk
Installing ip-tiny (5.6.0-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/base/ip-tiny_5.6.0-1_arm_cortex-a7_neon-vfpv4.ipk
Installing wireguard (1.0.20200506-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/base/wireguard_1.0.20200506-1_arm_cortex-a7_neon-vfpv4.ipk
Configuring libmnl0.
Configuring kmod-udptunnel4.
Configuring kmod-udptunnel6.
Configuring kmod-wireguard.
Configuring ip-tiny.
Configuring wireguard-tools.
Configuring wireguard.
Collected errors:
 * opkg_install_cmd: Cannot install package mod-udptunnel4.
root@OpenWrt:~# opkg install mod-udptunnel
Unknown package 'mod-udptunnel'.
Collected errors:
 * opkg_install_cmd: Cannot install package mod-udptunnel.
root@OpenWrt:~# opkg install kmod-udptunnel4
Package kmod-udptunnel4 (4.14.171-1) installed in root is up to date.
root@OpenWrt:~# opkg install luci-proto-wireguard luci-app-wireguard
Installing luci-proto-wireguard (git-20.069.54281-3fb8e3d) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/luci/luci-proto-wireguard_git-20.069.54281-3fb8e3d_all.ipk
Installing luci-app-wireguard (git-20.069.54281-3fb8e3d) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/luci/luci-app-wireguard_git-20.069.54281-3fb8e3d_all.ipk
Configuring luci-proto-wireguard.
Configuring luci-app-wireguard.
root@OpenWrt:~# Connection to openwrt closed by remote host.
Connection to openwrt closed.

Thats wireguard (BTW. wireguard tunneling is working just luci interface is broken)

DDNS

root@OpenWrt:~# opkg install ddns-scripts ddns-scripts_nsupdate luci-app-ddns
Installing ddns-scripts (2.7.8-20) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/packages/ddns-scripts_2.7.8-20_all.ipk
Installing ddns-scripts_nsupdate (2.7.8-20) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/packages/ddns-scripts_nsupdate_2.7.8-20_all.ipk
Installing libopenssl1.1 (1.1.1g-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/base/libopenssl1.1_1.1.1g-1_arm_cortex-a7_neon-vfpv4.ipk
Installing zlib (1.2.11-3) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/base/zlib_1.2.11-3_arm_cortex-a7_neon-vfpv4.ipk
Installing libatomic1 (7.5.0-2) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/targets/ipq40xx/generic/packages/libatomic1_7.5.0-2_arm_cortex-a7_neon-vfpv4.ipk
Installing librt (1.1.24-2) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/targets/ipq40xx/generic/packages/librt_1.1.24-2_arm_cortex-a7_neon-vfpv4.ipk
Installing libuv1 (1.34.2-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/packages/libuv1_1.34.2-1_arm_cortex-a7_neon-vfpv4.ipk
Installing bind-libs (9.16.2-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/packages/bind-libs_9.16.2-1_arm_cortex-a7_neon-vfpv4.ipk
Installing bind-client (9.16.2-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/packages/bind-client_9.16.2-1_arm_cortex-a7_neon-vfpv4.ipk
Installing luci-app-ddns (git-20.108.78014-f4651cb) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/luci/luci-app-ddns_git-20.108.78014-f4651cb_all.ipk
Installing luci-lib-ipkg (git-20.069.54281-3fb8e3d) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/packages/arm_cortex-a7_neon-vfpv4/luci/luci-lib-ipkg_git-20.069.54281-3fb8e3d_all.ipk
Configuring ddns-scripts.
Configuring luci-lib-ipkg.
Configuring luci-app-ddns.
Configuring libopenssl1.1.
Configuring zlib.
Configuring libatomic1.
Configuring librt.
Configuring libuv1.
Configuring bind-libs.
 192852  WARN : Service section disabled! - TERMINATE
Configuring bind-client.
 192852  WARN : No update_url found/defined or no update_script found/defined! - TERMINATE
Configuring ddns-scripts_nsupdate.
Collected errors:
 * resolve_conffiles: Existing conffile /etc/config/ddns is different from the conffile in the new package. The new conffile will be placed at /etc/config/ddns-opkg.

Also it is working (DNS records updated) but no luci status/configuration.
My worries are that now part of luci is stock/vanilla and some underlying modules are newer

root@OpenWrt:~# opkg list-installed | grep luci
liblucihttp-lua - 2019-07-05-a34a17d5-1
liblucihttp0 - 2019-07-05-a34a17d5-1
luci - git-20.057.55219-13dd17f-1
luci-app-ddns - git-20.108.78014-f4651cb
luci-app-firewall - git-20.057.55219-13dd17f-1
luci-app-opkg - git-20.057.55219-13dd17f-1
luci-app-wireguard - git-20.069.54281-3fb8e3d
luci-base - git-20.057.55219-13dd17f-1
luci-lib-ip - git-20.057.55219-13dd17f-1
luci-lib-ipkg - git-20.069.54281-3fb8e3d
luci-lib-jsonc - git-20.057.55219-13dd17f-1
luci-lib-nixio - git-20.057.55219-13dd17f-1
luci-mod-admin-full - git-20.057.55219-13dd17f-1
luci-mod-network - git-20.057.55219-13dd17f-1
luci-mod-status - git-20.057.55219-13dd17f-1
luci-mod-system - git-20.057.55219-13dd17f-1
luci-proto-ipv6 - git-20.057.55219-13dd17f-1
luci-proto-ppp - git-20.057.55219-13dd17f-1
luci-proto-wireguard - git-20.069.54281-3fb8e3d
luci-theme-bootstrap - git-20.057.55219-13dd17f-1
rpcd-mod-luci - 20191114

Regards
Weasel

router was restored by uboot procedure
using:
http://downloads.openwrt.org/releases/19.07.2/targets/ipq40xx/generic/openwrt-19.07.2-ipq40xx-generic-glinet_gl-b1300-squashfs-sysupgrade.bin
and looks vanilla after connecting http://192.168.1.1 (no root password etc.)

I don't see the install of luci-app-wireguard -- did you install that?

mod-udptunnel package is not found -- maybe you meant simply udptunnel?

1 Like

Typo, package was installed anyway

Installing kmod-udptunnel4 (4.14.171-1) to root...
Downloading http://downloads.openwrt.org/releases/19.07.2/targets/ipq40xx/generic/kmods/4.14.171-1-fa00c1231ac7d7840ec6ffe62dcad926/kmod-udptunnel4_4.14.171-1_arm_cortex-a7_neon-vfpv4.ipk

I did not paste installation procedure but as you can see:

root@OpenWrt:~# opkg list-installed | grep luci
liblucihttp-lua - 2019-07-05-a34a17d5-1
liblucihttp0 - 2019-07-05-a34a17d5-1
luci - git-20.057.55219-13dd17f-1
luci-app-ddns - git-20.108.78014-f4651cb
luci-app-firewall - git-20.057.55219-13dd17f-1
luci-app-opkg - git-20.057.55219-13dd17f-1
luci-app-wireguard - git-20.069.54281-3fb8e3d
luci-base - git-20.057.55219-13dd17f-1
luci-lib-ip - git-20.057.55219-13dd17f-1
luci-lib-ipkg - git-20.069.54281-3fb8e3d
luci-lib-jsonc - git-20.057.55219-13dd17f-1
luci-lib-nixio - git-20.057.55219-13dd17f-1
luci-mod-admin-full - git-20.057.55219-13dd17f-1
luci-mod-network - git-20.057.55219-13dd17f-1
luci-mod-status - git-20.057.55219-13dd17f-1
luci-mod-system - git-20.057.55219-13dd17f-1
luci-proto-ipv6 - git-20.057.55219-13dd17f-1
luci-proto-ppp - git-20.057.55219-13dd17f-1
luci-proto-wireguard - git-20.069.54281-3fb8e3d
luci-theme-bootstrap - git-20.057.55219-13dd17f-1
rpcd-mod-luci - 20191114

Regards
Weasel

But you did...

Unless the luci-app-wireguard was installed before or after this command, it wasn't installed here.