http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c29 --- Comment #29 from Daniel Dadap <ddadap@nvidia.com> --- (In reply to Christian Eggers from comment #28)
I didn't found a 471.92 version on the NVIDIA driver archive. Do you mean 461.92 (works fine) or 471.68 (just tested, doesn't work)?
I meant 471.92: https://www.nvidia.com/download/driverResults.aspx/171473/en-us If you tried 471.68, and found it also doesn't work, that's sufficient. To be clear: you are saying that you are seeing the same behavior (no displays are working, internal or external, with or without the dock) in Windows with 471.68 as you were with 472.12, correct?
You don't need a TB dock! The notebook alone is enough for having trouble.
I was referring to the originally reported issue on Linux, which according to my understanding only manifested when external displays were connected. I suspect that the different behavior you are seeing on Linux and Windows are different manifestations of the same regression in the NVIDIA driver's shared DisplayPort code. The other bug I was referring to in the internal bug tracker seemed to be a different regression, and had been narrowed down to having been introduced between 471.68 and 472.12, which is why I was curious whether you'd see behavior more similar to what you're seeing on Linux with a slightly earlier Windows driver. My understanding of the original bug you reported on Linux was that the internal display works when there are no external displays, and the internal display does not work when there are two external displays connected via the dock. It wasn't clear to me whether you are able to reproduce the same problem with only a single external display. Please correct my understanding if it is mistaken. In any case, it does seem that on Windows you run into problems with the notebook alone, but until we are completely sure that the Windows and Linux issues are related, I'd still want to attempt to get a proper reproduction of the issue as you originally reported it on Linux. -- You are receiving this mail because: You are on the CC list for the bug.