Creating new and bigger /boot partition

[Kobold]

@Nachlese

Yours is a bit of an XY question, isn’t it?

Not at all.

@Nachlese

Why would you want to have a bigger /boot?

Even a fresh install from 6.6 LTSC takes 180MB (i try to download it yesterday but the installation aborted because of no space) and the newer 6.7 Kernels extended hardcore for around 350MB, you can see it under known issues $ solutions in Stable release Topic.

@philm

Initramfs image can be bigger on 6.7 kernel due to Nvidia GSP Boot firmware

We all known that kernel 6.7 is very feature rich. One of the features is the inclusion of Nvidia’s GSP Boot firmware into Initramfs. However this will increase your image by 150 MB and the fallback image might be 240 MB in size. A way would be to remove kms from mkinitcpio.conf and redo your initramfs images. A discussion regarding that can be found at Arch Gitlab: kms hook increases the initramfs size heavily starting with 6.7 kernel (#238) · Issues · Arch Linux / Mkinitcpio / mkinitcpio · GitLab

@Nachlese

Rather than creating a new and bigger one
you may just clean out of there what is no longer needed

Not new info for me… i do this since 3,5 years for now… there is nothing left besides Kernel 6.1 now… take a look at my screenshot where i backup the /boot files… there is nothing else besides this one LTSC Kernel and it takes 130MB… only 70MB left, not enough room to switch Kernels.

@Nachlese

a kernel image and it’s corresponding initrd will take up ~50MB in /boot

This was maybe 3 years ago the case…