New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#1712 - LEDE 17.01.05 on BCM2710 (Raspberry Pi 3) defaults configuration on reboot #7941
Comments
jwbrack: From a quick glance, as compared to 17.01.04, it seems that squashfs is enabled by default now (although I tried a build with it disabled with no luck). It was my understanding that the overlayfs required to make squashfs work properly was not fully integrated and working for the Raspberry Pi 3b (at least way back on 17.01.01). Confirmed that "/overlay" and ".rom" are both completely empty both before and after any hand modifications, for both initial boot, and subsequent boots. |
127.0.0.1: Try using the ext4 image, since you're able to plug into another Linux computer and check the filesystem. Additionally, MicroSD card on RPi is not being recognize as a MTD device, it has a MBR (msdos) partition scheme. |
jwbrack: The firmware image from the Stable Releases is EXT4. Additionally, the image I built locally is EXT4. I'm loading both images via "dd if=<SOME_IMAGE> of=/dev/sdb bs=2M conv=fsync" on a SD card without any native partitions (all deleted prior with fdisk). I can boot the device, and have access to the serial terminal. Main differences I see between 17.01.4 and 17.01.5 in bootup are below. It seems that v17.01.5 is getting re-mounted as read-only, which would explain the issues that I am seeing (changes are cached and not written through to the SD card). This is absolutely repeatable (attempted 5+ times now comparing v17.01.4 to v17.01.5). LEDE v17.01.4 LEDE v17.01.5 |
127.0.0.1: The filesystem is corrupt and you need to check this ext4 filesystem on another Linux computer. |
jwbrack:
Supply the following if possible:
Device problem occurs on
Software versions of OpenWrt/LEDE release, packages, etc.
Steps to reproduce
The text was updated successfully, but these errors were encountered: