Let's talk about the LTS kernels

[deleted]

DataDrake You're my hero,a very good person and we know that you always made a lot of effort to keep Solus the best OS in the world, don't bother to reply to people that is rude.

I promise that in a near future you will receive a good contribution for all the love that you put in this beautiful OS. When you enable donations and publish Solus 4.2 I think that then it's going to be a really important chapter in Solus History 🙂

DNI_R

Going to 5.4 would mean that people that have older laptops with nvidia cards and optimus will have to face screen tearing all the time with nvidia drivers installed (which most likely will be 390.xx series since the newest drivers don't support many older cards and it's probably a risk to run it, then again i don't if the issue was solved in the newest drivers). At least this is an issue that i got after linux-current was upgraded from 5.3 to 5.4 on Solus (when 5.4 was first introduced and later reverted due to various issues - https://discuss.getsol.us/d/3240-screen-tearing-returned-after-latest-updates. And the sequel when 5.4 was re-introduced and the issue remains till this day: https://discuss.getsol.us/d/3432-screen-tearing-returned-once-again-after-the-latest-updates). For past few months i used mostly LTS kernel and screen tearing can be managed there with echo "nvidia-drm.modeset=1" | sudo tee /etc/kernel/cmdline.d/50-nvidia-drm.conf sudo clr-boot-manager update, but on linux-current, that doesn't work anymore. I am not knowledgeable about linux and nvidia drivers and don't know if it could be fixed in any other way on my laptop and i haven't found a solution for that, so i still use LTS since this happened and at least there is no screen tearing. I do have both kernels installed and boot into the linux-current occasionally to check if this was somehow fixed, but it seems that it isn't and (probably?) won't be.

So for now i chose "I had a bad experience with linux-current updates". I wouldn't be very happy with return of screen tearing on nvidia with 5.4 (for me it basically means that there will be no difference between the linux-current and LTS will be used for backup), but i guess you have to move forward. So whatever the decision is, i will respect it. At the worst scenario i will go back to Intel drivers (i don't know what the current situation with screen tearing is there though) and dual boot to windows to play games if i want.

GueGuerreiro

DataDrake I was using my laptop for work over the week, so I couldn't really do it earlier, but I've now opened the thread at https://discuss.getsol.us/d/4942-can-t-boot-into-latest-kernel, if you could lend me a hand there, I would greatly appreciate it.

Scupake

Please either keep a package for a 4.X kernel or make install a kernel like Liquorix or Zen easier, my computer for some reason can't boot into "default" 5.X kernels.

DataDrake

Scupake We have no plans to ever support a patched kernel like Liquorix or Zen. I feel dirty enough having to patch ours for proper AppArmor support, let alone having extensive patch sets to audit on top of normal kernel changelogs.

AguxOne

I'm not expert in this subject, but i'm suspecting that the kernel that Solus 4.1 is using right now is creating some issues. I tried so hard to install a fresh install of Solus 4.1 Plasma and Budgie, and finally gave up (my issues are related here in this post https://discuss.getsol.us/d/4931-unable-to-boot-solus-4-1-after-a-succesful-efi-fresh-install
However today i took time to look for and old Solus Iso, i found the Solus 4.0 Budgie ISO and tried to install it in exactly the same way.
Magically it booted right away without problems after a fresh install. However after aplying the Requiered Updates, i am left with a white blinking cursor when trying to boot.
I was reading that many had issues, so maybe it is related somehow. I am using a Ryzen 2200g processor, a uefi compatbile motherboard and an nvidia gtx1060.

g66925

DataDrake
In Oct 2019 I got rid of Win7 and started heavy using Solus. It is working rock-solid on LTS kernel (with one issue -- display remains dark after hibernation woke).

Hardware: ThinkPad X201s
CPU: Topology: Dual Core model: Intel Core i7 L 620 bits: 64 type: MT MCP L2 cache: 4096 KiB Graphics: Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1: 1600x1200~60Hz 2: 1920x1200~60Hz

When I boot current.5.4.12-143 or current.5.6.18-155, DE in couple minutes freezes (Caps Lock LED blinking).

Getta91

So I am kinda lost now...
@DataDrake, did the solus team decided to upgrade the LTS kernel or not?

DataDrake

Getta91 I've been in the middle of a sizable Haskell upgrade all week, so kernels haven't been on my mind. With everything else being upgraded this sync cycle I also didn't want to introduce even more churn. Based on the feedback I have received, I would like to upgrade to 4.14 for awhile while 5.4 stabilizes or the next LTS is announced, from there I will decide whether or not to upgrade to 5.4 or the latest LTS. We will skip 4.19 entirely.

sothis6881

DataDrake Seems like 5.10 will be the next LTS.

ghostv33

DataDrake be sure to include this fix if u can
As for some of us
Mate version breaks with latest kernel 🙂
https://discuss.getsol.us/d/4717-display-problem-installing-solus-mate

g66925

@DataDrake I did resolve problem with current kernel and my ThinkPad x201s here: <https://dev.getsol.us/T9183>. Therefore I can withdraw vote for kernel 4.9 version.

holski

I just got a tuf a15 that runs a 4800h and 2060 and Solus 4.1 won't boot (some ppm issue). The only OS that work on it are Fedora and OpenSUSE, so I am using fedora for now. But, I really want to get solus running on it. Solus saves me so much time because I can access my network folders from every piece of software because the Solus mounting utility is so easy and powerful. The OS is just a breeze. Can someone let me know if i would be able to put the iso on a USB with Balena, and the update it is live to try and get a newer kernel durring install. I think with the 4800H you need at least 5.6.3. I really can't wait until that is available with Solus OS.

PS Solus is running great on my thinkpad T450, and two T5500 with dual xeons, which is impressive range of hardware. Kudos to the people that made this!!! No more copying and pasting back and forth from network, or mounting to fstab in terminal <3

putzerstammer

holski

the latest kernel is 5.6.18

kaktuspalme

holski What you could try is install Solus in another Laptop or PC, update the system and then just swap the m.2 to your A15. Otherwise we have to wait until we get a new ISO 🙂

kp2401075

I've been using linux-current from solus3 days never had any issues.

elfprince

kp2401075 Same here, except on a couple occasions wifi chip was not supported. 🙂

Vibhi

I just updated mine Linux Kernel and after reboot i get screen saying something bad happend with logout button.I am using solus budgie 4.1.
How can i switch to LTS version of Kernel
AMD® A4-3330mx apu with radeon(tm) hd graphics × 2 with 1.5 GB RAM.

seagle

Vibhi this thread isn't intended for such support questions, you should have searched for existing problems like yours or opened a new thread if your question isn't answered anywhere already.

But since we're already here... Check out the articles on this page: https://getsol.us/articles/troubleshooting/
Probably most fitting to your question: https://getsol.us/articles/troubleshooting/boot-management/en/#bring-up-the-boot-menu-with-no-timeout-set

just

There are 8 (eight) Solus installations here. They are independent one from another. Each DE is installed in its own, separate, independent partition.

4 DEs run on 5.6.19-158.current kernel. They are installed in sda6, 7, 8, 9 partitions. From time to time each DE crashes on boot up. It's a pain.

4 other DEs run on 4.14.189-161.lts kernel. They are installed in sda10, 11, 12, 13 partitions. None crashes on boot up. No problems. Never.

The laptop has 2 (two) MBR (msdos)-partitioned internal hard disks. Each disk has 16 usable partitions. Paritions are labeled as:

sda1, sda2,.. sda16 on the 1st disk
sdb1, sdb2,.. sdb16 on the 2nd sisk

Seems like 5.6.19-158.current kernel can't distinguish well between two internal disks. From time to time it mixes sda... with sdb... partitions on boot up and in file managers. It's an early impression. Didn't investigate deeper yet.

Nothing similar happens in 4 other DEs, running on 4.14.189-161.lts kernel. They never crash on boot up. Never mix sda... with sdb... paritions in file managers. Solus DEs with LTS kernel seem to be rock-solid.

Conclusion.

Solus Plasma, Gnome, Mate, (...) with 5.6.19-158.current kernel are not reliable
Solus Plasma, Gnome, Mate, (...) with 4.14.189-161.lts kernel are more reliable

Thanks for reading

Edit: Typo.

niceloaf

DataDrake
Having a stable kernel is nice, but a backup is always worth it!

michaelh

just 2c from the peanut gallery: my girlfriend's 2019 Dell XPS 13 runs like butter on current but gets the black screen and cursor (no boot) with LTS. My personal (unsolicited) opinion is that 5.4 would likely be a good option at this point, but that said, i don't think 4.19 would be a bad option.

been using solus since it was evolve, and it has eclipsed all the other distros to become my daily driver and the distro i put on all my friends machines when they want to try linux. THANK YOU for your work.

« Previous Page Next Page »