I have a system76 laptop recently purchased. i7-10875H, 32 GB ram, 1TB NVMe SSD. Originally came with Pop OS. When I installed Garuda I left it there and went dual boot. I shrunk the drive to approximately 300 Gigs and left the rest for Garuda. No errors during install after reboot the screen came up to Loading initial ramdisk and just sits there. Reinstalled, instead of rebooting I stayed in the program and updated and loaded drivers and looked around some then I went to reboot again and still coming up to Loading initial ramdisk. As I was going to post this I turned it back on to get the error message again and it actually booted correctly. I shut it down and rebooted and now it only goes to frozen at loading initial ramdisk. So it only booted correctly once and I did nothing different that I can think of. Kind if hoping you can help me because I kind of like it but I am a Linux beginner at best.
It's been plugged in the entire time. I went back and started from the other Garuda boot option (sorry I'm not at that screen and since you're answering real time this is what's up) and it flashed that ramdisk portion and now it's stuck at this screen.
So ... I rebooted and it just keeps freezing at that loading ramdisk. You mentioned plugging it in and it was so I unplugged it and it booted?!??? Which makes no logical sense to me whatsoever and I don't know if it's just random. Like I said, I really like what you guys have done with this build and really hope I get to use it as my driver driver.
The final part of this while post is that it keeps freezing. It boots maybe 1 every 10 or more times that I try to boot up.
So that's it? Just problems with Nvidia drivers and too bad for me? Part of the reason I bought this laptop was because of the Nvidia gpu I guess if I have to switch back to pop os I will.
Ok, apologies but like I started with… “Linux beginner at best.”
I don’t know what you mean by that?? those are the words that are on my screen, “loading initial ramdisk”
I have no idea how to do that.
I’m once again sorry for my ignorance but I just don’t know these things. I’m smart I swear to god and I learn fast and go ahead and laugh at me but I thought the OS creator wrote the driver for whatever hardware or that there was a different driver for every os for a thing. Like I said, laugh if you want but I take it from the context of what you said that a linux driver is a linux driver is… Thank you because now I know.
I do, I’m just new to this. I appreciate your patience you really have an amazing product with Garuda and I’d like to use it as my main OS.
Thank you, I'm proud of it, best system I have ever had. I think I understand what you mean I will start with the live iso and go from there. Thank you for your help.
The answer is sometimes randomly it will boot with no issues with me not interfering with the boot process. That is seldom. Most often it won't boot. When I choose advanced options it gives me 4 of them,,, on linux-tkg-bmq, linux-tkg-bmq (fallback intramfs.), on linux-lts, on linux-lts (fallback intramfs.)
Most of the time it will boot to the very last one but not the first 3. I want you to know I really appreciate your help. Please let me know if there's anything I can do.
It won't boot that way. When the grub screen comes up instead of Garuda I select the second one down that gives me other options. That's The only way I've been able to get it to boot consistently.
I don't know if this matters at all please remember I'm just uneducated about this part, but my gpu fan comes on high when this is happening. I only mention that because in all my time of using pop os which is only a few weeks, I never heard my gpu fan come on at all.
At grub enter E to edit the boot command, remove quiet and splash and add nomodeset i915.modeset=0 nouveau.modeset=0 to the same line.
Then try again ALT-F5 to get a tty console after waiting a minute.
Disabling modesetting
You may want to disable KMS for various reasons, such as getting a blank screen or a “no signal” error from the display, when using the Catalyst driver, etc. To disable KMS add nomodeset as a kernel parameter. See Kernel parameters for more info.
Along with nomodeset kernel parameter, for Intel graphics card you need to add i915.modeset=0 and for Nvidia graphics card you need to add nouveau.modeset=0. For Nvidia Optimus dual-graphics system, you need to add all the three kernel parameters (i.e. "nomodeset i915.modeset=0 nouveau.modeset=0").
Note: Some Xorg drivers will not work with KMS disabled. See the wiki page on your specific driver for details.
This might be nothing, but how did you burn your iso?
I had to redo my iso two times before I could get a consistent boot from my cheap USB stick, I didn't try to figure out why, I just retried a couple times until I had one working and once working I installed to disk.
If you haven't tried this yet, it might be faster to try recreating the iso before trying a bunch of other things. I found it faster and easier to just keep reburning the iso until I got a copy that would boot. Also, I used dd to burn the iso from an ubuntu linux install, if you were using some installed package to burn, maybe try dd instead.
Example, don't just run this, you have to be sure you have your specific usb disk (sdX in my example), google how if you don't know for sure.