GarudaOS crash and boot issue

Hardware Report - Acer Nitro AN515-46 (Generated March 14, 2025)

System Overview

  • OS: Microsoft Windows 11 Pro, Version 10.0.26100 (Build 26100)
  • System Manufacturer: Acer
  • System Model: Nitro AN515-46
  • System Type: x64-based PC
  • BIOS Version: Insyde Corp. V1.16, Release Date: 24/12/2024
  • Total Physical Memory: 15,557 MB (approx. 16 GB)
  • Boot Device: Disk 0 (assumed from \Device\HarddiskVolume1)
  • Virtualization: Hypervisor detected, Virtualization-based Security running

Processor

  • Name: AMD Ryzen 7 6800H with Radeon Graphics
  • Manufacturer: AuthenticAMD
  • Number of Cores: 8
  • Number of Logical Processors: 16
  • Max Clock Speed: 3201 MHz

Physical Disks

  1. Disk 0:
  • Friendly Name: SAMSUNG MZVL2512HCJQ-00B07
  • Media Type: SSD
  • Bus Type: NVMe
  • Size: 512 GB (512,110,190,592 bytes)
  1. Disk 1:
  • Friendly Name: Fanxiang S501Q 512GB
  • Media Type: SSD
  • Bus Type: NVMe
  • Size: 512 GB (512,110,190,592 bytes)

Memory (RAM)

  • Manufacturer: Micron Technology
  • Part Number: MTC8C1084S1SC48BA1
  • Capacity: 16 GB (17,179,869,184 bytes)
  • Speed: 4800 MHz
  • Configuration: Single module detected

Motherboard

  • Manufacturer: RB
  • Product: Jimny_RBH

Video Controllers (GPUs)

  1. Primary GPU:
  • Name: NVIDIA GeForce RTX 3060 Laptop GPU
  • Adapter RAM: 4 GB (4,293,918,720 bytes)
  • Driver Version: 30.0.15.1274
  1. Integrated GPU:
  • Name: AMD Radeon​:trade_mark: Graphics
  • Adapter RAM: 512 MB (536,870,912 bytes)
  • Driver Version: 31.0.12028.2

Network Adapters

  • NIC 1: Killer E2600 Gigabit Ethernet Controller
  • NIC 2: RZ616 Wi-Fi 6E 160MHz
  • NIC 3: Bluetooth Device (Personal Area Network)

Additional Notes

  • BIOS Date: Updated to V1.16 as of December 24, 2024.
  • Disk Configuration: Both SSDs are NVMe, suggesting high-speed storage typical for modern laptops.
  • Hybrid Graphics: NVIDIA RTX 3060 (discrete) + AMD Radeon Graphics (integrated), likely using NVIDIA Optimus or similar switching technology.

Context for Troubleshooting (Garuda Linux Boot Issue)

This hardware report is generated to assist with diagnosing why Garuda Linux live USBs fail to boot on this specific Acer Nitro AN515-46 laptop, despite working on other systems (including the same model). Key details:

  • Background: The issue began after a sudden, unpredictable crash of Garuda Linux (Dragonized KDE edition) while in use. The crash occurred in the middle of work, with no prior warning or indication of instability. Following this crash, the system became unable to boot into the Garuda live USB, displaying only a black screen before the GRUB menu or boot options appear. This persists despite extensive troubleshooting.
  • Boot Failure: Garuda hangs on a black screen pre-GRUB, unlike other distros (e.g., Ubuntu, Fedora) that boot successfully on the same hardware.
  • Attempts Made:
    • Tested multiple Garuda editions (Dragonized, Mokka, Sway, KDE Lite, Hyprland) via Ventoy (updated), Rufus, and dd on various USB drives.
    • Wiped both SSDs (Samsung and Fanxiang) and reset BIOS settings to defaults.
    • Verified the USB works on three other PCs, including an identical Nitro AN515-46 model.

Did you try grub2?

1 Like

Yes, I did. I also tried to disable each of GPUs, tries with and without fast boot, tried with one NVME in and out.

If other OS work, just try the LTS version from 2024

Also tried with VPN

Only xfce with lts exist at the moment inside folder “garuda”
cosmic inside “community”

The story Acer + Nvidia.
To test over
→ disable dgpu → start live usb (no grub) → boot with open source
or
disable igpu → start live usb (no grub) → boot with open source
all relevant options inisde Bios must also be disabled fastboot /secure boot

Sorry, someone must have cleaned too well. :exploding_head:

The thing is that I used Garuda for a long time, and issue is not in drivers or anything like that.
It was stable AF on this exact laptop.

These two things are not necessarily related. And you would not be the first person who cannot boot a current live.iso.

This does not mean that the hardware is 100% identical. Even within a model series, the same SSDs/NVMe’s are not installed. Most often, however, it is WiFi/BT adapters that change within a model series. Since you obviously have windows dual boot…are you sure that a BIOS update was not installed via WU w/o being asked? Windows AND Acer are known for this kind of nonsense. BIOS version identical? BIOS settings identical?

Try removing ALL drives AND the WiFi/BT card.

Have you tried the LTS version?
If you still have an old Bird of Pray iso, try booting with it.


Edit: All your posts in this topic are only about the live.iso. But the most important information is missing: How far were you able to boot your installed Garuda Linux after it crashed suddenly, unpredictably and without warning or signs of instability during use?

4 Likes

So I’ve tried all those options with 25036. And installing 25038 now.
I hope it will help)

1 Like

Nope. Still no(

Very informative.

But you can boot the live.iso now? If so, please post your garuda-inxi.

1 Like

Also having problems here with the latest Mokka 250308 ISO. Currently have Dragonized Gaming installed on my desktop on a partitioned NVMe drive.

Tried making the bootable usb 3 ways: command line DD, Ventoy (latest version), and also with Rufus from Windows. It only seems to hang at the boot screen.

Brief overview of my sytem:
i7-11700k
32gb RAM
Radeon 6900XT
Multiple NVMe SSDs and a couple spinning hard drives of different file system formats, with a Windows 11 install on a separate SATA SSD.

give Arch Linux - isoimagewriter 24.12.3-1 (x86_64) a shot paru -S isoimagewriter i cant say it will work but its what i used to get a working install. once installed from the start menu type iso an it should be there

1 Like

Thanks for the suggestion. Just tried that and still no dice, unfortunately.

May just have to wait a while until some of the teething pains subside with this new release.

No, I mean that I still can’t even enter the first boot menu. It’s just permanently black.
I’ve tried via ventoy and via rufus.

Yup, same issue here.

Since I’m having a similar issue of not being able to boot the current Mokka live ISO, here’s my inxi if it helps to diagnose or debug:


Removed

Just a shot in the dark: Remove the AMD GPU and try to boot the live.iso with the Intel iGPU only.
The same the other way around, reinstall the AMD GPU and disable the Intel iGPU in the BIOS. Then try to boot the live.iso.

Did you try the method with ventoy and grub2?


@tak0dan : You have an optimus laptop, can you disable the iGPU or dGPU in the BIOS (even if I probably already know the answer at Acer…)?

3 Likes