Monitor resolution not listed in xrandr in KDE Plasma (Wayland)

yilmaz · 2025-01-17 12:35:47

Everything was fine before, but a few days ago, my monitor resolution (2560x1600 at 240hz) disappeared from all games. The maximum resolution shown in the games is 2048x1280 for some reason, even though the resolution in the desktop environment is still correct. Also I'm no longer able to change the resolution in System Settings, it says "2560x1600 (16:10) is the only resolution supported by this display". I'm actually not sure if I was able to change this before, but just putting it out there. I've discovered that even though the resolution is correct in Wayland, apps (mostly games) that use XWayland have the wrong resolution and appear blurry.

Below is the output of xrandr:

Screen 0: minimum 16 x 16, current 2048 x 1280, maximum 32767 x 32767
eDP-1 connected primary 2048x1280+0+0 (normal left inverted right x axis y axis) 345mm x 215mm
   2048x1280    239.82*+
   1600x1200    239.94  
   1440x1080    239.87  
   1400x1050    239.76  
   1280x1024    239.78  
   1280x960     239.80  
   1152x864     239.87  
   1024x768     239.74  
   800x600      239.81  
   640x480      239.72  
   320x240      238.24  
   1920x1200    239.94  
   1680x1050    239.81  
   1440x900     239.80  
   1280x800     239.70  
   1152x720     239.91  
   960x600      239.72  
   928x580      239.78  
   800x500      239.72  
   768x480      239.72  
   720x480      239.35  
   640x400      239.49  
   320x200      238.84  
   2048x1152    239.87  
   1920x1080    239.88  
   1600x900     239.83  
   1368x768     239.74  
   1280x720     239.96  
   1024x576     239.43  
   864x486      239.60  
   720x400      239.62  
   640x350      239.59

I've tried adding 2560x1600 by first running "cvt 2560 1600 240" and then using the output to add to xrandr with the following two commands, this added 2560x1600 to the bottom of the output of xrandr, however I got the following error when trying to change the resolution per https://wiki.archlinux.org/title/Xrandr … esolutions

xrandr --newmode "2560x1600" 1602.50  2560 2800 3088 3616  1600 1603 1609 1847 -hsync +vsync

xrandr --addmode eDP-1 2560x1600

xrandr --output eDP-1 --mode 2560x1600 // this command produced the below error

X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  21 (RRSetCrtcConfig)
  Value in failed request:  0x0
  Serial number of failed request:  22
  Current serial number in output stream:  22

However it still isn't shown in games. I've also tried "xrandr -s 0" but this did nothing. The problem wasn't there before, as I said, it suddenly became like this and I don't remember what I last changed before this started happening. I have done a system upgrade and it did not fix it either.

I've tried looking into the EDID file by running the following command (edid-decode installed from AUR) and it does indeed show the correct resolution:

sudo cat /sys/class/drm/card2-eDP-1/edid | edid-decode

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.4
  Vendor & Product Identification:
    Manufacturer: BOE
    Model: 2932
    Made in: week 1 of 2022
  Basic Display Parameters & Features:
    Digital display
    Bits per primary color channel: 10
    DisplayPort interface
    Maximum image size: 34 cm x 22 cm
    Gamma: 2.20
    Supported color formats: RGB 4:4:4
    First detailed timing includes the native pixel format and preferred refresh rate
    Display supports continuous frequencies
  Color Characteristics:
    Red  : 0.6777, 0.3203
    Green: 0.2558, 0.7080
    Blue : 0.1435, 0.0507
    White: 0.3193, 0.3378
  Established Timings I & II: none
  Standard Timings: none
  Detailed Timing Descriptors:
    DTD 1:  2560x1600   60.001671 Hz  16:10   105.603 kHz    287.240000 MHz (345 mm x 215 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    3 Vsync   6 Vback  151 Vpol N
    Display Range Limits:
      Monitor ranges (Range Limits Only): 60-240 Hz V, 422-422 kHz H, max dotclock 1150 MHz
    Alphanumeric Data String: 'BOE CQ'
    Display Product Name: 'NE160QDM-NM4'
  Extension blocks: 2
Checksum: 0xb0

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

Block 1, CTA-861 Extension Block:
  Revision: 3
  Native detailed modes: 0
  Colorimetry Data Block:
    BT2020RGB
    ST2113RGB
  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: 149 (1260.785 cd/m^2)
    Desired content max frame-average luminance: 115 (603.666 cd/m^2)
    Desired content min luminance: 16 (0.050 cd/m^2)
Checksum: 0xfa  Unused space in Extension Block: 112 bytes

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

Block 2, DisplayID Extension Block:
  Version: 2.0
  Extension Count: 0
  Display Product Primary Use Case: None of the listed primary use cases; generic display
  Video Timing Modes Type 7 - Detailed Timings Data Block:
    DTD:  2560x1600  240.000000 Hz  16:10   422.400 kHz   1148.928000 MHz (aspect 16:10, no 3D stereo, preferred)
               Hfront   48 Hsync  32 Hback   80 Hpol N
               Vfront    3 Vsync   6 Vback  151 Vpol N
  Adaptive Sync Data Block:
    Descriptor #1:
      Native Panel Range
      Fixed Average V-Total and Adaptive V-Total
      Supports Seamless Transition
      'Max Single Frame Duration Increase' field value without jitter impact
      'Max Single Frame Duration Decrease' field value without jitter impact
      Max Duration Increase: 0.00 ms
      Max Duration Decrease: 0.00 ms
      Min Refresh Rate: 60 Hz
      Max Refresh Rate: 240 Hz
  Checksum: 0xb0
Checksum: 0x90

And below is the contents of /sys/class/drm/card2-eDP-1/modes

2560x1600
2560x1600

For reference, I'm using a laptop (Asus G634JZ), my kernel version is 6.12.9-arch1-1, Nvidia driver version latest (565.77-11 installed from pacman). I would appreciate any help, I've run out of clues...

Last edited by yilmaz (2025-01-17 13:09:40)

yilmaz · 2025-01-17 14:27:56

Solved, I had 125% scaling and turns out I had accidentally selected "Scaled by the system" for legacy applications in System Settings. Setting it to "Apply scaling themselves" fixed it.

seth · 2025-01-17 15:42:53

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.

Also notice that xrandr cannot properly control wayland compositors, randr gets synthetic data so X11 clients can query outputs.

Arch Linux

#1 2025-01-17 12:35:47

Monitor resolution not listed in xrandr in KDE Plasma (Wayland)

#2 2025-01-17 14:27:56

Re: Monitor resolution not listed in xrandr in KDE Plasma (Wayland)

#3 2025-01-17 15:42:53

Re: Monitor resolution not listed in xrandr in KDE Plasma (Wayland)

Board footer