There is no data there, just empty space. And yes, for purely cosmetic reasons you could erase it or write 0's there or something, but it really doesn't matter at all.
Would a formulation like:
opkg install kmod-mtd-rw
insmod mtd-rw i_want_a_brick=1
cat /dev/mtd2 > /tmp/mtd2
mtd verify /tmp/mtd2 /dev/mtd2
mtd write /tmp/mtd2 /dev/mtd2
work?
Then you'd are also be re-writing the wifi calibration data as well as ethernet MAC addresses which isn't needed because they have already been validated and re-written by the installer.
1 Like
Isn't this akin to a child pushing his mess under the bed and informing his mother that he has tidied his room? Or perhaps a better analogy is the untidiness (wires, etc.) behind a plasterboard stud wall. Admittedly we do not live in a perfect world and imperfection abounds. We never perceive perfection (e.g. a straight line), and yet we can contemplate it. One must come to terms with the same. So perhaps accepting this includes living with these errors. It seems like that is what you are advocating here.
My philosophy here is simply not to touch things which we don't need to be touching. It's bad enough that due to the SPI-NAND driver incompatibility there is the need to rewrite the factory partition at all -- but at least I wanted to re-write only the relevant parts while validating that the offsets are correct (ie. un-doing shifting due to BMT compensating for a bad block).
I haven't ever seen log entries pointing to attempted reads of those dead gaps in /dev/mtd2 without it in the end being me trying to read something there (eg. in LuCI MTD backup function), so that's also a reason why this has never been an issue to me. If those log-lines show up during normal operation, I agree that we should try to get rid of them somehow.
1 Like
For master snapshots newer than 9a07895
If you upgrade with auc you need to manually install these packages and reboot to enable wifi after upgrade so make sure to have some form of wired access (or hotspot and vpn to the router or home network).
kmod-mt7915-firmware
kmod-mt7915e
kmod-mt7622-firmware
As pointed out you can also add the packages manually before by going to advanced update options through luci.
7 Likes
Is that a fix for this startup error I'm seeing with SNAPSHOT?
Mon Jan 9 18:39:53 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface wl0-ap0 wasn't started
Mon Jan 9 18:39:53 2023 daemon.notice netifd: radio0 (9412): Command failed: ubus call hostapd config_add {"iface":"wl0-ap0", "config":"/var/run/hostapd-wl0.conf"} (Invalid argument)
Mon Jan 9 18:39:53 2023 daemon.notice netifd: radio0 (9412): Usage: ubus [<options>] <command> [arguments...]
Mon Jan 9 18:39:53 2023 daemon.notice netifd: radio0 (9412): Options:
Mon Jan 9 18:39:53 2023 daemon.notice netifd: radio0 (9412): -s <socket>: Set the unix domain socket to connect to
blah blah blah...
Yes that looks like the error caused by either not having the driver/firmware installed and/or not rebooting after installing it.
1 Like
Help I've been trying to update package lists on a new flashed router for the past hour and even tried different versions and on the latest 22.03.3, reset, and still keep getting the below error. WAN access works fine. I can ping downloads.openwrt.org fine also in Putty. I am a noob at this though.
Executing package manager
Downloading https://downloads.openwrt.org/releases/22.03.3/targets/mediatek/mt7622/packages/Packages.gz
*** Failed to download the package list from https://downloads.openwrt.org/releases/22.03.3/targets/mediatek/mt7622/packages/Packages.gz
Downloading https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/base/Packages.gz
*** Failed to download the package list from https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/base/Packages.gz
Downloading https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/luci/Packages.gz
*** Failed to download the package list from https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/luci/Packages.gz
Downloading https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/packages/Packages.gz
*** Failed to download the package list from https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/packages/Packages.gz
Downloading https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/routing/Packages.gz
*** Failed to download the package list from https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/routing/Packages.gz
Downloading https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/telephony/Packages.gz
*** Failed to download the package list from https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/telephony/Packages.gz
Errors
Collected errors:
* opkg_download: Failed to download https://downloads.openwrt.org/releases/22.03.3/targets/mediatek/mt7622/packages/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/base/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/luci/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/packages/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/routing/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/releases/22.03.3/packages/aarch64_cortex-a53/telephony/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
The opkg update command failed with code 6.
hello try to disable or enable ipv6 my isp french has ipv6 and this option can obtain the packages 
1 Like
Thank you so much! Disabling ipv6 fixed the issue. It seems my ISP does not support it yet. Should I delete this interface? And also disable ipv6 on my main router which the openwrt one sits behind?
If you enable advanced mode you can add those packages to unattended sysupgrade and bob's your uncle.
2 Likes
hi is not nécessary dont worry 
1 Like
Hi,
All went fine with snapshot update. No need to do extra steps.
Regards
K
1 Like
For the Belkin do I need all the three kmod's or I need only kmod-mt7915e.
When I manually add all three to the auc it says unsupported packages for the rest two packages.
1 Like
Just flashed the latest snapshot (OpenWrt SNAPSHOT r21757-895f38ca1e / LuCI Master git-22.361.69865-deed682) and I noticed a few clusters of kernel errors.
Are these serious or (snapshot) expected?
Wed Jan 11 15:12:23 2023 kern.err kernel: [ 0.230297] OF: /thermal@1100b000: could not get #nvmem-cell-cells for /efuse@10206000/calib@198
Wed Jan 11 15:12:23 2023 kern.err kernel: [ 0.242745] OF: /ethernet@1b100000/mac@0: could not get #nvmem-cell-cells for /spi@1100d000/flash@0/partitions/partition@1c0000/macaddr@7fff4
Wed Jan 11 15:12:23 2023 kern.err kernel: [ 0.256038] OF: /ethernet@1b100000/mdio-bus/switch@0/ports/port@4: could not get #nvmem-cell-cells for /spi@1100d000/flash@0/partitions/partition@1c0000/macaddr@7fffa
Wed Jan 11 15:12:23 2023 kern.err kernel: [ 0.443365] mt7622-pinctrl 10211000.pinctrl: invalid group "pwm_ch7_2" for function "pwm"
Wed Jan 11 15:12:23 2023 kern.err kernel: [ 0.456204] mt-pmic-pwrap 10001000.pwrap: unexpected interrupt int=0x1
Wed Jan 11 15:12:23 2023 kern.err kernel: [ 0.633397] OF: Bad cell count for /spi@1100d000/flash@0/partitions
Wed Jan 11 15:12:23 2023 kern.err kernel: [ 0.639683] OF: Bad cell count for /spi@1100d000/flash@0/partitions
Did you copy-paste the names from here? If yes, double-check if the returned error contains a \t at the end of the entry name (e.g. it says "kmod-mt7622-firmware\t"). AUC sadly doesn't do any whitespace elimination on server-side, and tries to parse the package name as-is, and obviously the package name doesn't end with a Tab character (denoted by \t), so it says incompatible
Actually I've used Attended Sysupgrade from Luci adding the packages names before requesting firmware upgrade.
Yes, I got that. The question still stands - did you copy-paste, and did it end up adding a \t at the end of the package name?
I've written it manually. I didn't copy and paste.