I can't get my external moniter to work

Hello everyone,
This is my first time every using linux, everything was going well and i just installed garuda dragonized, during installation my moniter was working fine with proprietary drivers, but after installation it just wouldn’t work
PS, i am using an acer nitro 5 laptop with an external moniter, screen works fine

System:
Kernel: 6.6.2-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=b5c7108d-4efe-4d3a-a3c0-e1f0a940d572 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: Laptop System: Acer product: Nitro AN515-53 v: V1.28
serial: <superuser required>
Mobo: CFL model: Freed_CFS v: V1.28 serial: <superuser required>
UEFI: Insyde v: 1.28 date: 08/05/2019
Battery:
ID-1: BAT1 charge: 44.7 Wh (100.0%) condition: 44.7/48.9 Wh (91.4%)
volts: 17.0 min: 15.2 model: LG PABAS0241231 type: Li-ion serial: <filter>
status: full
CPU:
Info: model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Coffee Lake
gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF4
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 9 MiB desc: 1x9 MiB
Speed (MHz): avg: 888 high: 900 min/max: 800/4100 scaling:
driver: intel_pstate governor: powersave cores: 1: 900 2: 801 3: 900 4: 861
5: 896 6: 900 7: 900 8: 900 9: 900 10: 900 11: 900 12: 900 bogomips: 52799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630]
vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: none
bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile]
vendor: Acer Incorporated ALI 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:1c8d class-ID: 0300
Device-3: Realtek HD WebCam driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:8 chip-ID: 0bda:5621
class-ID: 0e02 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,nvidia
unloaded: nouveau alternate: fbdev,intel,nv,vesa dri: iris
gpu: i915,nvidia display-ID: 0
Monitor-1: eDP-1 res: 1536x864 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
drv: nvidia device: 1 drv: iris device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
inactive: device-2
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
GT2) device-ID: 8086:3e9b memory: 15.1 GiB unified: yes display-ID: :1.0
API: Vulkan v: 1.3.269 layers: 14 device: 0 type: integrated-gpu
name: Intel UHD Graphics 630 (CFL GT2) driver: mesa intel v: 23.2.1-arch1.2
device-ID: 8086:3e9b surfaces: xcb,xlib,wayland device: 1
type: discrete-gpu name: NVIDIA GeForce GTX 1050 driver: nvidia
v: 545.29.02 device-ID: 10de:1c8d surfaces: xcb,xlib,wayland device: 2
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 Cannon Lake PCH cAVS vendor: Acer Incorporated ALI
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA GP107GL High Definition Audio
vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403
Device-3: HP HyperX SoloCast driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:3
chip-ID: 03f0:078b class-ID: 0300
Device-4: Kingston HyperX Cloud Alpha S
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-3:5 chip-ID: 0951:16ed class-ID: 0300
serial: <filter>
API: ALSA v: k6.6.2-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: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 07:00.1 chip-ID: 10ec:8168
class-ID: 0200
IF: enp7s0f1 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:9
chip-ID: 8087:0aaa class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.1
lmp-v: 10 status: discoverable: no pairing: no class-ID: 7c010c
Device-2: SINO WEALTH Bluetooth Keyboard driver: hid-generic,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:7
chip-ID: 258a:00e1 class-ID: 0300
Drives:
Local Storage: total: 1.82 TiB used: 22.29 GiB (1.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S2000G
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: SBM02103 temp: 43.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 1.82 TiB size: 1.82 TiB (100.00%) used: 22.29 GiB (1.2%)
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: 1.82 TiB size: 1.82 TiB (100.00%)
used: 22.29 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 22.29 GiB (1.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
used: 22.29 GiB (1.2%) 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: 15.46 GiB used: 1024 KiB (0.0%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 60.0 C pch: 69.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Processes: 324 Uptime: 11m wakeups: 0 Memory: total: 16 GiB
available: 15.46 GiB used: 4.9 GiB (31.7%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 1979 libs: 570 tools: octopi,paru Shell: fish
v: 3.6.1 running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2023-11-22
Last full system update: 2023-11-22
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

Either use x11 in the login screen instead of Wayland or use the following kernel boot parameter:
nvidia-drm.modeset=1
With

sudo cp /etc/default/grub /etc/default/grub.bak && sudo sed '/^GRUB_CMDLINE_LINUX_DEFAULT=/s/"$/ nvidia-drm.modeset=1 "/g' -i /etc/default/grub && sudo update-grub
5 Likes

i typed in the command prompt, should i reboot?

You typed the one liner, right?
So, yes, you should reboot and leave Wayland in the login screen.
If it doesn’t work, logoff and on again, this time selecting plasma (x11) at login.

4 Likes

Interesting, switching to X11 fixed it, thank you so much for your help, i really want to get into linux but i didn’t know where to start. thank you again and have a good day / night

1 Like

#1 Rule - stay away from Wayland in KDE.
#2 Rule - see #1 Rule.

The Wayland protocol originated in Red Hat-owned Fedora with GNOME and is slowly bleeding into other desktop environments and other distributions. For right now, Wayland is supposed to work pretty well in GNOME (in non Arch-based distributions), but not so much KDE.

It’s easy to boot into Wayland by mistake. At first you think it’s fine, but then you start noticing little differences and things seem odd, like you’re kicking off on an acid trip. Then you start to believe KDE hates you so, no, it must be 'shrooms!

That what KDE in Wayland feels like. Not very pleasant. :frowning:

4 Likes

Also, I’d bet there may be a more current BIOS update available than 2019 for your machine. BIOS concern hardware and are frequently updated to do so. :slight_smile:

3 Likes

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