Some days ago I was also affected by the “no space left on device” situation below /boot. In my case the installation failed, the L5 remained boot-able and I could remove the older kernels. Today I see, that the removal was not fully complete:
I should clarify that this is a general statement about the behaviour of the package management system.
If your system has got itself in a mess or some files have been manually deleted outside of the package management system then the actual behaviour might be different.
Nevertheless, it is still a good idea to use the above apt list | ... command to ask the package management system what it thinks is the current situation.
These dtb files are being put into /boot by flash-kernel, so it’s possible that they’re not being tracked by package manager at all (my suggestion to try purge was just an educated guess). Removing these old files manually should be fine then - but personally I wouldn’t bother, they take something around 50KB of space
I do not fully understand, what this grep has to do with the old files, but here we go:
purism@pureos:~$ apt list | grep '^linux-image-.*-librem5'
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
linux-image-5.16.0-1-librem5/byzantium,now 5.16.3pureos1 arm64 [installed,automatic]
In order to gain further space, and especially now when it is clear that your big files like:
play no significant role any more, within your Librem 5 /boot partition, you might consider to remove them completely away (if not already done). And, @irvinewade, many thanks for sharing with us here this very relevant CLI command! As written here:
