Files
bc250-console/docs/update-channels.md
T
ckochandClaude Fable 5 4e452acc7d
Build Bazzite BC-250 / Check Bazzite channel digests (push) Has been cancelled
Build Bazzite BC-250 / Build Custom Image (push) Has been cancelled
Build Bazzite BC-250 / Build Custom 40CU Image (push) Has been cancelled
Build Bazzite BC-250 / Save Bazzite channel digest cache (push) Has been cancelled
Build Bazzite BC-250 / Publish GitHub Release (push) Has been cancelled
BC-250 console image: custom GNOME recipe with remote admin
Based on 62fixolab/Latest-Bazzite-AMD-BC-250-Patched-Images @ 347fd4d.

Adds on top of the fork:
- recipes/bc250-console-gnome.yml: governor + gnome-remote-desktop +
  openssh-server, sshd enabled, hhd.service masked, no signing module
  (local build + ISO path)
- files/console/usr/bin/bc250-remote-setup: one-time on-box SSH/RDP setup
- files/console/usr/lib/bootc/kargs.d/50-bc250-ttm.toml: ttm memory kargs
- BUILD-CONSOLE.md: build -> ISO -> validation instructions

files/console/ is separate from files/system/ so the 40-CU unlock tooling
stays out of this stable 24-CU image.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-06 18:54:30 -04:00

4.4 KiB

Bazzite Channel Packages

This repository publishes separate packages for each supported Bazzite update channel. The stable packages are recommended for daily use. Testing and unstable are available for people who deliberately want to test upstream Bazzite channels on BC-250 hardware.

Important

These are OCI images, not ISOs. Install them with rpm-ostree rebase, then reboot.

Warning

Bazzite does not support rebasing between different desktop environments. Stay on Deck, GNOME, or KDE when switching channels.

Which channel should I use?

Channel Use it when Risk
stable You want the recommended image for daily use Lowest
testing You want to preview the next Bazzite stable build Medium
unstable You are intentionally testing Bazzite development images Highest

Tip

If you are unsure, use stable.

Package naming

Normal packages:

Variant Stable Testing Unstable
Deck bazzite-bc250-patched-deck bazzite-bc250-patched-deck-testing bazzite-bc250-patched-deck-unstable
GNOME bazzite-bc250-patched-gnome bazzite-bc250-patched-gnome-testing bazzite-bc250-patched-gnome-unstable
KDE bazzite-bc250-patched-kde bazzite-bc250-patched-kde-testing bazzite-bc250-patched-kde-unstable

Experimental 40CU packages:

Variant Stable Testing Unstable
Deck 40CU bazzite-bc250-patched-deck-40cu bazzite-bc250-patched-deck-40cu-testing bazzite-bc250-patched-deck-40cu-unstable
GNOME 40CU bazzite-bc250-patched-gnome-40cu bazzite-bc250-patched-gnome-40cu-testing bazzite-bc250-patched-gnome-40cu-unstable
KDE 40CU bazzite-bc250-patched-kde-40cu bazzite-bc250-patched-kde-40cu-testing bazzite-bc250-patched-kde-40cu-unstable

Deck / Game Mode:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-deck:latest
systemctl reboot

GNOME:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-gnome:latest
systemctl reboot

KDE:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-kde:latest
systemctl reboot

Testing images

Deck / Game Mode:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-deck-testing:latest
systemctl reboot

GNOME:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-gnome-testing:latest
systemctl reboot

KDE:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-kde-testing:latest
systemctl reboot

Unstable images

Deck / Game Mode:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-deck-unstable:latest
systemctl reboot

GNOME:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-gnome-unstable:latest
systemctl reboot

KDE:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-kde-unstable:latest
systemctl reboot

Experimental 40CU images

The 40CU images include optional runtime tooling. They do not force extra CUs on boot.

Caution

32CU/40CU is silicon lottery. Read the full 40CU guide before saving any boot profile.

Stable Deck 40CU:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-deck-40cu:latest
systemctl reboot

Testing Deck 40CU:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-deck-40cu-testing:latest
systemctl reboot

Unstable Deck 40CU:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-deck-40cu-unstable:latest
systemctl reboot

Replace deck with gnome or kde to install the matching desktop variant.

Check your current image

rpm-ostree status

The current deployment should show something like:

ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-deck:latest

Move back to stable

Use the stable package for your current desktop environment:

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/62fixolab/bazzite-bc250-patched-deck:latest
systemctl reboot

Replace deck with gnome or kde if needed.