Your PS5's Zen 2 CPU needs the same boot configuration we used before.
First check:
cat /proc/cmdline
If clearcpuid=514 is not already present, run:
sudo rpm-ostree kargs --append=clearcpuid=514
The PS5 Bazzite documentation recommends rpm-ostree kargs for persistent boot arguments rather than editing cmdline.txt directly.
Power off the PS5 completely, then start Bazzite again through your Linux loader.
After Bazzite starts, verify:
grep -o 'clearcpuid=[^ ]*' /proc/cmdline
grep -qw umip /proc/cpuinfo && echo "UMIP ENABLED" || echo "UMIP DISABLED"
Expected result:
clearcpuid=514
UMIP DISABLED
Stop if UMIP remains enabled.
We previously used Fedora Distrobox to compile LinUwUx without modifying Bazzite's system packages.
Run:
distrobox create \
--name linuwux-build \
--image registry.fedoraproject.org/fedora:latest
Enter the container:
distrobox enter linuwux-build
Inside Distrobox, install the development dependencies:
sudo dnf install -y \
git \
curl \
gcc \
gcc-c++ \
make \
binutils \
pkgconf-pkg-config
Install Rust:
curl --proto '=https' --tlsv1.2 -sSf \
https://sh.rustup.rs | sh -s -- -y
source "$HOME/.cargo/env"
Verify:
cargo --version
rustc --version
LinUwUx currently requires Rust 1.98 or newer to build from source.
Run these commands inside Fedora Distrobox.
Clone the repository:
cd ~
git clone https://github.com/brcly/linuwux-runtime.git
cd ~/linuwux-runtime
Download the exact pull request that previously worked for Phantom Blade Zero:
git fetch origin pull/58/head:pr58
git switch pr58
Verify the selected branch:
git log -1 --oneline
The PR's latest commit was fda0e86, supporting the newer Artifact DLL loader layout.
GitHub
Now compile:
cargo xtask build
When compilation succeeds, verify the library exists:
ls -lh ~/linuwux-runtime/target/runtime/LinUwUx.so
Leave Distrobox:
exit
From this point onward, run commands in normal Bazzite Konsole.
Install the LinUwUx wrapper:
bash ~/linuwux-runtime/install.sh
That installer provides the wrapper but may download a standard release. Replace its library with the PR #58 version you just compiled:
install -m 644 \
~/linuwux-runtime/target/runtime/LinUwUx.so \
~/.local/share/linuwux/LinUwUx.so
Verify:
ls -lh ~/.local/bin/linuwux
ls -lh ~/.local/share/linuwux/LinUwUx.so
sha256sum \
~/linuwux-runtime/target/runtime/LinUwUx.so \
~/.local/share/linuwux/LinUwUx.so
The two SHA256 hashes should match.
LinUwUx's official setup uses these locations for the launcher and library.
GitHub
This is the same module that worked on your previous kernels 7.3.1-viva and 7.3.3-viva.
Clone it using Git. If Git isn't available on the Bazzite host, run the clone command inside your Fedora Distrobox, then return to Bazzite for compilation.
cd ~
git clone https://github.com/dnmodder/cpuid-fault-emulation.git
cd ~/cpuid-fault-emulation
Check that the running kernel's build tree is available:
ls /lib/modules/$(uname -r)/build/Makefile
Now compile:
make -C /lib/modules/$(uname -r)/build \
M="$PWD" LLVM= -j2 modules
This is the exact GCC-based build method we used previously. The module source supports AMD SVM-based CPUID fault emulation, which conflicts with KVM while active.
GitHub
Once finished, verify:
modinfo -F vermagic ./cpuid_fault_emulation.ko
modinfo -F vermagic kvm_amd
Both should start with your current kernel version.
Your earlier build emitted objtool warnings involving virtualize_processor and handle_vm_exit. These are not proof of a failed compilation, but they are unresolved kernel-level stability concerns. As your PS5 previously shut down unexpectedly, I recommend having the warnings reviewed before activating the experimental module again.
This version includes the corrected /proc/modules verification from our earlier troubleshooting. It does not touch any shader-cache files.
cat > ~/pbz-ready.sh <<'EOF'
#!/usr/bin/env bash
set -euo pipefail
MODULE="$HOME/cpuid-fault-emulation/cpuid_fault_emulation.ko"
echo "================================="
echo " PHANTOM BLADE ZERO PREPARE"
echo "================================="
echo "[1/4] Checking kernel..."
if [[ ! -f "$MODULE" ]]; then
echo "ERROR: CPUID module missing."
exit 1
fi
MODULE_KERNEL=$(modinfo -F vermagic "$MODULE" | awk '{print $1}')
RUNNING_KERNEL=$(uname -r)
if [[ "$MODULE_KERNEL" != "$RUNNING_KERNEL" ]]; then
echo "ERROR: Kernel mismatch."
echo "Module: $MODULE_KERNEL"
echo "Running: $RUNNING_KERNEL"
exit 1
fi
echo "Kernel compatible."
echo "[2/4] Checking UMIP..."
if grep -qw umip /proc/cpuinfo; then
echo "ERROR: UMIP enabled."
exit 1
fi
echo "UMIP disabled."
echo "[3/4] Preparing CPUID emulation..."
if grep -q '^cpuid_fault_emulation ' /proc/modules; then
echo "CPUID emulation already loaded."
else
sudo -v
if grep -Eq '^(kvm_amd|kvm) ' /proc/modules; then
echo "Unloading KVM..."
sudo modprobe -r kvm_amd kvm
fi
echo "Loading CPUID module..."
if ! sudo insmod "$MODULE"; then
echo "ERROR: Module loading failed."
sudo modprobe kvm_amd || true
exit 1
fi
fi
echo "[4/4] Verifying module..."
if grep -q '^cpuid_fault_emulation ' /proc/modules; then
echo "CPUID module loaded."
else
echo "ERROR: Verification failed."
exit 1
fi
echo
echo "================================="
echo " PREPARATION COMPLETE"
echo "================================="
echo "You can now start Phantom Blade Zero."
EOF
chmod +x ~/pbz-ready.sh
bash -n ~/pbz-ready.sh
The verification uses /proc/modules directly, avoiding the false failure we encountered previously with lsmod | grep -q and pipefail.
mkdir -p ~/.local/share/applications
cat > ~/.local/share/applications/pbz-ready.desktop <<'EOF'
[Desktop Entry]
Type=Application
Name=Prepare Phantom Blade Zero
Comment=Enable CPUID emulation for LinUwUx
Exec=konsole --hold -e /var/home/ps5/pbz-ready.sh
Icon=applications-games
Terminal=false
Categories=Game;
EOF
chmod +x ~/.local/share/applications/pbz-ready.desktop
kbuildsycoca6 --noincremental
You can now search for Prepare Phantom Blade Zero in the KDE Application Launcher.
This shortcut is intentionally manual rather than enabled at boot. It loads an experimental kernel module, so activation should remain an explicit action.
For your previous setup, we used:
proton-cachyos-11.0-20261015-slr-x86_64
You can install the same version if it's available, or another compatible x86-64 Steam Linux Runtime build.
The easiest method is ProtonUp-Qt:
flatpak install -y flathub net.davidotek.pupgui2
Open ProtonUp-Qt, select Steam, and install Proton-CachyOS SLR x86_64.
The CachyOS documentation explains that custom Proton versions should be installed under Steam's compatibilitytools.d directory and that Steam must be restarted to recognize them.
CachyOS
After installation, check:
find ~/.local/share/Steam/compatibilitytools.d \
-maxdepth 2 -name proton -print
Restart Steam, then select Proton-CachyOS in the game's Properties → Compatibility settings.
Open Steam in Desktop Mode.
Select Games → Add a Non-Steam Game → Browse.
Use the executable that worked in our previous setup:
/var/mnt/Games/NewFolder/PBZ.CSF.ZeiGames.com/platform/steam/PBZ.exe
This path assumes the games drive is still mounted at /var/mnt/Games. If your fresh installation mounted it elsewhere, browse to platform/steam/PBZ.exe in the existing game directory.
Rename the shortcut to Phantom Blade Zero.
Under Properties → Compatibility, force the Proton version installed in Step 8.
We previously had a Wine crash and stack-overflow error that was resolved after installing vcrun2022.
Install Protontricks:
flatpak install -y flathub com.github.Matoking.protontricks
Use it to find the new Steam shortcut ID:
flatpak run com.github.Matoking.protontricks -l
A fresh Bazzite installation can assign a different shortcut ID, so do not assume it is still 3876679650.
If the game doesn't appear yet, Steam may first need to initialize its Proton prefix with a launch attempt. Exit the game after the prefix is created.
Then run, replacing GAME_ID with the ID shown:
flatpak run com.github.Matoking.protontricks GAME_ID vcrun2022
Follow the Visual C++ installation dialogs. Protontricks supports installing Winetricks components into a selected Steam game's Proton prefix.
GitHub
Open Phantom Blade Zero → Properties → General → Launch Options.
Paste:
PROTON_AVX=1 LINUWUX_ARTIFACT_AMD_V2=1 /var/home/ps5/.local/bin/linuwux %command% -noraytracing
This preserves your previous setup: LinUwUx PR #58, AMD Artifact V2 support, Proton AVX, and the -noraytracing game argument.
Verify the library:
ls -lh ~/.local/share/linuwux/LinUwUx.so
Verify the module was built for the current kernel:
uname -r
modinfo -F vermagic \
~/cpuid-fault-emulation/cpuid_fault_emulation.ko
Verify UMIP:
grep -qw umip /proc/cpuinfo && echo "UMIP ENABLED" || echo "UMIP DISABLED"
If those checks pass, the recreated setup is ready for a controlled activation test. The previous unexpected shutdown and kernel warnings mean we can't guarantee stability.
Your normal launching workflow