github VivaLaVent/ps5-bazzite-deck v2.15

latest release: v2.16
pre-release23 hours ago

What's new

A pre-release on top of v2.14. v2.14.1 and v2.14.2 were withdrawn before they were complete; their changes are in this release. None of the fixes below has run on a console yet: please test and report, with the SUMMARY line of ps5-report.

  • Wi-Fi on the original PS5 (NXP IW620): no more frozen console when the Wi-Fi chip stops answering. While connecting, the driver could wait for ever for an answer that never came, and everything that touched the network froze with it until a restart (reported in detail by ziernaht). The connection attempt now fails instead and the console keeps working.
  • 1440p at 100 and 120 Hz: the picture was shifted up, on some monitors right out of the screen (consoles with the FLAVA3 HDMI chip; 60 Hz was fine). Those modes were sent with the blanking of the 60 Hz mode; now they go out with the monitor's own timing. Found with hwdnick's ps5-report. Consoles with the VERDE chip are unchanged.
  • A test switch for games closing and dropping you from Game Mode to the desktop (Predecessor, Expedition 33; more often with VRAM set to 4 GB). The kernel log then shows Failed to pin framebuffer: -ENOMEM: every picture needs one free block of VRAM, and a game that fills the VRAM leaves none. With the test switched on, the picture is taken from normal memory instead. It is off by default because the graphics driver normally avoids this for a reason (it has frozen the screen on some other AMD chips), and nobody has seen it work on a PS5 yet. It takes two kernel options, under What to test.
  • DirectMesh on every original PS5 and Slim. Some report GPU id 13db instead of 13fb, and there ps5-directmesh used the normal driver (found by rdmrocha).
  • A shell in emergency mode. When a start stopped there, the screen said "the root account is locked" and offered nothing. You now get a shell, where journalctl -xb shows what went wrong.
  • ps5-report has a section "Changed on this console": kernel options you added, kernel modules and services that are not the image's, packages added with rpm-ostree. It tells us at once whether a problem can come from such a change. It also shows the right resolution when the first display output is off.
  • Switching from Legacy: the script is safer in two cases where a first attempt had failed.

bootc

New install

You need a USB drive or SSD of 64 GB or more. Flashing erases it.

  1. Extract ps5-bazzite-deck-bootc-v2.15.img.7z.001 with 7-Zip (not Windows' built-in extraction). The first line of ps5-bazzite-deck-bootc-v2.15.img.sha256 is the .img's checksum; on Windows, certutil -hashfile ps5-bazzite-deck-bootc-v2.15.img SHA256 shows yours.
  2. Flash the .img with balenaEtcher (drives flashed with Rufus stopped in an emergency shell for several users; balenaEtcher fixed it). When Windows offers to format the drive afterwards, choose Cancel. On Linux with sudo dd if=ps5-bazzite-deck-bootc-v2.15.img of=/dev/sdX bs=4M status=progress conv=fsync (replace /dev/sdX with your drive).
  3. Start it with bazzite-bootc-loader-v2.15.elf.

The first start takes a few minutes. A PS5 Pro has its 60 compute units from the first start.

Switching from Legacy

In place, keeping users, games and Flatpaks. On the Legacy install, in a terminal or over SSH, with at least 30 GB free on the system drive:

curl -fsSLO https://raw.githubusercontent.com/VivaLaVent/ps5-bazzite-deck/main/tools/legacy-to-bootc.sh
sudo bash legacy-to-bootc.sh            # checks only, changes nothing
sudo bash legacy-to-bootc.sh --apply    # downloads the Stable image (about 7 GB) and sets it up beside Legacy

Then power off and start with bazzite-bootc-loader-v2.15.elf. The first start moves your home folders and Flatpaks over.

  • Nothing of the Legacy system is deleted until you run sudo bash legacy-to-bootc.sh --cleanup on the working bootc system, which frees about 20 GB.
  • If bootc doesn't start: on a PC, copy bzImage, initrd.img and cmdline.txt from legacy-backup/ on the drive's boot partition back to its top folder. Legacy starts again as before.
  • Not carried over: Decky Loader and packages installed into the system; install them again. Options you added to cmdline.txt are kept.
  • This script is new. A backup of anything you can't replace is a good idea before --apply.

Or flash: follow New install on a second drive, or on the same one after copying off what you want to keep.

Updating

This is a pre-release, on the Beta channel. On the PS5, in a terminal (Desktop Mode → Konsole) or over SSH (password ps5):

sudo bootc switch ghcr.io/vivalavent/ps5-bazzite-bootc:beta

Already on Beta: sudo bootc upgrade. It applies at the next start with the loader. bazzite-bootc-loader-v2.15.elf is the same loader as v2.13's and v2.14's; any of them works. Installed packages with rpm-ostree install? Use sudo rpm-ostree upgrade instead of sudo bootc upgrade.

Back to the stable release: the same bootc switch command with :stable instead of :beta. Steam's Settings → System → OS Update Channel does the same.

Problems

  • sudo bootc rollback, then power off or restart, and start with the loader.
  • If a new version doesn't start at all: ROLLBACK.txt on the drive's boot partition explains how to start the previous one from a PC. That needs bazzite-bootc-loader.
  • Report it in Discord with the file ps5-report saves.

Known issues

  • M.2 install in the emergency shell after an update (Couldn't find specified OSTree root '/sysroot//ostree/boot.1/…'), on v2.11 or older: the boot partition names the right version under the wrong counter. Either way gets you back in, and nothing on the M.2 is lost:
  • An already flashed drive on PS5 system software 4.x (any image before v2.11): fix it from a PC instead of flashing again. It changes one field, not your data, and only shows what it would do without --apply:
  • No HDR on consoles with the VERDE HDMI chip (ps5-report names the chip on its first lines): HDR is not offered there instead of coming out washed out. The official PS5 Linux kernel patches have just added an untested HDR option for VERDE; it comes with a planned kernel update.
  • PS5 Hardware Control's Restore on boot (up to its version 1.5.0) loads your saved curve but leaves the console's fan control on until you apply a curve or preset; a fix is with its developer. Until then, ps5_fan.curve=1 in cmdline.txt starts on the curve, and Restore on boot works.
  • The first start after updating from v2.5.1 or older still uses the old VRAM size; the 6 GB applies from the next start with the loader. With the old 512 MB, Game Mode can show a garbled block in the top-left corner. Power off and start with the loader once more.
  • Games dropping from Game Mode to the desktop with Failed to pin framebuffer: -ENOMEM in the kernel log: the VRAM is full. Try the test under What to test (two kernel options). Which VRAM size helps differs per game: 4 GB (0x100000000 in vram.txt) worked for Ratchet & Clank: Rift Apart, while other games fail more often at 4 GB. The default 6 GB, or 5 GB (0x140000000), is the safe choice.
  • The clock is wrong right after a start until the network time arrives; in that minute, downloads can fail with certificate errors (Bazaar, for example). The kernel can't read the console's clock yet; that comes with a planned kernel update. Set your time zone once with sudo timedatectl set-timezone <Region/City>.
  • Starting without the USB drive is experimental: it needs sudo ps5-m2-install --boot first, and the four files in /data/PS5/Linux/ have to be copied again after every update. Steps: wiki.
  • PS5 Pro: the CPU stays at 3.2 GHz. The Pro's power controller doesn't answer the clock requests the CPU driver sends, so the driver stays off there; whether boost alone works on a Pro is being tested.

What to test

  • Original PS5 on Wi-Fi: if Wi-Fi stops, does the rest of the console keep working, and can you reconnect? sudo dmesg | grep -iE "IOCTL timeout|command timeout" | tail shows whether the fix stepped in.
  • 1440p at 100 or 120 Hz: does the picture fill the screen exactly? Then switch to 60 Hz and back. With VRR at 1440p 120 Hz: does it still work? Please name the monitor or TV.
  • A game that dropped you to the desktop before (Failed to pin framebuffer: -ENOMEM): the test needs two kernel options, because taking the picture from normal memory also needs the graphics driver's S/G display, which is off by default on the PS5. Correction: the first version of these notes gave only the second option, which on its own does nothing.
    sudo rpm-ostree kargs --append=amdgpu.sg_display=1 --append=amdgpu.ps5_scanout_gtt=1
    Power off and start with the loader. Play the game in Game Mode, then sudo dmesg | grep -iE "pin framebuffer|system memory": "scanning out of system memory" means the switch stepped in. Tell us whether the game kept running, whether the picture looked right, and especially if the screen flickered or froze. To undo: sudo rpm-ostree kargs --delete=amdgpu.sg_display=1 --delete=amdgpu.ps5_scanout_gtt=1. If the picture is broken after the start, undo it over SSH, or start the previous version (sudo bootc rollback, or ROLLBACK.txt on the boot partition from a PC).
  • DirectMesh: ps5-directmesh vulkaninfo | grep -i mesh_shader lists VK_EXT_mesh_shader, then a game that needs Mesh shaders with ps5-directmesh %command%.

Sharing logs

bash <(curl -fsSL https://raw.githubusercontent.com/VivaLaVent/ps5-bazzite-deck/main/tools/ps5-report.sh)

Paste its SUMMARY line when you report results, and attach the saved file for a bug report.

Files

  • ps5-bazzite-deck-bootc-v2.15.img.7z.* – bootc disk image, 7-Zip multi-volume (extract from .001)
  • ps5-bazzite-deck-bootc-v2.15.img.sha256 – checksums for the bootc image and its volumes
  • bazzite-bootc-loader-v2.15.elf – the PS5 Linux loader for this release: soniciso1's ps5-linux-loader, which also hands Linux the PS5 Pro GPU firmware, the Wi-Fi firmware and the console's Bluetooth pairings
  • bazzite-bootc-loader-v2.15.elf.sha256 – loader checksum
  • linux-ps5-7.3.3-1.x86_64.rpm – PS5 Linux kernel RPM (used by the bootc image build)

Found a problem? Run ps5-report on the PS5 and post the file it saves in Discord.
Like the project? Support it on Ko-fi.

Don't miss a new ps5-bazzite-deck release

NewReleases is sending notifications on new releases.