# Bazzite 3.7.0 Update Released **URL:** \ **Category:** Bazzite\ **Tags:** announcements, bazzite-news\ **Created:** [August 27, 2024, 2:19pm UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726 "2024-08-27T14:19:49Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [August 27, 2024, 2:19pm UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726/1 "2024-08-27T14:19:49Z")
![Bazzite Tagline](https://global.discourse-cdn.com/free1/uploads/univeral_blue/original/2X/6/6efee91acd1eaaa58c47766f808433eedf85adc2.png) > This is the last Bazzite update to be released with a version number (in this case: 3.7.0), and every announcement from this point forward will focus strictly on new features that are added and categorized by the **[build date](https://github.com/ublue-os/bazzite/actions/workflows/build.yml)** and **[Github commit ID number](https://github.com/ublue-os/bazzite/commits/main/)**. > Bazzite and other [Universal Blue images](https://universal-blue.org/#images) follow the “continuous delivery / rolling release” methodology for system updates, so update version numbers like “3.7.0” are useless since most users already have this in the latest builds before this announcement landed. **[Update](https://universal-blue.discourse.group/t/draft-bazzite-3-7-0-update-released/3726#p-8917-upgrading-bazzite-9) ready to download for current users**⬇ **New ISOs available on our [website](https://download.bazzite.gg) for new users** 💿 # Keyboard-Less Installation ![New Installer](https://global.discourse-cdn.com/free1/uploads/univeral_blue/original/2X/1/151b0f1dda4242a8e24410243637bae05962f555.webp) > **Important Note** : Remember to change your password from the default password (`bazzite`) after installing it because everyone knows your password if you don’t. The new ISOs come with a default username and user password if the user never clicks “_User Creation_” in the installer which is useful for installing on handheld PCs. **It is recommended to change the default password after installation**. Be careful if you tap on “User Creation” and do not have a physical wired keyboard nearby since that activates a new user and will no longer work without one until you restart the installer. The new installer refinements also fixed the issues exclusive to the Steam Deck OLED hardware including requiring Ventoy exclusively for flashing for proper scaling and using Basic Graphics Mode in the installer. This also fixes issues installing on other handhelds like Ayaneo Next as well. The installer has a new cosmetic change with a Bazzite themed look to move away from the default Fedora branding that comes with the installer. # Smaller Update Sizes = Faster Updates w/ Rechunk [Rechunk](https://github.com/hhd-dev/rechunk) is now part of Bazzite which means updates can be between 2-5 times faster than previously. Gone are the days where the entire image had to be re-downloaded for every update. ## The test results for Rechunk conclude: > Experimentally, we have seen that on Bazzite, due to extensive changes to Kinoite, `rechunk` lowers the total image size by 1GB. Then, if a user updates weekly, they get around a 40% reduction in download size (from 5GB to 3GB). If they update every 1-2 days, they get a 60-80% reduction in download size (from 5GB to 1-1.5GB). **For images built back to back, the download size lowers by over 90%** to 100MB-300MB, which is the size of the RPM database (~110MB) and change. **- _[Antheas Kapenekakis](https://github.com/antheas), Rechunk developer_** # AMD Polaris Series Hardware Functional Again! ![Polaris GPU](https://global.discourse-cdn.com/free1/uploads/univeral_blue/original/2X/b/b133c37c45595e5619415183115e4e45a1f225e9.jpeg) **← An AMD Polaris series GPU** An older version of Gamescope is shipped and utilized when AMD Polaris hardware is detected. This makes HTPCs using Polaris AMD GPU hardware usable again, but since its an older Gamescope version then there may be missing features shipped in the newer Gamescope builds not present here. > **Caveat** : Physical keyboards cannot use the SHIFT key on this hardware. # Nvidia Drivers Updated to 560 > **[NVIDIA stable driver 560.35.03 released for Linux with Wayland fixes](https://www.gamingonlinux.com/2024/08/nvidia-stable-driver-560-35-03-released-for-linux-with-wayland-fixes/)** > > NVIDIA today released driver 560.35.03 as the latest stable version for Linux users, so here's all that's changed. The major highlights include bug fixes for KDE Plasma Wayland. A friendly reminder that Firefox may crash upon launching until that is fixed in the stable release. Use Firefox Nightly in a [Distrobox container](https://ublue-os.github.io/bazzite/Installing_and_Managing_Software/Distrobox/) or [another browser](https://flathub.org/apps/search?q=Browser) temporarily to avoid this issue until Mozilla releases the fix in their stable builds which should be relatively soon. # New Steam Gaming Mode Scheduler [`Sched_ext`](https://github.com/sched-ext/scx) is now part of bazzite now with the full set of LAVD, bfpland, and rusty. The scheduler should improve the speediness of navigating the user interface in Steam Gaming Mode and improve performance in minor ways in-game. # Gated Kernel Version & Lenovo Legion Go Issues Fixed A gated Linux kernel workflow was added to avoid future regressions with the Linux kernel and our users. This decision was already in the works, but a recent event pushed this workflow to exist earlier than expected due to a kernel regression that affected Lenovo Legion Go users running Bazzite. If you experienced issues with the recent Bazzite builds on your Lenovo Legion Go, then it was due to the 6.10 Linux kernel causing issues with UMA Buffer with the “Auto” option used. “Auto” is the correct and default option, but since an issue with the 6.10 kernel broke this option, the Bazzite team advised users who reported it to follow a workaround that was changing it to 4GB until we downgraded the kernel, which we did by now. If you have done this workaround, then update and change it back to “Auto” unless you have a specific reason to use 4GB. As a result of this incident the team rushed to have a kernel workflow to have a specific kernel pinned for a while to avoid major regressions with each Linux kernel release. # Other Highlights - Touch gestures for Steam Gaming Mode has made a return and can be disabled temporarily with HHD now. - TDP for GPD and Ayaneo Devices Fixed to restore properly after waking up from sleep. - HHD Bug Fixes & Improvements > The next Bazzite Buzz is planned later this week with more news surrounding Bazzite. * * * # Upgrading Bazzite > Updating **may take a while** and is dependent on your internet download speed plus the performance of the drive Bazzite is installed on. > View the [Updating Guide](https://ublue-os.github.io/bazzite/Installing_and_Managing_Software/Updates_Rollbacks_%26_Rebasing/updating_guide/) for more information. Current users can upgrade to the newest builds by updating their system and rebooting. User-installed applications will also be upgraded in the process. ## Desktop Images (_Bazzite_) Desktop images will usually auto-update once per day and apply on a reboot, but if you are impatient and want the update now, then open the **System Update** application. Alternatively, open the terminal and **enter** : ```command ujust update ``` Wait for it to finish, then reboot to be on the latest Bazzite build. ## Handheld/HTPC Images (_Bazzite-Deck_) In Steam Gaming Mode: Open the **Steam Menu** \> **Settings** \> **System** and press the **Check for updates** button. Alternatively, use the method for the “ **Desktop Images** ” listed above in Desktop Mode. * * * [Full changelog for 3.7.0](https://github.com/ublue-os/bazzite/releases/tag/v3.7.0) ---
**Author:** ![Plyply](https://avatars.discourse-cdn.com/v4/letter/p/82dd89/32.png) [@Plyply](https://universal-blue.discourse.group/u/Plyply)\ **Post date:** [August 29, 2024, 5:58am UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726/2 "2024-08-29T05:58:07Z")
> [@nicknamenamenick](#): > > As a result of this incident the team rushed to have a kernel workflow to have a specific kernel pinned for a while to avoid major regressions with each Linux kernel release. Are you saying kernels will be held back? For instance Arch and Fedora are on 6.10.6 iirc. ---
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [August 29, 2024, 1:14pm UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726/3 "2024-08-29T13:14:34Z")
If a major regression happens that affect our userbase then yes. In this case it affected Lenovo Legion Go users. ---
**Author:** ![Plyply](https://avatars.discourse-cdn.com/v4/letter/p/82dd89/32.png) [@Plyply](https://universal-blue.discourse.group/u/Plyply)\ **Post date:** [August 29, 2024, 1:26pm UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726/4 "2024-08-29T13:26:13Z")
Thanks for reply. So this issue with Legion Go hardware causes all Bazzite users to be forced on older kernels. How long will all users of Bazzite be on 6.9 kernels? Will this continue till 6.11 comes out? ---
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [August 29, 2024, 2:17pm UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726/5 "2024-08-29T14:17:24Z")
It causes all users yes. Kernel will upgrade when no major regressions affect the userbase. There’s a lot of Lenovo Legion Go users here. It’s not really a big deal to stay on an older kernel for a little longer. Regressions happen all the time on the Linux desktop. ---
**Author:** ![Mangosmurf](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@Mangosmurf](https://universal-blue.discourse.group/u/Mangosmurf)\ **Post date:** [August 29, 2024, 5:28pm UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726/6 "2024-08-29T17:28:59Z")
Regarding VRAM in Legion Go you write > [@nicknamenamenick](#): > > “Auto” is the correct and default option I use a ROG Ally with the same chipset, and in Windows at least using a static VRAM allocation has been shown in tests to often yield a slightly higher FPS than the Auto option. Is this different with Bazzite/Linux? ---
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [August 29, 2024, 5:34pm UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726/7 "2024-08-29T17:34:42Z")
Windows doesn’t handle auto VRAM well. The opposite is true under Linux which yields higher consistent framerates with the Auto option. ---
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [September 9, 2024, 12:00pm UTC](https://universal-blue.discourse.group/t/bazzite-3-7-0-update-released/3726/8 "2024-09-09T12:00:29Z")
This topic was automatically closed after 9 days. New replies are no longer allowed.