Unable to boot the garuda mokka installer

Hello, i’m trying to install garuda mokka (latest release) on my laptop, here are the specs:
CPU: 11th Gen Intel® Core​:trade_mark: i7-1165G7
RAM: 16gb DDR4
GPU: Nvidia Geforce MX450 + intel iris xe

I flashed the iso to my usb using dd (i also tried balenaetcher), but booting from it just blackscreens, i tried ventoy as some suggested and that got me to the selection screen but booting from either driver options just hanged for a bit on starting dracut premount hook but eventually powered off with the error dracut one or more files are corrupted
this cannot be a file or usb issue as i have tried two different usbs and both ventoy, balenaetcher and dd, i also checked that the hashes matched, im kinda stuck here.

Did you use the grub2 option in Ventoy when prompted, as opposed to the normal mode?
And, just in case…: you checked the checksum in the USB stick, right? Not in the folder where you did the download. Sometimes there can be errors when copying from PC to USB…

7 Likes

both normal and grub2 lead to the same outcome (dracut error), also yes i did checksum the iso in the usb

i retried with grub2 mode and it doesnt throw the error instead it just blackscreens, pressing any key brings me back to the boot selection menu??? (both driver options tested)

its me again, i thought i had found the issue but i didnt, apparently i was not making the write caching complete so i kinda corrupted the iso, i let it finish this time and retried with grub2 but still nothing

hi, for the last 3 days i have been trying to troubleshoot this issue, i want to install garuda mokka on my laptop, here are the specs:
CPU: ntel Core​: i7-1165G7
RAM: 16gb
GPU: Nvidia Geforce MX450 + intel iris xe

Flashing the usb directly gave a black screen, so i tried the recommended solution (ventoy with grub2) and that does get me to the selection screen but either driver options just lead me to a black screen (same behaviour for normal mode)
the iso is intact, i checked the checksum DIRECTLY FROM VENTOY
im running out of ideas, does someone have any idea on what the problem might be?

used to work with dedicated cards booting t a black screen, so nomodeset parameter in grub on boot perhaps?

You already had a topic open about this. Please do not make duplicate topics. I’ve moved posts to your already open topic.

3 Likes