xandr doesnt recognize native 2560x1440p resolution

anti4r · 2024-11-30 12:19:41

I have a Radeon 7900xt card on a Wayland gnome install with mesa vulkan-radeon libva-mesa-driver mesa-vdpau drivers installed, I try to configure the resolution on my 2560x1440p @ 360hz monitor with the following commands but it fails:

user@machine$ ~ cvt 2560 1440 
# 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz
Modeline "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync
user@machine$ ~ xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync
user@machine$ ~ xrandr --addmode DP-2 2560x1440_60.00
user@machine$ ~ xrandr --output DP-2 --mode 2560x1440_60.00
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

xrandr output:

user@machine$ ~ xrandr
Screen 0: minimum 16 x 16, current 1456 x 819, maximum 32767 x 32767
DP-2 connected primary 1456x819+0+0 (normal left inverted right x axis y axis) 590mm x 330mm
   1456x819     359.90*+
   1024x768     359.67  
   800x600      359.75  
   640x480      359.07  
   320x240      359.06  
   1280x800     359.63  
   1152x720     359.66  
   960x600      359.90  
   928x580      359.80  
   800x500      359.35  
   768x480      359.29  
   720x480      359.48  
   640x400      359.21  
   320x200      357.70  
   1368x768     359.62  
   1280x720     359.75  
   1024x576     359.88  
   864x486      359.63  
   720x400      359.24  
   640x350      358.82  
   2560x1440_60.00  59.96  

user@machine$ ~ xrandr --listmonitors
Monitors: 1
 0: +*DP-2 1456/590x819/330+0+0  DP-2

Last edited by anti4r (2024-11-30 12:21:16)

Lone_Wolf · 2024-11-30 12:30:08

on a Wayland gnome install

xrandr & cvt/cvt12 are for X .
Under wayland they are ran through a bare-boned X called xwayland and can do very little.

You'll have to use gnome tools to check things as wayland doesn't have a counterpart of xrandr .

anti4r · 2024-11-30 12:34:09

Thats what I thought, and in Gnome tools it even recognizes the resolution as 2560x1440 @ 360hz, but when I start a game in steam the game's resolution cannot be set past 1456x819 which is also the same resolution set automatically on xrandr.

Lone_Wolf · 2024-11-30 15:02:36

Which game ?

seth · 2024-11-30 19:26:55

Steam runs on xwayland - the resolution looks freakish, so this is likely some HiDPI scaling in action? (factor is 1.76. resp 0.57)

RedArcher · Yesterday 07:21:19

I might have a similar issue.

This xrandr command, which is in my i3 config file, does not work, and the resolution of the display appears to be of 1024x768.

exec xrandr --output HDMI-0 --mode 1920x1080 --rate 60

This is the new output of xrandr.

$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
None-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*+

$ xrandr --output HDMI-0 --mode 1920x1080 --rate 60
warning: output HDMI-0 not found; ignoring

$ xrandr --output None-1 --mode 1920x1080 --rate 60
xrandr: cannot find mode 1920x1080

I have also updated package nvidia-535xx-utils to version 535.216.01-3.

Last edited by RedArcher (Yesterday 07:25:25)

seth · Yesterday 07:53:24

Most likely unrelated, this smells as if the simplydumb device gets into the way.
Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

RedArcher · Yesterday 09:17:21

$ cat .local/share/xorg/Xorg.0.log  | curl -F 'file=@-' 0x0.st
http://0x0.st/XR5J.txt

seth · Yesterday 11:49:02

[    26.574] (II) Platform probe for /sys/devices/pci0000:00/0000:00:03.1/0000:1c:00.0/simple-framebuffer.0/drm/card0
[    26.861] (II) modeset(0): Refusing to try glamor on llvmpipe
[    26.863] (II) modeset(0): glamor initialization failed
[    26.863] (II) modeset(0): ShadowFB: preferred NO, enabled NO
[    26.863] (II) modeset(0): Output None-1 has no monitor section
[    26.863] (II) modeset(0): EDID for output None-1
[    26.863] (II) modeset(0): Printing probed modes for output None-1
[    26.863] (II) modeset(0): Modeline "1024x768"x60.0   47.19  1024 1024 1024 1024  768 768 768 768 (46.1 kHz eP)
[    26.872] (II) IGLX: Loaded and initialized swrast
[    26.872] (II) GLX: Initialized DRISWRAST GL provider for screen 0

Tada.

Apparently the "nvidia_drm.modeset=1" hack was removed from the 6.12 kernels. /grrr
Add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters

RedArcher · Yesterday 12:35:34

# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot:  amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

Restarting machine...

1. The screen tends to have a purple or pink colour.
2. The screen gets blanked (black) for a secind or two, sometimes).

Problem persists, even after removing nvidia_drm.modeset=1.

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw loglevel=3 quiet

$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
None-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*+

Xorg

$ cat .local/share/xorg/Xorg.0.log  | curl -F 'file=@-' 0x0.st
http://0x0.st/XR7A.txt

If the issue of corrupted kernel space has been solved, then I would want to switch back to the non-proprietary driver nouveau.

Last edited by RedArcher (Yesterday 12:52:55)

seth · Yesterday 18:38:32

http://0x0.st/XR7A.txt

[    49.400] (==) Log file: "/home/admin/.local/share/xorg/Xorg.0.log", Time: Sun Dec  1 14:38:10 2024
[    49.400] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=80f8e3f3-51ff-4a07-a8c6-62a9a416466b rw loglevel=3 quiet
[    49.408] (II) Platform probe for /sys/devices/pci0000:00/0000:00:03.1/0000:1c:00.0/simple-framebuffer.0/drm/card0

"initcall_blacklist=simpledrm_platform_driver_init" is not in the kernel parameters, the simplydumb device acts up.
nvidia_drm.modeset=1 is meanwhile default anyway but I'd just keep it there in case the hack returns.

In doubt use the LTS kernel (though "initcall_blacklist=simpledrm_platform_driver_init" should absolutely work)

Arch Linux

#1 2024-11-30 12:19:41

xandr doesnt recognize native 2560x1440p resolution

#2 2024-11-30 12:30:08

Re: xandr doesnt recognize native 2560x1440p resolution

#3 2024-11-30 12:34:09

Re: xandr doesnt recognize native 2560x1440p resolution

#4 2024-11-30 15:02:36

Re: xandr doesnt recognize native 2560x1440p resolution

#5 2024-11-30 19:26:55

Re: xandr doesnt recognize native 2560x1440p resolution

#6 Yesterday 07:21:19

Re: xandr doesnt recognize native 2560x1440p resolution

#7 Yesterday 07:53:24

Re: xandr doesnt recognize native 2560x1440p resolution

#8 Yesterday 09:17:21

Re: xandr doesnt recognize native 2560x1440p resolution

#9 Yesterday 11:49:02

Re: xandr doesnt recognize native 2560x1440p resolution

#10 Yesterday 12:35:34

Re: xandr doesnt recognize native 2560x1440p resolution

#11 Yesterday 18:38:32

Re: xandr doesnt recognize native 2560x1440p resolution

Board footer