error: ../../grub-core/kern/mm.c:552:out of memory
Hoping if this has bubbled up any further. Google searching ending up dry (mainly that most of the issues stem from a different portion of mm.c or reference bios options for video memory that I do not appear to have (I turned off the iGPU when I was using Nobara as it was causing issues)).
Haven't been able to boot a release since January. The "Press any key to continue..." does not work as it just eventually ends up back on the mobo logo screen and patiently awaits a reboot.
I have tried looking for a video memory option in bios, couldn't find one.
Unplugging all but a single 1080p monitor.
Setting
gfxmode=640x480 in kernel args, no noticeable change in output size.
https://github.com/ublue-os/bazzite/issues/2233
Unable to discern where the actual error threw: https://github.com/rhboot/grub2/blob/fedora-39/grub-core/kern/mm.c#L552
Any help or ideas is greatly appreciated.GitHub
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...
GitHub
grub2/grub-core/kern/mm.c at fedora-39 · rhboot/grub2
Ongoing downstream work on grub2, including Fedora and RHEL. This is not upstream; please send code upstream first - rhboot/grub2
Solution:Jump to solution
Found something https://discord.com/channels/1072614816579063828/1315844792961466378/1316565348702486609 for this person disabling TPM solved the issue. If you turn off secure boot does it make a difference?
17 Replies
I'd try rebasing to bazzite:stable with
brh rebase bazzite:stable and see if your issue has anything to do with nvidia. Looks like you have your working image pinned so you should be able to go back to your working image after testingit is indeed an issue with nvidia-open
Let's see if it's just an issue with just bazzite-nvidia-open:stable, try and rebase to bazzite-nvidia:stable with
brh rebase bazzite-nvidia:stable if that works, maybe stick with it for a while and seeDamn, same issue :/
At least we know now that it's something to do with Nvidia. What GPU do you have? and the rest of your hardware specs?
3080 Ti, see fastfetch above. Let me know if there's anything missing from that that you would want to know
And also how else I can help debug this issue so people who actually know what they are doing can get a fix in
Difficult to debug when you even start loading to OS. Thought of one more thing to try
brh rebase bazzite-nvidia-open:testing there is a new kernel in testing wonder if it's something that is already fixed and just hasn't gone into stable yetWorth a shot 🤷
while that pulls, how can I prune these images later and set the boot menu to always appear on boot? I had done rollback and pinned the working nvidia-open image, but it always ends up being second after the second reboot of the machine
You can turn off automatic updates
ujust toggle-update else it will update automatically and make that the default imageOkay, thanks. The testing image did also not work
Solution
Found something https://discord.com/channels/1072614816579063828/1315844792961466378/1316565348702486609 for this person disabling TPM solved the issue. If you turn off secure boot does it make a difference?
I believe i turned that off as Nobara did not support it, will go double check
If so try turn off TPM unless you dual-booting Windows 11... that might be a problem
That was the ticket. I am ashamed that my mind glossed over that as TPM == Secure boot. Foolish, but at least I learned something. Is there any real threat to having tpm off?
aside from dual booting windows which I will never again do
It's useful for auto decrypting your drive which you probably don't care about on a gaming pc
Considering I don't know why that would even be useful, I would concur lol.
Thanks for the help! marked as solved