I went through and booted to the live USB again and typed in all that same stuff but now it's even more broken than before. Doesn't boot up, then gives me an error message "not enough memory, press any key to continue" then it takes me to a screen with a little green box in the upper right hand corner and just sits there... if I press enter it takes me to the same initial error message I had and then press any key, then just a black screen with a cursor. Too bad I thought it was fixed not sure what to do at this point
Too bad. I can now see many side effects of that grub bug (again, not a Garuda issue) searching on the internet, including this one. I'm sure the process above was correct, the only problem I can think of is that your efibootmgr is still pointing to the old entry.
Could you please use your live USB and provide di output of
efibootmgr -v
1 Like
You did very well for the first serious usage of the terminal.
I just wanted to let ya know 
Bruce 
5 Likes
I tried once again going through the chroot procedure as before, and now it works... over the last day I've shut down, or restarted my computer several times (without using the live USB) and it boots just fine except: just after the BIOS splash screen, I get a black screen with "no memory available" printed several times, press any key to continue. Then it takes me to the normal Garuda boot selector screen, where you select boot, uefi, snapshot etc., except it is black and white instead of a colorful graphical menu like it was before. I select the first option like normal and it boots into the system just fine. Any idea why it gives me that no memory available message now?
This error message was mentioned also by some of the users affected by the GRUB issue. That bug seems very complex to understand completely, also due to the different configurations were it may or may not occur, and can give different side effects after reinstall.
Since the system is now bootable, I think you can only wait for the next GRUB update and follow our forum or other sources in the meanwhile. Eg
2 Likes
What I miss is an official statement of the Garuda team and a guidance or behavioral recommendation.
Other distros have solved this better ... sorry
We have made a habit of avoiding unnecessary work, so we link to arch wiki and the like, and do not repeat it here again and again.
5 Likes
Today I started my computer... got the original error again. So I put the live usb in to troubleshoot... then it booted just fine (not into usb). I typed efibootmgr - v into the terminal and got this:
╭─casper@casper in ~
╰─λ efibootmgr -v
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,0005,0006,0003,0004,0007
Boot0000* garuda HD(1,GPT,10986ec4-73d2-874f-9533-8beaab008938,0x1000,0x96000)/File(\EFI\GARUDA\GRUBX64.EFI)
dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 c4 6e 98 10 d2 73 4f 87 95 33 8b ea ab 00 89 38 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 47 00 41 00 52 00 55 00 44 00 41 00 5c 00 47 00 52 00 55 00 42 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0001* UEFI OS HD(1,GPT,10986ec4-73d2-874f-9533-8beaab008938,0x1000,0x96000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 c4 6e 98 10 d2 73 4f 87 95 33 8b ea ab 00 89 38 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot0003* ASUS DRW-24B1ST j BBS(CDROM,,0x0)0000424f
dp: 05 01 09 00 03 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot0004* Samsung SSD 980 PRO 1TB BBS(HD,,0x0)0000424f
dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot0005* UEFI: USB PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(4,0)/CDROM(1,0x8184fc,0x8000)0000424f
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 01 08 / 01 01 06 00 03 00 / 03 05 06 00 04 00 / 0402 18 00 01 00 00 00 fc 84 81 00 00 00 00 00 00 80 00 00 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
Boot0006* UEFI: USB, Partition 2 PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x3)/USB(4,0)/HD(2,MBR,0x0,0x8184fc,0x2000)0000424f
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 01 08 / 01 01 06 00 03 00 / 03 05 06 00 04 00 / 0401 2a 00 02 00 00 00 fc 84 81 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00
data: 00 00 42 4f
Boot0007* USB BBS(HD,,0x0)0000424f
dp: 05 01 09 00 02 00 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
╭─casper@casper in ~ took 211ms
╰─λ
That looks correct. There's only one entry for Garuda and it is the first in the order...
Strange.
There could be another option, to downgrade the grub package to the previous version and reinstall It. But I'd keep it as last chance.
1 Like
Could it have something to do with BIOS update? That's the only other change I've made to my computer recently was updating the BIOS. Maybe try going back to an older version of bios? I'm pretty sure gigabyte my motherboard manufacturer has all previous bios versions archived on their website.
No, just wait.
1 Like
Today I tried to start my computer and the problem is even worse. I can't even get to booting the live USB at this point. I try to boot Garuda, or load a snapshot, either way I get stuck at Loading Linux linux-zen... Loading initial ramdisk...
Not sure what to do it seems my computer is totally inoperable now.
EDIT: after initally typing this from my phone I figured out going into F12 from my bios I could get the live USB to boot, and did the chroot thing again from there, the computer then booted up (still with the "out of memory" error. This is just frustrating because it seems like randomly sometimes the system will boot up, sometimes won't, not a good feeling wondering if my computer is going to start up properly on any given day. I have always used Windows or MacOS in the past, and was loving Linux until this happened, had zero problems installing garuda or getting anything to work on it. (the reason I went with garuda in the first place was I use my pc for gaming about 50% of the time, along with recording audio into audacity, and general everyday uses browsing the internet etc., garuda was recommended as a good distro for gaming) Steam games have all worked great with the proton compatibility layer. Of course the other operating systems have their problems from time to time as well, and I like the idea of not having to have a microsoft account and get spied on through windows
I am really sorry to hear that. I understand your frustration because this is a really unfortunate time, with many bugs "raining down on us from above", and many users are frustrated.
We recently downgraded Grub in our repo to the previous working version.
In my opinion, since you can access the system, you could give it a try (unfortunately, it is a bug with so many facets and side-effects that you have to go by trial). Do a
garuda-update
after that
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=garuda --recheck
update-grub
and reboot.
4 Likes
Just did that, now on reboot I no longer get the "out of memory press any key" error message, and the system starts up quickly just like it did before this whole grub issue started. Nice!
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.