[SOLVED] hdmi output not working on kde wayland (nvidia gpu)

karemkassem · 2024-01-11 09:41:22

Hello,
I have been using arch linux for about four months now, but I haven't been able to solve the problem with getting the hdmi from my laptop to work properly on wayland on kde, I currently use x11 for this and I would love to make a full switch to wayland.

my laptop has an rtx-3050ti and I beleive that the problem stems from the fact that the hdmi port is connected directly to the gpu ( I tried usb to hdmi and it worked but used cpu graphics )

I'm running kde plasma and have followed this https://community.kde.org/Plasma/Wayland/Nvidia tutorial, and it did give me an output but it didn't use the gpu and was unusably laggy and buggy.
I have tried a lot of things but non solve my problem.
this is my first time asking something on the arch wiki and I'm really hoping you can help me.
thank you

Last edited by karemkassem (2024-01-15 13:01:18)

V1del · 2024-01-11 10:28:15

Just because things were laggy doesn't mean your GPU wasn't used and the things mentioned in that link you posted are a basic precondition to set up and non negotiable. This particular case is generally a bit special and chances are things are going to improve with newer nvidia drivers/Plasma 6 but this is generally potentially "expected".

FWIW one thing that was often an issue was a hardware cursor with an external monitor, you can try creating ~/.config/plasma-workspace/env/kwin_vars.sh

!#/bin/sh
export KWIN_FORCE_SW_CURSOR=1

set execute permissions and reboot/restart plasma.

If that didn't help, set things up to be "working but laggy" and post

sudo journalctl -b

https://wiki.archlinux.org/title/List_o … n_services

karemkassem · 2024-01-12 12:48:03

thanks for the reply V1del

Just because things were laggy doesn't mean your GPU wasn't used

the reason why I said that the gpu wasn't used is because in the system monitor and also in the nvidia settings the gpu usage was at 0% all the time unless I used prime-run on an application.

one more thing I forgot to mention is that in wayland session the nvidia settings don't give the same settings as in x11 ( for example it doesn't give me the powermizer setting ) I don't know if this helps.

 sudo journalctl -b

when I ran it in the terminal it gave a really long output (over 1000 lines), I'm not sure how much of it is needed, if you can tell me what of it you require I will reply with another reply.

 !#/bin/sh
export KWIN_FORCE_SW_CURSOR=1

I have tried this before, but I will try it again and post the result.

and once again
thank you

karemkassem · 2024-01-12 13:21:31

I've tried

!#/bin/sh
export KWIN_FORCE_SW_CURSOR=1

but unfortunately it didn't help

Note: I did exactly what V1del specified, I created ~/.config/plasma-workspace/env/kwin_vars.sh , and inputed into that file what is in the code block and then set execute permission via chmod +x, and then rebooted the system and tried it again.
also to add on what I said previously the gpu usage is at 0% , and also the gpu memory that is use is 2mb ( which is equal to when the gpu is not in use )

seth · 2024-01-12 14:00:43

The plan was to post the journal.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

And since you're currently using X11, please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General for an oversight on the output configuration.
nb. the caveats of https://wiki.archlinux.org/title/PRIME#Reverse_PRIME - they might apply likewise. You're eDP is active all the time?

karemkassem · 2024-01-12 14:18:04

the output for this command

sudo journalctl -b | curl -F 'file=@-' 0x0.st

is : output_url_link
I hope that this is what you meant you needed.

I am not really sure what you meant by eDP (and if you can explain further that would be appreciated ) but I will try to answer it in different contexts:
1- my laptop is on during the day and off during the night
2- my laptop screen is always on when I'm using an external display
3- I connect to the external display most of the times ( I need it for studying and coding for college)

for the xorg log:

[    35.794] (--) Log file renamed from "/var/log/Xorg.pid-1328.log" to "/var/log/Xorg.0.log"
[    35.795] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 12 16:00:17 2024
[    35.797] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    36.521] (II) config/udev: Adding input device Logitech MX Master 3 (/dev/input/event18)
[    36.521] (**) Logitech MX Master 3: Applying InputClass "libinput pointer catchall"
[    36.521] (**) Logitech MX Master 3: Applying InputClass "libinput keyboard catchall"
[    36.521] (**) Logitech MX Master 3: Applying InputClass "system-keyboard"
[    36.521] (II) Using input driver 'libinput' for 'Logitech MX Master 3'
[    36.521] (**) Logitech MX Master 3: always reports core events
[    36.523] (II) event18 - Logitech MX Master 3: is tagged by udev as: Keyboard Mouse
[    36.523] (II) event18 - Logitech MX Master 3: device is a pointer
[    36.523] (II) event18 - Logitech MX Master 3: device is a keyboard
[    36.523] (II) event18 - Logitech MX Master 3: device removed
[    36.547] (II) libinput: Logitech MX Master 3: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.547] (II) libinput: Logitech MX Master 3: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.547] (II) libinput: Logitech MX Master 3: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.547] (II) libinput: Logitech MX Master 3: needs a virtual subdevice
[    36.547] (II) XINPUT: Adding extended input device "Logitech MX Master 3" (type: MOUSE, id 10)
[    36.548] (**) Logitech MX Master 3: (accel) selected scheme none/0
[    36.548] (**) Logitech MX Master 3: (accel) acceleration factor: 2.000
[    36.548] (**) Logitech MX Master 3: (accel) acceleration threshold: 4
[    36.551] (II) event18 - Logitech MX Master 3: is tagged by udev as: Keyboard Mouse
[    36.552] (II) event18 - Logitech MX Master 3: device is a pointer
[    36.552] (II) event18 - Logitech MX Master 3: device is a keyboard
[    36.554] (II) config/udev: Adding input device Logitech MX Master 3 (/dev/input/mouse0)
[    36.554] (**) Logitech MX Master 3: Applying InputClass "system-keyboard"
[    36.555] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event10)
[    36.555] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
[    36.555] (**) Logitech USB Receiver: Applying InputClass "system-keyboard"
[    36.555] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
[    36.555] (**) Logitech USB Receiver: always reports core events
[    36.556] (II) event10 - Logitech USB Receiver: is tagged by udev as: Keyboard
[    36.556] (II) event10 - Logitech USB Receiver: device is a keyboard
[    36.556] (II) event10 - Logitech USB Receiver: device removed
[    36.587] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 11)
[    36.591] (II) event10 - Logitech USB Receiver: is tagged by udev as: Keyboard
[    36.591] (II) event10 - Logitech USB Receiver: device is a keyboard
[    36.593] (II) config/udev: Adding input device Logitech USB Receiver Mouse (/dev/input/event11)
[    36.593] (**) Logitech USB Receiver Mouse: Applying InputClass "libinput pointer catchall"
[    36.593] (II) Using input driver 'libinput' for 'Logitech USB Receiver Mouse'
[    36.593] (**) Logitech USB Receiver Mouse: always reports core events
[    36.595] (II) event11 - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[    36.595] (II) event11 - Logitech USB Receiver Mouse: device is a pointer
[    36.595] (II) event11 - Logitech USB Receiver Mouse: device removed
[    36.653] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.653] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.653] (II) libinput: Logitech USB Receiver Mouse: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.653] (II) XINPUT: Adding extended input device "Logitech USB Receiver Mouse" (type: MOUSE, id 12)
[    36.654] (**) Logitech USB Receiver Mouse: (accel) selected scheme none/0
[    36.654] (**) Logitech USB Receiver Mouse: (accel) acceleration factor: 2.000
[    36.654] (**) Logitech USB Receiver Mouse: (accel) acceleration threshold: 4
[    36.657] (II) event11 - Logitech USB Receiver Mouse: is tagged by udev as: Mouse
[    36.658] (II) event11 - Logitech USB Receiver Mouse: device is a pointer
[    36.659] (II) config/udev: Adding input device Logitech USB Receiver Mouse (/dev/input/mouse1)
[    36.660] (II) config/udev: Adding input device Logitech USB Receiver Consumer Control (/dev/input/event12)
[    36.660] (**) Logitech USB Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[    36.660] (**) Logitech USB Receiver Consumer Control: Applying InputClass "system-keyboard"
[    36.660] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control'
[    36.660] (**) Logitech USB Receiver Consumer Control: always reports core events
[    36.662] (II) event12 - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[    36.662] (II) event12 - Logitech USB Receiver Consumer Control: device is a keyboard
[    36.662] (II) event12 - Logitech USB Receiver Consumer Control: device removed
[    36.683] (II) libinput: Logitech USB Receiver Consumer Control: needs a virtual subdevice
[    36.684] (II) XINPUT: Adding extended input device "Logitech USB Receiver Consumer Control" (type: MOUSE, id 13)
[    36.684] (**) Logitech USB Receiver Consumer Control: (accel) selected scheme none/0
[    36.684] (**) Logitech USB Receiver Consumer Control: (accel) acceleration factor: 2.000
[    36.684] (**) Logitech USB Receiver Consumer Control: (accel) acceleration threshold: 4
[    36.687] (II) event12 - Logitech USB Receiver Consumer Control: is tagged by udev as: Keyboard
[    36.688] (II) event12 - Logitech USB Receiver Consumer Control: device is a keyboard
[    36.689] (II) config/udev: Adding input device Logitech USB Receiver System Control (/dev/input/event15)
[    36.689] (**) Logitech USB Receiver System Control: Applying InputClass "libinput keyboard catchall"
[    36.689] (**) Logitech USB Receiver System Control: Applying InputClass "system-keyboard"
[    36.689] (II) Using input driver 'libinput' for 'Logitech USB Receiver System Control'
[    36.689] (**) Logitech USB Receiver System Control: always reports core events
[    36.691] (II) event15 - Logitech USB Receiver System Control: is tagged by udev as: Keyboard
[    36.691] (II) event15 - Logitech USB Receiver System Control: device is a keyboard
[    36.691] (II) event15 - Logitech USB Receiver System Control: device removed
[    36.710] (II) XINPUT: Adding extended input device "Logitech USB Receiver System Control" (type: KEYBOARD, id 14)
[    36.714] (II) event15 - Logitech USB Receiver System Control: is tagged by udev as: Keyboard
[    36.714] (II) event15 - Logitech USB Receiver System Control: device is a keyboard
[    36.920] (**) Logitech MX Master 3: Applying InputClass "libinput pointer catchall"
[    36.920] (**) Logitech MX Master 3: Applying InputClass "libinput keyboard catchall"
[    36.920] (**) Logitech MX Master 3: Applying InputClass "system-keyboard"
[    36.920] (II) Using input driver 'libinput' for 'Logitech MX Master 3'
[    36.920] (**) Logitech MX Master 3: always reports core events
[    36.920] (II) libinput: Logitech MX Master 3: is a virtual subdevice
[    36.920] (II) libinput: Logitech MX Master 3: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.920] (II) libinput: Logitech MX Master 3: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.920] (II) libinput: Logitech MX Master 3: Step value 0 was provided, libinput Fallback acceleration function is used.
[    36.920] (II) XINPUT: Adding extended input device "Logitech MX Master 3" (type: KEYBOARD, id 19)
[    36.921] (**) Logitech USB Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[    36.921] (**) Logitech USB Receiver Consumer Control: Applying InputClass "system-keyboard"
[    36.921] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control'
[    36.921] (**) Logitech USB Receiver Consumer Control: always reports core events
[    36.921] (II) libinput: Logitech USB Receiver Consumer Control: is a virtual subdevice
[    36.921] (II) XINPUT: Adding extended input device "Logitech USB Receiver Consumer Control" (type: KEYBOARD, id 20)

thank you

Last edited by karemkassem (2024-01-12 14:19:20)

seth · 2024-01-12 14:36:44

I am not really sure what you meant by eDP

2- my laptop screen is always on when I'm using an external display

That's not your xorg log.

cat /var/log/Xorg.0.log | curl -F 'file=@-' 0x0.st

Jan 12 15:59:44 archlinux kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0

Enable https://wiki.archlinux.org/title/NVIDIA … de_setting (add "nvidia_drm.modeset=1" to the kernel parameters, do not set fbdev=1 for now)

karemkassem · 2024-01-12 14:52:30

(add "nvidia_drm.modeset=1" to the kernel parameters, do not set fbdev=1 for now)

I have done that, unfortunately it hasn't made a difference

cat /var/log/Xorg.0.log | curl -F 'file=@-' 0x0.st

output_link

seth · 2024-01-12 14:58:33

I have done that

Not according to the xorg log - it might be the cause of the missing edid:

[   133.377] (WW) NVIDIA(G0): Cannot find size of first mode for LG Electronics LG ULTRAFINE
[   133.377] (WW) NVIDIA(G0):     (DFP-0); cannot compute DPI from LG Electronics LG
[   133.377] (WW) NVIDIA(G0):     ULTRAFINE (DFP-0)'s EDID.

Edit: for clarification, your kernel commandline is in the log, I'm not speculating the failure to set that parameter based on the missing edid or something like that.
I just suspect that the missing setting also leads to the missing edid and w/o the output information to syncing problems.

Last edited by seth (2024-01-12 15:00:12)

karemkassem · 2024-01-12 15:02:50

what I did is create a file (and called it nvidia.conf) in the directory /etc/modprobe.d/ so at the end we get /etc/modprobe.d/nvidia.conf.
and in the file I added the parameter with the syntax :

options nvidia_drm modeset=1

and then rebooted my system

is there a different way that I need to do it in?

V1del · 2024-01-12 15:11:42

Don't create the file but set up the kernel parameter "nvidia-drm.modeset=1" on the kernel commandline (the kernel commandline currently has a side effect to disable a software device in the kernel that can lead to issues) https://wiki.archlinux.org/title/Kernel_parameters

karemkassem · 2024-01-12 15:34:22

set up the kernel parameter "nvidia-drm.modeset=1" on the kernel commandline

I did this, but it is the same thing as before , I get an output but the gpu isn't being use ( the gpu usage is still at 0% and the experience is still very laggy)

cat /var/log/Xorg.0.log | curl -F 'file=@-' 0x0.st

output_link
thank you

seth · 2024-01-12 15:50:14

I get an output but the gpu isn't being use

That's not possible, you're not rendering on the GPU, but w/o prime-run, you don't on X11 either.
The GPU must be active because it's where the output is wired.

Do you have another monitor to test?
What's the exact model of your monitor?
Can you get the edid w/

edid-decode /sys/class/drm/card*HDMI*/edid

?

Does the wayland output btw. also lag on the internal display?
On wayland run and post the output of

qdbus org.kde.KWin /KWin supportInformation

karemkassem · 2024-01-12 16:06:16

Do you have another monitor to test?

I tested on a tv before and I got the same result though I will try to try it on another monitor

the monitor is an LG ultrafine , it's model number : 27UP650

Does the wayland output btw. also lag on the internal display?

NO it doesn't lag on the internal display it is running smoothly and at 120 hz. I forgot to mention it.

this is the output of the command below

KWin Support Information:
The following information should be used when requesting support on e.g. https://forum.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like https://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 5.27.10
Qt Version: 5.15.12
Qt compile version: 5.15.12
XCB compile version: 1.16

Operation Mode: Xwayland

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12302003
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.breeze
Theme: 
Plugin recommends border size: None
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,5,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==============
Name: DRM
Active: true
Atomic Mode Setting on GPU 0: true
Atomic Mode Setting on GPU 1: true

Cursor
======
themeName: Adwaita
themeSize: 24

Options
=======
focusPolicy: 0
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 28
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: false
glStrictBindingFollowsDriver: true
glPreferBufferSwap: 101
glPlatformInterface: 2
windowsBlockCompositing: true
latencyPolicy: 
renderTimeEstimator: 
allowTearing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
---------
Name: eDP-1
Enabled: 1
Geometry: 0,360,1920x1080
Scale: 1.5
Refresh Rate: 60001
Adaptive Sync: incapable
Screen 1:
---------
Name: HDMI-A-1
Enabled: 1
Geometry: 1920,0,2560x1440
Scale: 1.5
Refresh Rate: 60000
Adaptive Sync: incapable

Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)
OpenGL version string: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL platform interface: EGL
OpenGL shading language version string: 4.60
Driver: Intel
GPU class: Unknown
OpenGL version: 4.6
GLSL version: 4.60
Mesa version: 23.3.2
Linux kernel version: 6.6.10
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---------------
colorpicker
outputlocator
magnifier
screenshot
screenedge
blur
contrast
kwin4_effect_sessionquit
kwin4_effect_logout
kwin4_effect_login
slidingpopups
kwin4_effect_windowaperture
slide
kwin4_effect_squash
kwin4_effect_morphingpopups
kwin4_effect_maximize
kwin4_effect_fullscreen
kwin4_effect_frozenapp
kwin4_effect_fadingpopups
kwin4_effect_fade
kwin4_effect_dialogparent
desktopgrid
highlightwindow
overview
tileseditor
windowview
blendchanges
startupfeedback
kscreen
screentransform

Currently Active Effects:
-------------------------
blur
contrast

Effect Settings:
----------------
colorpicker:

outputlocator:

magnifier:
magnifierSize: 
targetZoom: 1

screenshot:

screenedge:

blur:

contrast:

kwin4_effect_sessionquit:
pluginId: kwin4_effect_sessionquit
isActiveFullScreenEffect: false

kwin4_effect_logout:
pluginId: kwin4_effect_logout
isActiveFullScreenEffect: false

kwin4_effect_login:
pluginId: kwin4_effect_login
isActiveFullScreenEffect: false

slidingpopups:
slideInDuration: 53
slideOutDuration: 88

kwin4_effect_windowaperture:
pluginId: kwin4_effect_windowaperture
isActiveFullScreenEffect: false

slide:
horizontalGap: 45
verticalGap: 20
slideBackground: true

kwin4_effect_squash:
pluginId: kwin4_effect_squash
isActiveFullScreenEffect: false

kwin4_effect_morphingpopups:
pluginId: kwin4_effect_morphingpopups
isActiveFullScreenEffect: false

kwin4_effect_maximize:
pluginId: kwin4_effect_maximize
isActiveFullScreenEffect: false

kwin4_effect_fullscreen:
pluginId: kwin4_effect_fullscreen
isActiveFullScreenEffect: false

kwin4_effect_frozenapp:
pluginId: kwin4_effect_frozenapp
isActiveFullScreenEffect: false

kwin4_effect_fadingpopups:
pluginId: kwin4_effect_fadingpopups
isActiveFullScreenEffect: false

kwin4_effect_fade:
pluginId: kwin4_effect_fade
isActiveFullScreenEffect: false

kwin4_effect_dialogparent:
pluginId: kwin4_effect_dialogparent
isActiveFullScreenEffect: false

desktopgrid:
activeView: 
gridRows: 2
gridColumns: 2
animationDuration: 106
layout: 1
partialActivationFactor: 0
gestureInProgress: false
showAddRemove: true
desktopNameAlignment: 0
desktopLayoutMode: 0
customLayoutRows: 2

highlightwindow:

overview:
activeView: 
animationDuration: 106
layout: 1
ignoreMinimized: false
blurBackground: true
partialActivationFactor: 0
gestureInProgress: false
searchText: 

tileseditor:
activeView: 
animationDuration: 200

windowview:
activeView: 
animationDuration: 106
layout: 1
ignoreMinimized: false
mode: 0
partialActivationFactor: 0
gestureInProgress: false
searchText: 

blendchanges:

startupfeedback:
type: 1

kscreen:

screentransform:


Loaded Plugins:
---------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor
kwin5_plugin_screencast

Available Plugins:
------------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor
kwin5_plugin_screencast

seth · 2024-01-12 16:21:28

Scale: 1.5
Refresh Rate: 60001
Adaptive Sync: incapable

1. disable fractional scaling
2. try to run (both) outputs on 60Hz

karemkassem · 2024-01-12 16:28:19

I have disabled fractional scaling and ran both screens at 60hz, it seems to help but just a small amount the external screen is still extremely laggy

KWin Support Information:
The following information should be used when requesting support on e.g. https://forum.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like https://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 5.27.10
Qt Version: 5.15.12
Qt compile version: 5.15.12
XCB compile version: 1.16

Operation Mode: Xwayland

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12302003
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.breeze
Theme: 
Plugin recommends border size: None
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,5,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==============
Name: DRM
Active: true
Atomic Mode Setting on GPU 0: true
Atomic Mode Setting on GPU 1: true

Cursor
======
themeName: Adwaita
themeSize: 24

Options
=======
focusPolicy: 0
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 28
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: false
glStrictBindingFollowsDriver: true
glPreferBufferSwap: 101
glPlatformInterface: 2
windowsBlockCompositing: true
latencyPolicy: 
renderTimeEstimator: 
allowTearing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
---------
Name: eDP-1
Enabled: 1
Geometry: 0,540,2880x1620
Scale: 1
Refresh Rate: 60001
Adaptive Sync: incapable
Screen 1:
---------
Name: HDMI-A-1
Enabled: 1
Geometry: 2880,0,3840x2160
Scale: 1
Refresh Rate: 60000
Adaptive Sync: incapable

Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (ADL GT2)
OpenGL version string: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL platform interface: EGL
OpenGL shading language version string: 4.60
Driver: Intel
GPU class: Unknown
OpenGL version: 4.6
GLSL version: 4.60
Mesa version: 23.3.2
Linux kernel version: 6.6.10
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---------------
colorpicker
outputlocator
magnifier
screenshot
screenedge
blur
contrast
kwin4_effect_sessionquit
kwin4_effect_logout
kwin4_effect_login
slidingpopups
kwin4_effect_windowaperture
slide
kwin4_effect_squash
kwin4_effect_morphingpopups
kwin4_effect_maximize
kwin4_effect_fullscreen
kwin4_effect_frozenapp
kwin4_effect_fadingpopups
kwin4_effect_fade
kwin4_effect_dialogparent
desktopgrid
highlightwindow
overview
tileseditor
windowview
blendchanges
startupfeedback
kscreen
screentransform

Currently Active Effects:
-------------------------
blur
contrast

Effect Settings:
----------------
colorpicker:

outputlocator:

magnifier:
magnifierSize: 
targetZoom: 1

screenshot:

screenedge:

blur:

contrast:

kwin4_effect_sessionquit:
pluginId: kwin4_effect_sessionquit
isActiveFullScreenEffect: false

kwin4_effect_logout:
pluginId: kwin4_effect_logout
isActiveFullScreenEffect: false

kwin4_effect_login:
pluginId: kwin4_effect_login
isActiveFullScreenEffect: false

slidingpopups:
slideInDuration: 53
slideOutDuration: 88

kwin4_effect_windowaperture:
pluginId: kwin4_effect_windowaperture
isActiveFullScreenEffect: false

slide:
horizontalGap: 45
verticalGap: 20
slideBackground: true

kwin4_effect_squash:
pluginId: kwin4_effect_squash
isActiveFullScreenEffect: false

kwin4_effect_morphingpopups:
pluginId: kwin4_effect_morphingpopups
isActiveFullScreenEffect: false

kwin4_effect_maximize:
pluginId: kwin4_effect_maximize
isActiveFullScreenEffect: false

kwin4_effect_fullscreen:
pluginId: kwin4_effect_fullscreen
isActiveFullScreenEffect: false

kwin4_effect_frozenapp:
pluginId: kwin4_effect_frozenapp
isActiveFullScreenEffect: false

kwin4_effect_fadingpopups:
pluginId: kwin4_effect_fadingpopups
isActiveFullScreenEffect: false

kwin4_effect_fade:
pluginId: kwin4_effect_fade
isActiveFullScreenEffect: false

kwin4_effect_dialogparent:
pluginId: kwin4_effect_dialogparent
isActiveFullScreenEffect: false

desktopgrid:
activeView: 
gridRows: 2
gridColumns: 2
animationDuration: 106
layout: 1
partialActivationFactor: 0
gestureInProgress: false
showAddRemove: true
desktopNameAlignment: 0
desktopLayoutMode: 0
customLayoutRows: 2

highlightwindow:

overview:
activeView: 
animationDuration: 106
layout: 1
ignoreMinimized: false
blurBackground: true
partialActivationFactor: 0
gestureInProgress: false
searchText: 

tileseditor:
activeView: 
animationDuration: 200

windowview:
activeView: 
animationDuration: 106
layout: 1
ignoreMinimized: false
mode: 0
partialActivationFactor: 0
gestureInProgress: false
searchText: 

blendchanges:

startupfeedback:
type: 1

kscreen:

screentransform:


Loaded Plugins:
---------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor
kwin5_plugin_screencast

Available Plugins:
------------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor
kwin5_plugin_screencast

seth · 2024-01-12 21:47:23

seth wrote:

Can you get the edid w/
edid-decode /sys/class/drm/card*HDMI*/edid
?

(I cannot find an EDID for that monitor online and right now the missing or bogus edid is my best guess as to why the sync doesn't work properly. It's the sync because the internal display renders fine)

karemkassem · 2024-01-12 21:56:43

it seems that this directory doesn't exist.

I built edid-decode from github, and after running the command it outputs:

/sys/class/drm/card*HDMI*/edid: No such file or directory

and also thank you for your work

karemkassem · 2024-01-12 21:59:26

I searched through the directory and I found that card*HDMI* file doesn't exist (maybe you meant it this way an I misinderstood )

here is a list of all the files that are foun in the directory /sys/class/drm/

card0  card1  card1-DP-1  card1-DP-2  card1-eDP-1  renderD128  renderD129  version

and also one more thing
I ran the session through a usb c to hdmi adapter and the wayland session ran fine ( bt the adapter is cheap so it can only run at 4k30hz) maybe this helps

Last edited by karemkassem (2024-01-12 22:01:21)

seth · 2024-01-12 22:09:29

ls /sys/class/drm/card0
cat /sys/class/drm/card0/device/vendor

Does the HDMI connection perform better when you reduce it to 30Hz?

karemkassem · 2024-01-12 22:14:37

ls /sys/class/drm/card0

the output

dev  device  power  subsystem  uevent

cat /sys/class/drm/card0/device/vendor

the output

0x10de

Does the HDMI connection perform better when you reduce it to 30Hz?

not really, after all when I use the screen in x11 I use it 4k60hz with no real problem in the screen itself (ther is problems like screen tearing but they are because of x11 )

seth · 2024-01-12 22:20:14

card0 is the nvidia card, just without any data (as you'd typically see w/o nvidia_drm.modeset, but that's there)

In order to not tear, wayland has to manage the vblank signals - if that's not possible, you'll get a diashow from some forced timeout.
https://wiki.archlinux.org/title/PRIME# … ronization might get you the same behavior on X11 as currently is on wayland.

Hail-mary: install the 535xx versions of nvidia-utils and nvidia-dkms from the ALA.
There're some 545xx related issues reported, but I'm really not sure that's what you're facing here.

karemkassem · 2024-01-12 22:45:36

I have tried this and also I tried installing the nvidia-beta drivers but it always gave the same result
it looks like there isn't really a solution
thank you for your time
and if I somehow find a solution I will post it here

seth · 2024-01-12 22:48:21

Can you disable the IGP in the BIOS/UEFI and only use the nvidia GPU (rewiring the eDP there)?
Or disable the GPU and only use the IGP (rewiring the HDMI there)?
It's odd that no outputs show up in the nvidia drm card

karemkassem · 2024-01-12 23:04:07

I searched the BIOS but it had nothing of such sort.
though I have tried methods like envycontrol to use gpu but it gave no real results ( I've also tried optimus manager before but it completelt borkes my system)

Arch Linux

#1 2024-01-11 09:41:22

[SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#2 2024-01-11 10:28:15

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#3 2024-01-12 12:48:03

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#4 2024-01-12 13:21:31

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#5 2024-01-12 14:00:43

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#6 2024-01-12 14:18:04

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#7 2024-01-12 14:36:44

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#8 2024-01-12 14:52:30

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#9 2024-01-12 14:58:33

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#10 2024-01-12 15:02:50

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#11 2024-01-12 15:11:42

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#12 2024-01-12 15:34:22

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#13 2024-01-12 15:50:14

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#14 2024-01-12 16:06:16

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#15 2024-01-12 16:21:28

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#16 2024-01-12 16:28:19

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#17 2024-01-12 21:47:23

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#18 2024-01-12 21:56:43

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#19 2024-01-12 21:59:26

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#20 2024-01-12 22:09:29

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#21 2024-01-12 22:14:37

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#22 2024-01-12 22:20:14

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#23 2024-01-12 22:45:36

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#24 2024-01-12 22:48:21

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

#25 2024-01-12 23:04:07

Re: [SOLVED] hdmi output not working on kde wayland (nvidia gpu)

Board footer