On 20 November 2014 00:32, SGT. Garcia <darwinsker...@gmail.com> wrote: > On Nov 12 09:11 +0100, Rafał Miłecki wrote: >> Some devices like Netgear WNR1000v3 or WGR614v10 have partitions aligned >> to 0x1000. Using bigger blocksize stopped us from detecting some parts. >> >> Signed-off-by: Rafał Miłecki <zaj...@gmail.com> > > is this related: > > 6 bcm47xxpart partitions found on MTD device bcm47xxsflash > Creating 6 MTD partitions on "bcm47xxsflash": > 0x000000000000-0x000000040000 : "boot" > 0x000000040000-0x0000003f0000 : "firmware" > 0x00000004001c-0x00000004090c : "loader" > 0x00000004090c-0x00000014e400 : "linux" > mtd: partition "linux" must either start or end on erase block boundary or be > smaller than an erase block -- forcing read-only > 0x00000014e400-0x0000003f0000 : "rootfs" > mtd: partition "rootfs" must either start or end on erase block boundary or > be smaller than an erase block -- forcing read-only > mtd: device 4 (rootfs) set to be root filesystem > 1 squashfs-split partitions found on MTD device rootfs > 0x0000002b0000-0x0000003f0000 : "rootfs_data" > 0x0000003f0000-0x000000400000 : "nvram"
Yes. Partitions are created by bcm47xxpart driver. > full dmesg: http://codepad.org/2hiTlY4B > > i started getting this ever since i updated using sysupgrade. Some time ago (AA times) we were using different partitioner. So your pattition-related messages could look different. -- Rafał _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel