Garuda installation stucks on Wayland session

Hi there, Garuda folks!

I was planning to try Garuda (with Qtile), but unfortunately, I failed to install it.
I downloaded the latest ISO and initiated the installation, but after entering the password into the login manager, my installation got stuck at "Reached target Graphical Interface".
Ctrl-Alt-F2 does not work, so I'm unable to run anything and have no idea what to do in this situation.
Apologies for the attached photo, and thank you in advance for your help.

p.s. I was going to attach a photo, but new users can't do it... so the last 5 lines are:
[ OK ] Finished Hold until boot process finishes up.
[ OK ] Finished Terminate Plymouth Boot Screen.
[ OK ] Reached target Multi-User System.
[ OK ] Started Simple Desktop Display Manager.
[ OK ] Reached target Graphical Interface.

p.p.s it's not an nvidia issue (as Google suggests me), I have an AMD gpu

Welcome :slight_smile:

Please, can you post your garuda-inxi from live ISO?
Did you use the free driver from settings if live ISO start?

4 Likes

This has happened to me a few times in the past when trying to use the live USB. Make sure to try multiple times and if you manage to get to sddm, ensure you don't choose the Wayland session, as it doesn't work (yet). Make sure to choose the default session, not Wayland.

If you can't get the garuda-inxi on the Qtile version, try the dr460nized live ISO. That one boots normally for me most of the time - not sure what it is about the Qtile one but it likes to get stuck sometimes.

Welcome btw :smiley:

1 Like

Sure, here is the garuda-inxi output Garuda's PrivateBin
I've tried both free and proprietary drivers, but the issue persists with both of themsame

Nice, chroot and install other kernel.

System:
  Kernel: 6.2.13-zen-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_AU keytable=us tz=Europe/Athens
    misobasedir=garuda root=miso:LABEL=GARUDA_QTILE_RAPTOR quiet systemd.show_status=1 ibt=off
    systemd.unified_cgroup_hierarchy=1 driver=free nouveau.modeset=1 i915.modeset=1
    radeon.modeset=1
  Console: tty 2 DM: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: MPG X670E CARBON WIFI (MS-7D70) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 1.60 date: 03/24/2023
CPU:
  Info: model: AMD Ryzen 9 7950X bits: 64 type: MT MCP arch: Zen 4 gen: 5 level: v4 note: check
    built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x61 (97) stepping: 2
    microcode: 0xA601203
  Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache: L1: 1024 KiB desc: d-16x32
    KiB; i-16x32 KiB L2: 16 MiB desc: 16x1024 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 3160 high: 4500 min/max: 3000/5880 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 4500 2: 3000 3: 3623 4: 3000 5: 3000 6: 3000
    7: 3000 8: 3000 9: 3000 10: 4500 11: 4500 12: 3000 13: 3000 14: 3000 15: 3000 16: 3000
    17: 3000 18: 3000 19: 3000 20: 3000 21: 3000 22: 3000 23: 3000 24: 3000 25: 3000 26: 3000
    27: 3000 28: 3000 29: 3000 30: 3000 31: 3000 32: 3000 bogomips: 288027
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX] vendor: Gigabyte driver: amdgpu v: kernel
    arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: DP-1 empty: DP-2,HDMI-A-1,HDMI-A-2 bus-ID: 03:00.0 chip-ID: 1002:744c
    class-ID: 0300
  Device-2: AMD Raphael vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: none empty: DP-3, DP-4, DP-5, HDMI-A-3 bus-ID: 19:00.0 chip-ID: 1002:164e
    class-ID: 0300 temp: 44.0 C
  Display: server: X.org v: 1.21.1.8 driver: X: loaded: amdgpu unloaded: modesetting,radeon
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu tty: 384x108
  Monitor-1: DP-1 model: Dell U2723QE serial: <filter> built: 2022 res: 3840x2160 dpi: 163
    gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes: max: 3840x2160
    min: 720x400
  API: OpenGL Message: GL data unavailable in console and glxinfo missing.
Audio:
  Device-1: AMD driver: snd_hda_intel v: kernel bus-ID: 3-4:5 pcie: chip-ID: 03f0:078b gen: 4
    class-ID: 0300 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab30 class-ID: 0403
  Device-2: AMD Rembrandt Radeon High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 19:00.1
    chip-ID: 1002:1640 class-ID: 0403
  Device-3: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 19:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Device-4: HP HyperX SoloCast type: USB driver: hid-generic,snd-usb-audio,usbhid
  Device-5: Micro Star USB Audio type: USB driver: hid-generic,snd-usb-audio,usbhid
    bus-ID: 3-9:7 chip-ID: 0db0:d6e7 class-ID: 0300
  API: ALSA v: k6.2.13-zen-1-zen status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.70 status: off with: 1: pipewire-pulse status: off 2: wireplumber
    status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 0f:00.0 chip-ID: 14c3:0616 class-ID: 0280
  IF: wlp15s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 port: e000 bus-ID: 10:00.0 chip-ID: 10ec:8125 class-ID: 0200
  IF: enp16s0 state: down mac: <filter>
Bluetooth:
  Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 3-8:6
    chip-ID: 0e8d:0616 class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 2.74 TiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:5 vendor: Western Digital model: WD BLACK SN850X 1000GB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 620311WD temp: 48.9 C
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 1B2QJXD7 temp: 47.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB model: USB DISK 3.0 size: 14.46 GiB block-size:
    physical: 512 B logical: 512 B type: N/A serial: <filter> rev: PMAP 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)
  ID-1: swap-1 type: zram size: 61.96 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 48.2 C mobo: N/A
  Fan Speeds (RPM): N/A
  GPU: device: amdgpu temp: 44.0 C device: amdgpu temp: 49.0 C mem: 56.0 C fan: 12 watts: 18.00
Info:
  Processes: 480 Uptime: 3m wakeups: 0 Memory: 61.96 GiB used: 2.23 GiB (3.6%) Init: systemd
  v: 253 default: graphical tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1122
  libs: 323 tools: pamac,paru Shell: Bash v: 5.1.16 running-in: tty 2 inxi: 3.3.26
Garuda (2.6.16-1):
  System install date:     2023-06-22
  Last full system update: 2023-06-22 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       <superuser required>
  Failed units:            
1 Like

Thank you so much. I've never used login screens or SDDM before, and this thing looked so appealing that I didn't even notice the different sessions are available to choose from.
However, it's disappointing that Wayland isn't supported yet, as that's the main reason I wanted to try Qtile.

I've just tested it with Xorg, and the issue disappeared. If there's a way to initiate a Wayland session though, I'd be keen to give it a try

1 Like

Please forgive me if this question seems simple, but I'm still learning about Linux. If I use Xorg for a while to experiment with (or even grow accustomed to) Garuda and Qtile, would I be able to easily switch to Wayland later on (when it's operational) just by changing the session in SDDM? Or would this constitute a major change requiring most packages/system to be reinstalled?

Later on you can just simply select Wayland, no need to reinstall anything.

2 Likes

Good to know

Thank you all for help, folks

1 Like

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