Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#75020 - xrandr only reports a single resolution

Attached to Project: Arch Linux
Opened by Khurram Mahmood (makh) - Friday, 10 June 2022, 11:27 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 31 August 2022, 06:57 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 310mm x 170mm
1920x1080 60.00*+ 48.00
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Additional info:
* package version(s)
System:
Host: archtpe14 Kernel: 5.15.44-1-lts arch: x86_64 bits: 64 Desktop: Xfce
v: 4.16.0 Distro: Arch Linux
Machine:
Type: Laptop System: LENOVO product: 20RA007TUE v: ThinkPad E14
serial: <superuser required>
Mobo: LENOVO model: 20RA007TUE serial: <superuser required> UEFI: LENOVO
v: R16ET30W (1.16 ) date: 01/17/2021
Graphics:
Device-1: Intel CometLake-U GT2 [UHD Graphics] driver: i915 v: kernel
Device-2: AMD Lexa [Radeon 540X/550X/630 / RX 640 E9171 MCM]
driver: amdgpu v: kernel
Device-3: Chicony Integrated Camera type: USB driver: uvcvideo
Display: server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2 driver: X:
loaded: intel,modesetting gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 22.1.0
* config and/or log files etc.
* link to upstream bug report, if any


Steps to reproduce:
run the xrandr command; also the Display control of xfce reports only one resoltion
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 31 August 2022, 06:57 GMT
Reason for closing:  Upstream
Comment by Khurram Mahmood (makh) - Thursday, 16 June 2022, 07:43 GMT
Hi,
I tested my laptop using current grml to find xrandr values as:
[code]
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1920x1080 60.00*+ 59.97 59.96 59.93 48.00
1680x1050 59.95 59.88
1600x1024 60.17
1400x1050 59.98
1600x900 59.99 59.94 59.95 59.82
1280x1024 60.02
1440x900 59.89
1400x900 59.96 59.88
1280x960 60.00
1440x810 60.00 59.97
1368x768 59.88 59.85
1360x768 59.80 59.96
1280x800 59.99 59.97 59.81 59.91
1152x864 60.00
1280x720 60.00 59.99 59.86 59.74
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
1024x576 59.95 59.96 59.90 59.82
960x600 59.93 60.00
960x540 59.96 59.99 59.63 59.82
800x600 60.00 60.32 56.25
840x525 60.01 59.88
864x486 59.92 59.57
800x512 60.17
700x525 59.98
800x450 59.95 59.82
640x512 60.02
720x450 59.89
700x450 59.96 59.88
640x480 60.00 59.94
720x405 59.51 58.99
684x384 59.88 59.85
680x384 59.80 59.96
640x400 59.88 59.98
576x432 60.06
640x360 59.86 59.83 59.84 59.32
512x384 60.00
512x288 60.00 59.92
480x270 59.63 59.82
400x300 60.32 56.34
432x243 59.92 59.57
320x240 60.05
360x202 59.51 59.13
320x180 59.84 59.32
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)

[/code]

But in arch I get only one resolution option.

Thankyou
Comment by Federico (fedev) - Thursday, 07 July 2022, 11:22 GMT
I'm experiencing something similar and I'd say it is not an xrandr problem but a problem related to the Kernel.

For the max resolution for my display xrandr returns (kernel 5.15.52-1-lts):

2560x1440 165.00*+ 40.00 +

same laptop but with kernel 5.18.9-arch1-1 returns:

2560x1440 40.00*+

and just to be clear, all resolutions are affected. Also, it is not just xrandr the one hit by this issue, gnome (wayland or xorg) both report the same refresh rate as xrandr. The journal "modeline" entries are different between both kernels. It shows all correct resolutions and refresh rates in the LTS kernel but not so for 5.18.9. In 5.18.9 there is an additional error stating:

"modeset(0): failed to set mode: Invalid argument"

This wouldn't bother me so much if not because I'm not able to change to any screen resolution under kernel 5.18.9-arch1-1. Attempting to change results in a black screen which eventually returns back to the same resolution it was set to before. I can only change screen resolutions under the mentioned LTS kernel.

Attached are the outputs of xrandr with both kernels for comparison.
Comment by Toolybird (Toolybird) - Sunday, 31 July 2022, 04:10 GMT
Is this still happening? Problems with graphics drivers and/or kernel issues are best reported upstream or debugged through forums/IRC/etc. Arch cannot do much with the info provided. In the case of @fedev, it appears to be a kernel regression so have you considered bisection? Or maybe try latest -rc kernel?
Comment by Federico (fedev) - Sunday, 31 July 2022, 07:05 GMT
I went on to the IRC channel and asked around. It seems there was a change made which was supposed to select the highest available refresh rate for the reported resolutions. The problem is that at the same time, the list being used changed the way the refresh rates were reported. Resulting in the lowest refresh rate showing.

This by the way affects only Intel graphics. I was told maintainers of the driver are aware of this, might just take time to have it fixed. The alternative is to export the edid list (from the kernel that works) and set the new kernel to use it. I believe this workaround was added to the wiki.
Comment by Toolybird (Toolybird) - Wednesday, 31 August 2022, 06:56 GMT
I'm going to assume if this isn't resolved with latest kernels and/or mesa, it's covered by the relevant wiki entry [1]

[1] https://wiki.archlinux.org/title/Xrandr#Adding_undetected_resolutions

Loading...