Skip to content

Kernels

4 Topics 26 Posts

Discussion about Soplos Kernels

  • Kernel number limit

    4
    0 Votes
    4 Posts
    12 Views
    subdesS
    Hi Dan, Thank you so much for the kind words! We're really glad you're enjoying Soplos, especially coming from so many years on Debian Stable with Xfce. If any questions come up or you find anything to improve, we're here. Best regards
  • VMware Workstation

    10
    0 Votes
    10 Posts
    75 Views
    subdesS
    Hi masterpier, Great that it's working for you on Tyson, and thanks for sharing your impressions on performance and KDE! About the welcome screen script: it installs exactly the same package (soplos-vmware-modules) as doing it from the terminal, and it has worked fine for other users. Most likely your system just needed updating before using it. It's always a good idea to do that before installing anything from the welcome screen: sudo apt update sudo apt full-upgrade If it fails again after updating, let us know what message it showed and we'll take a look. Thanks for your feedback and for supporting the project. Best regards, The Soplos Linux Team
  • Kernel & intel mbp

    10
    0 Votes
    10 Posts
    158 Views
    subdesS
    Thanks for the offer, Dan669! Good news is we've already validated Soplos on aluminum unibody MacBook Pros across several generations, including 64-bit EFI models like yours, so your 5,5 and 9,2 wouldn't really add new coverage there. Appreciate the willingness to help test though!
  • Soplos Kernels

    2
    0 Votes
    2 Posts
    98 Views
    subdesS
    Hi JoeDirt, thanks for asking. The big list under "Soplos Kernels" is pre-populated directly from our repository — those are prebuilt kernels available via apt, not something generated by a system update. On Secure Boot: those prebuilt kernels from the "Soplos Kernels" tab aren't signed — no shim — so they won't boot with Secure Boot enabled. But as you mentioned, Soplos Kernel Installer also lets you compile your own kernel with MOK (Machine Owner Key) signing, and that does work with Secure Boot on. That's the path you already used when you manually built your "signed" kernel. So your options are: disable Secure Boot to use the prebuilt kernels, or keep compiling your own with MOK if you want to stay on Secure Boot.