Bazzite update doesn't change kernel
Hi, it's mi first post here. I'm having some trouble using both system update and sudo ujust update, it does run without any issue, download and install everything, and after rebooting, nothing changes.
I attach screens from system update, showing download of kernel ...103, and then after reboot the fastfetch showing the old kernel 102.
Actually same is for MESA which I suppose should be 25.0.1 on stable right now, but I'm still stuck with 24.3.4.
19 Replies
That means the update is failing to apply entirely
systemctl status ostree-*
And post the outputs here
here is the output
regfile copy says: "no space on device"
From df -h I'm seeing /boot has 100% space taken, du -ah /boot | sort -h lists old kernel images, is it safe to delete them somehow?
here's the rpm-ostree status -v output:
this looks to me like you have 9 ostree deployments, but your rpm-ostree status output only shows 2?
true, I bet the -1 is the most recent one, I'll now check the configure-grub to see how many of ostree's are there
im guessing
ostree admin status also only shows the current and staged deployments?there's also 9 of them
yeah you will need to unpin like 5 of them i'd suggest
give me 2 seconds
I'll follow the bazzite FAQ of rebasing/unpinning as I saw it there
to unpin you just run
sudo ostree admin pin --unpin <index number>sure, thanks. So the unpinned ones should remove itselfs after reboot?
personally i prefer unpinning (if pinned) then undeploying
sudo ostree admin undeploy <index> so theyre immediately removed, but you can do as you prefer
if you want to do this i suggest you to start from the oldest deployment (in your case, should be 9 8 7 6 f.ex)
just try to do whats the safest for you lolI'll give it a try now, thank You
okay, the undeploying does free /boot space, but as I unpinned from 9 do 6, then it's not available to undeploy, as those numbers are out of index xD
ah yeah if you unpinned then rebooted, they would've been nuked upon reboot
does updating work now? if yes, i'd advise to remove more pinned images and just keep 3-4 max
yes it updated, kernel changed, same with MESA
now I wonder if it indeed nuked at reboot because I don't see that much space freed (240 MB for now), but at least know where the problem was
Thank You very much guys, I mark this as solved now
yw, and again maybe its best to keep pinned deployments at a minimum
I will now, I remember I pinned some few weeks ago when switching between testing and stable