Troubleshooting kernel size problem

For Developers
1

I'm working on porting over an existing image to a new device. I have everything working and booting, wifi, etc. But the problem is (I think) being able to pad the kernel to the right size for the created partitions. I'm reusing confiabits as a base and modified the parititions and they are loading ok. Here is the problem log:

[    1.533159] 5 fixed-partitions partitions found on MTD device spi0.0
[    1.539898] Creating 5 MTD partitions on "spi0.0":
[    1.544704] 0x000000000000-0x000000040000 : "u-boot"
[    1.551412] 0x000000040000-0x000000050000 : "u-boot-env"
[    1.558120] 0x000000050000-0x000000090000 : "Factory"
[    1.564423] 0x000000090000-0x000001000000 : "firmware"
[    1.571077] 2 uimage-fw partitions found on MTD device firmware
[    1.577016] Creating 2 MTD partitions on "firmware":
[    1.582026] 0x000000000000-0x000000323568 : "kernel"
[    1.586984] mtd: partition "kernel" doesn't end on an erase/write block -- force read-only
[    1.596442] 0x000000323568-0x000000f70000 : "rootfs"
[    1.601635] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only
[    1.612062] mtd: setting mtd5 (rootfs) as root device
[    1.617200] 1 squashfs-split partitions found on MTD device rootfs
[    1.623394] 0x0000006f0000-0x000000f70000 : "rootfs_data"
[    1.630068] 0x000000000000-0x000001000000 : "fullflash"
2

What are you doing?

3

I'm not sure what you mean. I'm using confiabits as a base for compiling v24.10.1 for an extender that is not listed. I have everything working, but when I reboot, my Luci additions disappear because of the errors I mentioned about being mounted read only.

4

That log look pretty normal at the first glance.
It is typical that the rom-like read-only kernel and rootfs are not from erase block boundaries. But the r/w overlay rootfs_data is properly at block boundary.

1 Like
5

Yes, I found that out. I am not completely sure what happened as now it's working ok. I was forcing sysupgrade using -F because of the incorrect device name but I fixed that. I'm not sure if that forces overwriting config. Anyway, it's working now. Thanks!

Just for anyone else: It still is showing the read-only warnings.

6

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