Solus Updates for Week 10, 2025

brent

mkl brent

Did not happen for me. (Gnome DE)

was just a psa--I've never seen update results affect everyone that got them; only a handful 🙂 . likely had to do with theming

mkl

brent was just a psa

What's a psa/PSA ?

brent

mkl short for Public Service Announcement. meaning I was letting people know I had a fix if it happened to anyone else

edit: a slang-y term mostly

BuzzPCSOS

brent Well I'm glad that's been cleared up! Like so many others I googled PSA and just got results for "PSA test". Was wondering how that fitted in.
I hate TLAs, they always mean something that isn't featured on internet searches.

banger

Remote desktop turning on after reboot is fixed thanks Reilly.

brent

BuzzPCSOS I hate TLAs, they always mean something that isn't featured on internet searches.

I'm not asking what that is 🙂 !

BuzzPCSOS

brent Three Letter Acronyms 😄

Animpacz

pomon

Ah, ok. Can I simply enlarge it like other partitions?

Here is the output:
sudo clr-boot-manager list-kernels

com.solus-project.current.6.12.17-314
' com.solus-project.current.6.12.12-313
com.solus-project.current.6.12.9-312
com.solus-project.lts.6.6.80-265
com.solus-project.lts.6.6.75-264
com.solus-project.lts.5.15.87-196

sudo du -d1 -h /boot

415M /boot/EFI
32K /boot/loader
415M /boot

ls /boot/EFI/com.solus-project/

bootloaderx64.efi
BOOTX64.CSV
grubx64.efi
initrd-com.solus-project.current.6.12.12-313
initrd-com.solus-project.current.6.12.9-312
initrd-com.solus-project.lts.5.15.87-196
initrd-com.solus-project.lts.6.6.75-264
initrd-com.solus-project.lts.6.6.80-265
kernel-com.solus-project.current.6.12.12-313
kernel-com.solus-project.current.6.12.17-314
kernel-com.solus-project.current.6.12.9-312
kernel-com.solus-project.lts.5.15.87-196
kernel-com.solus-project.lts.6.6.75-264
kernel-com.solus-project.lts.6.6.80-265
mmx64.efi

Should I delete some older ones? Is this necessary or will they be removed automatically?

pomon

Animpacz
I need to emphasize that any actions related to kernels and the /boot partition are very risky, so please be very careful.

I see that you have the latest kernel 6.12.17, so try switching to it if you haven't already:

sudo clr-boot-manager set-kernel com.solus-project.current.6.12.17-314 && sudo clr-boot-manager update

If you don’t have the LTS kernel installed, remove its related entries.
Check: eopkg li | grep linux-lts
Remove: sudo clr-boot-manager remove-kernel <kernel-name>

If that doesn't help, try deleting old kernel-related entries in:
/boot/EFI/com.solus-project/
Keep only the two most recent ones.
After making any changes, always run:

sudo clr-boot-manager update
or
sudo usysconf run -f

If you have the possibility, meaning free space before or after the /boot partition, you can resize it using a tool like gparted.

brent

BuzzPCSOS I don't consider PSA old-school, archaic, or out of date in the least since I still hear/read it in modern vernacular...of course I wouldn't trust or believe google if I asked for a common weather report so there's that and it makes the search engine problem in line from what i'd expect from them...

Obviously 248 🙂!! acronyms cropped up (according to acronym finder) but I know my info about Libre Writer was no t a Prostrate Specific Antigen or Planning and Services Act (pasa technically, correct?), Psoriatic Arthritis (PA, no???). But I could see it is close to the Public Service Association or even the Postal Services Act.

The more AI, the worse the search engine. Remember when search engines were reliable? How could they possibly have deteriorated with time?
Eh---I digress

mkl

pomon If you have the possibility, meaning free space before or after the /boot partition, you can resize it using a tool like gparted.

I think it should be mentioned that this requires booting into a live system so that the partitions are not mounted. Right?

snowee

pomon
You touched upon a topic that I always wanted to ask:

Is removing old kernel-related EFI entries a recommended best practice for annual spring-cleaning and general maintenance?

After all, if one has continuously updated Solus over a sufficiently long period of time, eventually the boot partition will be clogged up with old entries (even if you have 1GB as recommended), which will lead to issues such as the one Animpacz and many others in the past have encountered, correct?

Animpacz

pomon

Switching (set-kernel) to the lates kernel prompts a similar error message demanding more space.

As I always want to use the latest kernel available I removed the package linux-lts.

Also I removed all lts and older concurrent kernels with clr-boot-manager together with the entries under
'/boot/EFI/com.solus-project/'.
After cleaning up and a successful execute sudo clr-boot-manager update and sudo usysconf run -f the latest kernel was selected and I could reboot into the new kernel.

The output of df -h | grep boot is now:

/dev/nvme0n1p1 489M 183M 306M 38% /boot

..and from sudo du -d1 -h /boot is now:

183M /boot/EFI
24K /boot/loader
183M /boot

Your instruction were clear and worked well, it looks good now and I got a better understanding of it. Thank you a lot!

pomon

mkl The /boot partition does not mount at system startup (that's the case in my situation). Unless you mounted it manually later. Therefore, there shouldn't be any issues performing operations like resizing this partition. However, if any problems arise, then yes, you should definitely use Solus Live.

snowee As I mentioned earlier, any operation on system files, including the /boot partition, can lead to system corruption, so I recommend extra caution.
I removed unnecessary entries in /boot/EFI/com.solus-project/, I ran sudo clr-boot-manager update, and restarted. Everything is fine.

minh

Just to update the issue I have since the update of Linux Kernel in previous post.
https://discuss.getsol.us/d/11355-solus-updates-for-week-6-2025/18.
During the weekend, I have chance to try the Plasma on beside current Xfce that I have been used for some months. Just to check if reinstall fix this issue.

What I found is not problem of Nvidia to combine with the latest kernel. It's something between latest kernel vs the /boot partition on my M2 (nvme) instead.

I have tried to boot Plasma or Xfce from the /boot partition setup on SSD. I could boot them both (use latest kernel).
And then I tried to boot them from the old /boot partition setup on M2, they both having same error.

Error preparing initrd: Device error
start_image () returned Device Error

So my conclusion is that something to do with latest Linux Kernel vs /boot partition on M2 drive. It works fine with SSD. And nothing to do with Nvidia drive. Hope it helps someone to troubleshoot this issue.

Phiqu

I also reinstalled Solus xfce now with Week10 besides CachyOS on my nvme.
I still get the:
Error preparing initrd: Device error start_image () returned Device Error
But Solus finally booting again with current kernel and current nvidia driver for my 1070.

Edit.
With "Solus Linux Bootloader" I get the Device Error from above. When I choose the "Linux Boot Manager" as priority boot option for Solus it is booting without any error.

brent

@BuzzPCSOS @mkl

actually pretty common to use PSA at this joint.
But when i did go online, like you, I got nowhere.
I will spell it out next time I have a fix for someone, noted. Common at Solus, uncommon on Google. Makes sense.

Harvey

Cherry-picked vivaldi-stable 7.1.3570.60

WetGeek

Now downloading the Vivaldi upgrade at 340 KB/s on a fast i7 laptop, and has been at it for several minutes. Something seems very familiar about that.

Harvey

WetGeek

Probably just the connection between you and the server, as it downloaded at 15.03MB/s for me. It is also no where near the file size limit issue that caused issues with our CDN recently.

mkl

WetGeek
vivaldi-stable-7.1.3570.60-284-1-x86_64.eopkg (147.1 MB)100% 49.72 MB/s [00:00:00]
Just a few seconds here...

« Previous Page Next Page »