Change resolution not possible and second monitor unknowen

Hello Garuda users.

I am new to Linux and Garuda. I installed Garuda shortly.
First I installed Garuda with OSS-drivers and everything worked fine and looked well.
But Garuda wasnt starting games from Steam. So I installed nvidia drivers with the help of the setup assistent, because I have a nvidia card.

After installing nvidia drivers graphics “crashed” after reboot.
-Garuda doesnt recognize my second screen.
-My resolution is 1024x768 and I cant change it.
…and games still dont work…

:frowning:
Please help me. Thank you.

My garuda-inxi output is:

System:
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=de288c63-1ab4-4211-a8d9-66b967eec0ed rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_wayland vt: 1
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Micro-Star product: MS-7C37 v: 2.0
serial: <superuser required>
Mobo: Micro-Star model: MPG X570 GAMING PLUS (MS-7C37) v: 2.0
serial: <superuser required> UEFI: American Megatrends v: A.70
date: 01/09/2020
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 3
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Device-2: hidpp_battery_1 model: Logitech MX Keys Wireless Keyboard
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701013
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 3799 high: 3900 min/max: 2200/4559 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3600
2: 3900 3: 3802 4: 3900 5: 3900 6: 3593 7: 3900 8: 3900 9: 3900
10: 3600 11: 3900 12: 3900 13: 3598 14: 3900 15: 3900 16: 3606
bogomips: 124798
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] driver: nvidia
v: 545.29.02 alternate: nouveau,nvidia_drm non-free: 545.xx+
status: current (as of 2023-10; EOL~2026-12-xx) arch: Turing
code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 2d:00.0 chip-ID: 10de:1e84 class-ID: 0300
Device-2: WaveRider USB Live camera driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3
chip-ID: 0c46:64ab class-ID: 0102 serial: <filter>
Display: wayland server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_wayland driver: X: loaded: modesetting,nouveau,nvidia
alternate: fbdev,nv,vesa gpu: nvidia display-ID: 0
Monitor-1: Unknown-1 res: 1024x768 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia
device: 2 drv: swrast gbm: drv: kms_swrast surfaceless: drv: nvidia
wayland: drv: swrast x11: drv: swrast inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 16.0.6 256 bits)
device-ID: ffffffff:ffffffff memory: 30.55 GiB unified: yes
display-ID: :1.0
API: Vulkan v: 1.3.269 layers: 14 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 2070 SUPER driver: nvidia v: 545.29.02
device-ID: 10de:1e84 surfaces: xcb,xlib device: 1 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: xcb,xlib,wayland
Audio:
Device-1: NVIDIA TU104 HD Audio driver: snd_hda_intel v: kernel pcie:
gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 2d:00.1 chip-ID: 10de:10f8
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: WaveRider USB Live camera driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3
chip-ID: 0c46:64ab class-ID: 0102 serial: <filter>
Device-4: GN Netcom Jabra Link 370 driver: jabra,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-6:4
chip-ID: 0b0e:245d class-ID: 0300 serial: <filter>
Device-5: Plantronics Blackwire C5220 headset (remote control and
3.5mm audio adapter) driver: plantronics,snd-usb-audio,usbhid type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-2:2
chip-ID: 047f:c053 class-ID: 0300 serial: <filter>
API: ALSA v: k6.6.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.85 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 RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 2.26 TiB used: 206.68 GiB (8.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: Force MP510
size: 447.13 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: ECFM22.6
temp: 39.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 QVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
Partition:
ID-1: / raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 28.72 GiB (6.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 28.72 GiB (6.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 28.72 GiB (6.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 446.83 GiB size: 446.83 GiB (100.00%)
used: 28.72 GiB (6.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
zswap: no
ID-1: swap-1 type: zram size: 31.29 GiB used: 0 KiB (0.0%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 56.4 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 378 Uptime: 3m wakeups: 0 Memory: total: 32 GiB
available: 31.29 GiB used: 3.04 GiB (9.7%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1939 libs: 566 tools: gnome-software,octopi,pamac,paru
Shell: fish v: 3.6.1 running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2023-11-16
Last full system update: 2023-11-17
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

Have you tried a X11 session? Nvidia can have some issues with Wayland still (hopefully to get better in the coming months).
When you are logging into Garuda ( SDDM), there should be an option to change from Wayland to X11

4 Likes

Hi @n8trufe , adding to what @Kayo said, Wayland gaming is not ready yet actually due to a lot of issues , it is going to be fixed in the future , so Wayland is not ready yet use X11 instead .

2 Likes

How can I switch to this x11-Session?

You select x11 or Wayland in the login screen

2 Likes

when logging in. Lower left with it saying “desktop session”. Click that, and select X11 for your plasma session

3 Likes

in the login screen bottom left

2 Likes

For Wayland instead you could try this:

3 Likes

Ah, thanks. I didnt see that I can click on Wayland in the login. So i was confused.
But now with x11, everything seems to work properly so far.

Thank you for your Help.

2 Likes

You’re not half as confused as Wayland. If I can ever track that little sucker down, I’ll… :frowning:

You folks realize, don’t you, that Wayland, SystemD, and other modern woes can be traced to one man–Lennart Poettering! He belongs to that Red Hat terrorist organization.

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