I’m new to Linux and have decided to dual boot garuda. I have gone through the installation and everything seemed fine.
However when boot into garuda I cannot login through the gui. It almost looks like it accepts my login info but redirects back.
I am able to login through terminal which I can access using ctrl + alt + f2.
Could this be an issue with graphics drivers?
When I booted off the USB installer. I was not able to boot via nvidia drivers I had to boot with open source drivers, despite having an nvidia card.
Does anyone have any idea what my next step is to get the GUI working?
I am unable to provide my garuda-inxi output as I cannot access the browser from the terminal in my linux instance. If you know how I can copy that out here please let me know.
This command should generate a URL to share the output:
garuda-inxi | nc termbin.com 9999
Thanks Kayo! Output is as follows:
Kernel: 6.6.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc
available: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=8a012afb-5d5c-4505-9a7c-08a66184433a rw rootflags=subvol=@ quiet loglevel=3 ibt=off
Console: tty 3 DM: SDDM Distro: Garuda Linux base: Arch Linux
Type: Desktop Mobo: BIOSTAR model: Z270GTN serial: <superuser required>
UEFI: American Megatrends v: 5.12 date: 02/23/2017
Info: model: Intel Core i5-7600K bits: 64 type: MCP arch: Kaby Lake gen: core 7 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 865 high: 960 min/max: 800/4200 scaling: driver: intel_pstate
governor: powersave cores: 1: 960 2: 800 3: 900 4: 800 bogomips: 30399
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: ZOTAC driver: N/A alternate: nouveau
non-free: 545.xx+ status: current (as of 2023-10; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3
speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1b81 class-ID: 0300
Display: server: X.org v: 184.108.40.206 with: Xwayland v: 23.2.2 driver: X:
loaded: modesetting,nouveau alternate: fbdev,nv,vesa gpu: N/A tty: 102x38
Monitor-1: Unknown-1 size-res: N/A in console modes: 1024x768
API: Vulkan v: 1.3.269 layers: 4 device: 0 type: cpu name: llvmpipe (LLVM 16.0.6 256 bits)
driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM 16.0.6) device-ID: 10005:0000 surfaces: N/A
API: OpenGL Message: GL data unavailable in console, glxinfo missing.
Device-1: Intel 200 Series PCH HD Audio vendor: Biostar Microtech Intl Corp
driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a2f0
Device-2: NVIDIA GP104 High Definition Audio vendor: ZOTAC driver: snd_hda_intel v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
chip-ID: 10de:10f0 class-ID: 0403
Device-3: SteelSeries ApS Arctis 7 driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-5:5 chip-ID: 1038:12ad class-ID: 0300
Device-4: Creative Pebble V3 driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9:7 chip-ID: 041e:3272 class-ID: 0300
API: ALSA v: k6.6.1-zen1-1-zen status: kernel-api tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.85 status: off with: 1: pipewire-pulse status: off 2: wireplumber
status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Device-1: Intel Ethernet I219-V vendor: Biostar Microtech Intl Corp driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Local Storage: total: 2.96 TiB used: 8.32 GiB (0.3%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD BLACK SN850X 2000GB
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: 620311WD temp: 40.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST31000524AS size: 931.51 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter> fw-rev: JC4B
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter>
fw-rev: 1B6Q scheme: GPT
ID-1: / raw-size: 100 GiB size: 100 GiB (100.00%) used: 8.29 GiB (8.3%) fs: btrfs dev: /dev/sda2
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 25.9 MiB (26.9%) fs: vfat
dev: /dev/sdb2 maj-min: 8:18
ID-3: /home raw-size: 100 GiB size: 100 GiB (100.00%) used: 8.29 GiB (8.3%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 100 GiB size: 100 GiB (100.00%) used: 8.29 GiB (8.3%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 100 GiB size: 100 GiB (100.00%) used: 8.29 GiB (8.3%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.46 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
System Temperatures: cpu: 40.0 C mobo: N/A
Fan Speeds (rpm): N/A
Processes: 151 Uptime: 1m wakeups: 0 Memory: total: 16 GiB note: est. available: 15.46 GiB
used: 658.5 MiB (4.2%) Init: systemd v: 254 default: graphical tool: systemctl Compilers:
gcc: 13.2.1 Packages: pm: pacman pkgs: 1199 libs: 355 tools: paru Shell: Bash v: 5.2.15
running-in: tty 3 inxi: 3.3.31
System install date: 2023-11-17
Last full system update: 2023-11-17
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: Probably (Run as root to verify)
Yes, please read
Follow the manual, it works.
Thanks SGS. I actually did stumble upon that page in my investigation.
Its quite late here now so I’ll take a crack at it tomorrow and update then.
I gave it a crack. Things looked promising on boot after following everything outlined in the article.
I also stopped seeing errors starting the vconsole service but I still receive a black screen for a few screens and then land back on the login screen when I login through GUI
I probably couldn’t help you either if you told me exactly what you did.
Maybe there are some Nvidia GPU’s that wayland doesn’t like?
Can you log in via TTY3?
chroot via live ISO?
Sometimes corrupt download makes problems too, remove safely the stick after copying.
CPU has integrated GPU?
Did you install with free drivers, too?
I gave it a crack
That guide describes enabling kernel mode setting with mkinitcpio, but Garuda is configured to use dracut instead. If you installed mkinitcpio while trying to set this up, you should remove it because it can introduce conflicts.
The way to enable kernel mode setting with dracut is described here:
Early kernel module loading
Dracut enables early loading (at the initramfs stage, via
modprobe) through it’s
--force_drivers command or
force_drivers+="" config entry line. For example:
force_drivers+=" nvidia nvidia_modeset nvidia_uvm nvidia_drm "
Be sure to keep those “padding” spaces (next to the quotes) when you set up the config file.
Then, regenerate the initramfs.
So I was able to login to the live session via open source drivers (Nvidia didn’t work for live session) but I don’t think their was an open to choose which drivers to install with. I guess I could try install the open source drivers for now to get the GUI working and then tackle the Nvidia drivers later.
Thanks Bluish, I did notice that mkinitcpio was not being used during the process and modified the dracut config. So I think I did that correctly.
I knew this was for advanced users when getting into it and I appreciate the help, at least I know its the gpu drivers as I just wanted to make sure I was tackling the right thing.
Thanks for all your help. I’ll reach out if I run into something else or update this post if I manage to get it sorted. I might just jump to one of the other distros and see if I can get the GUI working there in the meantime