Buoll
UBUniversal Blue
•Created by Buoll on 2/25/2025 in #🛟bazzite-help
error: ../../grub-core/kern/mm.c:552:out of memory
23 replies
UBUniversal Blue
•Created by Buoll on 2/1/2025 in #🛟bazzite-help
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.26 replies
UBUniversal Blue
•Created by Buoll on 1/23/2025 in #🛟bazzite-help
NVMe M.2 drive not consistently mounting on startup
So I've got 6 drives plugged into my unholy mess of a machine. 3 standard HDD's of varying sizes, 2 NVMe M.2 SSD's (one boot/root, the other just storage), and a 2.5" SSD.
During my initial setup, I used the Partition Manager to set the mount point for each of the non-root drives under /var/mnt/, the same way I did in Nobara a few months ago (though on non-atomic I believe I just did directly under /mnt/). For whatever reason, the storage M.2 drive occasionally fails to mount on start up (I'd say about 50/50). It's frustrating for Steam as that's where most of my games are, and mounting while the computer is already started, all the games seem to need to re-do their vulkan shaders for whatever reason.
I'm hesitant to point to a hardware issue at this point as it was working flawlessly before I installed Bazzite, and I am able to immediately mount it no issues when it does not auto mount. The only changes between Nobara and switching to Bazzite is that I installed and freshly formatted a new M.2 NVMe in the old Nobara's drives slot (which is currently sitting on my desk), the drive in question was never touched. Is there a better way I should be setting the mount points, or what additional info is needed to help me troubleshoot this? MOBO is also less then 4 months old.
15 replies