Hi @h31. Have you been able to install 19.07.02 in WR902AC v1? If so, any tips?
Thanks,
Marcelo
Please use this topic only for what it is intended for: Reporting devices that can not save settings.
For any questions, please open a new topic.
Thanks!
someone help me plz .
D-Link DIR-859
-----------------------------------------------------
OpenWrt 19.07.2, r10947-65030d81f3
-----------------------------------------------------
root@OpenWrt:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 2816 2816 0 100% /rom
tmpfs 29776 284 29492 1% /tmp
tmpfs 29776 64 29712 0% /tmp/root
tmpfs 512 0 512 0% /dev
/dev/mtdblock7 11456 428 11028 4% /overlay
overlayfs:/overlay 11456 428 11028 4% /
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "bootloader"
mtd1: 00010000 00010000 "bdcfg"
mtd2: 00010000 00010000 "devdata"
mtd3: 00010000 00010000 "devconf"
mtd4: 00f80000 00010000 "firmware"
mtd5: 0018ffc0 00010000 "kernel"
mtd6: 00df0000 00010000 "rootfs"
mtd7: 00b30000 00010000 "rootfs_data"
mtd8: 00010000 00010000 "art"
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.8M 2.8M 0 100% /rom
tmpfs 29.1M 284.0K 28.8M 1% /tmp
tmpfs 29.1M 64.0K 29.0M 0% /tmp/root
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock7 11.2M 428.0K 10.8M 4% /overlay
overlayfs:/overlay 11.2M 428.0K 10.8M 4% /
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~#
root@OpenWrt:~# mount
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
/dev/mtdblock7 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
You are not affected by this problem.
Please open a new topic for your problem.
WHR-G300N v2 keeps resetting settings after reboot.
root@OpenWrt:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 3072 3072 0 100% /rom
tmpfs 13808 288 13520 2% /tmp
tmpfs 13808 64 13744 0% /tmp/root
overlayfs:/tmp/root 13808 64 13744 0% /
tmpfs 512 0 512 0% /dev
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 0003e000 00010000 "u-boot"
mtd1: 00002000 00010000 "u-boot-env"
mtd2: 003a0000 00010000 "firmware"
mtd3: 00160000 00010000 "kernel"
mtd4: 00240000 00010000 "rootfs"
mtd5: 00010000 00010000 "rootfs_data"
mtd6: 00010000 00010000 "user_property"
mtd7: 00010000 00010000 "art"
root@OpenWrt:~#
version 19.07.2
That's with 19.07.0 or 19.07.1 or 19.07.2?
sorry, 19.07.2 tiny from current link on WHR-G300Nv2 page. Have not tried the other ones (unless you think it would work better).
Thanks for your feedback, I have updated the WHR-G300N v2 dataentry accordingly.
WHR-G300N v2 lose configuration after reboot. I am using the tiny build 19.07.3.
-----------------------------------------------------
OpenWrt 19.07.3, r11063-85e04e9f46
-----------------------------------------------------
root@OpenWrt:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 3072 3072 0 100% /rom
tmpfs 13808 264 13544 2% /tmp
tmpfs 13808 64 13744 0% /tmp/root
overlayfs:/tmp/root 13808 64 13744 0% /
tmpfs 512 0 512 0% /dev
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 0003e000 00010000 "u-boot"
mtd1: 00002000 00010000 "u-boot-env"
mtd2: 003a0000 00010000 "firmware"
mtd3: 00160000 00010000 "kernel"
mtd4: 00240000 00010000 "rootfs"
mtd5: 00010000 00010000 "rootfs_data"
mtd6: 00010000 00010000 "user_property"
mtd7: 00010000 00010000 "art"
Hello.
I also have this problem with WR841ND v9 and 19.07.2 and .3.
Tried also clean install (clean firmware mtd1 partition, tftp 18.06, upgrade to 19.07).
EDIT: What I see the problem is mainly with the Tiny package for 4MB devices.
I just tried to install community build of 19.07.3 and it works OK.
So this is probably the way, as 4MB devices were deprecated...
Netgear "wnr2000 v3" is resetting to stock when rebooted.
OpenWrt 19.07.3, r11063-85e04e9f46
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 3072 3072 0 100% /rom
tmpfs 13864 48 13816 0% /tmp
tmpfs 13864 68 13796 0% /tmp/root
overlayfs:/tmp/root 13864 68 13796 0% /
tmpfs 512 0 512 0% /dev
dev: size erasesize name
mtd0: 00040000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 003a0000 00010000 "firmware"
mtd3: 00159440 00010000 "kernel"
mtd4: 00246bc0 00010000 "rootfs"
mtd5: 00010000 00010000 "rootfs_data"
mtd6: 00010000 00010000 "art"
Same issue with XDX RN502J (no config save between reboots).
root@OpenWrt:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 3072 3072 0 100% /rom
tmpfs 14136 72 14064 1% /tmp
tmpfs 14136 60 14076 0% /tmp/root
overlayfs:/tmp/root 14136 60 14076 0% /
tmpfs 512 0 512 0% /dev
root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 00010000 00010000 "factory"
mtd3: 003b0000 00010000 "firmware"
mtd4: 001485ed 00010000 "kernel"
mtd5: 00267a13 00010000 "rootfs"
mtd6: 00040000 00010000 "rootfs_data"
root@OpenWrt:~# logread | grep jffs2
Thu Feb 27 21:05:24 2020 kern.notice kernel: [ 0.000000] Kernel command line: console=ttyS0,57600 rootfstype=sq
uashfs,jffs2
Thu Feb 27 21:05:24 2020 kern.info kernel: [ 0.433249] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMOD
E_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Thu Feb 27 21:05:24 2020 user.notice kernel: [ 10.506316] mount_root: jffs2 not ready yet, using temporary tmpfs
overlay
Thu Feb 27 21:05:59 2020 kern.err kernel: [ 60.534639] jffs2: Too few erase blocks (4)
Thu Feb 27 21:05:59 2020 daemon.err mount_root: failed - mount -t jffs2 /dev/mtdblock6 /rom/overlay: Not a tty
That's with which 19.07.x relase exactly?
With 19.07.2.
I did a bit more research into the OpenWrt documentation, and figured out that my device is in the 4 Mb flash / 32 MB RAM category, and that was causing the issue. I build a custom image using imagebuilder, removing some packages and it works now, i.e. it saves config between reboots.
Issue present in device Model: TP-Link TL-WDR3600 v1 Architecture: Atheros AR9344 rev 2:
# mount
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
/dev/mtdblock4 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.5M 2.5M 0 100% /rom
tmpfs 60.8M 1.1M 59.7M 2% /tmp
tmpfs 60.8M 60.0K 60.7M 0% /tmp/root
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock4 3.9M 3.6M 244.0K 94% /overlay
overlayfs:/overlay 3.9M 3.6M 244.0K 94% /
# cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00010000 "u-boot"
mtd1: 007d0000 00010000 "firmware"
mtd2: 00185dad 00010000 "kernel"
mtd3: 0064a250 00010000 "rootfs"
mtd4: 003e0000 00010000 "rootfs_data"
mtd5: 00010000 00010000 "art"
No, it's not. The tl-wdr3600 has 8 MB flash, which -while not plenty- is sufficient for modern OpenWrt, now and within the immediate future. Your paste shows that you have a 3.9 MB large overlay at your disposal, but at the same time you already filled up 3.6 MB of that, leaving you with only 244 KB 'free' space. With jffs2 needing at least 5 free erase and you being down to 4 and under, that is a problem - you need to reset (firstboot) your device to recovery and keep a closer eye on your flash usage in the future. But your device is not one with systemic flash shortage, as 4 MB flash devices would be. 8 MB isn't much, it needs some attention to keep it at bay, but it is workable.
There must be something wrong with the sysupgrade image. I literally just did a firstboot reset and the device is full and not saving settings between reboots.