You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently restarted using my old Kingston MobileLite Wireless MLW221 router, and decided to flash the latest stable OpenWrt release (17.01.4). The device was last flashed with Chaos Calmer r49363, and it worked without any problems. Now, on the latest revision, it outputs a lot of "jffs2: Newly-erased block contained word 0xdec0adde at offset x", rendering the device unusable due to lack of persistence of setting after a reset. I've tried multiple times to flash it via sysupgrade, by flashing the Kingston stock image via TFTP then the OpenWrt one via TFTP, all of this procedures working perfectly with the old Chaos Calmer image. As seen in the logs, the old build boots up without any issues, while the newer one doesn't. I've tried the buildbots' image, building my own minimal image, and a image with all the necessary target hardware packages, but still the same result. What can I try to fix this issue? Thank you!
The text was updated successfully, but these errors were encountered:
pcmihnea:
I've recently restarted using my old Kingston MobileLite Wireless MLW221 router, and decided to flash the latest stable OpenWrt release (17.01.4). The device was last flashed with Chaos Calmer r49363, and it worked without any problems. Now, on the latest revision, it outputs a lot of "jffs2: Newly-erased block contained word 0xdec0adde at offset x", rendering the device unusable due to lack of persistence of setting after a reset. I've tried multiple times to flash it via sysupgrade, by flashing the Kingston stock image via TFTP then the OpenWrt one via TFTP, all of this procedures working perfectly with the old Chaos Calmer image. As seen in the logs, the old build boots up without any issues, while the newer one doesn't. I've tried the buildbots' image, building my own minimal image, and a image with all the necessary target hardware packages, but still the same result. What can I try to fix this issue? Thank you!
The text was updated successfully, but these errors were encountered: