penny-farthing
At this time, I'm still experiencing this issue following the latest Solus update:
Vérification de l'intégrité de linux-current Cassé
Fichier corrompu : usr/lib64/modules/6.18.12-329.current/modules.softdep
The following packages are broken:
linux-current
Reinstall the broken packages? (oui/non)oui
Taille totale du/des paquets(s) : 238.87 MB
Téléchargement 1 / 1
Paquet linux-current trouvé dans le dépôt Solus
linux-current-6.18.12-329-1-x86_64.eopkg [en cache]
Finished downloading packages.
Désactivation des interruptions clavier pour les opérations sur les fichiers.
Installation 1 / 1
linux-current-6.18.12-329-1-x86_64.eopkg [en cache]
Installation de linux-current, version 6.18.12, millésime 329
Extraction des fichiers de linux-current
linux-current installé
[âś“] Syncing filesystems success
[âś—] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L590): FATAL: Cannot mount boot device /dev/sdb5 on /boot: Invalid argument
[âś—] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L590): FATAL: Cannot mount boot device /dev/sdb5 on /boot: Invalid argument
[âś“] Running depmod on kernel 6.18.12-329.current success
administrateur@solus-pc ~ $ uname -a
Linux solus-pc 6.18.12-329.current #1 SMP PREEMPT_DYNAMIC 2026-02-17 x86_64 GNU/Linux
administrateur@solus-pc ~ $
Should I be worried about it?
Here's what I've done since:
1) sudo eopkg, then sudo eopkg up -y, then sudo eopkg check after rebooting => situation unchanged
2) Revert to the restore point prior to the Solus update (sudo eopkg history -t 706), then reboot, then sudo eopkg up -y, then reboot again => situation also unchanged