[Bug 1189165] New: Internal laptop screen cannot be enabled after upgrading to Nvdia 470.57.02-lp152.43.1
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 Bug ID: 1189165 Summary: Internal laptop screen cannot be enabled after upgrading to Nvdia 470.57.02-lp152.43.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs@suse.de Reporter: ceggers@arri.de QA Contact: sndirsch@suse.com Found By: --- Blocker: --- After the latest Nvdia drivers from 2021-07-26 have been installed via automatic software upgrades, my internal laptop screen cannot be enabled anymore while the laptop is connected to the thunderbolt docking station. nvidia-settings, KDE system-settings and xrandr only show the two external screens connected to the docking station. The RPM repository http://download.nvidia.com/opensuse/leap/15.2/ misses older versions of the driver, so how can I downgrade to the previous version (which worked fine for me)?
xrandr Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 16384 x 16384 VGA-0 disconnected (normal left inverted right x axis y axis) DP-5.1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 1680x1050 59.95 1600x1200 60.00 1600x900 60.00 1440x900 59.89 1280x1024 60.02 1280x800 59.81 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-5.2 connected 1920x1200+1920+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 1680x1050 59.95 1600x1200 60.00 1600x900 60.00 1440x900 59.89 1280x1024 60.02 1280x800 59.81 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) DP-6 disconnected (normal left inverted right x axis y axis)
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c1 --- Comment #1 from Stefan Dirsch <sndirsch@suse.com> --- Unfortunately we can only provide the latest driver version as RPM. But you can install a previous driver version manually if needed. Download it here: https://www.nvidia.com/en-us/drivers/unix/linux-amd64-display-archive/ -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c2 --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> --- This is the one we packaged before. 460.84 https://www.nvidia.com/Download/driverResults.aspx/175875/en-us -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS Assignee|gfx-bugs@suse.de |sndirsch@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c3 --- Comment #3 from Stefan Dirsch <sndirsch@suse.com> --- In case you get this driver working, the output of xrandr with that one would be useful.. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c4 --- Comment #4 from Christian Eggers <ceggers@arri.de> --- (In reply to Stefan Dirsch from comment #3)
In case you get this driver working, the output of xrandr with that one would be useful..
Can I package the previous version myself into RPM format? If not, shall I first uninstall the RPM packages before running the .run file from Nvidia? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c5 --- Comment #5 from Stefan Dirsch <sndirsch@suse.com> --- Oh. The result of running nvidia-bug-report.sh would be very much appreciated. And please, before installing the previous driver manually please uninstall the nvidia pacakges: nvidia-computeG05 nvidia-glG05 x11-video-nvidiaG05 nvidia-gfxG05-kmp-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c6 --- Comment #6 from Christian Eggers <ceggers@arri.de> --- Created attachment 851573 --> http://bugzilla.opensuse.org/attachment.cgi?id=851573&action=edit File generated by nvidia-bug-report.sh -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c7 --- Comment #7 from Stefan Dirsch <sndirsch@suse.com> --- (In reply to Christian Eggers from comment #4)
(In reply to Stefan Dirsch from comment #3)
In case you get this driver working, the output of xrandr with that one would be useful..
Can I package the previous version myself into RPM format? If not, shall I first uninstall the RPM packages before running the .run file from Nvidia?
In theory yes, but you would neeed RPM packaging skills and knowledge how to use our build service. Project: X11:Drivers:Video Package: nvidia-gfxG05 You would need to checkout with osc a version for the old drvier and manually build it on your system. Build instructions are in the README file. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c8 --- Comment #8 from Christian Eggers <ceggers@arri.de> --- Step 1: uninstall nvidia RPMs, reboot --> NOUVEAU driver is active (at the first look, everything is fine now, all three monitors are working)
xrandr Screen 0: minimum 320 x 200, current 5630 x 1650, maximum 16384 x 16384 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) eDP-1 connected 1920x1080+3710+570 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.02*+ 47.99 1680x1050 60.00 1400x1050 60.00 1280x1024 59.95 1280x960 59.99 1152x864 59.97 1024x768 59.95 800x600 59.96 640x480 59.94 720x400 59.97 640x400 59.96 640x350 59.84 DP-3 disconnected (normal left inverted right x axis y axis) VGA-1 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 1600x1200 60.00 1680x1050 59.95 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x800 59.81 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-5 connected 1920x1200+2130+20 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 1600x1200 60.00 1680x1050 59.95 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x800 59.81 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-6 disconnected (normal left inverted right x axis y axis)
next step: install nvidia-460 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c9 --- Comment #9 from Christian Eggers <ceggers@arri.de> --- Step 2: Install nvidia driver 460 (.run file): - reboot (once) after the preinstall script was executed (for disabling the nouveau driver) --> got the fbdev driver after reboot, internal monitor only - started the installer again, didn't let the installer modify my xorg.conf - reboot --> nvidia driver is now active all three screen are working again So my problem seems to be a regression between 460 and 470.
xrandr Screen 0: minimum 8 x 8, current 5630 x 1650, maximum 16384 x 16384 VGA-0 disconnected (normal left inverted right x axis y axis) DP-5.1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 1680x1050 59.95 1600x1200 60.00 1600x900 60.00 1440x900 59.89 1280x1024 60.02 1280x800 59.81 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-5.2 connected 1920x1200+2130+20 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 1680x1050 59.95 1600x1200 60.00 1600x900 60.00 1440x900 59.89 1280x1024 60.02 1280x800 59.81 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected 1920x1080+3710+570 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.02*+ 47.99 DP-5 disconnected (normal left inverted right x axis y axis) DP-6 disconnected (normal left inverted right x axis y axis)
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c10 --- Comment #10 from Stefan Dirsch <sndirsch@suse.com> --- Indeed. It's interesting that nvidia detects the internal screen as DP-4 and not as eDP-X as other drivers do. One thing I changed for 470.xx in addition was to enable modeset option for nvidia-drm module. It's needed for Wayland support. Maybe that's the culprit and not the driver update. Could you give this a try to verify this? cat > /etc/modprobe.d/50-nvidia-default.conf << EOF options nvidia-drm modeset=1 EOF You would need to rebuild initrd I guess. mkinitrd -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c11 --- Comment #11 from Stefan Dirsch <sndirsch@suse.com> --- I mean with the 460.xx driver, which you currently have installed. If with that configuration internal display is missing again, we would have found the culprit. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c12 --- Comment #12 from Christian Eggers <ceggers@arri.de> --- (In reply to Stefan Dirsch from comment #11)
I mean with the 460.xx driver, which you currently have installed. If with that configuration internal display is missing again, we would have found the culprit.
I simply (temporarly) added "nvidia-drm.modeset=1" to the kernel command line within the grub shell. If I remember correctly, modprobe uses this information also for non-builtin modules. Verify:
sudo cat /sys/module/nvidia_drm/parameters/modeset Y
Result: All three monitors are still working fine. --> seems to be related to the 470 driver itself. If required, I can make the reverse test (470 RPM with modeset=0). But this had to wait until it's weekend. Thank you very much! Christian -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c13 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddadap@nvidia.com Summary|Internal laptop screen |Regression in nVidia |cannot be enabled after |470.57.02 since 460.84: |upgrading to Nvdia |Internal laptop screen |470.57.02-lp152.43.1 |cannot be enabled any | |longer --- Comment #13 from Stefan Dirsch <sndirsch@suse.com> --- Thanks a lot! No need to reverse test and verify the resgression. It's now obvious to me. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c15 --- Comment #15 from Christian Eggers <ceggers@arri.de> --- (In reply to Stefan Dirsch from comment #14)
Meanwhile driver 470.63.01 is available, but I haven't packaged it yet. So you would have to use the .run file to install it manaully and verify if it fixes the regression in 470.57.02.
With driver 470.63.01, the problem still persists. Additionally this shows that the bug is not related to RPM packaging. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c16 --- Comment #16 from Stefan Dirsch <sndirsch@suse.com> --- Thanks a lot for verification! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c18 --- Comment #18 from Christian Eggers <ceggers@arri.de> --- (In reply to Stefan Dirsch from comment #17)
470.74 meanwhile available (also as packages) ...
Unfortunately the bug did not disappear. After uninstalling version 460 and installing the 470.74 RPMs (and several reboots), the internal laptop screen still does not work. So I switched back to 460 again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c19 --- Comment #19 from Stefan Dirsch <sndirsch@suse.com> --- Thanks a lot for retesting and providing your feedback! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c20 --- Comment #20 from Daniel Dadap <ddadap@nvidia.com> --- Thanks for reporting this issue. I've filed NVIDIA internal bug 3391094 to track it; hopefully we'll be able to locate the same model of notebook (Dell Precision 7510) and docking station (HP Thunderbolt 3Dock) internally, or at the very least, a combination of notebook + dock that can reproduce the issue. Do you also see the issue if the displays are connected directly to the notebook? Can it reproduce with only one display on the docking station or are two required? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c21 --- Comment #21 from Stefan Dirsch <sndirsch@suse.com> --- @Daniel Thanks for tracking this issue on your side! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c22 --- Comment #22 from Christian Eggers <ceggers@arri.de> --- (In reply to Daniel Dadap from comment #20)
Do you also see the issue if the displays are connected directly to the notebook? Can it reproduce with only one display on the docking station or are two required? I need extra cables for this (the Laptop has one HDMI and one Mini-DP). I'll test as soon I get the cables.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c23 --- Comment #23 from Daniel Dadap <ddadap@nvidia.com> --- (In reply to Christian Eggers from comment #22)
I need extra cables for this (the Laptop has one HDMI and one Mini-DP). I'll test as soon I get the cables.
Okay, thanks. Since the external displays are currently connected via DP-MST in the docking station, you are likely to see different behavior with directly connected ports, particularly with the HDMI port, which will use TMDS rather than DP. No need to obtain the additional cables if you don't already have them on the way; I am hoping we will be able to reproduce this internally at NVIDIA soon. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c24 --- Comment #24 from Daniel Dadap <ddadap@nvidia.com> --- Another useful experiment, if you are already set up to boot Windows on this system (no need to try this if you don't already have Windows installed), would be to see if the same behavior regression occurs on Windows 470 vs. 460 drivers. The Linux and Windows drivers share most of the driver code that involve DisplayPort, so it could be useful to see if the problem is in the common DP code or in the Linux/X11 specific portions. -- You are receiving this mail because: You are on the CC list for the bug.
Another useful experiment, [...] would be to see if the same behavior regression occurs on Windows 470 vs. 460 drivers. Unfortunately this test became a quite lengthy procedure. At the start of the installation of 472.12 (just after the decompression was finished), all 3 screens switched off and stayed in this state. After waiting 30 minutes, I shut down the laptop by shortly pressing the power button. After a reboot (and disconnecting the docking station), the laptop screen again switched off during
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c25 --- Comment #25 from Christian Eggers <ceggers@arri.de> --- (In reply to Daniel Dadap from comment #24) the Windows start procedure. I wasn't able to get any display running anymore (neither the internal one, nor the displays connected to the docking station, nor a TV directly on HDMI). I tried hitting Ctrl+F8 during next reboot in order to enter Windows protected mode, but I had no success. The only way to get the display running again was to boot the Windows installation via VirtualBox from Linux. After that I could uninstall the 472 driver via the Control Panel. After another reboot (without VirtualBox) the system started with SVGA resolution and I could revert to the "previous" driver (27.21.14.5241, originally installed by Windows Update) via the Device Manager. I repeated the procedure (without the docking station) with the same result: ---> 472.12 is not usable at all on Dell Precision 7510. <--- As a last step I tried 461.92. The installation blocked quite long when updating the driver, but after that the process finished without any problems. After rebooting and reconnecting the docking station, all 3 screens are still working. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c26 --- Comment #26 from Daniel Dadap <ddadap@nvidia.com> --- Thanks for attempting that experiment. This does seem to support the idea of a regression in the core DisplayPort code between 460 and 470 on this particular system, with the symptom being rather more dramatic on Windows. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c27 --- Comment #27 from Daniel Dadap <ddadap@nvidia.com> --- While searching the NVIDIA internal bug database for reports of similar issues on Windows, I found that 472.12 in particular had a major regression that renders several notebooks completely unusable in Windows, compared to 471.92. If you have the opportunity to test 471.92 on Windows, that would help isolate whether the 472.12 problems you ran into are related to the original bug you observed on Linux. In the meantime, NVIDIA staff have attempted to reproduce the originally reported problem with available notebooks and TB docks, but were unable to. We are currently attempting to locate hardware that matches your configuration more closely in the hopes of being able to reproduce the problem internally. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c28 --- Comment #28 from Christian Eggers <ceggers@arri.de> --- (In reply to Daniel Dadap from comment #27)
While searching the NVIDIA internal bug database for reports of similar issues on Windows, I found that 472.12 in particular had a major regression that renders several notebooks completely unusable in Windows, Nice to hear this. Without my Linux system, I would be in severe trouble (this is my company's device).
compared to 471.92. If you have the opportunity to test 471.92 on Windows, that would help isolate whether the 472.12 problems you ran into are related to the original bug you observed on Linux. 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)?
In the meantime, NVIDIA staff have attempted to reproduce the originally reported problem with available notebooks and TB docks, but were unable to. You don't need a TB dock! The notebook alone is enough for having trouble.
-- You are receiving this mail because: You are on the CC list for the bug.
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.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c30 --- Comment #30 from Christian Eggers <ceggers@arri.de> --- (In reply to Daniel Dadap from comment #29)
I meant 471.92: https://www.nvidia.com/download/driverResults.aspx/171473/en-us My browser show 461.92 here :-)
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? I tested 471.68 with only without docking station. As soon as the actual driver was installed, the display went off and stayed in this state.
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. Originally (under Linux) I didn't try without the dock.
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. I agree. Under both OS, the internal display does not work. Under Linux, at least the external displays (on the dock) are usable. Maybe under Windows the external displays would also work if I were able to login...
In my setup it's normal that Windows enables only one display prior login, while under Linux always all displays are enabled at this time.
... My understanding of the original bug you reported on Linux was that the internal display works when there are no external displays, I actually didn't test this...
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.
It seems that I have to install 470 on Linux another time and recheck without docking station... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c31 --- Comment #31 from Daniel Dadap <ddadap@nvidia.com> --- (In reply to Christian Eggers from comment #30)
My browser show 461.92 here :-)
Indeed. The internal bug states 471.92 in several places, so I'm not sure whether that's a typo for the actual public 461.92 version, or if that's actual data from a 471.92 build that's not broadly available.
Originally (under Linux) I didn't try without the dock.
Ah. I suppose I must have incorrectly inferred the "internal display works without dock" detail. Sorry about that. No need to pursue further experiments on your end at this time; it will be difficult for us to make much progress here without an NVIDIA internal reproduction, so we're going to continue pursuing that. Thank you again for reporting the issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c32 --- Comment #32 from Christian Eggers <ceggers@arri.de> --- Short update: As support for "openSUSE Leap 15.2" will end in a few months, I decided to make a fresh install of openSUSE Leap 15.3. Under this version, installation of the 460.84 driver is not possible anymore (deactivation of the Nouveau driver has no effect). Although I guess that this can easily be fixed, I see no future is these workarounds. openSUSE releases kernel updates every few weeks which always require to repeat the whole installation procedure of the NVidia driver. This involves multiple reboots and is simply too cumbersome for regular use. @NVidia: Please try to get a Dell Precision 7510 and fix the original problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c33 --- Comment #33 from Christian Eggers <ceggers@arri.de> --- Hi Stefan, it looks like the status on the bug will not change in the near future. Manually uninstalling and reinstalling the self extracting driver after every kernel update is quite time consuming- Can you please provide the source RPM from which the last 460 driver has been built? I couldn't find the "official" version on software.opensuse.org nor in the Nvidia repo. thank, Christian -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c34 --- Comment #34 from Stefan Dirsch <sndirsch@suse.com> --- https://build.opensuse.org/package/show/X11:Drivers:Video/nvidia-gfxG05 Here you need to checkout the version for 460.84 with osc: r118 You need to be experienced with our buildservice. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c35 --- Comment #35 from Christian Eggers <ceggers@arri.de> --- In order to add support for openSUSE Leap 15.3, I had to create a copy of the package. After adding the .run file to the working copy, I could build in install the RPMs. Until NVidia has fixed the issue, this seems to be the best solution for me. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c36 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ceggers@arri.de Flags| |needinfo?(ceggers@arri.de) --- Comment #36 from Stefan Dirsch <sndirsch@suse.com> --- I suggest to try again with 470.94 or even 510.39.01 (new G06 driver series). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c37 --- Comment #37 from Christian Eggers <ceggers@arri.de> --- (In reply to Stefan Dirsch from comment #36)
I suggest to try again with 470.94 or even 510.39.01 (new G06 driver series).
I tested both (on Linux), but without any new results. The internal laptop screen can not be enabled and is not shown in the output of `xrandr -q`. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189165 http://bugzilla.opensuse.org/show_bug.cgi?id=1189165#c38 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ceggers@arri.de) | --- Comment #38 from Stefan Dirsch <sndirsch@suse.com> --- Ok. Thanks for giving it a try! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com