Can't install any distro
Super weird, but I have a pair of SSD drives, had been installing various distros on my second drive to test them on my system for a few weeks now. During that time, I had upgraded Windows to 24H2...had issues, so I formatted the machine, wiped all the partitions (both drives), and reinstalled Windows 23H2 on my primary. All was good with the Windows install, but when I tried to install Bazzite again, I get an out of error warning.
error: ../../grub-core/kern/mm.c:552:of of memory.
I thought it was an issue with my Ventoy, or my ISO, but I am getting a similar error across all my distro install attempts. I even redownloaded and reinstalled Ventoy and all the ISO's, no luck. (even Linux Mint)
I am wondering if there is something that hosed my drive partitions when I reinstalled?
I have tried everything I can think of (Fast Boot on/off, UEFI on/off, Secure Boot on/off). I just tried CachyOS and Nobara and they died almost instantly after I selected the install button from grub. (I can get the other errors if it helps, but I just wanted to get Bazzite installed, I liked that best)
Anyway, I am only a couple weeks into learning Linux, and generally pretty good at troubleshooting, but this has me stumped. I searched the help threads here and saw one with a similar issue that had fixed it by disabling a Thunderbolt setting. I tried that, but it didn't work.
1 Reply
The one thing in common between all your tests is Ventoy. Ventoy is great but I'm thinking it's the Ventoy loader that is failing to load for some reason. https://arstechnica.com/civis/threads/live-iso-boot-issue-out-of-memory-error.1502492/ Similar issue to you, looks like their issue was secure boot being enabled which you have already disabled.
I'd try a different USB flash drive with Fedora Media Writer (which works on Windows) or perhaps Rufus and see if you can get into the installer
Ars OpenForum
Live ISO Boot Issue - out of memory error
The other day I was using Ventoy to test out some different distros. Initially I was doing it because I had some instability with my main machine that were either tied to recent Windows updates or were a return of some hardware instability due to some fiddling (my fault). So I decided to run...