CentOS - Jan 2018 - Nvidia maximum pixel clock issue in kmod-nvidia-384.98

On Wed Jan 03 07:43:04 PM, Phil Perry wrote:
> > On CentOS 7 I'm running into an issue with the latest nvidia
driver
> > from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64
> > This driver version seem to introduce issue in detecting video modes
> > when a monitor is connected using DVI. As soon as the machine attempts
> > to start X, nothing happens and the monitor goes into sleep mode
> > reporting that it has 'no signal'.
> > 
> > It is interesting because it occurs with several monitors, but only
> > when they are connected through DVI. When using VGA it works like a
> > charm.
> > Also it did work without problems with the previous driver version
> > (kmod-nvidia-384.90-1.el7_4.elrepo.x86_64), with the exact same setup.
> > 
> > In this case the issue occurs with an Nvidia NVS 315. I don't know
if
> > other nvidia cards are affected.
I can confirm that this happens with the driver downloaded from NVIDIA.
I had to fall back to the .90 driver to get it to work for all my
NVS 315s (with dual DVI) running on 7.4 / 6.9.

Cheers,
Zube

On 03/01/18 20:14, Zube wrote:
> On Wed Jan 03 07:43:04 PM, Phil Perry wrote:
> 
>>> On CentOS 7 I'm running into an issue with the latest nvidia
driver
>>> from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64
>>> This driver version seem to introduce issue in detecting video
modes
>>> when a monitor is connected using DVI. As soon as the machine
attempts
>>> to start X, nothing happens and the monitor goes into sleep mode
>>> reporting that it has 'no signal'.
>>>
>>> It is interesting because it occurs with several monitors, but only
>>> when they are connected through DVI. When using VGA it works like a
>>> charm.
>>> Also it did work without problems with the previous driver version
>>> (kmod-nvidia-384.90-1.el7_4.elrepo.x86_64), with the exact same
setup.
>>>
>>> In this case the issue occurs with an Nvidia NVS 315. I don't
know if
>>> other nvidia cards are affected.
> 
> I can confirm that this happens with the driver downloaded from NVIDIA.
> I had to fall back to the .90 driver to get it to work for all my
> NVS 315s (with dual DVI) running on 7.4 / 6.9.
> 
Thank you for the confirmation. I found a similar report on debian also 
relating to NVS315 with the 384.98 driver so I'm guessing this is 
hardware specific:

https://www.mail-archive.com/debian-bugs-dist at
lists.debian.org/msg1570324.html

I couldn't find any reports upstream at nvidia so am unsure if they are 
aware of the issue. For reference, my GK208 [GeForce GT 730] in my test 
system is unaffected by the issue and is working fine with the 384.98 
driver over DVI.

There is an updated version 387.34 short-lived branch driver available 
in the elrepo testing repository that you could test to see whether the 
issue has been fixed in this latest release (only available for el7 
currently).

On Thu, January 4, 2018 05:22, Phil Perry wrote:
> I couldn't find any reports upstream at nvidia so am unsure if they are
> aware of the issue. For reference, my GK208 [GeForce GT 730] in my test
> system is unaffected by the issue and is working fine with the 384.98
> driver over DVI.
keep in mind that an nVIDIA GeForce is a consumer graphics device and the
NVS xxx series device is a business product similar to the nVIDIA Quadro
...
(with Windows they have different video drivers ...)

On Thu, Jan 4, 2018 at 5:22 AM, Phil Perry <pperry at elrepo.org>
wrote:
> On 03/01/18 20:14, Zube wrote:
>>
>> I can confirm that this happens with the driver downloaded from NVIDIA.
>> I had to fall back to the .90 driver to get it to work for all my
>> NVS 315s (with dual DVI) running on 7.4 / 6.9.
Thanks. For reference, I did the same test. With the driver downloaded
from NVIDIA the issues also occurs in my case.
> I couldn't find any reports upstream at nvidia so am unsure if they are
> aware of the issue.
Where do you look for this at nvidia, in the community forums? Or is
there another publicly available bug tracking system? (which I was
unable to find)
> There is an updated version 387.34 short-lived branch driver available in
> the elrepo testing repository that you could test to see whether the issue
> has been fixed in this latest release (only available for el7 currently).
Surprisingly, I couldn't reproduce the issue anymore. Therefore at
first sight it seems to be fixed in the 387.34 driver.

I posted a question at nvidia anyway:
https://devtalk.nvidia.com/default/topic/1028268/linux/nvidia-maximum-pixel-clock-issue-in-kmod-nvidia-384-98/
(although I'm not sure it is the right place, still having some issues
finding my way at nvidia.com, other suggestions or directions are
welcome of course)

Will short-lived drivers ever make it into the official elrepo
repository? Or will only the long-lived drivers be included in the
official repository?