[SOLVED] Kde desktop environment unable to start, unable to set 165hz

snow1 · 2024-10-17 09:59:59

Hello fellow Arch enthusiasts,

for the past months I have been destroying my head about this problem.
I am possibly just missing out on something simple but here's the deal:

------------------------------------------------------------------------------------------------------------------

My setup:
Nvidia Geforce RTX 3050 8GB
12th gen Intel i5-12400F
2x Corsair Vengance DDR4 8GB
MSI B660 A Pro DDR4

NVIDIA Driver version: 560.35.03
Plasmashell version: 6.2.1
------------------------------------------------------------------------------------------------------------------
I have been using Arch for a little over a year now and I have never been having problems with either Nvidia or KDE.
I am using Arch on my Laptop and my main Desktop PC. The Problem occurs only on my PC.
Since a few months now I have been unable to use KDE Plasma with X11 and neither Wayland.
I think the problem started after updating from KDE 5 to KDE 6, I am not completely sure though.
Sddm works just fine.
But after logging in and after the Plasma greeter my screen goes blank and my monitor goes into sleep mode.
I am able to open a console with the keyboard shortcut. When I log into i3 though everything works well.
But I am unable to put my screen refreshrate above 120hz, although my monitor has got the ability to go up to 165hz.
when setting it manually through xrandr my monitor just goes blank.
When setting it in a Xorg config file or the 10-monitor... config file sddm doesn't even appear and I have to change it again through ssh.
When setting it through the gui nvidia-settings the screen goes blank for a bit of time, then returns to the refreshrate which was set before.

------------------------------------------------------------------------------------------------------------------

Launching nvidia settings through terminal shows an error message:

(nvidia-settings:7682): GLib-GObject-CRITICAL **: 23:54:01.135: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

----------------------------------------

When attmpting to change refreshrate:

(nvidia-settings:7682): GLib-CRITICAL **: 23:54:30.350: Source ID 2048 was not found when attempting to remove it

(nvidia-settings:7682): GLib-CRITICAL **: 23:55:12.460: Source ID 10326 was not found when attempting to remove it

------------------------------------------------------------------------------------------------------------------

For that reason I though it had to do something with the nvidia drivers and not Kde.
And because it works fine on my Laptop which doesen't have a nvidia gpu.
I have reinstalled the drivers countless times in different ways, but it didn't seem to help it.
I have also tried switching to lts-kernel with nvidia-lts drivers, and the nvidia-open drivers but that didn't work, except for when using i3.
I have read through countless articles and forums, but I can't seem to find a solution.
I have followed the instructions on Arch wiki, they don't work for me.
Decided to abandon the problem for a few months and just use 120hz. Worked perfectly.
Made a win 11 VM with single gpu passthrough. Drivers correctly detatch and attach in start and stopscript, no faults after some minor script modification.
Installed Nvidia Drivers on the VM. There they work without any problems. 165 hz works perfectly.
------------------------------------------------------------------------------------------------------------------

output of:

lspci -k | grep -A 2 -E "(VGA|3D)"

shows that nvidia kernel driver is in use

output of:

sudo dmesg --level=err,warn

didn't show anything critical from my research, but some warnings:

kern  :warn  : [17. Okt 10:12] nvidia: loading out-of-tree module taints kernel.
kern  :warn  : [  +0,000007] nvidia: module license 'NVIDIA' taints kernel.
kern  :warn  : [  +0,000001] Disabling lock debugging due to kernel taint
kern  :warn  : [  +0,000000] nvidia: module license taints kernel.
kern  :warn  : [  +0,048108] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  560.35.03  Fri Aug 16 21:39:15 UTC 2024
kern  :warn  : [  +0,006671] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
kern  :warn  : [  +0,001132] usb: port power management may be unreliable
kern  :warn  : [  +0,000143] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
kern  :warn  : [  +6,551829] platform INT3515:01: deferred probe pending: Serial bus multi instantiate pseudo device driver: Error creating i2c-client, idx 0

------------------------------------------------------------------------------------------------------------------

some output from journalctl I filtered out:

older errors:
These have been resolved but maybe they could still help with finding the solution:

org_kde_powerdevil[1675]: busno=2, All features that should not exist detected. Monito>

dolphin[4222]: "applications.menu"  not found in  QList("/etc/xdg/menus")

kactivitymanagerd[4239]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service>

(sd-pam)[765]: pam_systemd(systemd-user:session): Failed to release session: Caller do>

kernel: BUG: kernel NULL pointer dereference, address: 0000000000000350
kernel: #PF: supervisor read access in kernel mode
kernel: #PF: error_code(0x0000) - not-present page
kded6[809]: org.kde.wacomtablet.common: d->name.isEmpty? true
kded6[809]: org.kde.wacomtablet.common: d->name.isEmpty? true

------------------------------------------------------------------------------------------------------------------

current errors related to kde:
sddm crash?
sddm works normally but shows this:

sddm[615]: Auth: sddm-helper exited with 1
sddm[615]: Error from greeter session: "Process crashed"
systemd[1]: system-systemd\x2dcoredump.slice: Consumed 1.800s CPU time, 328.5M memory >
sddm[615]: Auth: sddm-helper (--socket /tmp/sddm-auth-488af013-c54b-42f7-9a5a-b1a59cbe>

forceful termination

sddm-helper[25912]: Signal received: SIGTERM

systemd-coredump[723]: [?] Process 707 (sddm-greeter-qt) of user 969 dumped core.

from coredumpctl list

Wed 2024-10-16 18:12:18 CEST   707  969  969 SIGSEGV inaccessible /usr/bin/sddm-greeter-qt6

could be because of force shutdownm, but unsure

something with themeexplorer:

Okt 16 11:25:52 toyotasupra plasmathemeexplorer[7556]: file:///usr/share/kpackage/genericqml/org.kde.plasma.themee>

error from xorg logs:

ACPI: failed to connect to the ACPI event daemon; the daemon
      may not be running or the "AcpidSocketPath" X
      configuration option may not be set correctly.  When the
      ACPI event daemon is available, the NVIDIA X driver will
      try to use it to receive ACPI event notifications.  For
      details, please see the "ConnectToAcpid" and
      "AcpidSocketPath" X configuration options in Appendix B: X
       may not be running or the "AcpidSocketPath" X
       configuration option may not be set correctly.  When the
       ACPI event daemon is available, the NVIDIA X driver will
       try to use it to receive ACPI event notifications.  For
       details, please see the "ConnectToAcpid" and
       "AcpidSocketPath" X configuration options in Appendix B: X

------------------------------------------------------------------------------------------------------------------

output of nvidia-smi

 +-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 560.35.03              Driver Version: 560.35.03      CUDA Version: 12.6     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3050        Off |   00000000:01:00.0  On |                  N/A |
|  0%   37C    P5             N/A /  115W |     513MiB /   8192MiB |      7%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A       611      G   /usr/lib/Xorg                                 147MiB |
|    0   N/A  N/A       749      G   picom                                          39MiB |
|    0   N/A  N/A      1054      G   /usr/lib/firefox/firefox                      275MiB |
+-----------------------------------------------------------------------------------------+

----------------------------------------------------------------------------------------------------------------------
After runing Plasmashell form within i3 in therminal:
Not sure if it's just because of running it inside i3 or something else
After running plasmashell command the desktop environment does open, but applications don't work correctly

Once after logging into X11, after having done something in plasmashell in i3 before, the plasmagreeter froze in the last frame and a message popped up that kde is unable to start. I had the option to press okay but after that the screen went blank again. I couldn't reproduce this.

plasmashell logs:

Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")
kf.kirigami.platform: Failed to find a Kirigami platform plugin for style "Fusion"
kf.plasma.quick: Applet preload policy set to 1
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:178:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth":
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:201:9
Toolbox not loading, toolbox package is either invalid or disabled.
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:50:9: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel"
qt.dbus.integration: Could not connect "org.cups.cupsd.Notifier" to PrinterFinishingsChanged(QString, QString, QString, uint, QString, bool) :
org.kde.plasma.libtaskmanager: Failed to determine whether virtual desktop navigation wrapping is enabled:  "The name is not activatable"
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap

after clicking something in kde gui:

file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/ApplicationsPage.qml:207: TypeError: Cannot call method 'forceActiveFocus' of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/ApplicationsPage.qml:207: TypeError: Cannot call method 'forceActiveFocus' of null

---------------------------------------------------------------------------------------------------------------------------------------------------------------

I can provide more information if needed.
Hopefully someone can find the solution but I have to give up for now. I still have i3 and a fully functioning vm so I am able to use my PC normally.
I would sleep a lot better though having this issue fixed and KDE not just being unusable bloatware on my PC.
Nvidia and KDE have been following me in my dreams. I hope I didn't provide too much unnecessary Information
Sry if I respond to messages late as I currently do not have a lot of time.
Thanks.

Feel free to laugh,
Erik

Last edited by snow1 (2024-10-23 20:47:50)

seth · 2024-10-17 14:12:51

https://wiki.archlinux.org/title/KDE#Un … lution_set
Also/otherwise please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General (all of it, not just some lines)

snow1 · 2024-10-17 16:24:59

seth wrote:

https://wiki.archlinux.org/title/KDE#Un … lution_set
Also/otherwise please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General (all of it, not just some lines)

1. I have two different files in my ~/.local/kscreen folder
one for my monitors ID and one for the ID "None-1". The one for my monitor is set correctly (165.003 ... hz, 1920 x1080).
The other one ist set to 60 hz.
Is the second one supposed to be there?

2. log files from /var/log :
https://www.mediafire.com/file/pxcssaun … 0.log/file
https://www.mediafire.com/file/m31q952l … 1.log/file

In case you need the "old" ones as well:
https://www.mediafire.com/file/vn9876nb … g.old/file
https://www.mediafire.com/file/k2rxr1bm … 1.log.old/

log file from ~/.local/share/xorg/ in case there is difference:
https://www.mediafire.com/file/9qkc79ad … other/file

seth · 2024-10-17 17:52:33

Is the second one supposed to be there?

No, that's the simpledrm device and you absolutely don't want to use that.
Your current log has

[     8.363] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=eb0e8153-1551-49fc-b856-18842f87af40 rw rcutree.gp_init_delay=1 nvidia-drm.modeset=1 intel_iommu=on loglevel=3 quiet

and the "nvidia-drm.modeset=1" blocks the simpledrm device, so that's good because it cannot get in the way, you want to get rid of the stale kscreen entry. Actually just remove them all and see whether that helps (they'll be regenerated w/ proper values automatically)

[     8.363] (==) Using config file: "/etc/X11/xorg.conf"

Also remove that file and don't recreate it (it's nvidia-settigns generated cruft)
The only part about it that's not complete nonsense is

[     8.494] (**) NVIDIA(0): Option "MetaModes" "1920x1080_120 +0+0"

but the mode gets overridden by kscreen anyway and even if not, you'd set that otherwise.

snow1 · 2024-10-17 18:32:59

seth wrote:

Actually just remove them all and see whether that helps (they'll be regenerated w/ proper values automatically)
Also remove that file and don't recreate it (it's nvidia-settigns generated cruft)
The only part about it that's not complete nonsense is
[     8.494] (**) NVIDIA(0): Option "MetaModes" "1920x1080_120 +0+0"
but the mode gets overridden by kscreen anyway and even if not, you'd set that otherwise.

Oh wow that actually fixed it xD. Thanks a lot.
So it wasn't the nvidia drivers fault. How would you now recommend setting the resolution and refreshrate?
Should I do it through kscreen settings or differently?

And one more question. Do you know what could have caused the simpledrm device configuration being generated leading to the fault?
I made the xorg.conf but that was after the problem occurred.

seth · 2024-10-17 18:43:45

How would you now recommend setting the resolution and refreshrate?
… do it through kscreen setting

The simplydumb device was added to the kernel as failsafe so you can have a graphical wayland session despite your graphics stack being messed up - don't get me started on how many levels that's just between silly and dumb…
Esp. initially the nivdia driver wasn't prepared for that and could not take over, so you had two GPUs in the system (one being fake software emulation) what got you the "None-1" entry from kscreen.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

snow1 · 2024-10-17 18:46:46

Oh wow that actually fixed it xD. Thanks a lot.
So it wasn't the nvidia drivers fault. How would you now recommend setting the resolution and refreshrate?
Should I do it through kscreen settings or differently?

Well it didn't fix it completely.
Kde does work now but I still can't change my refreshrate to 165 hz (I tried it through kde settings).

seth · 2024-10-17 18:51:11

xrandr -q
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

You'll need https://aur.archlinux.org/packages/edid-decode-git

snow1 · 2024-10-17 18:55:05

seth wrote:

xrandr -q
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
You'll need https://aur.archlinux.org/packages/edid-decode-git

Good I will try that now.

seth · 2024-10-17 19:00:01

That's not for "try", that's for "it'll produce some ouput for you to post"

snow1 · 2024-10-17 19:01:23

seth wrote:

That's not for "try", that's for "it'll produce some ouput for you to post"

I just found out xD.
Here's the output:

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DVI-D-0 disconnected primary (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
   1920x1080     60.00*+ 165.00   143.98   119.98   119.88    59.94    50.00  
   1680x1050     59.95  
   1600x1200     60.00  
   1440x900      74.98    59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x720      59.94    50.00  
   1152x720      60.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    59.94    59.93  
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
/sys/class/drm/card0
/sys/class/drm/card0/edid: No such file or directory
=================
/sys/class/drm/card0-DP-1
EDID of '/sys/class/drm/card0-DP-1/edid' was empty.
=================
/sys/class/drm/card0-DVI-D-1
EDID of '/sys/class/drm/card0-DVI-D-1/edid' was empty.
=================
/sys/class/drm/card0-HDMI-A-1
edid-decode (hex):

00 ff ff ff ff ff ff 00 26 cd 78 66 30 05 00 00
14 21 01 03 80 3c 22 78 2a dd 60 a4 55 50 9f 27
0e 50 54 a5 6b 80 71 00 81 40 81 80 a9 40 b3 00
95 00 95 0f d1 c0 02 3a 80 18 71 38 2d 40 58 2c
45 00 56 50 21 00 00 1e 00 00 00 ff 00 31 31 38
38 39 33 32 30 31 31 33 32 38 00 00 00 fd 00 38
a5 1e b8 28 00 0a 20 20 20 20 20 20 00 00 00 fc
00 50 4c 32 37 36 31 48 0a 20 20 20 20 20 01 ed

02 03 49 f1 50 90 05 04 03 02 01 11 12 13 14 06
07 15 16 1f 3f 23 09 07 07 83 01 00 00 67 03 0c
00 10 00 38 44 67 d8 5d c4 01 50 80 00 6d 1a 00
00 02 01 28 a5 e6 00 00 00 00 00 e3 05 c3 01 e6
06 05 01 62 62 00 e2 00 d5 86 6f 80 a0 70 38 40
40 30 20 35 00 56 50 21 00 00 1a 5a 87 80 a0 70
38 4d 40 30 20 35 00 56 50 21 00 00 1a d0 94 80
a0 70 38 1e 40 08 20 35 00 56 50 21 00 00 1a a4

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.3
  Vendor & Product Identification:
    Manufacturer: IVM
    Model: 26232
    Serial Number: 1328 (0x00000530)
    Made in: week 20 of 2023
  Basic Display Parameters & Features:
    Digital display
    Maximum image size: 60 cm x 34 cm
    Gamma: 2.20
    DPMS levels: Off
    RGB color display
    First detailed timing is the preferred timing
  Color Characteristics:
    Red  : 0.6435, 0.3330
    Green: 0.3154, 0.6220
    Blue : 0.1533, 0.0566
    White: 0.3125, 0.3281
  Established Timings I & II:
    IBM     :   720x400    70.081663 Hz   9:5     31.467 kHz     28.320000 MHz
    DMT 0x04:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    DMT 0x06:   640x480    75.000000 Hz   4:3     37.500 kHz     31.500000 MHz
    DMT 0x09:   800x600    60.316541 Hz   4:3     37.879 kHz     40.000000 MHz
    DMT 0x0b:   800x600    75.000000 Hz   4:3     46.875 kHz     49.500000 MHz
    Apple   :   832x624    74.551266 Hz   4:3     49.726 kHz     57.284000 MHz
    DMT 0x10:  1024x768    60.003840 Hz   4:3     48.363 kHz     65.000000 MHz
    DMT 0x12:  1024x768    75.028582 Hz   4:3     60.023 kHz     78.750000 MHz
    DMT 0x24:  1280x1024   75.024675 Hz   5:4     79.976 kHz    135.000000 MHz
    Apple   :  1152x870    75.061550 Hz 192:145   68.681 kHz    100.000000 MHz
  Standard Timings:
    GTF     :  1152x720    59.999964 Hz  16:10    44.760 kHz     67.319000 MHz
    DMT 0x20:  1280x960    60.000000 Hz   4:3     60.000 kHz    108.000000 MHz
    DMT 0x23:  1280x1024   60.019740 Hz   5:4     63.981 kHz    108.000000 MHz
    DMT 0x33:  1600x1200   60.000000 Hz   4:3     75.000 kHz    162.000000 MHz
    DMT 0x3a:  1680x1050   59.954250 Hz  16:10    65.290 kHz    146.250000 MHz
    DMT 0x2f:  1440x900    59.887445 Hz  16:10    55.935 kHz    106.500000 MHz
    DMT 0x30:  1440x900    74.984427 Hz  16:10    70.635 kHz    136.750000 MHz
    DMT 0x52:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz
  Detailed Timing Descriptors:
    DTD 1:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz (598 mm x 336 mm)
                 Hfront   88 Hsync  44 Hback  148 Hpol P
                 Vfront    4 Vsync   5 Vback   36 Vpol P
    Display Product Serial Number: '1188932011328'
    Display Range Limits:
      Monitor ranges (GTF): 56-165 Hz V, 30-184 kHz H, max dotclock 400 MHz
    Display Product Name: 'PL2761H'
  Extension blocks: 1
Checksum: 0xed

----------------

Block 1, CTA-861 Extension Block:
  Revision: 3
  Underscans IT Video Formats by default
  Basic audio support
  Supports YCbCr 4:4:4
  Supports YCbCr 4:2:2
  Native detailed modes: 1
  Video Data Block:
    VIC  16:  1920x1080   60.000000 Hz  16:9     67.500 kHz    148.500000 MHz (native)
    VIC   5:  1920x1080i  60.000000 Hz  16:9     33.750 kHz     74.250000 MHz
    VIC   4:  1280x720    60.000000 Hz  16:9     45.000 kHz     74.250000 MHz
    VIC   3:   720x480    59.940060 Hz  16:9     31.469 kHz     27.000000 MHz
    VIC   2:   720x480    59.940060 Hz   4:3     31.469 kHz     27.000000 MHz
    VIC   1:   640x480    59.940476 Hz   4:3     31.469 kHz     25.175000 MHz
    VIC  17:   720x576    50.000000 Hz   4:3     31.250 kHz     27.000000 MHz
    VIC  18:   720x576    50.000000 Hz  16:9     31.250 kHz     27.000000 MHz
    VIC  19:  1280x720    50.000000 Hz  16:9     37.500 kHz     74.250000 MHz
    VIC  20:  1920x1080i  50.000000 Hz  16:9     28.125 kHz     74.250000 MHz
    VIC   6:  1440x480i   59.940060 Hz   4:3     15.734 kHz     27.000000 MHz
    VIC   7:  1440x480i   59.940060 Hz  16:9     15.734 kHz     27.000000 MHz
    VIC  21:  1440x576i   50.000000 Hz   4:3     15.625 kHz     27.000000 MHz
    VIC  22:  1440x576i   50.000000 Hz  16:9     15.625 kHz     27.000000 MHz
    VIC  31:  1920x1080   50.000000 Hz  16:9     56.250 kHz    148.500000 MHz
    VIC  63:  1920x1080  120.000000 Hz  16:9    135.000 kHz    297.000000 MHz
  Audio Data Block:
    Linear PCM:
      Max channels: 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block:
    FL/FR - Front Left/Right
  Vendor-Specific Data Block (HDMI), OUI 00-0C-03:
    Source physical address: 1.0.0.0
    DC_36bit
    DC_30bit
    DC_Y444
    Maximum TMDS clock: 340 MHz
  Vendor-Specific Data Block (HDMI Forum), OUI C4-5D-D8:
    Version: 1
    Maximum TMDS Character Rate: 400 MHz
    SCDC Present
  Vendor-Specific Data Block (AMD), OUI 00-00-1A:
    Version: 2
    Feature Caps: 0x01
    Minimum Refresh Rate: 40 Hz
    Maximum Refresh Rate: 165 Hz
    Flags 1.x: 0xe6 (MCCS)
    Flags 2.x: 0x00
    Maximum luminance: 0 (50.000 cd/m^2)
    Minimum luminance: 0 (0.000 cd/m^2)
    Unknown: 0x00 0x00
  Colorimetry Data Block:
    xvYCC601
    xvYCC709
    BT2020YCC
    BT2020RGB
    Gamut Boundary Description Metadata Profile P0
  HDR Static Metadata Data Block:
    Electro optical transfer functions:
      Traditional gamma - SDR luminance range
      SMPTE ST2084
    Supported static metadata descriptors:
      Static metadata type 1
    Desired content max luminance: 98 (417.710 cd/m^2)
    Desired content max frame-average luminance: 98 (417.710 cd/m^2)
    Desired content min luminance: 0 (0.000 cd/m^2)
  Video Capability Data Block:
    YCbCr quantization: Selectable (via AVI YQ)
    RGB quantization: Selectable (via AVI Q)
    PT scan behavior: Always Overscanned
    IT scan behavior: Always Overscanned
    CE scan behavior: Always Overscanned
  Detailed Timing Descriptors:
    DTD 2:  1920x1080  119.982181 Hz  16:9    137.260 kHz    285.500000 MHz (598 mm x 336 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   56 Vpol N
    DTD 3:  1920x1080  143.981451 Hz  16:9    166.587 kHz    346.500000 MHz (598 mm x 336 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   5 Vback   69 Vpol N
    DTD 4:  1920x1080  165.003465 Hz  16:9    183.154 kHz    380.960000 MHz (598 mm x 336 mm)
                 Hfront    8 Hsync  32 Hback  120 Hpol P
                 Vfront    3 Vsync   5 Vback   22 Vpol N
Checksum: 0xa4
=================

seth · 2024-10-17 19:05:06

So the mode is there and picked up, what actually happens if you run "xrandr --output HDMI-0 --rate 165"?

snow1 · 2024-10-17 19:10:00

seth wrote:

So the mode is there and picked up, what actually happens if you run "xrandr --output HDMI-0 --rate 165"?

Nothing actually happens.
After running the command my refreshrate stays as it was before.
I am also instantly returned to the bash prompt and there doesn't seem to be anything loading.

when I change it from 60 to 120 my screen goes blank for a few seconds then returns with the new refreshrate.
And KDE settings still show 120 hz after the command for 165 hz.
And it is the same in i3.

Last edited by snow1 (2024-10-17 19:13:30)

seth · 2024-10-17 19:20:45

What do "xrandr -q" and your monitor OSD report afterwards?
Can you switch to 144Hz?
HDMI < 2.0 and cables other than "Premium High Speed" and "Ultra High Speed" (sigh, yes, that's the official grading) would not allow the modes > 340MHz (144Hz being kinda on the edge there) but the modes would be filtered by default and trying to set them would get you an error.

snow1 · 2024-10-17 19:26:49

Here's my xrandr -q output for HDMI-0 and the stuff on top:

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767

HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
   1920x1080     60.00 + 165.00   143.98   119.98*  119.88    59.94    50.00  
   1680x1050     59.95  
   1600x1200     60.00  
   1440x900      74.98    59.89  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x720      59.94    50.00  
   1152x720      60.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    59.94    59.93

But it kind of wouldn't make sense if it didn't work on my arch machine, because it works on the win 11 vm with 165 hz?
So I do seem to have the specifications.

Oh and 144 hz also doesn't work.

my monitors OSD also show 120 hz.

Last edited by snow1 (2024-10-17 19:40:15)

snow1 · 2024-10-17 19:58:06

I just tried setting it with these options /etc/X11/xorg.conf.d/10-monitor.conf :

Section "Screen"
    Identifier "Screen0"
    Monitor "HDMI-0"
    Option  "MetaModes" "HDMI-0: 1920x1080_144 +0+0"
EndSection

Resulting in a solution in a similar Post.
But that just gave me a black screen after login and I had to ssh again.

I also tried logging into wayland but there I still have no visuals. I was able to reboot without it though xD.
Disregarding that I didn't see anything the system worked.

Last edited by snow1 (2024-10-17 20:08:03)

seth · 2024-10-17 20:07:18

I suspect that windows does https://wiki.archlinux.org/title/NVIDIA … ubsampling
/etc/X11/xorg.conf.d/20-nvidia.conf

Section "Device"
    Identifier "mynvidiagpu"
    Driver  "nvidia"
    Option "ForceYUV420" "True"
EndSection

Last edited by seth (2024-10-17 20:27:45)

snow1 · 2024-10-17 20:17:04

seth wrote:

I suspect that windows does https://wiki.archlinux.org/title/NVIDIA … ubsampling
/etc/X11/xorg.conf.d/20-nvidia.conf
Section "Device"
    Identifier "mynvidiagpu"
    Option "ForceYUV420" "True"
EndSection

It appears to not be the case
It still remains as is after creating the config rebooting and retrying to set it.

Last edited by snow1 (2024-10-17 20:23:38)

seth · 2024-10-17 20:28:02

My bad, I forgot the driver…

snow1 · 2024-10-17 20:28:46

With these Options and then also adding the 10-monitor.conf file doesn't even let me into sddm.
In my xorg.conf.d I also have a 10-nvidia-drm-outputclass.conf file. It contains:

 1 Section "OutputClass"
 2     Identifier "intel"
 3     MatchDriver "i915"
 4     Driver "modesetting"
 5 EndSection
 6
 7 Section "OutputClass"
 8     Identifier "nvidia"
 9     MatchDriver "nvidia-drm"
10     Driver "nvidia"
11     Option "AllowEmptyInitialConfiguration"
12     Option "PrimaryGPU" "yes"
13     ModulePath "/usr/lib/nvidia/xorg"
14     ModulePath "/usr/lib/xorg/modules"
15 EndSection

seth wrote:

My bad, I forgot the driver…

Ah okay reading it now xD

Last edited by snow1 (2024-10-17 20:48:40)

snow1 · 2024-10-17 20:36:55

seth wrote:

My bad, I forgot the driver…

Still doesn't seem to fix it though .

Oh wait do I have to replace the Identifyer the one for my gpu?
Changing it to "Nvidia Card" as seen in different posts didn't fix it.

Also on my HDMI cable it says that it is indeed "high speed".

Last edited by snow1 (2024-10-17 21:06:40)

seth · 2024-10-18 06:58:20

The identifier is freetext, you can put there whaever you want. Doesn't matter.
144Hz and 165Hz are often stand-ins for https://wiki.archlinux.org/title/Variable_refresh_rate but the EDID doesn't suggest that capacity (nor actually YCbCr 4:2:0)

The irritating part is that you're not even getting errors from xrandr, though your OP actually had

when setting it manually through xrandr my monitor just goes blank.

Is this still the case?

When testing this w/ the VFIO throughput, did you check the frequency in the monitor OSD or just believed windows?

snow1 · 2024-10-18 08:19:41

seth wrote:

When testing this w/ the VFIO throughput, did you check the frequency in the monitor OSD or just believed windows?

In the vm OSD does indeed say 165 hz.
Yesterday I tried changing the rate without specifying the output. That was probably the reason it did absolutely nothing. I found that out because I tried it on i3 again today and there my rate was still 60 also when trying just 120.
If I specify the output as HDMI-0 it does change to 120. But now if I try making it 165 monitor is blank again but doesn't return to normal. Probably because of the force thing in the 20-... conf.

when setting it manually through xrandr my monitor just goes blank.

It was a bit of a longer time ago it could also have been that my monitor went blank for a bit longer but then returned with the refreshrate set before. I know that with setting it in the config it definitely didn't show anything. Sorry for mixing it up a bit.
But now it actually doesn't return and just stays blank with the monitor going into sleep mode.

After setting it to 120 hz now it was also logged into my Xorg.0.conf:

[   960.743] (II) NVIDIA(0): Setting mode "HDMI-0: 1920x1080_120 @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"

But there is nothing about the 165 hz option

Last edited by snow1 (2024-10-18 08:59:02)

snow1 · 2024-10-18 08:27:25

And I tried installing simplescreenrecorder today to demonstrate that it does actually do nothing (which resulted to not be the case with the output specification).
And when opening I got an error message saying that my proprietary nvidia driver is using "flipping", which could lead to known issues during recording. It then asks me to turn that off.
May that have something to do with the general problem?

Last edited by snow1 (2024-10-18 09:11:26)

seth · 2024-10-18 13:09:14

May that have something to do with the general problem?

Hardly.

If I specify the output as HDMI-0 it does change to 120. But now if I try making it 165 monitor is blank again but doesn't return to normal.

Do you have a spare cable?

Arch Linux

#1 2024-10-17 09:59:59

[SOLVED] Kde desktop environment unable to start, unable to set 165hz

#2 2024-10-17 14:12:51

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#3 2024-10-17 16:24:59

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#4 2024-10-17 17:52:33

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#5 2024-10-17 18:32:59

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#6 2024-10-17 18:43:45

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#7 2024-10-17 18:46:46

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#8 2024-10-17 18:51:11

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#9 2024-10-17 18:55:05

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#10 2024-10-17 19:00:01

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#11 2024-10-17 19:01:23

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#12 2024-10-17 19:05:06

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#13 2024-10-17 19:10:00

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#14 2024-10-17 19:20:45

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#15 2024-10-17 19:26:49

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#16 2024-10-17 19:58:06

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#17 2024-10-17 20:07:18

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#18 2024-10-17 20:17:04

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#19 2024-10-17 20:28:02

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#20 2024-10-17 20:28:46

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#21 2024-10-17 20:36:55

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#22 2024-10-18 06:58:20

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#23 2024-10-18 08:19:41

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#24 2024-10-18 08:27:25

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

#25 2024-10-18 13:09:14

Re: [SOLVED] Kde desktop environment unable to start, unable to set 165hz

Board footer