Skip to main content

Notes: Nitrux 3.7.1

By Uri Herrera31 October, 2024Notes

Below is a list of release notes we recommend reading before installing the distribution.

📜 Table of Contents

  1. Installing Nitrux
  2. About Memory Usage, is Nitrux eating my RAM?
  3. Virtualizing Nitrux
  4. Filesystem, Security, Privacy, and Anonymization Features Information
  5. Upgrading Nitrux from a Previous Version
  6. Using NX Desktop
  7. Software Management
  8. Creating and Managing Backups
  9. Creating OpenRC and User Services
  10. Creating Network Shares
  11. Support for Other Desktop Environments
  12. Wayland Information
  13. PipeWire Information
  14. MESA Information
  15. Plasma X11 Session Information
  16. Latte Dock Information
  17. NVIDIA Proprietary Driver Information
  18. General Gaming Information
  19. Using Kernel Boot to swap Kernels
  20. Using VMetal in Nitrux
  21. Using Hypervisors in Nitrux
  22. Energy Saving Information
  23. Virtual Consoles (TTY) Information
  24. Editing the GRUB Menu in Nitrux
  25. Using Fcitx5 to change the Input Method
  26. Misc. Information

🗒 Notes

Installing Nitrux

Disclaimer: Nitrux is a Linux distribution comprised of various free and open-source software. Each program’s distribution terms are detailed in /usr/share/doc/*/copyright. Nitrux OS comes with NO WARRANTY, as permitted by law.

About Memory Usage, is Nitrux eating my RAM?

  • Un[u̶s̶e̶d̶]cached RAM is wasted RAM
    • Starting with Nitrux 3.7.1, you may notice that the system uses more RAM than previous versions. This increase primarily results from our optimizations. These changes enable better handling of high-speed network traffic, improved caching mechanisms, and enhanced system responsiveness. Higher memory usage in this context signifies that the system is leveraging available resources more effectively to deliver a smoother and more efficient user experience.
  • Why This Matters
    • Faster Network Performance:
      • Enhanced Buffer Sizes: Larger TCP buffers allow the system to handle higher data throughput, reducing latency and improving overall network stability.
      • Efficient Packet Handling: Increased packet queues enable better management of burst traffic, minimizing packet loss during high network loads.
    • Smoother Multitasking:
      • Increased Caching: Allocating more RAM for application and filesystem caches allows quicker application launches and faster access to frequently used files, enhancing productivity during heavy workloads.
      • Optimized Memory Management: Adjustments ensure that more data is kept in memory before being written to disk, reducing I/O wait times and improving overall system performance.
    • Improved Stability:
      • Higher Free Memory Thresholds: By maintaining higher free memory levels, the system prevents memory shortages that could lead to stalling or reduced performance during intensive tasks.
  • Rest Assured
    • Nitrux is configured to use hardware capabilities to ensure top-tier performance and reliability. The observed increase in RAM usage manifests our commitment to delivering a smoother, faster, and more secure user experience by intelligently leveraging available memory resources. The system ensures that resources are not idle by utilizing available RAM for caching, buffering, and managing system processes, leading to a more responsive and efficient computing experience. Modern operating systems intelligently manage memory allocation. If applications require more memory, the system reallocates resources as needed, ensuring that critical tasks receive the necessary memory without manual intervention.

Virtualizing Nitrux

Disclaimer: We do not develop VirtualBox, GNOME Boxes, or VMware Workstation/Player. If you have issues with these hypervisors, such as graphical problems, please inform their developers at their respective bug trackers.

Filesystem, Security, Privacy, and Anonymization Features in Nitrux

Upgrading Nitrux from a Previous Version

Using NX Desktop

Software Management

  • Nitrux is a distribution that doesn’t revolve around a package manager like other distributions; in Nitrux, the preferred method of obtaining new software is using AppImages. However, we understand that not all software is available as an AppImage. So, by default, we have included various options for users, such as Flatpak and Distrobox, to complement AppImages.
  • Users can also create their AppImages; to do that, see the following tutorials.

Creating and Managing Backups

  • Nitrux users can back up their data using Kup since version 1.1.9 (July 27th, 2019). You can find Kup in System Settings→Backups.

Creating OpenRC and User Services

Creating Network Shares

Support for Other Desktop Environments

  • By default, Nitrux uses the Plasma desktop with our customization layer, NX Desktop. Our desktop shell, Maui Shell, is being developed. Our focus is on Plasma and MauiKit. However, users can install other desktop environments using Distrobox. For more information, see our tutorial, Installing other DEs in Nitrux.
    • ⚠️ Important: Using Distrobox to install other desktop environments is a feature considered “an experiment” by the Distrobox developer, so keep that in mind.
  • Regarding Maui Shell, as of September 1st, 2023, Maui Shell development focuses on Qt6. Therefore, we’re not providing new ISO files at the moment. To test Maui Shell, please compile it using a container.
    • ⚠️ Important: Please report issues with Maui Shell at its bug tracker.

Wayland Information

  • Starting with Nitrux 2.8.1, the distribution uses a Wayland session (Plasma Wayland) by default.
  • Screen sharing is still an issue in Wayland for applications like Discord or Zoom, especially when sharing the entire screen; sharing individual windows may work under Wayland. We recommend using the Plasma X11 session for these applications; see Plasma X11 Session Information.
  • We also include a configuration file for SDDM to use rootless Wayland, but it’s not enabled by default, as it can cause games using DXVK or VKD3D not to work. SDDM using Wayland is experimental.

PipeWire Information

  • Since Nitrux 2.6.0, the distribution uses PipeWire by default.

MESA Information

  • Due to a significant issue with MESA from Git preventing any keyboard input, Nitrux no longer includes development versions of MESA.
  • If using a graphics processor that uses MESA drivers and the GUI does not work, check whether your GPU is loading its firmware. To check, run the following command after logging in to a TTY.
lspci -v | grep -A 10 -i "VGA compatible controller"
lshw -C display

Disclaimer: We do not develop or package MESA. To file bugs against MESA, please use their bug tracker here.

Plasma X11 Session Information

  • Starting with Nitrux 2.8.1, the Plasma X11 session is no longer the default. However, we understand that Wayland may not provide the best experience for many users, especially those with NVIDIA graphic processors. For these users, run the command below to restore the Plasma X11 session as a selectable session in SDDM. 
sudo overlayroot-chroot

mv /usr/share/xsessions/orig.plasma.desktop.bak /usr/share/xsessions/plasma.desktop

sync

exit

Latte Dock Information

  • As of July 2022, Latte Dock is no longer maintained by its developer, meaning there’s no guarantee it will continue to work. Since Nitrux 2.9.0, Latte Dock is no longer included in the distribution.

NVIDIA Proprietary Driver Information

Please note that starting from version 2.5.0 Nitrux includes the latest available NVIDIA proprietary driver.

  • Nitrux includes the latest version of the NVIDIA proprietary driver when we build and publish our ISO files.

Disclaimer: We do not develop the NVIDIA proprietary driver. For issues with the NVIDIA driver, including bugs and adding support for graphics cards, please visit NVIDIA Support.

  • For some laptops with supported discrete graphics through the NVIDIA proprietary driver, adding our X11 configuration for PRIME (where supported) may be necessary to work correctly.
    • Download the script below to add our X11 configuration if your laptop requires it.
      • ⚠️ Important: The script file below creates files in the root directory; see XFS Features and Root Immutability in Nitrux.
      • 🔰 Information: The default TTY for the graphical session can change if your computer utilizes the NVIDIA proprietary driver.
sudo overlayroot-chroot

mount -t devtmpfs dev /dev

mount -t devpts devpts /dev/pts

axel -a -o /usr/bin https://raw.githubusercontent.com/Nitrux/storage/master/Other/nvidia-x11-laptop-conf

chmod +x /usr/bin/nvidia-x11-laptop-conf

nvidia-x11-laptop-conf

rm -f /usr/bin/nvidia-x11-laptop-conf

sync

umount /dev/pts

umount /dev

exit

General Gaming Information

  • Nitrux uses the Liquorix kernel, described as “an enthusiast Linux kernel designed for uncompromised responsiveness in interactive systems, enabling low latency in A/V production, and reduced frame time deviations in games.”

Disclaimer: We do not develop, maintain, or package the Liquorix kernel. Please file bug reports at their bug tracker or ask for assistance on their forums.

  • For a general overview of gaming-related topics in Nitrux, see Gaming in Nitrux pt. 1: Get Started and Gaming in Nitrux pt. 2: Extra Goodies.
  • Nitrux includes a desktop launcher to install Steam, Bottles, and Heroic Games Launcher from the applications menu; we do not include these applications by default.
    • 🔰 Information: These applications will be installed in the background after clicking the launcher in the application menu. The installation time will vary depending on the speed of the connection to the Internet.
  • Alternatively, users can install Lutris (from Flathub) to run Windows software.

Disclaimer: We do not develop Steam or the Steam Flatpak. To report issues about the Steam Flatpak, create an issue at their bug tracker. Also, we do not develop Bottles, Heroic Games Launcher, or Lutris. Please create an issue at their respective bug trackers to report problems with these applications.

  • Nitrux includes a desktop launcher to install the itch.io Store application, which will download and run the official Linux installer; we do not include it by default.
    • 🔰 Information: For more information about running the itch.io Store application in Nitrux, see itch.io Store.

Disclaimer: We do not host, maintain, or create the content at the itch.io Store, nor develop the itch.io client Store application. Please file bug reports at their bug report website here.

Using Kernel Boot to swap Kernels

  • The Kernel Boot (kboot) utility provides a solution to make it friendlier when loading other Linux kernels on the fly. kboot is designed for a particular purpose, making it easier to allow for a faster transition from the currently running kernel to a new kernel and avoiding the time-consuming hardware initialization and bootloader stages. It performs the following steps:
    1. Reads the settings in the specified configuration file.
    2. Then, it uses kexec to load the selected kernel using the parameters from the configuration file.
  • In kernel-related topics, for manual building kernel modules using DKMS, see Building DKMS drivers in Nitrux.

Using VMetal in Nitrux

  • VMetal allows users to run Windows in parallel to Nitrux, providing access to Windows software while allowing them to use their Linux desktops simultaneously. VMetal uses QEMU and KVM (Kernel-based Virtual Machine) on the software side and VFIO and IOMMU on the hardware side, meaning that Windows directly accesses the hardware it utilizes.

Disclaimer: Due to the magnitude of possible hardware combinations and UEFI firmware versions, we cannot guarantee that a specific hardware combination will work out of the box when using VMetal. We do not possess the means to test or acquire every consumer-available product to verify that it will work in VMetal. We have tested VMetal only on the computers we have access to that meet the criteria. Therefore, YMMV. If VMetal works in your hardware configuration, please use hw-probe to let us know what hardware you’ve used.

Using Hypervisors in Nitrux

Energy Saving Information

  • Nitrux includes energy-optimizing software like Powertop and TLP.
    • 🔰 Information: To adequately use Powertop, run it while using the battery so its auto-tune functionality creates the file “saved_results.powertop” in /var/cache/powertop. When using Powertop for calibration, it will toggle various functions like backlight or WiFi. Thus, it may turn your screen black for some time, lose the network connection, etc. Do not touch the machine during the calibration.
    • 🔰 Information: Powertop needs to run 370+ measurements before correctly displaying values for the power usage estimation. Each lasts 20 seconds, meaning Powertop must run for 1h30 in total. To do this, run the commands below. Check the available options in Powertop by running the following command powertop --help. 
sudo overlayroot-chroot

mount -t devtmpfs dev /dev

powertop --calibrate

sync

umount /dev

exit
  • To configure TLP, create or modify our configuration file in the directory /etc/tlp.d using a text editor. Alternatively, TLP UI is available from Flathub; see Software Management.
    • 🔰 Information: For more extensive information about configuring TLP, see the documentation for TLP. TLP UI will write to the default TLP configuration file in the overlay. We recommend copying the edited file in the overlay to the lower directory or editing our configuration file directly.

Virtual Consoles (TTY) Information

  • Nitrux has nine virtual consoles or TTYs (e.g., TTY1, TTY2, etc.) accessible via key combinations like Ctrl+Alt+F1 to Ctrl+Alt+F9 by default. Each console can run a separate login session. The graphical session is available in TTY #9, while the boot console is in TTY #1. Switching to different TTYs can result in graphical corruption in specific setups, i.e., switching from TTY #9 to TTY#2. To workaround this issue, switch to TTY #8 before switching to TTY #9.

Editing the GRUB Menu in Nitrux

  • Run the following commands to edit the GRUB Menu, such as adding or modifying kernel parameters. 
sudo overlayroot-chroot

mount -t devtmpfs dev /dev

mount -t auto $(findfs LABEL=NX_VAR_LIB) /var/lib

micro /etc/default/grub

update-grub

sync

umount /dev /var/lib

exit

Using Fcitx5 to Change the Input Method

  • Since Nitrux 2.8.0, we’ve included Fcitx5 to switch input methods easily. To switch between the input methods the user configures, do the following.
    • First, you should configure the shortcut for Fcitx5 and ensure that it doesn’t conflict with an existing shortcut. Then, add the desired additional input method to the input method group you’re using with Fcitx5.
    • Next, select “Fcitx5 Wayland Launcher” in System Settings→Input method→Virtual Keyboard, log out and log back in.

Misc. Information

  • Visit the following link to see how to contribute to the distribution.
  • We have discontinued minimal ISO releases of the distribution.
  • We have discontinued OVA releases of the distribution.
  • Nitrux is exclusively a 64-bit Linux distribution; we do not use, include, or provide support for 32-bit software.
  • Nitrux has various command-line utilities, including a file manager, text editor, web browser, remote desktop, system monitor, and a single game. Below is a list of these command-line utilities.
    • ftp, hdparm, htop, links2, mc, micro, ncdu, pipx, tmate, tree, and nsnake.
  • Here are various articles, tutorials, and other resources on our blog.
Post Views: 0
Next Post