Live usb install lag

I have a big issue trying to install Garuda on my pc. The live usb itself works well and i have no issues. That is until i try to use the installer app. As soon as it opens my fps goes below 1 and everything is delayed by seconds. This makes it impossible to set a username, password and passkey. It lags so much that keystrokes repeat themselves a random amount of times.
I have searched on this forum and on the web for answers but have unfortunatelly not found anything. I do not have Garuda installed right now for obvious reasons but i would love to use it.
I have tried to re-flash the usb with a new set if files btw.

post the garuda-inxi after you boot the live version

3 Likes

Ill do it as soon as i get back home.

System:
Kernel: 6.17.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64
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
Desktop: KDE Plasma v: 6.5.1 tk: Qt v: N/A info: frameworks v: 6.19.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Inet_AB product: N/A v: N/A
serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX Z790-F GAMING WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3001 date: 03/07/2025
CPU:
Info: model: 13th Gen Intel Core i9-13900K 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: 0x12F
Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2
st: 16 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32
KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
Speed (MHz): avg: 800 min/max: 800/5300:4300 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 21: 800 22: 800 23: 800 24: 800 25: 800
26: 800 27: 800 28: 800 29: 800 30: 800 31: 800 32: 800 bogomips: 191692
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD103 [GeForce RTX 4080] vendor: ASUSTeK driver: nvidia
v: 580.95.05 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-08) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ ports: active: DP-3 empty: DP-1,
DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 0000:01:00.0 chip-ID: 10de:2704
class-ID: 0300
Device-2: Elgato Systems GmbH Facecam driver: hid-generic,usbhid,uvcvideo
type: USB rev: 3.0 speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-8.2:3
chip-ID: 0fd9:0078 class-ID: 0300 serial: <filter>
Display: wayland server: X.org v: 1.21.1.20 with: Xwayland v: 24.1.9
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
display-ID: 0
Monitor-1: DP-3 model: Acer X32 FP serial: <filter> built: 2022 res:
mode: 3840x2160 hz: 160 scale: 145% (1.45) to: 2648x1490 dpi: 138 gamma: 1.2
size: 708x398mm (27.87x15.67") diag: 812mm (32") ratio: 16:9 modes:
max: 3840x2160 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast surfaceless: drv: nvidia wayland: drv: swrast x11: drv: swrast
inactive: gbm,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 25.2.6-arch1.1
glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 21.1.4 256 bits)
device-ID: ffffffff:ffffffff memory: 30.32 GiB unified: yes
display-ID: :1.0
API: Vulkan v: 1.4.328 layers: 11 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 4080 driver: nvidia v: 580.95.05
device-ID: 10de:2704 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 21.1.4 256 bits) driver: mesa llvmpipe v: 25.2.6-arch1.1 (LLVM
21.1.4) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl,nvidia-smi wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 0000:00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 0000:01:00.1 chip-ID: 10de:22bb class-ID: 0403
Device-3: SCUF Gaming Envision Pro Controller
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-11.2:9 chip-ID: 2e95:434d class-ID: 0300
serial: <filter>
Device-4: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2:2
chip-ID: 0b05:1a52 class-ID: 0300
API: ALSA v: k6.17.6-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.9 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: Intel Raptor Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 0000:00:14.3 chip-ID: 8086:7a70 class-ID: 0280
IF: wlp0s20f3 state: down mac: <filter>
Device-2: Intel Ethernet I226-V vendor: ASUSTeK driver: igc v: kernel
port: N/A bus-ID: 0000:05:00.0 chip-ID: 8086:125c class-ID: 0200
IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:11 chip-ID: 8087:0033
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.4
lmp-v: 13 status: discoverable: no pairing: no class-ID: 6c0104
RAID:
Hardware-1: Intel Volume Management Device NVMe RAID Controller Intel
driver: vmd v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:a77f rev:
class-ID: 0104
Drives:
Local Storage: total: 1.85 TiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SFYRD2000G
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK31.7 temp: 29.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: Cruzer size: 29.82 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s
lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1.26 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.05 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 36.8 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 31.05 GiB used: 5.85 GiB (18.8%)
Processes: 501 Power: uptime: 8m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.38 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1724 libs: 469 tools: octopi,paru Compilers:
gcc: 15.2.1 Shell: Bash v: 5.3.3 default: fish v: 4.1.2 running-in: konsole
inxi: 3.3.39
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.11.1-1):
System install date:     2025-12-15
Garuda release:          251103
Last full system update: 2025-12-15 ↻
Is partially upgraded:   No
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)
Relevant software:       snapper NetworkManager dracut nvidia-utils nvidia-open-dkms garuda-hardware-profile-nvidia garuda-hardware-profile-standard
Windows dual boot:       <superuser required>
Failed units:
--- System Health Check Report ---
22/25 checks run in 0.48 seconds ⌛
Powered by garuda-health 🦅

--- HIGH ---
- Snapper snapshots directory is missing (fix available)

--- INFO ---
- A reboot is pending (update applied since last reboot)

Run garuda-health --fix to apply fixes.

Sounds like an issue with the graphics stack.

Have you tried booting the live.iso with the “Boot with open source drivers” option?

3 Likes

I tried using open just now and holy hell is it 10 times worse. It took 30 minutes to get into the live media and now its ever less fps than before. Even in the live enviroment itself its unusable. before it was only while the installer app or terminal was open.

It may be an Nvidia+Wayland issue. You can try x11 instead of Wayland (it’s not preinstalled). Boot the live iso, once you’re on the desktop, open the konsole:

sudo pacman -Sy

and then:

sudo pacman -S plasma-x11-session

When that is done, close the konsole and log out (no reboot!). At the login screen, select “Plasma (x11)” as your desktop session, log back in (garuda/garuda) and check whether calamares works without issues.

If that doesn’t help, enable the UHD 770 iGPU of your i9-13900K in the BIOS, connect the monitor to the motherboard so that the iGPU is used, boot the live.iso again with open source drivers and check if it works.

5 Likes

Using x11 worked. Its no longer lagging at all. Does that mean i have to use x11 after install too?

No one can tell you that in advance. If the same issues occur after installation and after the first system update, then try x11 as described above (but then reboot after installing x11 - logout/login was only intended for the live session). And if there is a problem after installation, please open a new topic and include all necessary information, including a current garuda-inxi.

4 Likes

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