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!
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!
FS#76202 - [nvidia] Don't recognize second monitor on 520.56.06-3
Attached to Project:
Arch Linux
Opened by anton (pseudoterm-slave) - Friday, 14 October 2022, 11:07 GMT
Last edited by Toolybird (Toolybird) - Saturday, 22 October 2022, 20:26 GMT
Opened by anton (pseudoterm-slave) - Friday, 14 October 2022, 11:07 GMT
Last edited by Toolybird (Toolybird) - Saturday, 22 October 2022, 20:26 GMT
|
DetailsAppears after updating to 520.56.06-3
Second monitor is connected with Displayport. It is visible in nvidia-settings, but there are no image though. The problem was solved by using nvidia-modeprobe, but it appears again after reboot. Gtx1050 2gb graphic card. $ sudo dmesg | grep nvidia [ 4.289395] nvidia: loading out-of-tree module taints kernel. [ 4.289408] nvidia: module license 'NVIDIA' taints kernel. [ 4.312689] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 4.734338] nvidia-nvlink: Nvlink Core is being initialized, major device number 237 [ 4.735583] nvidia 0000:26:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [ 4.916373] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint. [ 4.938624] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 520.56.06 Thu Oct 6 21:22:53 UTC 2022 [ 5.073287] nvidia-uvm: Loaded the UVM driver, major device number 235. [ 5.073310] [drm] [nvidia-drm] [GPU ID 0x00002600] Loading driver [ 5.073313] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:26:00.0 on minor 0 [ 11.130658] audit: type=1100 audit(1665744516.373:44): pid=619 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="nvidia" exe="/usr/bin/login" hostname=nikitapc addr=? terminal=/dev/tty1 res=failed' Steps to reproduce: Update nvidia drivers and reboot |
This task depends upon
Closed by Toolybird (Toolybird)
Saturday, 22 October 2022, 20:26 GMT
Reason for closing: None
Additional comments about closing: "The problem was solved"
Saturday, 22 October 2022, 20:26 GMT
Reason for closing: None
Additional comments about closing: "The problem was solved"
Comment by Sven-Hendrik Haase (Svenstaro) -
Tuesday, 18 October 2022, 22:48 GMT
I'm not sure this is a packaging problem. We didn't change anything in this regard. Can you report this upstream?
Comment by anton (pseudoterm-slave) -
Saturday, 22 October 2022, 07:47 GMT
I found the gist of problem. I use ohmyzsh as default shell. Since last update when I execute startx from it, the problem appears. I tried to execute startx from bash, and now the second monitor works fine.
Comment by Toolybird (Toolybird) -
Saturday, 22 October 2022, 20:26 GMT
It makes no sense at all that a change of shell could cause this...oh well.