20250131 release Breaking OS?
I ran into some issues where grub was failing with a memory error (posted below).
When selecting from the menu after bios and selecting the second image (ostree:1 instead of ostree:0 (not very descriptive)), I am able to boot back into 20250127 with no issue. At a loss for what the issue is.
rpm-ostree status -v for the attached file.15 Replies
Nvidia driver?
Potentially? Nothing online was helpful or I didn't have the bios settings mentioned, etc.
Running a 3080 Ti
Rebase to Nvidia-open
The proprietary driver is abandonware and these sorts of issues are only going to get more common until it's dead for good.
You can do so from the working :1 image
so I'm using the nvidia open bazzite image, haven't touched anything nvidia
Hmm, first I've seen this issue then
Select :1 and then
rpm-ostree rollback
That'll hold it for the time beingokay, so since I'm booted into that currently, just run that ostree command?
Yep
also not sure if this of additional interest from that 31 version status
SecAdvisories: FEDORA-2025-42ee7772e3 Low libsoup3-3.6.4-1.fc41.i686
FEDORA-2025-42ee7772e3 Low libsoup3-3.6.4-1.fc41.x86_64
ran the rollback, rebooting now. Will I need to do anything in the future for getting the continued image updates?
Same out of memory issue, didn't get that image menu either, just sitting on the mobo logo screen now
Hmm getting back to the menu and selecting the now first choice ostree:0 brought me back. Not sure what it tried to boot the first time
Or if this is some sort of hardware failure somewhere and it just sometimes works and there is no correlation to the images?
:1 is now :0
You should be good going forward
That was my assumption but that's what I got on the first reboot after the rollback. Didn't have a choice for selection of either so I assumed it went with the now ostree:0
@Kyle Gospo surface arg might be interfering on this
System boot ends in Grub Out of Memory (OOM)
Real mode area (RMA) is a part of RAM which is used by GRUB2 for its operations and to load all the required boot components (Mods, drivers, initrd etc) for successful booting. The size of the RMA is negotiated from GRUB2 as well as from Linux kernel. The current size of the RMA is 512 MB. In most scenarios, the current RMA size is large enough...
(missed the top thread here with mentions of not using @'s, my apologies Kyle and antheas)
Reviving this as I have yet to get a good pull of bazzite-nvidia-open that has not given me
out of memory error in grub-core/kern/mm.c (image above in this thread). Last stable version I have working is 41.20250127. I also cannot seem to get the rpm-ostree rollback to stick after the first power cycle, so it's just become; power on, get memory error, press reboot button. select ostree:1. I can keep rolling back but I am a forgetful person, so the pinning of 41.20250127 has at least made my system usable.
Maybe interesting point is that "pressing any key to continue" does not do anything, and eventually I just see my mobo logo, and nothing will happen til reset the machine.
I've included fastfetch and rpm-ostree status here if that's of any help.
Also came across this but there hasn't been any more comments on it: https://github.com/ublue-os/bazzite/issues/2233GitHub
Grub "Out Of Memory" on boot · Issue #2233 · ublue-os/bazzite
Describe the bug I installed bazzite-nvidia-41 and it competed successfully. After rebooting and selecting the boot option in grub, the message "out of memory" is shown followed by a &quo...
