Unable to update with OWUT

@OpenWrt:~# owut blob
{
  "client": "owut/2024.08.09~8a6becd8-r1",
  "target": "mediatek/filogic",
  "profile": "bananapi_bpi-r4",
  "version": "SNAPSHOT",
  "version_code": "r27334-a66f6c1bfb",
  "filesystem": "squashfs",
  "diff_packages": true,
  "packages": [
    "mkf2fs",
    "wpad-basic-mbedtls",
    "kmod-mt7916-firmware",
    "kmod-mt7996e",
    "busybox",
    "kmod-hwmon-pwmfan",
    "nano",
    "openssl-util",
    "kmod-phy-marvell",
    "kmod-phy-aquantia",
    "procd-ujail",
    "base-files",
    "libustream-mbedtls",
    "fitblk",
    "firewall4",
    "pciutils",
    "uboot-envtools",
    "dnsmasq",
    "procd",
    "usbutils",
    "hostapd-utils",
    "kmod-rtc-pcf8563",
    "kmod-usb3",
    "kmod-phy-realtek",
    "kmod-eeprom-at24",
    "wpad-openssl",
    "kmod-sky2",
    "odhcp6c",
    "ethtool",
    "uci",
    "luci-ssl",
    "dropbear",
    "mtd",
    "odhcpd-ipv6only",
    "procd-seccomp",
    "kmod-crypto-hw-safexcel",
    "kmod-mt7915e",
    "kmod-i2c-mux-pca954x",
    "urandom-seed",
    "ppp",
    "kmod-leds-gpio",
    "kmod-gpio-button-hotplug",
    "kmod-sfp",
    "kmod-mt7996-firmware",
    "logd",
    "e2fsprogs",
    "ca-certificates",
    "f2fsck",
    "ca-bundle",
    "luci",
    "owut",
    "kmod-phy-marvell-10g",
    "wireless-tools",
    "urngd",
    "ppp-mod-pppoe"
  ]
}

No arguments were passed, I just ran "OWUT Upgrade" as the command each time.

Well, we have a problem! opkg should never have allowed this, since:

$ opkg -A whatconflicts wpad-openssl
Root set:
  wpad-openssl
What conflicts with root set
        wpad-basic-mbedtls 2023-09-08-e5ccbfc6-8        conflicts with hostapd
... about 20 other packages ...

You never should have been able to build firmware with or install those two packages together, and need to remove one.

I assume you'd like to keep openssl, since mbedtls is the default and the openssl could only be there by adding it manually, so

$ opkg remove wpad-basic-mbedtls

then try the owut upgrade again.

I actually tried this before and it says there is nothing to remove, I'll try again right now though.

Edit:
@OpenWrt:~# opkg remove wpad-basic-mbedtls
No packages removed.

Oho, that might be the "uninstalled package" bug I found a while back.

What's the output this ubus call, does it list both packages?

$ ubus call rpc-sys packagelist '{"all":true}' | grep wpad
                "wpad-basic-mbedtls": "...",
                "wpad-openssl": "...",

If you do see both, then it's probably that bug, so try editing /usr/lib/opkg/status and find the wpad-basic-mbedtls entry. If it's there, with a line that says Status: install user not-installed, then you can manually delete the whole entry (should be about 8 lines). There are some details in the bug report linked above. (You might want to scan the file for not-installed and see if there are any other packages that might return from the dead and delete them, too.)

Both were there and the zombi mbedtls was there as well (no other zombies). Running OWUT again now.

Edit: Successfully updated.

Edit 2: Spoke too soon, it updated but seems to have taken down my SFP port and Wi-Fi, digging into why.

Not sure about SFP port, but WiFi sounds suspiciously like the wpad package didn't get everything needed...

I'm guessing that's likely. It started broadcasting 2.4g after I played with it (no idea what I did that got that up), but the 5g/6g bands are dead. I swapped to just the standard Wan/Ethernet1 port instead of the SFP for now to get connectivity back; it's detecting and showing no errors on the SFP and properly negotiating the speed, but no WAN through it for some reason. Trying to play with it while working but can't do anything that will risk taking me offline for the day until tonight, lol.

Hmm. You might start by doing another owut blob and comparing what you've got now with that one you posted yesterday. If any of the kmods related to the radio chips are missing, that's the culprit in the lack of 5g. (Had an issue a year or two ago with a Belkin RT3200 when the single kmod for 5g got split into two or three, and had to manually install the new split out ones. No doubt a different cause than yours, but the effect feels the same.)

Thanks, should have thought of that... First thing missing in the dif between the two is "kmod-mt7996e"; however, it shows as installed when I try to install it.

New blob:

~# owut blob
{
  "client": "owut/2024.09.07~6564aa2a-r1",
  "target": "mediatek/filogic",
  "profile": "bananapi_bpi-r4",
  "version": "SNAPSHOT",
  "version_code": "r27346-c7ba5574f5",
  "filesystem": "squashfs",
  "diff_packages": true,
  "packages": [
    "mkf2fs",
    "kmod-mt7916-firmware",
    "busybox",
    "kmod-hwmon-pwmfan",
    "nano",
    "openssl-util",
    "kmod-phy-marvell",
    "kmod-phy-aquantia",
    "procd-ujail",
    "base-files",
    "libustream-mbedtls",
    "fitblk",
    "firewall4",
    "pciutils",
    "uboot-envtools",
    "dnsmasq",
    "procd",
    "usbutils",
    "hostapd-utils",
    "kmod-rtc-pcf8563",
    "kmod-usb3",
    "kmod-phy-realtek",
    "kmod-eeprom-at24",
    "wpad-openssl",
    "kmod-sky2",
    "odhcp6c",
    "ethtool",
    "uci",
    "luci-ssl",
    "dropbear",
    "mtd",
    "odhcpd-ipv6only",
    "procd-seccomp",
    "kmod-crypto-hw-safexcel",
    "kmod-mt7915e",
    "kmod-i2c-mux-pca954x",
    "urandom-seed",
    "ppp",
    "kmod-leds-gpio",
    "kmod-gpio-button-hotplug",
    "kmod-sfp",
    "kmod-mt7996-firmware",
    "logd",
    "e2fsprogs",
    "ca-certificates",
    "f2fsck",
    "ca-bundle",
    "luci",
    "owut",
    "kmod-phy-marvell-10g",
    "wireless-tools",
    "urngd",
    "ppp-mod-pppoe"
  ]
}

It seems like it may be similar to your issue but I reached the depth of my knowledge it seems. It shows that it's broadcasting and the wireless config seems right and I see the drivers installed (the only difference being the blob difference I mentioned), but it's not really broadcasting and shows 91dbm of noise and zero connections; wifi analyzers and just regular scanning for wifi on phone/etc are not showing any broadcasts.

Yeah, I'm completely unfamiliar with that device. Time to start a new thread and get some fresh eyes on it.

Will do when I get back to a real keyboard. Your assistance has been extremely appreciated, thank you and also a big thanks for writing and supporting OWUT as well.

1 Like