Skip to content
  • Announcements regarding our community

    3 10
    3 Topics
    10 Posts
    elsie19E
    It's the end of the year, and 2025.4 snapshot images are here! It's been a quiet few months, but we are proud to announce our end-of-year snapshots. To upgrade to 2025.4, please run rpk update -y Our key highlight this time around is the release of our UBXI Lomiri Desktop package, and our first official UBXI spin images, featuring Lomiri on PINE64 devices. This key delivery is tied to our sponsorship with UBports, and we hope you are as happy as we are that it has come to fruition. If you want to try out Lomiri on other devices, the ubxi-lomiri-desktop package is also available from Pacstall. Rhino Linux in 2026 We are planning on shaking up our release process for the upcoming year, with the goal of more frequent snapshot releases. Often we have held our releases back due to specific platforms experiencing issues, where others have been prepped and ready. We intend to break this up so that tried and tested images make their way through the cycle, without being bogged down and held behind by other platforms. In addition, we aim to have more smaller, maintenance-style releases, featuring the latest package updates, so that upgrades do not build up for so long. By breaking up our release process, we hope that we can continue to iterate and resolve issues at a more timely pace than we previously had. With this new process, not every release will necessarily be worthy of a blog post. Throughout the year, we will still be providing "Updates to Rhino Linux" blogs at a similar frequency to our current cycle, with a collection and breakdown of our changes from the last time we posted about them. Finally, we are still actively working towards several commitments we made in 2025, with us now aiming to release additional UBXI packages and disk image spins sometime in the new year, as well as improving our OS builder workflows and documentation. Read the full release announcement here: https://blog.rhinolinux.org/news-24 Website: https://rhinolinux.org/ Download: https://rhinolinux.org/download GitHub: https://github.com/rhino-linux Donate: https://opencollective.com/rhino-linux-and-pacstall Many thanks and happy holidays rolling, The Rhino Linux Team
  • A place to talk about whatever you want

    12 26
    12 Topics
    26 Posts
    D
    By the time you reach Malakor in The Bastion, the match has already asked a lot from you. Ammo, focus, clean movement, all of it. That's why so many players start looking at things like CoD BO7 Bot Lobbies for sale just to get reps in and learn the flow before the real pressure hits. The boss itself isn't only hard because it does big damage. It's hard because the whole fight punishes hesitation. If your team goes in half-ready, with weak weapons or no clear jobs, you'll feel it almost straight away. The best runs usually aren't flashy. They're organised, calm, and built on prep done early. Get the Railgun sorted early The biggest mistake people make is treating the Aetheric Railgun like a side objective. It isn't. It's the run. You want that thing upgraded as soon as possible, because Malakor's shield phase drags forever without it. Once the fight starts, the generator overload mechanic becomes the centre of everything. You're watching for the ritual cue, lining up the shot, and trying not to get body-blocked by a swarm at the same time. It's messy, and that's the point. One player missing the timing can throw the whole cycle off. If you're playing with a squad, keep comms short and clear. No one needs a speech in that moment. Just call the prompt, call the side, take the shot. Control the floor before it controls you After the shield breaks, the arena gets much nastier. The Void Rifts are what usually ruin good attempts. They slow your movement, clutter your screen, and make dodging feel awkward at the worst possible time. You'll notice really quickly that standing still to reload is a gamble. A bad step and suddenly you're trapped in damage while Malakor winds up a heavy hit. What helps most is giving each player one simple responsibility. One person keeps the boss angled away and draws heat. The others clear lanes, stabilise rifts, and avoid bunching up. It doesn't need to look perfect. It just needs to stay controlled enough that nobody panics and burns all their resources too soon. Save enough for the ugly last stretch Loads of teams reach the final chunk of Malakor's health and then completely lose discipline. That last stretch is where the fight gets sloppy. The screen shakes, enemies flood in, and everyone starts thinking the kill is already secured. It isn't. This is the moment to dump field upgrades, lethal equipment, and any damage burst you've been holding, but not at the cost of awareness. Keep moving in small circles. Keep one eye on the mobs. If you tunnel vision the boss, you can still get folded with almost nothing left on his bar. Plenty of failed clears happen right there, and it feels awful every time. Why the clear feels worth it What makes Malakor memorable isn't just the difficulty. It's that the fight asks for proper Zombies fundamentals under pressure: movement, timing, communication, and not doing anything silly when the room gets loud. Once the boss finally drops, the rewards feel earned because the game made you work for every phase. If you're still chasing a cleaner run, it helps to practise routes, sharpen your setup, and use reliable community resources like U4GM for game items and services that can save time before you jump back in. Stay sharp on the generators, keep the Railgun ready, and the whole fight starts to feel a lot more manageable.
  • Get help and support for Rhino Linux

    4 18
    4 Topics
    18 Posts
    Y
    $ sudo apt install nvidia-driver-590-open The following packages were automatically installed and are no longer required: gcc-15-base:i386 gnome-bluetooth libclang-cpp21 libicu76 libimath-3-1-29t64 libllvm20:i386 libqt5charts5 libsimdutf29 libwoff1 linux-headers-6.18.0-8 linux-headers-6.18.0-9 linux-headers-6.18.0-9-generic linux-image-6.18.0-9-generic linux-modules-6.18.0-9-generic linux-tools-6.18.0-9 linux-tools-6.18.0-9-generic nvidia-firmware-580-580.126.09 nvidia-firmware-580-580.95.05 Use 'sudo apt autoremove' to remove them. Installing: nvidia-driver-590-open Installing dependencies: nvidia-dkms-590-open nvidia-kernel-source-590-open REMOVING: nvidia-dkms-590 nvidia-driver-590 nvidia-kernel-source-590 Summary: Upgrading: 0, Installing: 3, Removing: 3, Not Upgrading: 3 4 not fully installed or removed. Download size: 8,292 kB Freed space: 88.6 MB Continue? [Y/n] Get:1 http://ca.archive.ubuntu.com/ubuntu devel/restricted amd64v3 nvidia-kernel-source-590-open amd64 590.48.01-0ubuntu5 [8,260 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu devel/restricted amd64v3 nvidia-dkms-590-open amd64 590.48.01-0ubuntu5 [17.4 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu devel/restricted amd64v3 nvidia-driver-590-open amd64 590.48.01-0ubuntu5 [14.0 kB] Fetched 8,292 kB in 1s (8,021 kB/s) (Reading database ... 400319 files and directories currently installed.) Removing nvidia-driver-590 (590.48.01-0ubuntu5) ... Removing nvidia-dkms-590 (590.48.01-0ubuntu5) ... Removing all DKMS Modules Done. INFO:Disable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad update-initramfs: deferring update (trigger activated) Removing nvidia-kernel-source-590 (590.48.01-0ubuntu5) ... Selecting previously unselected package nvidia-kernel-source-590-open. (Reading database ... 399711 files and directories currently installed.) Preparing to unpack .../nvidia-kernel-source-590-open_590.48.01-0ubuntu5_amd64v3.deb ... Unpacking nvidia-kernel-source-590-open (590.48.01-0ubuntu5) ... Selecting previously unselected package nvidia-dkms-590-open. Preparing to unpack .../nvidia-dkms-590-open_590.48.01-0ubuntu5_amd64v3.deb ... Unpacking nvidia-dkms-590-open (590.48.01-0ubuntu5) ... Selecting previously unselected package nvidia-driver-590-open. Preparing to unpack .../nvidia-driver-590-open_590.48.01-0ubuntu5_amd64v3.deb ... Unpacking nvidia-driver-590-open (590.48.01-0ubuntu5) ... Setting up nvidia-kernel-source-590-open (590.48.01-0ubuntu5) ... Setting up linux-image-6.19.0-5-generic (6.19.0-5.5) ... I: /boot/initrd.img is now a symlink to initrd.img-6.19.0-5-generic Setting up linux-image-6.19.0-3-generic (6.19.0-3.3+1) ... I: /boot/initrd.img.old is now a symlink to initrd.img-6.19.0-3-generic Setting up nvidia-dkms-590-open (590.48.01-0ubuntu5) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia/590.48.01 DKMS files... Building for 6.13.0-061300rc1-generic, 6.18.0-9-generic, 6.19.0-3-generic and 6.19.0-5-generic Building for architecture x86_64 Building initial module nvidia/590.48.01 for 6.13.0-061300rc1-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch... done. Building module(s).............. done. Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia.ko Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-modeset.ko Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-drm.ko Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-uvm.ko Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-peermem.ko Installing /lib/modules/6.13.0-061300rc1-generic/updates/dkms/nvidia.ko.zst Installing /lib/modules/6.13.0-061300rc1-generic/updates/dkms/nvidia-modeset.ko.zst Installing /lib/modules/6.13.0-061300rc1-generic/updates/dkms/nvidia-drm.ko.zst Installing /lib/modules/6.13.0-061300rc1-generic/updates/dkms/nvidia-uvm.ko.zst Installing /lib/modules/6.13.0-061300rc1-generic/updates/dkms/nvidia-peermem.ko.zst Running depmod... done. Building initial module nvidia/590.48.01 for 6.18.0-9-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch... done. Building module(s).............. done. Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia.ko Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-modeset.ko Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-drm.ko Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-uvm.ko Signing module /var/lib/dkms/nvidia/590.48.01/build/nvidia-peermem.ko Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia.ko.zst Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-modeset.ko.zst Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-drm.ko.zst Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-uvm.ko.zst Installing /lib/modules/6.18.0-9-generic/updates/dkms/nvidia-peermem.ko.zst Running depmod... done. Building initial module nvidia/590.48.01 for 6.19.0-3-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch... done. Building module(s)............(bad exit status: 2) Failed command: unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j10 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNEL_IBT= modules ERROR (dkms apport): kernel package linux-headers-6.19.0-3-generic is not supported Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64) Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information. dpkg: error processing package nvidia-dkms-590-open (--configure): installed nvidia-dkms-590-open package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of nvidia-driver-590-open: nvidia-driver-590-open depends on nvidia-dkms-590-open (<= 590.48.01-1); however: Package nvidia-dkms-590-open is not configured yet. nvidia-driver-590-open depends on nvidia-dkms-590-open (>= 590.48.01); however: Package nvidia-dkms-590-open is not configured yet. dpkg: error processing package nvidia-driver-590-open (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for dracut (110-1ubuntu2) ... update-initramfs: Generating /boot/initrd.img-6.18.0-9-generic Processing triggers for linux-image-6.19.0-5-generic (6.19.0-5.5) ... /etc/kernel/postinst.d/dkms: Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Autoinstall of module nvidia/590.48.01 for kernel 6.19.0-5-generic (x86_64) Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch... done. Building module(s)..............(bad exit status: 2) Failed command: unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j10 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19.0-5-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-5-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNEL_IBT= modules ERROR (dkms apport): kernel package linux-headers-6.19.0-5-generic is not supported Error! Bad return status for module build on kernel: 6.19.0-5-generic (x86_64) Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information. Autoinstall on 6.19.0-5-generic failed for module(s) nvidia(10). Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. run-parts: /etc/kernel/postinst.d/dkms exited with return code 1 dpkg: error processing package linux-image-6.19.0-5-generic (--configure): installed linux-image-6.19.0-5-generic package post-installation script subprocess returned error exit status 1 Processing triggers for linux-image-6.19.0-3-generic (6.19.0-3.3+1) ... /etc/kernel/postinst.d/dkms: Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Autoinstall of module nvidia/590.48.01 for kernel 6.19.0-3-generic (x86_64) Applying patch 0001-uvm-Fix-build-failure-for-Linux-kernel-6.19-and-late.patch... done. Building module(s)............(bad exit status: 2) Failed command: unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j10 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.19.0-3-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.19.0-3-generic/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNEL_IBT= modules ERROR (dkms apport): kernel package linux-headers-6.19.0-3-generic is not supported Error! Bad return status for module build on kernel: 6.19.0-3-generic (x86_64) Consult /var/lib/dkms/nvidia/590.48.01/build/make.log for more information. Autoinstall on 6.19.0-3-generic failed for module(s) nvidia(10). Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. run-parts: /etc/kernel/postinst.d/dkms exited with return code 1 dpkg: error processing package linux-image-6.19.0-3-generic (--configure): installed linux-image-6.19.0-3-generic package post-installation script subprocess returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: nvidia-dkms-590-open nvidia-driver-590-open linux-image-6.19.0-5-generic linux-image-6.19.0-3-generic Error: Sub-process /usr/bin/dpkg returned an error code (1) Tried with both nvidia-driver-590 and nvidia-driver-590-open
  • 2 Topics
    3 Posts
    J
    I could not figure out how to do it with pacstall, but with some experimentation with apt, this works sudo apt remove linux-modules-6.17.0-061700rc6-generic for example
  • The Rhino Linux issue tracker.

    32 35
    32 Topics
    35 Posts
    oklopferO
    Associated tracker issue: https://github.com/rhino-linux/tracker/issues/126 oklopfer created this issue in rhino-linux/tracker open Important Pacstall update (February 2026) #126 A recent change in upstream Ubuntu's coreutils (via uutils) causes breakage to Pacstall, which prevents it from being able to run *any* commands. We have pushed an [emergency patch](https://github.com/pacstall/pacstall/releases/tag/6.3.9) to resolve this issue, but running `rpk update` may result in Pacstall being unable to update itself. To fix this, please run the following command to update it manually: ```bash LC_ALL=C pacstall -U ``` We apologize for any caused inconvenience.
  • Distributed hotfixes for Rhino Linux will be announced here.

    1 3
    1 Topics
    3 Posts
    oklopferO
    https://github.com/rhino-linux/rhino-setup/pull/85 oklopfer opened this pull request in rhino-linux/rhino-setup merged fix: nix install #85