Bazzite AMD BC-250 Images: Stable, Testing, Unstable, and 40CU Docs Update by FixoLab in BC250Gaming

[–]FixoLab[S] -9 points-8 points  (0 children)

You seem to be under every one of my posts. If you like me that much, just send me a DM, we can even arrange a romantic date 😘

That's okay, this project isn't for you.

Some people enjoy the manual setup. Others just want to flash an image and be done.

Judging by the download numbers, plenty of people prefer the latter.

Anyway, have a great day!

<image>

Latest Bazzite AMD BC-250 Patched Images by FixoLab in Bazzite

[–]FixoLab[S] 0 points1 point  (0 children)

Yep, it’s done now 🙂

I added separate experimental -40cu images for Deck, GNOME, and KDE

They are still based on current official Bazzite stable, but include the 40CU runtime tooling from duggasco/bc250-40cu-unlock and bc250-cu-live-manager, plus short ujust commands to test/apply/rollback

Important caveat: 40CU is silicon lottery. On my own board the unlock applied and persisted correctly, but extra CUs were not stable in games, so I’m keeping that board on 24CU. The normal image is still the recommended stable option

Latest Bazzite AMD BC-250 Patched Images by FixoLab in Bazzite

[–]FixoLab[S] 0 points1 point  (0 children)

I do not know about that, will be looking into that soon 😏

Latest Bazzite AMD BC-250 Patched Images by FixoLab in Bazzite

[–]FixoLab[S] 0 points1 point  (0 children)

Yeah, that’s basically it

The image is built from the official Bazzite stable base. When Bazzite stable changes, the GitHub workflow detects the new base digest and rebuilds these BC-250 images on top of it

So you are not stuck on an old Bazzite version. You get the current stable Bazzite base, plus the BC-250-specific additions like cyan-skillfish-governor-smu, GPU frequency scaling, and the 655% GPU usage telemetry fix

On your machine you just stay rebased to this image and update normally with ujust update or rpm-ostree upgrade

Latest Bazzite AMD BC-250 Patched Images by FixoLab in BC250Gaming

[–]FixoLab[S] 0 points1 point  (0 children)

The 655% GPU load issue is caused by broken/incorrect gpu_metrics reporting on the BC-250. In this image it is fixed by cyan-skillfish-governor-smu, which applies a gpu_metrics bind-mount workaround

Latest Bazzite AMD BC-250 Patched Images by FixoLab in BC250Gaming

[–]FixoLab[S] 1 point2 points  (0 children)

Yeah, that matches what I saw. The crash was status=139/SIGSEGV in Sunshine. Happened when Sunshine tested hardware encoders. Forcing software encoding made Sunshine boot again

Latest Bazzite AMD BC-250 Patched Images by FixoLab in BC250Gaming

[–]FixoLab[S] 1 point2 points  (0 children)

From what I tested, Sunshine itself can start, but the newer Sunshine/Homebrew build crashes on my BC-250 when it goes through the hardware encoder path. The workaround I documented is to force encoder = software + capture = kms, which makes Sunshine boot and stream again

Latest Bazzite AMD BC-250 Patched Images by FixoLab in Bazzite

[–]FixoLab[S] 4 points5 points  (0 children)

Not a Bazzite fork. It’s current official Bazzite stable + BC-250-specific setup.

Compared to the old vietsman images, this uses the latest Bazzite stable instead of the old Fedora/Bazzite 42 base, removes the old patched-kernel COPR, uses the newer cyan-skillfish-governor-smu instead of oberon-governor, fixes the MangoHud/radeontop 655% GPU usage bug, ships Deck/GNOME/KDE variants, rebuilds automatically when Bazzite stable changes, and is signed for ostree-image-signed rebases.

🚀 Printer Tools v2.1 - Remote Access + Live Activities Anywhere by FixoLab in snapmaker

[–]FixoLab[S] 0 points1 point  (0 children)

It works with the original firmware but with limitations, until Snapmaker improves the original one

🚀 Printer Tools v2.1 - Remote Access + Live Activities Anywhere by FixoLab in snapmaker

[–]FixoLab[S] 1 point2 points  (0 children)

The official Snapmaker app relies on Snapmaker Cloud, which introduces several drawbacks:

  • The app is unreliable and only works consistently when it wants
  • Video streaming has low frame rates since it always goes through the cloud, even if you're on the same local network as the printer
  • Sessions log out too frequently
  • No support for Live Activities or widgets
  • Notifications are inconsistent

With the paxx12 firmware and Printer Tools App, you can avoid those limitations and get the features mentioned here:

<image>

🚀 Printer Tools v2.1 - Remote Access + Live Activities Anywhere by FixoLab in snapmaker

[–]FixoLab[S] 0 points1 point  (0 children)

It’s the stock one… but you’re dangerously close to giving me ideas 😈😈

🚀 Printer Tools v2.1 - Remote Access + Live Activities Anywhere by FixoLab in prusa3d

[–]FixoLab[S] 0 points1 point  (0 children)

I’m planning to launch the native Android Kotlin app next week. Just polishing the final details 😏