Axios
I've been experiencing the same situation since the Solus updates of weeks 8 and 9 (see my last post https://discuss.getsol.us/d/12495-week-9-2026/28 in 2)) and @AAndresH (in the same post) replied to me that it's a false positive (https://discuss.getsol.us/d/12495-week-9-2026/34)
pomon
I consulted the issue you mentioned and the suggested terminal commands give the following results:
administrateur@solus-pc ~ $ uname -r
6.18.13-330.current
administrateur@solus-pc ~ $ sudo clr-boot-manager mount-boot
[sudo] password for administrateur:
administrateur@solus-pc ~ $ sudo du -d1 -h /boot
260M /boot/EFI
20K /boot/loader
4,0K /boot/System Volume Information
260M /boot
administrateur@solus-pc ~ $ df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/sdb6 131G 35G 90G 28% /
devtmpfs 7,7G 0 7,7G 0% /dev
tmpfs 7,8G 0 7,8G 0% /dev/shm
efivarfs 128K 87K 37K 71% /sys/firmware/efi/efivars
tmpfs 3,1G 2,1M 3,1G 1% /run
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-journald.service
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-resolved.service
tmpfs 7,8G 8,0K 7,8G 1% /tmp
/dev/sda1 901G 757G 99G 89% /home
tmpfs 1,6G 204K 1,6G 1% /run/user/1007
/dev/sdb5 1022M 260M 763M 26% /boot
administrateur@solus-pc ~ $ sudo clr-boot-manager list-kernels
* com.solus-project.current.6.18.13-330
administrateur@solus-pc ~ $ ls /boot/EFI/com.solus-project/
bootloaderx64.efi initrd-com.solus-project.current.6.18.13-330
BOOTX64.CSV initrd-com.solus-project.current.6.18.13-330.nvidia
freestanding-com.solus-project.nvidia-firmware kernel-com.solus-project.current.6.18.13-330
grubx64.efi mmx64.efi
I would notify that at the end of the package status check by sudo eopkg check, if we validate the reinstallation of the linux-current package as suggested, this results in the anomaly message that you and I have noticed and also that there is only one kernel left on our system (I am also on Solus Budgie).
