Below is the topology of the setup:

• Pump goes to the the stock fan header.
• 2 x 120mm rad fans go to channel one of the hub
• 1 x 80mm VRM fan goes to channel two of the hub
• Sensor one of the fan hub goes to the ram backplate, this is just for monitoring ram temps
• Sensor two goes to the VRM’s directly under the VRM fan

Pump: You set the onboard header to 100% for the pump, or a custom curve so the pump goes to 100% over 40C or 50C, but these pumps wont run any lower than about 70% speed, so this is not all that important, they are very quiet, even at 100%.

120mm Rad Fans: You need to create a profile in OpenLinkHub to control the main 120mm rad fans, you combine CPU and GPU temp input data and create a fan curve for them, I set them to turn off under 40C and 100% at 80C, slight ramp up to 65C then aggressive ramp to 80C, they will usually run at 50 to 60% under extreme loads and will be almost un-audible.

VRM Cooling Fan: You need to create a profile in OpenLinkHub you use the input from sensor two and create a fan curve for the VRM fan, I set mine for zero (off) under 40C and ramp up to 60% at 70C this is usually enough, but you can fin tune it from here.

Before you start, if you have a Microslop Winblows machine, I suggest updating the firmware on the Hub, and using the Corsair software, create yourself some failsafe profiles for the fans, to run at 40% to 60% and use the sensor date from both sensor one and sensor two for this, this way during boot up and shutdown or in the even that OpenHubLink goes down, the hub falls back to its internal cooling profile.

I also set the RGB strip on my Pro case to display the GPU temp, it shifts from green to red, depending on the temp, its a nice easy way to see how things are if your not running Mangohud, but this is totally optional.

This was running prior to the latest update, does anyone know what could cause this and the potential fix? Happy to share more details and apologies if this is vague

I tested the daisy chain method and while all the fans started spinning the led on the aio pump didn’t light up. Can or should I use a different header for the pump? If so, which one?

I am getting very slow download speeds on wifi while using Bazzite specifically. I’m dual booted with Window 11 on its own separate drive and the issue isn’t a problem there, nor am I experiencing generally slow internet on any other device. Here is my wifi speed test on Bazzite when communicating to the most local server to me:

Due to the age of my account here, I can’t post images of my other speed tests. The speed test for wifi on Bazzite is clocking about 23.60 Mbps and Win 11 is clocking 472.65 Mbps which is the expected speed range I should be getting. I’m also getting around 470 Mbps on my other devices (phone, tablet, other computers). Ethernet speed tests are more or less the same between the OSs: 90-95 Mbps.

I looked around to find some troubleshooting steps on reddit, github, discord, and this forum and attempted those steps from people running into similar issues. Here is what I’ve tried:

-Set metered connection to “no”. Issue persists.

-Turned off IPv6. Issue persists

-Turned off power-saver mode. Issue persists.

-Tested with iwd on and off. issue persists regardless.

-Did a system update yesterday. issue persists.

I use the built in wifi card that shipped with my mobo. Mobo is ROG MAXIMUS Z790 HERO BTF and built in card is Intel WiFi AX211. The only primary difference between the Windows 11 and Bazzite installation unique to wifi is that I had to install the asus driver for the wifi card to get it to connect to my network. Bazzite worked OOB. But since I’m getting expected speeds on everything else, it doesn’t seem like the asus driver is doing anything uniquely special.

Does anybody have any ideas on some additional troubleshooting steps I can take to improve the wifi performance short of doing a full reinstall of the distro? I’m not quiet sure where to go from here beyond doing the distro reinstall hail mary. Also if anybody needs anymore info about my system for troubleshooting, let me know.

I don’t have a guide, but Old Lamer is doing one at the moment, he will have a video up soon.

Assembly isn’t too hard, you just need to pay attention to cable management.

I recommend fitting the rad into the back half of the case, fit you 180 USB adaptors, run the cables for them, then slot in the PSU.

If you going to use the Commander Duo hub, then these pics show where I put the thermal sensors for it, and they also depict the best orientation for the radiator, this one is the V1 AIO, if you have the V4 then there pipes stick out a little more as the pump is actually on the radiator, its a little tighter fit, but they still go int he same way.

This video shows hoe the parts go in the front of the case.

NexGen3D: Calibrate Your Flow Rate #bc250 #gamingconsole #3dprinting #steammachine

This one shows how the threaded inserts are installed:

NexGen3D: How To Install the Threaded Inserts in the DIY Steam Machine #bc250 #steammachine

I also drill a small hole through the frame of the fans to run small cable ties through for cable and pipe management, makes things nice and neat, you can drill in this location, or through the side of the frame near the screw hole.

CPU Information
Name AMD Ryzen 5 5600X
Topology 1 Processor, 6 Cores, 12 Threads
Identifier AuthenticAMD Family 25 Model 33 Stepping 2
Base Frequency 4.65 GHz
L1 Instruction Cache 32.0 KB x 6
L1 Data Cache 32.0 KB x 6
L2 Cache 512 KB x 6
L3 Cache 32.0 MB
Instruction Sets sse2 sse3 pclmul fma3 sse41 aesni avx avx2 shani vaes

Memory Information
Size 15.5 GB
DIMM DDR4 Synchronous Unbuffered (Unregistered) 3600 MHz (0.3 ns)

Device Name NVIDIA GeForce RTX 3070
Driver Version: 595.58.03 CUDA Version: 13.2
Max Clocks
Graphics : 2100 MHz
SM : 2100 MHz
Memory : 7001 MHz
Video : 1950 MHz
Temperature
GPU Current Temp : 45 C
GPU T.Limit Temp : N/A
GPU Shutdown Temp : 98 C
GPU Slowdown Temp : 95 C
GPU Max Operating Temp : 93 C
GPU Target Temperature : 83 C
Memory Current Temp : N/A
Memory Max Operating Temp : N/A
GPU Power Readings
Average Power Draw : 24.58 W
Instantaneous Power Draw : 24.54 W
Current Power Limit : 280.00 W
Requested Power Limit : 280.00 W
Default Power Limit : 280.00 W
Min Power Limit : 100.00 W
Max Power Limit : 350.00 W

I want to provide the image ready to use for my team so toolbox may not work.

Any Ideas, best practices?

Kind regards

Martin

Good news - I did manage to run the game. How? I created a new partition on my drive (using GParted) and installed Linux Mint (using Fedora Media Writer), ran system updates (including the Mint recommended NVidia drivers), installed Steam and then installed and ran the game. It ran first time without any issues. So I am now dual booting, but seriously I am in the process of moving any critical docs from Bazzite to Mint and will be using Mint as my primary distro. I’ll keep Bazzite going for a while (out of curiosity), but will not be spending much time in it (maybe run it once a week). I have other distros I want to explore, and to be honest I found Bazzite too restrictive for me wanting to really try different things. It may be ideal as a “console” environment but I want to use it more as a desktop replacement. So I will have to say its not the main one for me, right now.

Thanks again to the community for your assistance, you’re awesome!

I recently discovered an article which points to the huge problem of Linux adoption from a user perspective (link at the bottom of the post). They may express it more precisely than I do, as I am not a native speaker; it’s kinda hard for me. In the section about desktop environments (“The desktop layout is too different”), the author of the article says the same thing I am trying to say. The default is bad, and it damages broad user adoption.

In the pre-Bazzite times, a few of my friends refused to stick with Fedora Silverblue only because of the default desktop layout of GNOME 40+. This, in theory, should be discussed with GNOME developers, but I believe they are not very open to this discussion. And the fact that everybody does about the same defaults (KDE, COSMIC, etc.) is not going to convince them.
I really love GNOME, I just hate it’s defaults.

But since Bazzite’s popularity is enormous, I decided it should be brought to your attention, as you are among the ones who are shaping the mainstream Linux desktop nowadays.

I’ve asked myself (and searched through threads on Discord and here) and for the most part anything asking about A8 support goes unanswered. Competitors such as CachyOS are in the same boat where A8 support isn’t discussed and core functionality is missing.

Windows is… well, it’s Windows.

Absolutely adore what the Bazzite team does and what they’ve accomplished so far, just a little sad to see our A8s in this state for so long, and with the Legion Go 2 being literally twice the price, simply purchasing another Z2 extreme device isn’t really plausible for most people.

• 48 is unused yet pinned,
• 49 is used and pinned,
• 50 is used yet unpinned.

[[date -d tomorrow +%d == “01” ]] && message Satensteinl “Tomorrow is the first, backups today”

and also, I can schedule the backup using crontab to run the backups after 10pm today

You say systemd can do that check at every reboot?

The tool has grown quite a bit over the last few weeks. It still creates and updates GitHub-backed custom bootc image repos, and it could already scan the current rpm-ostree / bootc system to carry layered packages into a new image repo. The newer work has mostly expanded the build options, update workflow, and safety checks. I have NOT tested all these features yet; in fact, I’d love it if anybody uses it and could report any issues If not, that’s ok. I’m just having fun with it anyhow, but I think it could be useful for people.

The github stuff in the notable changes is only if you fork it and muck with it yourself. Generally a user would clone and run it (yea, I’ll package it up at some point with actual release numbers)

Notable changes:

• It now supports both Containerfile and BlueBuild based repos.
• Fedora Atomic users can optionally add Homebrew using the Universal Blue brew OCI layer.
• The app can show recent GitHub Actions build status without leaving the terminal UI.
• Containerfile users can run a local Podman test build before pushing changes.
• It handles cosign signing setup and can now rotate the repo’s cosign signing key from the update menu.
• The update flow has gotten more useful overall: BlueBuild support, Homebrew toggles, build status, local test builds, and key rotation are now part of the guided workflow.
• There has been a lot of hardening around generated workflows, pinned GitHub Actions, signing edge cases, GitHub error handling, and tests.
• The docs and guardrails are clearer, especially around what the tool manages and what users should review.

It is still beta and still AI-assisted, so please treat it cautiously. Review what it changes, keep backups where appropriate, and expect rough edges. But it is much more capable than it was when I first posted it.

Repo:

There is a lot of other stuff in the DX image that I wouldn’t really use (except VM-related stuff). So layering virt-viewer, swtmp, etc. to a gaming image e.g. bazzite-nvidia-open:stable
seems leaner than rebasing to an image with a lot of stuff I wouldn’t use.

On the other hand, the DX image turns my “layered” maintenance burden into the maintainers’.

So I guess, for my use case, the DX image aligns better with Bazzite’s overall philosophy.

Definitely makes sense to remove QEMU and ROCM if you’re on a handheld or HTPC - but on Desktop?

EDIT: according to:

unpinning old, unused, runtimes with:

flatpak pin --remove runtime/org.gnome.Platform/x86_64/48
flatpak pin --remove runtime/org.gnome.Platform.Locale/x86_64/48

should allow them to be removed with:

flatpak uninstall --unused

But, I’d say that Bazzite should notice orphaned runtimes and do the unpinning itself whenever the last thing using it is removed:

By best guess would be to use the DisplayPort and try the UGREEN 8K adapter: Amazon.com: UGREEN 8K@60Hz Active Display Port to HDMI Unidirectional Adapter with 4K@240Hz 2K@240Hz, DP 1.4 PC to HDMI 2.1 Display G-SYNC Male to Female Cable, Aluminum Converter Compatible with AMD NVIDIA : Electronics

It will happen at some point, but it will propably take time until apps move to a newer runtime.

From ujust update:

Info: (pinned) runtime org.gnome.Platform branch 48 is end-of-life, with reason:
The GNOME 48 runtime is no longer supported as of March 24, 2026. Please ask your application developer to migrate to a supported platform.

Doing a ujust —choose and selecting clean-system gives me:

These runtimes in installation 'system' are pinned and won't be removed; see flatpak-pin(1):
runtime/com.vysp3r.ProtonPlus.Locale/x86_64/stable
runtime/io.github.flattool.Warehouse.Locale/x86_64/stable
runtime/org.freedesktop.Platform.Compat.i386/x86_64/24.08
runtime/org.freedesktop.Platform.GL.default/x86_64/24.08
runtime/org.freedesktop.Platform.GL.default/x86_64/24.08extra
runtime/org.freedesktop.Platform.GL.default/x86_64/25.08
runtime/org.freedesktop.Platform.GL.default/x86_64/25.08-extra
runtime/org.freedesktop.Platform.GL32.default/x86_64/24.08
runtime/org.freedesktop.Platform.GL32.default/x86_64/24.08extra
runtime/org.freedesktop.Platform.Locale/x86_64/24.08
runtime/org.freedesktop.Platform.VulkanLayer.MangoHud/x86_64/23.08
runtime/org.freedesktop.Platform.VulkanLayer.OBSVkCapture/x86_64/23.08
runtime/org.freedesktop.Platform.VulkanLayer.vkBasalt/x86_64/23.08
runtime/org.freedesktop.Platform.codecs-extra/x86_64/25.08-extra
runtime/org.freedesktop.Platform.ffmpeg-full/x86_64/24.08
runtime/org.freedesktop.Platform/x86_64/24.08
runtime/org.gnome.Platform.Locale/x86_64/48
runtime/org.gnome.Platform.Locale/x86_64/49
runtime/org.gnome.Platform/x86_64/48
runtime/org.gnome.Platform/x86_64/49
runtime/org.kde.KStyle.Adwaita/x86_64/6.9
runtime/org.kde.Platform.Locale/x86_64/6.9
runtime/org.kde.Platform/x86_64/6.9
runtime/org.kde.filelight.Locale/x86_64/stable
runtime/org.kde.gwenview.Locale/x86_64/stable
runtime/org.kde.haruna.Locale/x86_64/stable
runtime/org.kde.kcalc.Locale/x86_64/stable
runtime/org.kde.okular.Locale/x86_64/stable
Nothing unused to uninstall

Winnowing that down to org.gnome.Platform:

flatpak uninstall --unused | grep -E "org.gnome.Platform"
runtime/org.gnome.Platform.Locale/x86_64/48
runtime/org.gnome.Platform.Locale/x86_64/49
runtime/org.gnome.Platform/x86_64/48
runtime/org.gnome.Platform/x86_64/49

Showing all installed org.gnome.Platform runtimes:

flatpak list --runtime | grep -E "org.gnome.Platform"
GNOME Application Platform version 48 org.gnome.Platform 48 system
GNOME Application Platform version 49 org.gnome.Platform 49 system
GNOME Application Platform version 50 org.gnome.Platform 50 system

The apps using them:

flatpak list --app --columns=application,runtime | grep -E "org.gnome.Platform"
com.github.tchx84.Flatseal org.gnome.Platform/x86_64/49
com.vysp3r.ProtonPlus org.gnome.Platform/x86_64/50
io.github.flattool.Warehouse org.gnome.Platform/x86_64/49
io.github.ilya_zlobintsev.LACT org.gnome.Platform/x86_64/49
it.mijorus.gearlever org.gnome.Platform/x86_64/49

I’m going to hold off on unpinning/uninstalling branch 48 and see if the correction gets picked up in future Bazzite versions. EDIT: the above shows nothing’s using branch 48.

Running bazzite on my ROG ally x docked through an hdmi 2.1 capable dock, with an hdmi 2.1 cable, to an LG C5 and no matter what I do I cannot get it all to work at the same time.

If I turn on VRR, and 4k 120hz, then turn on HDR last, the tv does not turn on hdr (can check in the settings if it is currently active) and all the colors look very muted .

If i turn on HDR first and set the resolution, when i turn VRR on in game mode settings, it also doesnt turn on.

No matter what I do I cannot get it to work, even on 4:2:2, even on 4k 100hz instead of 120 or 144.

It does work on 4k 60hz.

Does anyone have any ideas on how to get this to work, hdmi 2.1 limitation on linux? Can I use a different dock of some sort.

What is the most effective method for determining whether this is a software or hardware issue?

FWIW I can pull up the keyboard with Xbox+X, but I can’t get a mouse cursor so I’m relying on touchscreen ATM.

• put the rpm file in build_files/
• in build.sh add dnf5 install -y /ctx/some.rpm

Now I have downloaded a printer driver rpm package which I did not find in the Fedora package list or on COPR.

Question: Where do I need to put that package so that I can install it in my build_files/build.sh?

Step 1, switch off zram:

Create a file /etc/systemd/zram-generator.conf which overrides the system zram settings. The file can be empty. In mine I’ve put a comment to myself:

# This empty file overrides `/usr/lib/systemd/zram-generator.conf`.

Step 2, create a swapfile:

Assuming the system is using btrfs (this is the default on Bluefin, so I assume Bazzite is the same). Change the size to whatever makes sense for you.

sudo btrfs filesystem mkswapfile --size 8G /var/swapfile

Add the swapfile to /etc/fstab. The entry for me looks like this:

/var/swapfile    none    swap    pri=0    0 0

Step 3, enable zswap (optional):

sudo rpm-ostree kargs --append='zswap.enabled=1'

Step 4, reboot.

Step 5, confirm settings:

The command cat /proc/swaps can confirm the active swap. It should now show only your swapfile.

Example:

> cat /proc/swaps
Filename				Type		Size		Used		Priority
/var/swapfile                           file		8388604		0		0

If you enabled zswap, check it is enabled:

> sudo dmesg | grep -F zswap
[    0.000000] Command line: BOOT_IMAGE=(hd1,gpt5)/ostree/default-2ee8f203d4c5b97fd5fc04daf879a9dad7dc1c405c8aba2b6ddbda907ce9816e/vmlinuz-6.18.13-200.fc43.x86_64 rd.luks.uuid=luks-0c755fd5-99d6-4578-bb46-328eb72fd038 rd.lvm.lv=vg0/root rhgb quiet root=UUID=8e069d8e-b937-4ad1-a692-cd921ee55f6f rootflags=subvol=ub_root rw ostree=/ostree/boot.0/default/2ee8f203d4c5b97fd5fc04daf879a9dad7dc1c405c8aba2b6ddbda907ce9816e/0 rd.luks.options=discard zswap.enabled=1
[    0.048097] Kernel command line: BOOT_IMAGE=(hd1,gpt5)/ostree/default-2ee8f203d4c5b97fd5fc04daf879a9dad7dc1c405c8aba2b6ddbda907ce9816e/vmlinuz-6.18.13-200.fc43.x86_64 rd.luks.uuid=luks-0c755fd5-99d6-4578-bb46-328eb72fd038 rd.lvm.lv=vg0/root rhgb quiet root=UUID=8e069d8e-b937-4ad1-a692-cd921ee55f6f rootflags=subvol=ub_root rw ostree=/ostree/boot.0/default/2ee8f203d4c5b97fd5fc04daf879a9dad7dc1c405c8aba2b6ddbda907ce9816e/0 rd.luks.options=discard zswap.enabled=1
[    1.116601] zswap: loaded using pool lzo

I am not well enough informed of the tradeoffs to have opinions on whether the Bazzite defaults should be changed but I know that Chris Down recommends disk swap with zswap instead of zram (ref).

What i made is pretty amasing atleast for me since i am huge atomic fan boy and also nix fan boy and desktop side hyprland. So what if i combine all of these together with bootable container… and from idea it is the reality.

Using base-nvidia as base image i started to make progress adding Noctalia shell from copr repo meta package and there adding more hyprland what i wanted that wasent on meta package and the first boots always succesfull. there was time to go the nix way and adding nix easy as it is always on builder, but the small first boot setup had to do changing some stuff due immutale nature and then it was all good again.

Temporary Resolution (Immediate Execution):
sudo mkdir -p /var/nix
sudo mount --bind /var/nix /nix
sudo systemctl restart nix-daemon
Permanent Resolution (Persistence Across System Reboots):

A systemd mount unit must be created to ensure the persistence of the bind mount.
sudo nano /etc/systemd/system/nix.mount
Insert the following configuration into the file:
[Unit]
Description=Mount /var/nix to /nix
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target

[Mount]
What=/var/nix
Where=/nix
Type=none
Options=bind

[Install]
WantedBy=local-fs.target
Activate the newly created mount unit:
sudo systemctl daemon-reload
sudo systemctl enable nix.mount

this made nix setup work so now i dont need to figure anything about flatpaks or permissions no need to have brew or other stuff and i can manage dotfiles and nix all as decalrative way and backup all as repo. Nix is flake centric using flakes and home-manager so all settings always in hand on fresh boot or recovery way.

The build is still in baby steps and i will eventually make more tweaks and stuff so it has everything i want on my workflow and yes no distrobox or toolbox needed since nix is working on user level.

It took sometime to figure how to sign nvidia, but that was easy as it can after reading ujust and there it was after 1 minute all signed all good. only thing not sure yet does base-nvidia use open drivers or still on propriatery ones not like that is huge thing more like want to know only.

Any way nice to be here and hope we have good time.

About me little Older grumpy person already back to school in mid life. Third degree coming now on IT field and programming. Focussing on UNI Bachelor of Applied Sciences and Bachelor of Business Administration. Freelancer programmer sort of i guess been doing some stuff when i have energy and motivation and messing around with Linux and Tech stuff with self hosting and server maintance.

But even that is not required

Meaning I could just build my new GPU in and don’t do anything and everything works?

So, this is to say that I think that the systemd-oomd is working when memory is appropiated slowly by a program, but may me the problem is when it is appropiated faster, not giving oomd time to kill the process.

At the same time, I don’t know if a more aggressive oomd setting could result in false positives, killing programs erroneously…

I cant take these crashes anymore

For custom builds you can use the custom build workshop

I’d like to switch from that to an AMD gpu.

Is there any chance I can switch without having to reinstall? I’d like to do some benchmarks first… Thanks!