Saijin_Naib 5.10 would be our current, not LTS. Our linux-lts is designed for what we consider older, "legacy" hardware that has notable regressions in newer kernels. The RCs aren't available since they're just on an experimental source repo that we have, not something we're going to be supporting more broadly since it'd require additional driver support, build time, etc. Mostly used as a rare playground to test changes or in this case, just get a head start on 5.10 so we can push it to unstable as soon it's released as a proper stable release.

@DataDrake has a fairly clear idea on how he wants to address LTS going forward. My work / testing is limited to future current.

      JoshStrobl Thank you for the clarification.

      I will see if/how I may help test the future LTS then.

        Saijin_Naib In further testing against current (5.6) on my HP EliteBook 2740p, I find that the issue with suspend/resume remains, and in addition, I am subject to random hard-freezes during usage/idling. Performance seems better than LTS, and accessory/peripheral functionality is solid.

        The freeze seems to occur typically within 30min of boot and leads to the system being entirely unresponsive, requiring a hard reset via the power switch.

        Given what I have access to, I'd say that maybe the 4.19 branch might be safer for this vintage hardware, given my issues with 5.6 currently.

            a month later

            i clicked others ( I want latest kernel supporting latest hardware). I wish Solus team uploads 5.9 kernel soon

              And, it’s probably no secret in this forum, 5.10 is expected to be released this upcoming weekend.

                The most fun part of Solus is " It's fast, snappy with latest updates and also sometimes some funny things that doesn't work or sometimes one just need more support" and its all done fine.

                Validated 5.10-rc7 locally on both my desktop and laptop, I've already updated our linux-current locally for it (previously was using our internal linux-next builds), went through and patched all the kernel modules where necessary (namely NVIDIA graphics drivers and VirtualBox). 5.10 is expected to come out Sunday U.S. (Monday here in Finland), so assuming that happens as scheduled I'll get it landed in unstable on Monday.

                Linux 5.10, as well as updates to firmware, nvidia-390-glx-driver, open-vm-tools, openrazer, and virtualbox are now in the unstable repo. Assuming no blockers, should get landed into the stable repo this Friday. If you use the unstable repo, we encourage you to update and test!

                  So this new kernel has fsync support ? I read the changelog but I dont understand very much

                    Saijin_Naib
                    5.10 exhibits the same issues with suspend/resume as the 5.6 branch kernel on my EliteBook 2740p, but positive aspects regarding performance/responsiveness/connectivity are also the same.

                    So, mostly works, but random locks and can't suspend/resume/hibernate.

                    Likely upstream issue? Out of scope due to older hardware (1st gen i5-540m)?

                        JoshStrobl

                        Upgraded my 2 virtual systems (one Budgie, one KDE) using the unstable repo. Upgrade, reboot and login went fine. The initial reboot seemed to take longer than normal, but could have been due to workloads on the host ESXi system.

                          Saijin_Naib 5.10.1-161 works with suspend/resume and otherwise doesn't seem to be unstable under normal usage unlike 5.10.0 and 5.6.x!

                          I find it hard to believe that 5.10.1 would magically work but not 5.10.0 seeing as 5.10.1 fixes two issues which were in regards to specific raid configurations and had nothing to do with suspend / resume.

                              As of now I only needed to switch to the LTS kernel for a small bluetooth problem (posted in the support section). Other than that, I guess I will just keep it as a backup. Current is working fine for me since I guess two years by now. So thanks for all the effort!