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!

                • [deleted]

                • Post #112

                gsf Yea but not valve's fsync 😀

                  With next update kernel will be updated systemd and networkmanager?

                    No issues so far and seems a little bit faster. Great work.

                    sothis6881 Updated to new kernel 5.10.1.XX the system failed to boot to budgie desktop. Tried several times getting same problem had to boot in alternate kernel working fine. Is anybody else faced the similar issue? If fixed, can you explain the solution.