Have all new stuff all AMD. Running bazzite and the gpu ( 9070 xt ) does not work, when I plug in the monitor to either port type it just compresses everything up at the top of the screen all warped. Everything works fine on the MB ports not sure what I might have done to screw it up. Saw some posts talking about proper versions for the kernel and mesa and both those seemed to be new enough for the GPU ( 6.14.4-104.bazzite.fc42.x86_64 (64-bit) ) and Mesa 25.0.1
Those errors seemed to be in games from their posts though my monitor will not even display the desktop or anything else properly what am I missing?
edit
I was waiting for the card to come down in price and I put my old 3060 TI into this new system at first. How do I check if the drivers updated to new ones or if I have to do it manually? Maybe that is what is wrong
Duuuude I was trying to replace my 3060 ti as well, but all 9070s in my region sold out in 2 minutes (I’m not kidding). Now it’s still 80€ more expensive than launch (which is another 80€ more expensive than the US launch; wtf). I am at wits end…
Me too, I finally saw it only $100 above MSRP and I caved since I was worried it would actually end up going up more due to uncertain tariff situation here.
Does the boot screen look ok? Does the login screen look ok?
I had a problem with my new 9070 on debian KDE, and the issue was with color accuracy setting
Yeah boot and password screen look fine. I tried changing from accurate color to efficient color but that did not do anything for me. Now I am getting a message every 10 minutes or so pop up saying “UUPD Some system updates failed” but no specifics. I really appreciate everyone trying to help but it is looking more and more like a reinstall is going to be needed.
Have you checked the bios on your board? Just did a bazzite/AMD situation myself with a 9070. My aorus b650 needed bios updates.
I will double check this one. I had gone in on initial setup and not noticed updates needed but I will check again, good looking out.
It’s probably something simpler than that, but these are new GPUs so it’s worth ruling it out. Good news is modern boards typically aren’t very complicated to update
I went back and double checked, I did get the AMD one but I got the one marked for old cards not the 9k series
I was waiting for the card to come down in price and I put my old 3060 TI into this new system at first
Did you install the Nvidia version of Bazzite? And if so, did you rebase to the non-Nvidia version?
Either way it might be worth a clean install.
What is rebase?
Rebase is essentially switching the versions of Bazzite you have installed without a complete reinstall
Try
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
Or whatever your preferred configuration is.
Yeah that did not seem to work using the rebase command I copied from Bazzites website for the version I need it gave me an error part way through
Necroscope@bazzite:~$ rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable Pulling manifest: ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable Checking out tree e71e4f5… done Enabled rpm-md repositories: charm updates fedora rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates rpmfusion-nonfree tailscale-stable hardware_razer terra terra-source updates-archive Importing rpm-md… done rpm-md repo ‘charm’ (cached); generated: 2025-04-01T23:42:24Z solvables: 553 rpm-md repo ‘updates’ (cached); generated: 2025-05-16T02:31:33Z solvables: 12763 rpm-md repo ‘fedora’ (cached); generated: 2025-04-09T11:06:59Z solvables: 76879 rpm-md repo ‘rpmfusion-free-updates’ (cached); generated: 2025-05-09T06:48:03Z solvables: 41 rpm-md repo ‘rpmfusion-free’ (cached); generated: 2025-04-12T09:12:27Z solvables: 358 rpm-md repo ‘rpmfusion-nonfree-updates’ (cached); generated: 2025-05-09T07:07:05Z solvables: 20 rpm-md repo ‘rpmfusion-nonfree’ (cached); generated: 2025-04-12T09:32:45Z solvables: 218 rpm-md repo ‘tailscale-stable’ (cached); generated: 2025-05-14T23:57:33Z solvables: 120 rpm-md repo ‘hardware_razer’ (cached); generated: 2025-05-07T19:14:40Z solvables: 23 rpm-md repo ‘terra’ (cached); generated: 2025-05-16T04:46:14Z solvables: 2412 rpm-md repo ‘terra-source’ (cached); generated: 2025-05-16T04:46:16Z solvables: 365 rpm-md repo ‘updates-archive’ (cached); generated: 2025-05-16T02:58:46Z solvables: 12814 error: Packages not found: lact
Looks like I will probably just have to do a reinstall with the proper one
Note that they give you a different ISO when you choose AMD vs Nvidia on the bazzite website. So when you do the reinstall, make sure to grab the ISO for AMD.
Yeah that’s probably best
Test with a fedora 42 live usb to verify it isn’t bazzite I’d say
What is that, using a different operating system to try to boot? Is this just to check if the hardware itself is bad?
It’s to verify if either a configuration in Bazzite is the cause(such as your drivers), or if it is hardware related. The other comment asking if you installed the Nvidia version of Bazzite suspects driver issues as well, so a live USB would be able to rule it out or confirm it.
Alternatively, and probably the better option is to just take backups of your files and such and then reinstall Bazzite to the system, making sure you are using a version that is compatible with your graphics card. You don’t seem as though you know a tonne about Linux, so I would probably recommend that over trying to rebase the OS, as it will generally be easier for you to do I think, and more completely insure system stability.
It’s someone shilling their own personal OS preference.
Sorry you have to be caught up in all this. Good luck.
Basically, linux can be used before installing and its called a live disk. Make a boot drive with etcher and boot into it. Been using Nebora project (fedora 42) and its been great so far
Is it this issue? - https://github.com/ublue-os/bazzite/issues/2344
Someone fixed a similar issue by setting their display color accuracy to “Prefer Efficency” instead of “Prefer Accuracy”
you can boot ostree:1 change the setting, run sudo ostree admin pin 1 then rebase back to testing (not reboot to ostree:0) that should hopefully work around it