Garuda installation stalling at 78% (running mhwdcfg operation)

Cryo · April 29, 2025, 10:47am

Hello everyone!

Feel a bit silly posting for assistance so soon, but its great to be posting on an active forum again!- loving the Linux community.
Currently trying to install Garuda dragonized gaming edition onto a separate NVMe specifically for Linux as I make the full transition over, only using windows for Tarkov (EAC issues with Linux). Originally installed mint, realized it was far too similar to windows and I really wanted change. Garuda coming with Nvidia drivers seemed like a great introduction to a more stimulating OS. -I’ve really tried to do my research and want to learn/teach myself. Bear with my trash terminology we’re getting there :P.

Had issues even getting the USB to boot, searched forums and Ventoy did the trick. Normal setup wouldn’t work, grub2 did- but wouldn’t progress. Running text version of Ventoy fixed and I was able to boot into the Garuda DE using Nvidia proprietary drivers.
Ran through the installation wizard, selected the correct drive, selected full erase and proceeded with install.
PC then blackscreened. No alternative bootloader is showing in EUFI (only windowsbootloader, not GRUB?).
I booted to windows to check the health/partition of the drive to check it had installed correctly and all seems ok?
I tried booting from the USB into the OS, when checking EFI bootloaders in Ventoy I get a few results, but all are /windows and boot me into the windows 11 OS.

My next guess was that the Garuda installation may have had a fault/corrupted due to the blackscreen once the installer was finished.

Booted from USB
Ran installer
Selected NVMe/Erase

But now during the installation process I’m getting stuck at the 78% mark with “Running mhwdcfg operation”. Tried hard resetting and completing the installation process again to no avail. Also tried running ventoy off of an external SSD incase the flashdrive was the issue- but still not progressing past this point. Honestly only posting here as I’ve run out of ideas. I’ve tried looking up the operation, various terms in the logs but not finding anything helpful.

I also tried running “sudo -E calamares -D8” as posted on another post incase the issue was related to the GUI launch of the installer. Any help would be appreciated.
Not sure if I am able to access/post any useful garuda-inxi logs as I am only booting from USB, but here they are, terminal logs where it freezes underneath. Currently posting from the Garuda DE- PC doesn’t freeze, launcher just doesn’t progress. >

Garuda-inxi logs:

System:
Kernel: 6.13.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
lang=en_US keytable=us tz=UTC misobasedir=garuda
root=miso:LABEL=GARUDA_DR460NIZEDGAMING_BROADWIN quiet
systemd.show_status=1 checksum=y driver=nonfree nouveau.modeset=0
i915.modeset=1 radeon.modeset=1 rdinit=/vtoy/vtoy
Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A info: frameworks v: 6.11.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: Z790 UD AX v: x.x
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: F5 date: 06/06/2023
CPU:
Info: model: 13th Gen Intel Core i5-13600KF bits: 64 type: MST AMCP
arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
microcode: 0x12C
Topology: cpus: 1x dies: 1 clusters: 8 cores: 14 threads: 20 mt: 6 tpc: 2
st: 8 smt: enabled cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32
KiB, 8x64 KiB L2: 20 MiB desc: 6x2 MiB, 2x4 MiB L3: 24 MiB desc: 1x24 MiB
Speed (MHz): avg: 800 min/max: 800/5100:3900 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800
17: 800 18: 800 19: 800 20: 800 bogomips: 139776
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA102 [GeForce RTX 3080 Lite Hash Rate]
vendor: Micro-Star MSI driver: nvidia v: 570.124.04
alternate: nouveau,nvidia_drm non-free: 550/565.xx+ status: current (as
of 2025-01; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: none off: DP-1 empty: DP-2,DP-3,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:2216 class-ID: 0300
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
s-diag: 692mm (27.26")
Monitor-1: DP-1 mapped: DP-0 note: disabled model: Acer XB271HU
serial: <filter> built: 2020 res: mode: 2560x1440 hz: 60 scale: 100% (1)
dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland
API: OpenGL v: 4.6.0 vendor: nvidia v: 570.124.04 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2
memory: 9.77 GiB
API: Vulkan v: 1.4.304 layers: 5 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3080 driver: N/A device-ID: 10de:2216
surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
Device-2: NVIDIA GA102 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
Device-3: Logitech G733 Gaming Headset
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-12:9 chip-ID: 046d:0ab5 class-ID: 0300
API: ALSA v: k6.13.5-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8852CE PCIe 802.11ax Wireless Network
driver: rtw89_8852ce v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: 4000 bus-ID: 05:00.0 chip-ID: 10ec:c852 class-ID: 0280
IF: wlp5s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 06:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Broadcom BCM4360 802.11ac Dual Band Wireless Network Adapter
driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 07:00.0 chip-ID: 14e4:43a0 class-ID: 0280
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:10 chip-ID: 0bda:0852
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Device-2: Broadcom BCM20702A0 Bluetooth 4.0 driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6.4:6
chip-ID: 0a5c:21e8 class-ID: fe01 serial: <filter>
Report: ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6
status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 2.73 TiB used: 7.11 GiB (0.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Crucial model: CT500P2SSD8
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P2CR048 temp: 43.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Kingston model: SNV2S1000G
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: SBM02103 temp: 44.9 C
scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: WDC WDS240G2G0A-00JH30
size: 223.58 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0000 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM010-2EP102
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: CC43 scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Verbatim model: Vi550 S3
size: 238.47 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
fw-rev: 0101 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.17 GiB used: 1007.2 MiB (3.2%)
priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
max-streams: 20 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 50.0 C mobo: 45.0 C gpu: nvidia temp: 57 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 32 GiB available: 31.17 GiB used: 7.32 GiB (23.5%)
Processes: 429 Power: uptime: 57m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.43 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1775 libs: 522 tools: octopi,paru Compilers:
clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 4.0.0
running-in: konsole inxi: 3.3.37
warning: database file for 'garuda' does not exist (use '-Sy' to download)
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
warning: database file for 'chaotic-aur' does not exist (use '-Sy' to download)
Garuda (2.7.2-1):
System install date:     2025-04-29
Last full system update: 2025-04-29 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       <superuser required>
Failed units:            snapper-cleanup.service

TERMINAL LOGS:

2025-04-29 - 20:16:53 [6]: virtual void Calamares::JobThread::run()
2025-04-29 - 20:16:53 [6]:     Starting job "Set password for user root" ( 26 / 35 ) 
2025-04-29 - 20:16:53 [6]:     .. Running "usermod" "-p" "$y$j9T$bw.cezHH2Rqx4.avy7bng.$T87Js7XXOjyFURtup0xAEyn.hS5p7k6OIcCkQsr38J3" "root" 
2025-04-29 - 20:16:53 [6]: virtual void Calamares::JobThread::run()
2025-04-29 - 20:16:53 [6]:     Starting job "Set hostname CryoLINUX_PC" ( 27 / 35 ) 
2025-04-29 - 20:16:53 [6]: virtual void Calamares::JobThread::run()
2025-04-29 - 20:16:53 [6]:     Starting job "displaymanager" ( 28 / 35 ) 

2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: Found gettext "en_GB" in "/usr/share/locale/en_GB" 
2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: "lightdm selected but not installed" 
2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: "gdm selected but not installed" 
2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: "mdm selected but not installed" 
2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: "lxdm selected but not installed" 
2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: "slim selected but not installed" 
2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: "Using rootMountPoint '/tmp/calamares-root-h2827uei'" 
2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: ".. selected DE plasma" 
2025-04-29 - 20:16:53 [6]: [PYTHON JOB]: "Setting up autologin for user cry." 
2025-04-29 - 20:16:53 [6]: virtual void Calamares::JobThread::run()
2025-04-29 - 20:16:53 [6]:     Starting job "mhwdcfg" ( 29 / 35 ) 
2025-04-29 - 20:16:53 [6]:     .. Running QList("mhwd", "-a", "pci", "nonfree", "0200", "--pmconfig", "/opt/mhwd/pacman-mhwd.conf") 

2025-04-29 - 20:16:53 [6]:     .. Running QList("mhwd", "-a", "pci", "nonfree", "0280", "--pmconfig", "/opt/mhwd/pacman-mhwd.conf") 

2025-04-29 - 20:17:16 [6]:     .. Running QList("mhwd", "-a", "pci", "nonfree", "0300", "--pmconfig", "/opt/mhwd/pacman-mhwd.conf")

My only other thought is to boot windows, remove the partitions/wipe the drive and try again?
MOBO is Gigabyte Auorus Z790.
Secure boot disabled, fast boot disabled.
It is my understanding mhwdcfg operations are installing/config for drivers, debated trying running opensource drivers when installing but then worried i’ll run into issues like using the intergrated graphics on my CPU/nvidia driver installation issues.

Hoping to hear back soon, I’ll keep troubleshooting. Been two days between work but i’m determined to get this working. Thanks!

EDIT 1:

Not sure if this helps, found the command “journalctl” and these are the logs

╭─garuda@garuda in ~ as 🧙 took 2s
╰─λ journalctl
Apr 29 19:57:15 archlinux kernel: Linux version 6.13.5-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 14.2.1 20250207, GNU ld (GNU Binutils) 2.44) #1 ZEN SMP PREE>
Apr 29 19:57:15 archlinux kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC lang=en_US keytable=us tz=UTC misobasedir=garuda >
Apr 29 19:57:15 archlinux kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Apr 29 19:57:15 archlinux kernel: BIOS-provided physical RAM map:
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003587afff] usable
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x000000003587b000-0x000000003897afff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x000000003897b000-0x0000000038bdefff] ACPI data
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x0000000038bdf000-0x00000000390d0fff] ACPI NVS
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000390d1000-0x0000000039f65fff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x0000000039f66000-0x0000000039ffefff] type 20
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x0000000039fff000-0x0000000039ffffff] usable
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x000000003a000000-0x000000003dffffff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x000000003ec00000-0x000000003fffffff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000fc000000-0x00000000fc00ffff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Apr 29 19:57:15 archlinux kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008bfffffff] usable
Apr 29 19:57:15 archlinux kernel: NX (Execute Disable) protection: active
Apr 29 19:57:15 archlinux kernel: APIC: Static calls initialized
Apr 29 19:57:15 archlinux kernel: efi: EFI v2.8 by American Megatrends
Apr 29 19:57:15 archlinux kernel: efi: ACPI=0x3902e000 ACPI 2.0=0x3902e014 TPMFinalLog=0x38ffb000 SMBIOS=0x39a58000 SMBIOS 3.0=0x39a57000 MEMATTR=0x2b35c418 ES>
Apr 29 19:57:15 archlinux kernel: efi: Remove mem98: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
Apr 29 19:57:15 archlinux kernel: e820: remove [mem 0xc0000000-0xcfffffff] reserved
Apr 29 19:57:15 archlinux kernel: efi: Not removing mem99: MMIO range=[0xfc000000-0xfc00ffff] (64KB) from e820 map
Apr 29 19:57:15 archlinux kernel: efi: Not removing mem100: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
Apr 29 19:57:15 archlinux kernel: efi: Not removing mem101: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
Apr 29 19:57:15 archlinux kernel: efi: Not removing mem102: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
Apr 29 19:57:15 archlinux kernel: efi: Not removing mem104: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
Apr 29 19:57:15 archlinux kernel: efi: Remove mem105: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
Apr 29 19:57:15 archlinux kernel: e820: remove [mem 0xff000000-0xffffffff] reserved

Split lock detection, crashing the kernel has me concerned- but scouring different forums I can’t find anything of note. Thanks!

EDIT 2:

Reformatting drive/deleting partitions and trying again didn’t work. Officially out of ideas. Pls help :^)

nepti · April 29, 2025, 12:23pm

Disconnect all internal drives and leave only the NVMe installed on which you want to install Garuda Linux. Then boot the live.iso and select the option with the open source drivers. In the live environment, open the KDE partitionmanager and delete all existing partitions so that the NVME only has unallocated space (no partitions). Make sure that everything is unmounted before you start the installer, try the option “Erase disk” and check if the installation and the following reboot works without issues (the nvidia drivers are only installed after the reboot during the initial setup / system update). If so, then you can reconnect the other drives.

And check whether there is an up-to-date BIOS for your mobo:

gampel · April 29, 2025, 12:28pm

Bios update could be a option

after → relevant bios entries ( s-boot,f-boot etc + inside M$ fastboot disabled)
upps nepti was faster

Jeshu · April 29, 2025, 12:44pm

@nepti gave very good advise. Now just in case your DKMS modules play up, like they do with my nvidia card installing Garuda’s chosen nvidia drivers after the update at first run, i 'll provide you with an option, so if this error does occur, (keep an eye on your nvidia driver installation and see if the dkms modules throw up errors when compiled, if so run the command below. Removing all conflicting files and only reinstalling them after the command below has successfully finished.) you can safely reboot your Garuda installation.

See how you go

sudo pacman -Sy nvidia-open-dkms egl-wayland lib32-nvidia-utils lib32-opencl-nvidia nvidia-settings opencl-nvidia nvidia-utils

filo · April 29, 2025, 12:45pm

Hi there, welcome to the forum.
For sure you should first try reinstalling by choosing the free drivers option (installing Nvidia drivers later should not be a problem).
Anyway, if that fails, I remember that the solution to a very similar problem from a few years ago (unfortunately the post has links that are no longer active) was to modify part of the following file in the live USB:

/usr/lib/calamares/modules/mhwdcfg/main. py

from:

def run(self):
for b in self.bus:
for id in self.identifier['net']:
self.configure(b, id)
for id in self.identifier['video']:
self.configure(b, id)

return None

to:

def run(self):
return None

And retry the installation.

I don’t know if calamares has changed in the meantime (I’m not on my machine at the moment), but in the end it’s a simple thing to try as a last resort…

Cryo · April 29, 2025, 12:59pm

Thanks @all for your replies.
Ended up finding on some forum that adding ibt=off in the grub text editor before launching may help when I was investigating the kernel error.

Added it, reran the installer afterwards (using the NVIDIA proprietary drivers option) and it installed without any problems. Rebooted and it automatically loaded with 0 issues or hassles. Thankfully didn’t have to unscrew my mobo to get access to my other drives to try to install the OS (I’m guessing this was incase I was selecting the wrong drive?)

I reformatted and wiped the drive through windows, so either doing it through Linux fixed it, or adding the ibt=off parameter in grub resolved the issue.

In relation to the ibt command, from looking online I’m worried this may leave me vulnerable to different types of exploits?
Going to see if I can troubleshoot/test if the NVIDIA drivers have install a game just to check for any errors.
I had updated the mobo drivers through the gigabyte app centre software (although I understand it’s trash. But mobo is olderrrrr, it should have most up to date update).
Just paranoid that there will be something unstable/something that may go wrong, is there a way I can stress test any issues immediately?

Thank you all for your help, excited to join the community and move over to Linux, already really enjoying the troubleshooting- feels rewarding.

nepti · April 29, 2025, 2:51pm

This was in case some drive was faulty or not recognized correctly for some other reason and thus prevented the installation. There are also several cases where an existing windows (efi) partition has prevented the installation of Linux.

You don’t really need to worry about that.
The kernel parameter ibt=off to disable indirect branch tracking is set by default after the installation of Garuda Linux for compatibility reasons. You should rather worry about the quality of the nvidia drivers on linux and about nvidia driver updates going wrong.

I have marked your post as solution.
If there are other issues, just open a new topic (ONE issue per topic ).

Welcome to the community.

system · May 1, 2025, 2:52pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.