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

It also uses OpenRC instead of systemd. New in this release is kboot, a utility to switch kernels on-the-fly without needing a reboot, and VMetal, which allows users to run Windows in parallel to Nitrux to provide users of access to Windows software.

  • Pieresqi@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Looks interesting but I think claims of VMetal in regards of gaming are kind of bullshit. I have been looking into running windows/Linux in VM and have it full access to GPU (GPU pass through) and there are 2 major problems.

    1. Nvidia and amd being scummy and having firmware limiters in consumer GPUs to segment their products. This should be “fixable” by modifying firmware but … Yeah… Not very comfortable thing to do

    2. Motherboards not having support or worse have broken implementation of iommu.

    Maybe my “research” was bad. Let’s hope someone will correct me.

    • d3Xt3r@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Not sure what firmware limiters you’re talking about? I’m using a cheap ASUS board (B450i-gaming), a Zen 2 CPU and a 6600 XT, and single GPU passthru works just fine for me on Arch using this guide. (I haven’t tried VMetal or this new release of Nitrux yet). Yes, some manufactures are iffy about IOMMU support, mostly Intel-CPU and Intel-based boards in my experience, but if you’re using AMD you should be fine.

      There is something called an ACS override patch, but that’s a kernel patch not a GPU firmware patch, and from my understanding, that’s for dual-GPU users. Regardless, it doesn’t modify your firmware in any way.

      • Pieresqi@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Not sure what firmware limiters you’re talking about?

        The same limitation mentioned it the guide you shared:

        This solution basically hands over the GPU to guest OS upon booting the VM and hands it back to the host OS upon powering off the VM. The obvious downside of this is that you can’t use the host OS (at least graphically) while the guest is running. It is therefore highly recommended that you set up SSH access to your host OS just in case of issues.

        Also thanks for sharing it. I will try it some other time. 🙂

        Patch NVIDIA BIOS (only for Pascal GPUs)

        Only 10xx is affected or older cards are too ?? 😑