Storage: Samsung 970 EVO NVME M.2 SSD (2880) 500GB (Intended Destination for Garuda - Clean drive, nothing on it.)
I'm attempting to do a bare metal installation of Garuda KDE Dragonized (Gaming Edition) in dual boot on my main rig that runs Windows 10.
I initially ran the iso from a multi-boot USB flash drive with Ventoy and a few different distros loaded on it with no issues. Garuda booted off the USB, I went through the installation, erased the destination SSD and put Garuda on it. When I got the message that Garuda was done installing, I removed the USB drive and checked the box to restart and waited. The latte dock disappeared, I waited about 30 minutes and the system didn't restart so I powered down the PC with the power button and restarted.
I selected Garuda from the grub menu and booted it up. I put my credentials into the login splash screen and sat waiting for the OS to load (got stuck on the Eagle head logo) it sat there frozen for about 20 minutes so I powered down my PC again, booted into Windows from the bootloader and wiped the SSD in diskpart so I could reinstall since I figured I jumped the gun on disconnecting the USB drive after I got the message that Garuda installed successfully.
I tried install off the USB again and that was the first time I got the error in the picture. It goes through the loading script, gets about halfway and errors out.
Since then, I have tried loading in UEFI and without from the USB, running with the opensource drivers and the Nvidia drivers, I flashed my BIOS on my motherboard from F10 to F11 (the newest version), disabled XMP, reflashed Garuda on a new USB flash drive with Rufus and with Balena Etcher, redownloaded the ISO off the main site and reflashed a different USB flash drive with Rufus and Etcher. Still getting this error. Did I bork my hardware? Not sure what's going on here or what to try next. Any advice would be appreciated.
I really wanted to install Linux on my main computer so I can learn it and I had my heart set on this distro. Thanks for reading.
Thank you, I went ahead and downloaded the .iso from the source and verified the SHA 256 Checksum. After, I loaded the iso onto another brand new flash drive with Balena Etcher and I'm still running into the same Kernel Panic error. I've spent the last few days googling and checking the wikis for a solution on how to capture the necessary logs. Since the installation is going immediately into a kernel panic from the grub, I haven't been able to find any documentation on how to capture the logs to post here.
I just flashed the image with Ventoy onto a new flash drive with nothing else on it and tried to run it. Basically the same thing is happening. It loads the grub menu, I can select to run with Nvidia drivers or opensource drivers. It gets to the part of the initialization for live media, then goes into a kernel panic. Just for my own sanity, I ran a full pass of memtest86+ with no errors too.
I added the command to the grub menu like you suggested. Confirmed it does try to bypass the live media setup in the initialization, but goes into a KP after. I also tried disconnecting my Logitech G815 keyboard and only using a non-rgb, e-waste keyboard instead like what was tried in the thread you posted too to see if that made a difference — sadly same deal. I was hopeful for that because that live service / live media module was as far as the installation would go before going into a KP.
It's going to be worth trying some other installer images, e.g. an older Garuda image, the Garuda barebones image, the EndeavourOS image, the basic Arch installer image (maybe even Ubuntu etc.), and see if there is any commonality.
The fact that the error didn't happen to begin with - and then started happening - suggests something else changed, though.