Archer A6 v3 Snapshot overlay size

I installed the snapshot yesterday on Archer A6 v3. The overlay size is only 8 MB. It should be 16 MB. I can't figure out where in the commits is the cultprit. Could someone pls guide me in the right direction?

 OpenWrt SNAPSHOT, r26308-4341901f05
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@OpenWrt2:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00010000 "u-boot"
mtd1: 00f60000 00010000 "firmware"
mtd2: 00326e92 00010000 "kernel"
mtd3: 00c3916e 00010000 "rootfs"
mtd4: 00870000 00010000 "rootfs_data"
mtd5: 00050000 00010000 "config"
mtd6: 00010000 00010000 "radio"

root@OpenWrt2:~# cat /proc/partitions
major minor  #blocks  name

  31        0        256 mtdblock0
  31        1      15744 mtdblock1
  31        2       3227 mtdblock2
  31        3      12516 mtdblock3
  31        4       8640 mtdblock4
  31        5        320 mtdblock5
  31        6         64 mtdblock6

Bootlog:

[    1.471844] spi-mt7621 1e000b00.spi: sys_freq: 220000000
[    1.478730] spi-nor spi0.0: w25q128 (16384 Kbytes)
[    1.483710] 4 fixed-partitions partitions found on MTD device spi0.0
[    1.490193] OF: Bad cell count for /palmbus@1e000000/spi@b00/flash@0/partitions
[    1.497575] OF: Bad cell count for /palmbus@1e000000/spi@b00/flash@0/partitions
[    1.505180] Creating 4 MTD partitions on "spi0.0":
[    1.510035] 0x000000000000-0x000000040000 : "u-boot"
[    1.516953] 0x000000040000-0x000000fa0000 : "firmware"
[    1.523593] 2 uimage-fw partitions found on MTD device firmware
[    1.529576] Creating 2 MTD partitions on "firmware":
[    1.534539] 0x000000000000-0x000000326e92 : "kernel"
[    1.539508] mtd: partition "kernel" doesn't end on an erase/write block -- force read-only
[    1.548964] 0x000000326e92-0x000000f60000 : "rootfs"
[    1.553946] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only
[    1.564586] mtd: setting mtd3 (rootfs) as root device
[    1.569819] 1 squashfs-split partitions found on MTD device rootfs
[    1.575991] 0x0000006f0000-0x000000f60000 : "rootfs_data"
[    1.583018] 0x000000fa0000-0x000000ff0000 : "config"
[    1.589442] OF: Bad cell count for /palmbus@1e000000/spi@b00/flash@0/partitions
[    1.597085] 0x000000ff0000-0x000001000000 : "radio"
[    1.603441] OF: Bad cell count for /palmbus@1e000000/spi@b00/flash@0/partitions

DTS files:

Original commit DTS for the device

Latest commit DTS file

I cant see any difference between these two, and yet the stable versions show 16mb but the snapshot has only 8mb. any pointers?

Use the stable version?

Unless you can code and become a developer.

Lol yeah that's always there. But I compile my own version. And the snapshot kernel is on 6.6 :smiling_face:. Am not expert but can get away with compiling etc, though can't find the issue here.

Well, I cannot code, so you should have enough attention, now, to pull someone in that can.

1 Like

I think the reduced overlay size has nothing to do with the code (the DTS files).
Did you add additional packages in your build?
Check this:
https://openwrt.org/docs/techref/flash.layout#partitioning_of_nor_flash-based_devices

The overlay filesystem has to be backed by a writable area in the flash memory rootfs_data.
When the read-only rootfs part gets bigger because of additional packages etc., the writable part gets smaller.

EDIT:

Because of the explanation above, the overlay size can never be 16Mb on a device with only 16Mb flash.

1 Like

ok i feel stupid now. thanks for clarifying. Doesnt look like we have 16mb in the stable build either.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.