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#71367 - [nvidia] using version 465.31-11 Xorg fails to correctly detect multiple displays

Attached to Project: Arch Linux
Opened by Simon Tunnat (imon) - Saturday, 26 June 2021, 13:23 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 15 July 2021, 14:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After updating nvidia to version 465.31-11 Xorg / xrandr fails with the following error:


X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 21 (RRSetCrtcConfig)
Serial number of failed request: 74
Current serial number in output stream: 74


The issue only occurs on the first login. After logging out (including stopping Xorg) and a login in again the command works normally again.

After downgrading nvidia to version 465.31-10 the issues does NOT occur at all anymore.

I also noticed that there no output regarding the external outputs in Xorg.log.
I added log files for the first (failing) and the for second (successful) login.

Another thing I noticed: the TTY login screen was shown on all outputs before the first login and only shown on the internal display after the logout.


Additional info:

The device with the the issues is a HP ZBOOK with a Intel and an Nvidia GPU.
I'm not using a full desktop manager, only the i3 window manager with a lot of custom scripts.


Command that was executed:

xrandr --output eDP1 --mode 1920x1080 --left-of DP-1-2 --rotate normal --output DP-1-2 --mode 1920x1080 --left-of DP-1-5 --rotate normal --output DP-1-5 --mode 1920x1080 --rotate normal --dpi 96

   Xorg.first-login.log (39.2 KiB)
   Xorg.second-login.log (40.6 KiB)
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 15 July 2021, 14:28 GMT
Reason for closing:  Upstream
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 04 July 2021, 20:55 GMT
Can't reproduce and I'm not sure we can somehow confirm this to be a packaging issue. Does the issue still occur?
Comment by Simon Tunnat (imon) - Saturday, 10 July 2021, 10:23 GMT
I still have that issue with Nvidia version 465.31-14.
Still the only solution I could find was to revert back to version 465.31-10.

I also tried to reproduce the bug on a Lenovo P52 notebook with no success.
Seems to be very hardware specific.
Comment by Simon Tunnat (imon) - Saturday, 10 July 2021, 10:24 GMT
Also the full model name of the affected notebook is the following:

HP ZBook Fury 15 G7
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 15 July 2021, 14:27 GMT
Sorry, I don't think there's anything we can do here at all. This is a proprietary binary blob after all. I looked into this briefly but I think this is not a packaging problem. At this point, you're probably better of telling NVIDIA about this directly on their forums.

Loading...