Rebased to Nvidia, now I'm having issues. Please help.
Hey guys, I rebased from the AMD KDE Gamemode -> AMD KDE Desktop and had no problems. I then became extremely frustrated with dealing with DP adapters because AMD doesn't have HDMI 2.1 support on Linux. I then rebased to bazzite-nvidia-open:stable, shutdown my PC, and then reinstalled my 4070 super.
The problem is now on boot it randomly boots into bazzite:stable or bazzite-nvidia-open:stable. I sometimes don't even see the menu to choose which one to boot into. The next time I finally boot into bazzite-nvidia-open:stable again, is there a way to permanently delete bazzite:stable? Has anyone else had this problem? Thank you.
32 Replies
Also, I am currently on bazzite:stable while typing this. I guess it is using the open-source Nvidia drivers right now?
This is what I get from using
bruh
I've booted into the right one once, but then I rebooted and ended up right back to bazzite:stable
I now rebased to bazzite-nvidia:stable, then to bazzite-nvidia-open:stable to see if it would fix it. Restarted, finally now booted into bazzite-nvidia-open:stable, but using
bruh I am still getting this. Which means its just going to boot into the old one again. Why does it keep switching which one it is going to boot into?
I updated and got rid of the other installation versions but now I get this:
Is this right? Shouldn't it be staying on the same image or am I misunderstanding what this means?
This looks like you have 2 identical images now. That's a bit weird, but fine if it's not troublesome. You'll always have at least 2: your current one and your previous one.
I'm going to reboot and see if it ends up booting into the old one. I REALLY don't want to reinstall
To have a bit more info about your images
rpm-ostree statusis a bit more detailed
There is no need to reinstall don't worry.
You'll only have nvidia-open to boot into available
So that seems to have been the aim
Yeah so It won't boot into the old one before I updated right? It should progress normally now?
The old non nvidia one is not on your system anymore.
I'm talking about 42.20250715 instead of 42.20250715.1 from
rpm-ostree statusIt's weird that you'd randomly boot into old deployments.
I thankfully got rid of the AMD versions at least
Yeah idk
Let me reboot real quick
If you need to either have the grub menu show longer or not show at all (unless after failed boot or holding esc), that's possible.
Good news, I rebooted into 42.20250715.1 instead of 42.20250715
But this definitely isn't normal right? lmao
It's still there
That looks fine I think. from what command is this exactly?
from running bruh
Just tells you that that's the branch you're on currently and will also boot next time
When you run bruh do you get that too?
Yeah, that's fine as it is
yup
Okay thanks a bunch
Idk what was wrong earlier when I rebased
I was booting back and forth between Nvidia and AMD
When in doubt about the active image and next, use the rpm-ostree status one. The one with the white dot is the active one and the listed order is the order for the next boot enless you intervene.
I don't even see the grub menu when booting
Maybe because of LUKS
It's probably either set to autohide or you boot so fast your monitor doesn't activate till it's too late. You can see the current setting with
ujust configure-grub
The default timeout is 3 seconds, but this can be set manually if you want. I just autohide it and press esc if i need it.I'll set it to Always Show to test it out. Anyways, thanks for the help. I marked my post as solved.