OpenWrt Forum Archive

Topic: UCI not saving changes

The content of this topic has been archived on 20 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello.

I'm very newbie at OpenWRT. I'm trying with 14.07 and a Sagem F@ast 2604 only for testing purpose. Now I'm trying to up wifi using uci command. I'm getting success but after a router reboot I have the original configuration for wireless even I've submited a uci commit command.

I don't know if is a router limitation or if is not the right way to write in the flash memory.

Regards and thank in advanced

Try to install OpenWRT again: sometimes the installation fails silently, and the overlay system becomes read-only.

Hello.

Thanks for your answer. How to check if the installation was successful?

Regards

Run mount on the command line make sure you have an /overlay partition and that it is read-write (rw).

Models with 4 MB flash and you are building your own image, you may have put too much stuff in for the jffs to be formatted.

(Last edited by mk24 on 30 May 2017, 22:01)

Hello.

The only read only partition is /dev/root mounted on /rom, others including overlayfs:/tmp/root are rw mounted, overlay has used only 1% of total space.

I've tried to modified using vi on /tmp/root/etc/config/wireless, but changes doesn't remain after a reboot.

Regards

This is an incomplete install.  /tmp is in RAM, you don't have a permanent overlay.

mount should show a MTD device mounted on /overlay with a jffs2 filesystem.

/dev/mtdblock3 on /overlay type jffs2 (rw,noatime)

(Last edited by mk24 on 31 May 2017, 12:43)

No, I have not anything mounted of type jffs2. It was installed using OEM firmware method. Exists some kind of install log?

Regards

Run firstboot, or re-flash with the sysupgrade image.  In either case you should see the jffs being built when you examine the dmesg log after the reboot.  There is no permanent log of this though.

Thank you very much, firstboot command did the thing: now I can save changes in configuration, no the problem is the very slow LuCI web interface.

REgards

The discussion might have continued from here.