New Dragonized install - monitors not recognized

[Witchdoctor]

Hi. Newbie here. I installed Garuda Dragonized and it does not recognize my monitors. Both displays show as Unkown-1. I have searched the forums and not found anything that looks like my exact issue. I ran garuda - inxi and see it recognizes my GPU, Nvidia GTX1080 but the 2 monitors I have it does not. When I first booted into Dragonized from my thumb drive I could see the exact name of the monitors and the resolution was fantastic. After installing I am not sure how to make the monitors display correctly. I am doing something wrong, I just don’t know what it is yet. Thank you in advance for any assistance!!

garuda-inxi 
System:
Kernel: 6.5.9-zen2-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=f6a967f8-1eaf-4f2e-8e4b-0165dd25026d 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 Mobo: MSI model: Z270-A PRO (MS-7A71) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 1.10
date: 02/03/2017
CPU:
Info: model: Intel Core i7-7700K bits: 64 type: MT MCP arch: Kaby Lake
gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 9 microcode: 0xF4
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 800 min/max: 800/4500 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 bogomips: 67200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: Gigabyte 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: 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:1b80
class-ID: 0300
Device-2: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10:4
chip-ID: 046d:082d 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: nvidia 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.57 GiB unified: yes
display-ID: :1.0
API: Vulkan v: 1.3.269 layers: 10 device: 0 type: discrete-gpu
name: NVIDIA GeForce GTX 1080 driver: nvidia v: 545.29.02
device-ID: 10de:1b80 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: Intel 200 Series PCH HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
chip-ID: 8086:a2f0 class-ID: 0403
Device-2: NVIDIA GP104 High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403
Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-10:4
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Device-4: Turtle Beach Stealth Pro Xbox
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:8 chip-ID: 10f5:2199 class-ID: 0300
serial: <filter>
API: ALSA v: k6.5.9-zen2-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.84 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 driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:3165 class-ID: 0280
IF: wlp4s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-13:7 chip-ID: 8087:0a2a
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 4.2
lmp-v: 8 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 6.6 TiB used: 14.59 GiB (0.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKKW256G7
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: PSF109C temp: 48.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA200
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: ABB0 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Toshiba model: HDWE140 size: 3.64 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD
rpm: 7200 serial: <filter> fw-rev: FP1R scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B6Q scheme: GPT
Partition:
ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 14.59 GiB (1.6%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 580 KiB (0.2%) fs: vfat dev: /dev/sdc1 maj-min: 8:33
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 14.59 GiB (1.6%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 14.59 GiB (1.6%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
used: 14.59 GiB (1.6%) fs: btrfs dev: /dev/sdc2 maj-min: 8:34
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.31 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 70.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 244 Uptime: 17m wakeups: 0 Memory: total: 32 GiB
available: 31.31 GiB used: 2.59 GiB (8.3%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1853 libs: 532 tools: octopi,paru Shell: fish v: 3.6.1
running-in: konsole inxi: 3.3.31
Garuda (2.6.17-1):
System install date:     2023-11-05
Last full system update: 2023-11-06
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

[filo]

@Witchdoctor

wm: kwin_wayland

First of all, try logging in an x11 session to see if you have the same problem there.
For Wayland, try adding this kernel boot parameter:

Incorrect Graphics driver - llvmpipe

Finally got it to work following steps 1 -3 of this guide here How to Get Wayland to Work on Nvidia Graphics Cards - Make Tech Easier 3. Enable Direct Rendering Manager Linux’s Direct Rendering Manager (DRM) allows the kernel to work with GPUs. For Nvidia and Wayland to get along, we have to make sure that the kernel uses Nvidia’s DRM mode setting within your bootloader’s kernel parameters: Edit your default GRUB configuration (again, always ensure a backup exists): sudo nano /etc/default/g…

[elite]

@Witchdoctor

glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 16.0.6 256 bits)

I would definitely add the kernel boot parameter and restart. It should help.

[Witchdoctor]

I must say… holy … crap! The desktop looks soooo much better when its not all blown up.

Ok choosing x11 did do the trick there. (Side note: I had to google what that meant, log into an x11 session. As I suspected it was super simple).

Do I need to do the llvmpipe thing next as you guys suggested still? I can go jump into that next no problem. I am not sure if I should be using Wayland or x11 login.

Thank you so much!!!

man this is so much easier on the eyes now.

[filo]

I suggest you should try adding that kernel boot parameter in the linked post (use garuda boot options, much easier ) and try again with Wayland.
There is still no universal answer to which one is better. It is too much HW/system dependant.
Just try and make your own decision.

[Witchdoctor]

Thank you so so much!!

It sounds like its a personal preference thing. I was not sure. Everything I am presented with at this time from the OS is all new to me… so I am like a kid in a candy shop.

I will give the linked post a go!