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.

    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.

    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.

      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).

        8 days later

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

          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.

              13 days later
              7 days later

              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

                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 🙂

                  13 days later

                  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.

                    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

                      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.

                      6 days later
                      19 days later

                      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.

                      11 days later

                      HP EliteBook 2740p
                      Solus 4.1 - Budgie
                      linux-current: Failure upon suspend/resume
                      linux-lts: Suspend/resume work properly

                      I am thankful you maintain both current and LTS, as my wont is to go current/bleeding-edge unless something breaks (hello, suspend/resume),, in which case, lts/stable is a wonderful thing to have.

                      Like you stated. 4.19 seems like a half-measure with likely nearly as much work as going to a 5.x LTS... I'd say maybe going all the way to 5.x LTS will buy you more time to patch/push fixes upstream against a kernel that should in theory, support more hardware than the 4.19 branch... We hope.

                      I know this platform is ancient, but it is performant enough, and I can't get over the form-factor and repariability.

                      (Just discovered Solus after distro-hopping for over a week, seeking a distro where I have easy access to the geospatial tools I need, and they're actually UP TO DATE!!!

                      Solus is wonderful, and has taken the place of Lubuntu for me, which is something since I've been using that since 10.04)

                        12 days later

                        Just my 2 cents or Euro equivalent...Debian Stable offers newer kernels via the Backports repo for those instances where the stable kernel (Solus LTS equivalent) doesn't work well. I'm wondering why users with newer hardware would want to use an LTS kernel.

                        Edit -- Just checked the Debian Testing repos and as of now, the kernel version that would be used in the next stable release would be 5.8.10.x, so maybe it might be a good idea to update the LTS kernel.