Bazzite Aug 31 Update

Hello folks, another week another set of fixes.

Huge thanks to everyone who’s been reporting their issues and trying out testing builds, you’ve all been a big help.

What’s new

  • An issue with rendering under gamemode on RDNA2 GPUs in Mesa 26.2.1 has been fixed.
  • More improvements for various handhelds have been deployed, MSI Claw users should especially have a much better experience. If your handheld still has input issues reporting here will allow us to fix this for you as quickly as possible.
  • Many more handhelds have RGB control in Steam -> Settings -> Customization -> Joystick Lights. Still missing are Ayaneo/Ayn and ASUS Ally, which are coming. For now using the dualshock controller via OGUI will allow control.
  • Some additional devices have had TDP control added through Steam. As a reminder, TDP is controlled in the right-hand Steam QAM menu. If you don’t see the TDP Limit checkbox & slider, make sure your performance profile is set to custom or performance and you’ve scrolled down. If you don’t see TDP control at all (For instance, Strix Halo users who we’ve added additional support for in this release), please report here so we can get your device added ASAP.
  • A memory leak with Intel Arc GPUs has been resolved
  • Some additional fixes have been backported for HDMI 2.1 VRR and issues have been reported upstream. We’ll continue to pull in more as they’re available.
  • A bug in xwaylandbridge causing odd behavior with unfocused windows in KDE has been resolved.
  • ROM Properties shell extension issues with folder previews in both KDE and GNOME have been patched.
  • A regression where some games would freeze upon returning from sleep has been resolved - if you still see similar issues please report it with ujust logs-last-boot attached so we can provide personalized support.
  • Latest openrazer is once again available
  • Fixed an issue where changelogs could become out of sync, added Nvidia-LTS kernel version to changelog display.
  • Various small fixes for ujust scripts and the Bazzite Portal.
  • Issues with default screen orientation on various handhelds have been fixed, including OneXPlayer devices.
  • Now using OGC Kernel 7.2.1.

Something to look out for

We’ve seen a few users reporting whole-system freezes that we found were caused by certain decky loader extensions. If you’re using a hardware-controlling extension try disabling it and seeing if the problem goes away before reporting to us.

What’s coming

Desktop TDP control will be returning as a native GNOME extension and as a KDE applet, mimicking the power profile UI already present in these desktop environments. You’ll have all the same features as game mode since they use the same back-end. A preview of the GNOME version of this can be found in testing, and KDE is only shortly behind.

And as already mentioned, fan control is being worked on for OGUI and will return as soon as possible. We appreciate your continued patience through this transition period.

That’s all for now, thanks again everyone!

Blockquote

Can you elaborate on this? I had to stop using Game Mode because games would freeze. They worked fine in desktop mode though. Although it was not a “whole-system” freeze, it was just the game and I could easily exit out of it and restart it.

I’m just not smart enough to fix it so I stopped using it :face_with_diagonal_mouth: but I could easily disable some extensions or even delete Decky entirely, its not that important and at this point seems to cause a lot of problems. I just never would have guessed it would cause games to freeze.

That sounds very different, if you upload a “ujust logs-this-boot” after it happens I can take a look for you.

Unfortunately I was also not able to get it to boot to desktop mode without causing problems so I installed CachyOS but I ran into the same problems, and then I installed Bazzite without Game Mode, so I don’t have access to those logs anymore :frowning:

I was hoping my black screen and freezes would be over after this huge update. but it is not.
Although: when the computer freezes, I don’t get a black screen anymore, but just a static desktop on my screen: I can’t call that a fix.
The issue seems to come from the Other Settings in the Power Management options.
When the timer is set on 1 minutes or so, the computer just stops working after one minute.
No matter how the power profile is set. So my fix for now is to put the timer on 999 to avoid this problem.
Isn’t this a setting meant for laptops and portable gaming systems?
This shouldn’t interact with the hardware of a gaming PC on AC power.
Also any other power management options are causing problems, that’s why it’s disabled.

Thanks for the RDNA2 fix, it appears that was my issue when I tried to play some games.

We really appreciate the effort and the work put into the OS

Totally happy with Bazzite here :smiling_face_with_three_hearts: The only bug reported is the bootup on 640*480, but after a reboot not seen this anymore. This was only one time. KDE let’s you decide how it appears and I like the deep red/brown from my desk also in KDE.

But I’ve red that Btrfs uses compression, is this true? My SSD is 2TB and only Bazzite use this and it is the only OS installed. I ditched Windows out.

At this time I play The Witcher 3 and Cyberpunk and it works great. No crashes in games.

Greetz from Holland :+1:

I have to add: since the timer of the power profile is set to 999 minutes, Bazzite seems to run nicely. Today, I had no issues at all. Glad to have my favorite OS back in business.

Thanks for the good work!

Hi, I wanted to know if there are touch control setting somewhere in bazzite? I put Bazzite on my PS Vita, but the backside touch controls seem a bit sluggish. And I was wondering if there were some settings I could tweak in Bazzite.

Of course it is also partly my fault, for loading up Battlefield via Sunshine.

Edit: Worst case scenario, I will have to use either my Steam Deck or Lenovo. But it would be nice to have something smaller, for when I am on the couch watching TV.

I am rebasing back to 43. With newer updates I notice more bugs in games, in some games drop of the FPS, in others the controller buttons loose pushed state and the character stumbles/releases aim/shoots etc.
The opengamecontroller (or whatever it is called) is dissatisfactory compared to HDD, so..
Don’t want to figure what else there is broken, so better skip this 44 altogether, it seems

Be sure to report your issues so they can be looked at, that’s how this all improves. We’re working hard on every report.

Well now it is freezing in desktop mode too :frowning:

Summary

Sep 08 15:33:33 kernel: Linux version 7.2.3-ogc3.1.fc44.x86_64 (root@702ca2082189) (gcc (GCC) 16.2.1 2>
Sep 08 15:33:33 kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/ostree/default-acc88ce31f22b3e2e430594918f>
Sep 08 15:33:33 kernel: BIOS-provided physical RAM map:
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009c3efff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x0000000009c3f000-0x0000000009ffffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000000a20e000-0x000000000affffff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000000b020000-0x000000009a069fff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000009a06a000-0x000000009a06afff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000009a06b000-0x000000009a096fff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000009a097000-0x000000009a097fff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000009a098000-0x00000000b971afff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000b971b000-0x00000000bae86fff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000bae87000-0x00000000bafeefff] ACPI data
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000bafef000-0x00000000bcaa8fff] ACPI NVS
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000bcaa9000-0x00000000bd9fefff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000bd9ff000-0x00000000beffffff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000bf000000-0x00000000bfffffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000c0000000-0x00000000efffffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000f8000000-0x00000000fd1fffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fd300000-0x00000000fd5fffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fd800000-0x00000000fe9fffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fea10000-0x00000000feb7ffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fec02000-0x00000000fec0ffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fec11000-0x00000000fec2ffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fec31000-0x00000000fecfffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fed01000-0x00000000fed3ffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fed45000-0x00000000fed7ffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fed90000-0x00000000fedc1fff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fedd0000-0x00000000fedd3fff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [gap 0x00000000fedd6000-0x00000000feffffff]
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] device reserved
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000083f37ffff] System RAM
Sep 08 15:33:33 kernel: BIOS-e820: [mem 0x000000083f380000-0x000000083fffffff] device reserved
Sep 08 15:33:33 kernel: NX (Execute Disable) protection: active
Sep 08 15:33:33 kernel: APIC: Static calls initialized
Sep 08 15:33:33 kernel: efi: EFI v2.7 by American Megatrends
Sep 08 15:33:33 kernel: efi: ACPI=0xbca92000 ACPI 2.0=0xbca92014 TPMFinalLog=0xbca5c000 SMBIOS=0xbd826>
Sep 08 15:33:33 kernel: random: crng init done
Sep 08 15:33:33 kernel: efi: Remove mem320: MMIO range=[0xf0000000-0xf7ffffff] (128MB) from e820 map
Sep 08 15:33:33 kernel: e820: remove [mem 0xf0000000-0xf7ffffff] device reserved
Sep 08 15:33:33 kernel: efi: Remove mem321: MMIO range=[0xfd200000-0xfd2fffff] (1MB) from e820 map
Sep 08 15:33:33 kernel: e820: remove [mem 0xfd200000-0xfd2fffff] device reserved
Sep 08 15:33:33 kernel: efi: Remove mem322: MMIO range=[0xfd600000-0xfd7fffff] (2MB) from e820 map
Sep 08 15:33:33 kernel: e820: remove [mem 0xfd600000-0xfd7fffff] device reserved
Sep 08 15:33:33 kernel: efi: Not removing mem323: MMIO range=[0xfea00000-0xfea0ffff] (64KB) from e820 >
Sep 08 15:33:33 kernel: efi: Remove mem324: MMIO range=[0xfeb80000-0xfec01fff] (0MB) from e820 map
Sep 08 15:33:33 kernel: e820: remove [mem 0xfeb80000-0xfec01fff] device reserved
Sep 08 15:33:33 kernel: efi: Not removing mem325: MMIO range=[0xfec10000-0xfec10fff] (4KB) from e820 m>
Sep 08 15:33:33 kernel: efi: Not removing mem326: MMIO range=[0xfec30000-0xfec30fff] (4KB) from e820 m>
Sep 08 15:33:33 kernel: efi: Not removing mem327: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 m>
Sep 08 15:33:33 kernel: efi: Not removing mem328: MMIO range=[0xfed40000-0xfed44fff] (20KB) from e820 >
Sep 08 15:33:33 kernel: efi: Not removing mem329: MMIO range=[0xfed80000-0xfed8ffff] (64KB) from e820 >
Sep 08 15:33:33 kernel: efi: Not removing mem330: MMIO range=[0xfedc2000-0xfedcffff] (56KB) from e820 >
Sep 08 15:33:33 kernel: efi: Not removing mem331: MMIO range=[0xfedd4000-0xfedd5fff] (8KB) from e820 m>
Sep 08 15:33:33 kernel: efi: Remove mem332: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
Sep 08 15:33:33 kernel: e820: remove [mem 0xff000000-0xffffffff] device reserved
Sep 08 15:33:33 kernel: DMI: SMBIOS 3.3.0 present.
Sep 08 15:33:33 kernel: DMI: Gigabyte Technology Co., Ltd. B550I AORUS PRO AX/B550I AORUS PRO AX, BIOS>
Sep 08 15:33:33 kernel: DMI: Memory slots populated: 2/4
Sep 08 15:33:33 kernel: tsc: Fast TSC calibration using PIT
Sep 08 15:33:33 kernel: tsc: Detected 3393.433 MHz processor
Sep 08 15:33:33 kernel: e820: update [mem 0x00000000-0x00000fff] System RAM ==> device reserved
Sep 08 15:33:33 kernel: e820: remove [mem 0x000a0000-0x000fffff] System RAM

We need a complete log to help you, can you upload that to our GitHub?

No I’m not going anywhere near GitHub or any other corporate surveillance shitholes. Sorry.

Can’t really help you then, sorry

Yeah I didn’t think so. Really disappointing to see such a promising project with zero commitment to open platforms to engage with your users. It’s not fair to ask them to subject themselves to such things just to participate.