But I am just thinking now, prompted by your error messages, that does it also remove WPS (at least from LuCI), although WPS should not be tied to enterprise functionality, I think.
Might be that I need to revert the change.
hnyman, thank you for your quick reply! I have upgraded the router keeping the configuration. Do I need to factory reset to get wifi working again?
Just try master-r14954-aafbfc6ac3-20201116
I reverted back to using the full wpad (with eap and wps).
ok, thank you! It's working again.
@hnyman any reason why you keep this patch? https://github.com/hnyman/openwrt/commit/90113cd70f33449a68827e63501dcc688c14d007
I get lost why you ask that mvebu question here in the WNDR3700 build thread?
I wanted to see in 2017 if mvebu WRT3200ACM benefits from CPU frequency scaling as that seemed to work with ipq806x R7800. I have since then carried the patch in my WRT3200ACM build.
Discussion related to that is in
My bad. I read the title wrong.
OpenSSL Benchmark
|r11257| Atheros AR7161 rev 2 | Netgear WNDR3800 | MIPS 24Kc V7.4 @ 800mhz | 531.66 | 1.1.1h | 65355520 | 44770650 | 19420730 | 6043310 | 6151880 | 2182490 | 11227110 | 9601370 | 8440490 | 9.0 | 339.6 | 25.5 | 26.6 |
Hello Hnyman,
For some time, the updates have removed the system settings. I just tried to switch from r14190 to r15383 and the same failure happened again.
Do you think that if I redo all the settings with the r15383 I will be able to continue updating without problem?
Yours truly,
I have regularly updated my wndr3700v2 and settings have stayed intact in sysupgrades.
There should be nothing that prevents keeping settings.
Ps.
If you have 3700v1, please be aware that my build may again be nearing the size limits of the 8 MB flash in 3700v1
Thank you for your quick reply.
Of course I have the WNDR3700v1 router.
I have reverted to the r14190. Restoring the settings worked fine.
You are certainly right; it is a question of memory space.
I tried a two-step update. First an update without keeping the settings. Then install the backup as a second step.
I have the following error messages:
Unpack failed at ClassConstructor.eval (https://192.168.1.1/luci-static/resources/view/system/flash.js?v=git-20.311.85590-5c5b134:8:1039)The restore command failed with code 1
tar: can't remove old file etc/profile: No space left on device
If you still have it there, could you please look at the size of the overlay partition?
What does df -h say for its total size?
The result with the r14190:
root@WNDR3700:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 5.3M 5.3M 0 100% /rom
tmpfs 28.9M 456.0K 28.4M 2% /tmp
/dev/mtdblock5 768.0K 256.0K 512.0K 33% /overlay
overlayfs:/overlay 768.0K 256.0K 512.0K 33% /
tmpfs 512.0K 0 512.0K 0% /dev
Would you like the result with the r15383?
With the r15383 without restoring the backup.
root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 5.3M 5.3M 0 100% /rom
tmpfs 28.5M 548.0K 27.9M 2% /tmp
tmpfs 28.5M 116.0K 28.4M 0% /tmp/root
overlayfs:/tmp/root 28.5M 116.0K 28.4M 0% /
tmpfs 512.0K 0 512.0K 0% /dev
So, with r15383 there is not room for a normal jffs2 overlay any more, as it is not created.
Can you
- grep system log for "overlay" and "jffs2", and also
- use "dmesg" to to show the kernel log section with MTD partition definition. Especially the lines kernel, rootfs and rootfs_data are the crucial ones.
I mean this section (from wndr3700v2).
[ 0.694464] Creating 4 MTD partitions on "spi0.0":
[ 0.699257] 0x000000000000-0x000000050000 : "u-boot"
[ 0.705132] 0x000000050000-0x000000070000 : "u-boot-env"
[ 0.711243] 0x000000070000-0x000000ff0000 : "firmware"
[ 0.720158] 2 netgear-fw partitions found on MTD device firmware
[ 0.726224] Creating 2 MTD partitions on "firmware":
[ 0.731194] 0x000000000000-0x000000201440 : "kernel"
[ 0.737018] 0x000000201440-0x000000f80000 : "rootfs"
[ 0.742753] mtd: device 4 (rootfs) set to be root filesystem
[ 0.750082] 1 squashfs-split partitions found on MTD device rootfs
[ 0.756319] 0x0000007f0000-0x000000f80000 : "rootfs_data"
[ 0.762572] 0x000000ff0000-0x000001000000 : "art"
I am trying to figure out how much the v1 image would need to be slimmed down. Possibly it needs to be switched from openssl to wolfssl (or mdebtls).
[ 0.694231] Creating 4 MTD partitions on "spi0.0":
[ 0.699024] 0x000000000000-0x000000050000 : "u-boot"
[ 0.704837] 0x000000050000-0x000000070000 : "u-boot-env"
[ 0.710988] 0x000000070000-0x0000007f0000 : "firmware"
[ 0.719890] 2 netgear-fw partitions found on MTD device firmware
[ 0.725953] Creating 2 MTD partitions on "firmware":
[ 0.730925] 0x000000000000-0x000000201440 : "kernel"
[ 0.736703] 0x000000201440-0x000000780000 : "rootfs"
[ 0.742466] mtd: device 4 (rootfs) set to be root filesystem
[ 0.749791] 1 squashfs-split partitions found on MTD device rootfs
[ 0.756026] 0x000000740000-0x000000780000 : "rootfs_data"
[ 0.762265] 0x0000007f0000-0x000000800000 : "art"
I need help for the precise syntax for grep.
Thanks. Looks like the is only 256 kB free (from 740000 to 780000). Should be at least one 64 kB block more, 320 kB.
Examples here:
root@router2:~# logread | grep overlay
Thu Dec 31 16:27:14 2020 user.info kernel: [ 20.911739] mount_root: loading kmods from internal overlay
Thu Dec 31 16:27:14 2020 user.info kernel: [ 78.481562] mount_root: overlay filesystem has not been fully initialized yet
Thu Dec 31 16:27:14 2020 user.info kernel: [ 78.490631] mount_root: switching to jffs2 overlay
Thu Dec 31 16:27:14 2020 kern.warn kernel: [ 78.500988] overlayfs: upper fs does not support tmpfile.
root@router2:~# logread | grep jffs2
Thu Dec 31 16:27:14 2020 kern.notice kernel: [ 0.000000] Kernel command line: console=ttyS0,115200 rootfstype=squashfs,jffs2
Thu Dec 31 16:27:14 2020 kern.info kernel: [ 0.609585] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Thu Dec 31 16:27:14 2020 kern.warn kernel: [ 21.599560] jffs2_scan_eraseblock(): End of filesystem marker found at 0x10000
Thu Dec 31 16:27:14 2020 kern.warn kernel: [ 21.606814] jffs2_build_filesystem(): unlocking the mtd device...
Thu Dec 31 16:27:14 2020 kern.warn kernel: [ 21.614903] jffs2_build_filesystem(): erasing all blocks after the end marker...
Thu Dec 31 16:27:14 2020 kern.notice kernel: [ 77.641315] jffs2: notice: (600) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Thu Dec 31 16:27:14 2020 kern.notice kernel: [ 77.917472] jffs2: notice: (598) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Thu Dec 31 16:27:14 2020 user.info kernel: [ 78.490631] mount_root: switching to jffs2 overlay
your output will be different, as there is not enough space.
Thank you so much.
It seems that both logs are empty.
Yeah, the relevant lines may only be visible on the first boot after flash, when the jffs2 overlay is created.