[SOLVED] nvidia drivers failed to detect external monitor

X1aomu · 2018-09-29 02:15:27

last night i upgrade my whole system then poweroff, and I noticed that linux kernel and nvidia driver were listed in the upgrade list.
Today I found that my external monitor connected by HDMI was not detected xrandr.

I almostly upgrade my whole system every day. Thus it must caused by recently update. My current packages versions are:
linux-4.18.10.arch1-1
nvidia-410.57-2

Update:
Problem solved.
I eventually found there are packages name nvidia-390xx-* in the official repository. I installed them and then everything goes back.
I also visited nvidia's offcial website to query my hardware's supported drivers. It's 390, not 410.
So things is clear, the new vesion driver does not support my hardware. My 960M is sticked to verson 390...

2nd Update:
It's not clear to say the new version driver doesn't support my card. I made a little bit change in /usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf then version 410 works fine with my hardware. See https://bbs.archlinux.org/viewtopic.php … 1#p1810281
But I'm not sure that this work around won't break someones usercase.

Last edited by X1aomu (2018-09-30 00:43:11)

jaergenoth · 2018-09-29 07:18:06

410 still supports GTX 960M. You can see it here in the "Supported products" tab: https://www.nvidia.co.uk/download/drive … 7949/en-uk

410 did break my setup too, xrandr doesn't list it anymore when listing providers (`xrandr --listproviders´), and I can't use it as a PRIME output anymore.
Had to revert back to 396.54.

jaergenoth · 2018-09-29 07:28:54

Now that I took a better look at this, it seems this commit removed the PrimaryGPU option from "/usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf":
https://git.archlinux.org/svntogit/pack … f64b5f0441

Adding it back resolved my problem, maybe this will help you too. I'm now running 410 without any problems.

X1aomu · 2018-09-29 07:35:33

jaergenoth wrote:

410 still supports GTX 960M. You can see it here in the "Supported products" tab: https://www.nvidia.co.uk/download/drive … 7949/en-uk
410 did break my setup too, xrandr doesn't list it anymore when listing providers (`xrandr --listproviders´), and I can't use it as a PRIME output anymore.
Had to revert back to 396.54.

That's strange. What I visited is https://www.nvidia.com/Download/index.aspx. Choose OS Linux 64-bit with 960M, then the result is 390.87.
I don't know if 410 for linux will support 900M Series later. But for now, the only thing I can do is stay in nvidia-390xx.
I have a feeling of being abandoned by Nvidia. Sad

X1aomu · 2018-09-29 07:48:28

jaergenoth wrote:

Now that I took a better look at this, it seems this commit removed the PrimaryGPU option from "/usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf":
https://git.archlinux.org/svntogit/pack … f64b5f0441
Adding it back resolved my problem, maybe this will help you too. I'm now running 410 without any problems.

Excellent! I just tried it and everything is fine. Thank you very much.

xuanrui · 2018-09-29 07:50:25

Apparently, just the NVIDIA UK website claims that 410.57 has support for 960M, but not the US website. It seems that not even NVIDIA is sure what hardware does 410.57 support! We might need to get an official answer from NVIDIA first. https://www.nvidia.com/download/driverR … 8279/en-us.

If you didn't upgrade to 410, DO NOT! It will likely break your system. After updating, I began getting really poor graphic performance: turns out my system was falling back to the integrated Intel graphics, since 410.57 apparently broke support for my hardware. I installed 390xx instead and everything worked fine again. Since probably very few people are using the RTX 20 series, IMO the logical thing to do here is probably revert back to 396 and provide 410 in a separate package.

jaergenoth wrote:

410 still supports GTX 960M. You can see it here in the "Supported products" tab: https://www.nvidia.co.uk/download/drive … 7949/en-uk
410 did break my setup too, xrandr doesn't list it anymore when listing providers (`xrandr --listproviders´), and I can't use it as a PRIME output anymore.
Had to revert back to 396.54.

Scimmia · 2018-09-29 14:35:23

The US site does list it, it's just a beta driver.
https://www.nvidia.com/download/find.aspx

Last edited by Scimmia (2018-09-29 14:35:31)

V1del · 2018-09-29 15:39:16

The likely real reason is that the drop in files for Xorg have been adjusted. If you were using PRIME without your own config you can either do the one outlined in the Optimus article, or readd the PrimaryGPU directive as mentioned by jaergenoth .

This is a bit of a weird case, with the current situation this can't be relevantly fixed without breaking someones potential usecase. Maybe the config files should be split into a nvidia-optimus-support package or similar...

X1aomu if this is solved for you please mark the topic as such by editing the title, it's likely too long remove some unnecessary fluff like the after last upgrade. https://wiki.archlinux.org/index.php/Co … ow_to_post

Last edited by V1del (2018-09-29 15:44:25)

xuanrui · 2018-09-30 05:51:36

Can confirm that adding the PrimaryGPU line fixes my problem. Maybe this should be reported to the package managers and added back to the package.

V1del · 2018-09-30 09:27:58

Follow the discussion in FS60102 for rationale on why it was changed in the first place (to fix someone's usecase) and why the change by extension broke another usecase.

FWIW as I'm not using this setup, can any of you test if adding the xorg.conf described in https://wiki.archlinux.org/index.php/NV … ing_nvidia makes it work again, even without having PrimaryGPU set?

jaergenoth · 2018-09-30 15:53:23

V1del wrote:

Follow the discussion in FS60102 for rationale on why it was changed in the first place (to fix someone's usecase) and why the change by extension broke another usecase.
FWIW as I'm not using this setup, can any of you test if adding the xorg.conf described in https://wiki.archlinux.org/index.php/NV … ing_nvidia makes it work again, even without having PrimaryGPU set?

This does work still, I remember using that before 10-nvidia-drm-outputclass.conf was added to nvidia-utils.

X1aomu · 2018-10-01 14:37:03

V1del wrote:

Follow the discussion in FS60102 for rationale on why it was changed in the first place (to fix someone's usecase) and why the change by extension broke another usecase.
FWIW as I'm not using this setup, can any of you test if adding the xorg.conf described in https://wiki.archlinux.org/index.php/NV … ing_nvidia makes it work again, even without having PrimaryGPU set?

It does work for me. Now I consider it as a better choice as it will not break package manager.

Arch Linux

#1 2018-09-29 02:15:27

[SOLVED] nvidia drivers failed to detect external monitor

#2 2018-09-29 07:18:06

Re: [SOLVED] nvidia drivers failed to detect external monitor

#3 2018-09-29 07:28:54

Re: [SOLVED] nvidia drivers failed to detect external monitor

#4 2018-09-29 07:35:33

Re: [SOLVED] nvidia drivers failed to detect external monitor

#5 2018-09-29 07:48:28

Re: [SOLVED] nvidia drivers failed to detect external monitor

#6 2018-09-29 07:50:25

Re: [SOLVED] nvidia drivers failed to detect external monitor

#7 2018-09-29 14:35:23

Re: [SOLVED] nvidia drivers failed to detect external monitor

#8 2018-09-29 15:39:16

Re: [SOLVED] nvidia drivers failed to detect external monitor

#9 2018-09-30 05:51:36

Re: [SOLVED] nvidia drivers failed to detect external monitor

#10 2018-09-30 09:27:58

Re: [SOLVED] nvidia drivers failed to detect external monitor

#11 2018-09-30 15:53:23

Re: [SOLVED] nvidia drivers failed to detect external monitor

#12 2018-10-01 14:37:03

Re: [SOLVED] nvidia drivers failed to detect external monitor

Board footer