boot.img too big

changed the description

By Christian Poulter on 2024-10-03T20:50:48

changed the description

By Christian Poulter on 2024-10-03T20:51:01

changed the description

By Christian Poulter on 2024-10-03T20:51:14

added initramfs label

moved from pmbootstrap#2461 (closed)

By Robert Eckelmann on 2024-10-03T21:53:06

added device-samsung-espresso10 release-edge labels

added type::support label

This is likely a regression from 3c55399f.

By Newbyte on 2024-10-04T14:31:00

assigned to @MightyM17 and @sicelo

By Newbyte on 2024-10-04T14:31:43

changed milestone to %v24.12 Release

unassigned @sicelo

By Sicelo on 2024-10-05T07:49:56

@Newbyte I don't maintain espresso, so I've unassigned myself.

Since the problem seems to be due to large initramfs, I don't see what @MightyM17 can do either. Perhaps you should assign this to the maintainers of the initramfs?

The same is probably true if the issue is due to the kconfig changes, since they're also imposed by the kconfig checks. Or could we be allowed to revert some of them in order to reduce kernel size? For example, linux-postmarketos-omap probably doesn't need the Waydroid and Containers stuff, since I doubt the SoCs in question are beefy enough for Waydroid and containers to begin with. UEFI stuff is also not needed for our kernel. I haven't checked how much weight these three add to the kernel size though but I guess not having them would help in some little way .

@chpoulter you may also want to have a look at !5636 (merged). Haven't tested it myself yet, but if you're lucky it might help.

By Sicelo on 2024-10-05T09:35:09

@Newbyte I don't maintain espresso, so I've unassigned myself.

I assigned you since you maintain the omap kernel, which is where the culprit is. But if you're not interested in working on this, then you are of course welcome to unassign yourself.

Perhaps you should assign this to the maintainers of the initramfs?

The problem is not a growing initramfs but a growing kernel, so I don't think so.

The same is probably true if the issue is due to the kconfig changes, since they're also imposed by the kconfig checks. Or could we be allowed to revert some of them in order to reduce kernel size? For example, linux-postmarketos-omap probably doesn't need the Waydroid and Containers stuff, since I doubt the SoCs in question are beefy enough for Waydroid and containers to begin with. UEFI stuff is also not needed for our kernel. I haven't checked how much weight these three add to the kernel size though but I guess not having them would help in some little way

For exynos4, we were able to maintain compliance with the new kconfig check while also fitting the tiny 8 MB boot partitions of some devices: !5569 (merged). However, whether this is feasible for omap I cannot say. It might make sense to let community devices opt-out of e.g. UEFI booting if it doesn't make sense on their platform.

By Newbyte on 2024-10-05T09:35:09

Related issue: #3040 (closed)

Not sure if this is possible, but maybe it would be more future-proof to use some sort of bootloader in the KERNEL partition, which fetches initramfs and kernel from DATAFS. Then you are free in kernel/initramfs size. You could also boot different operations systems - similar like grub on PCs - plus you could add a loading battery program.

But just a suggestion ...

Yes, this is a good idea. It' exactly how u-boot is used on the Nokia N900, which uses the same postmarketOS kernel.

Someone would just need to do something similar for espresso. Want to give it a go perhaps?

I had an unsuccessful try with porting uboot mainline, the downstream version of it (for ig galaxy nexus) is what worked, maybe try giving that a go

mentioned in merge request !5716 (merged)

unassigned @root

boot.img too big

Child items 0

Activity