Bugzilla – Bug 1227132
Leap 15.6 installation lost Display port output
Last modified: 2024-07-09 07:48:04 UTC
Booted LP15.6 DVD iso from a USB and tried first to run the upgrade, which lost the Display port output before or in the beginning of the green bar progress at the screen bottom. Tried also Installation from the boot menu, and the same happened, the DP signal was lost, just a black monitor. The output was not held ok during the installation before I connected a DVI(-D)pro cable between this Nvidia GPU and the monitior. Includes the system output, here with Tw-Slowroll installed on this hardware: inxi -FGSz System: Kernel: 6.9.5-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 46.2 Distro: openSUSE Tumbleweed-Slowroll 20240605 Machine: Type: Desktop System: MSI product: MS-7971 v: 1.0 serial: <superuser required> Mobo: MSI model: Z170-A PRO (MS-7971) v: 1.0 serial: <superuser required> UEFI: American Megatrends v: 1.K0 date: 07/10/2018 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 975 min/max: 800/4200 cores: 1: 1000 2: 1000 3: 1000 4: 1000 5: 800 6: 1000 7: 1000 8: 1000 Graphics: Device-1: NVIDIA GM206 [GeForce GTX 960] driver: nvidia v: 550.90.07 Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 24.1.0 compositor: gnome-shell driver: X: loaded: nvidia unloaded: fbdev,modesetting,vesa gpu: nvidia,nvidia-nvswitch resolution: 2560x1440~60Hz API: OpenGL v: 4.6.0 vendor: nvidia v: 550.90.07 renderer: NVIDIA GeForce GTX 960/PCIe/SSE2 API: EGL Message: EGL data requires eglinfo. Check --recommends. Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio driver: snd_hda_intel Device-2: NVIDIA GM206 High Definition Audio driver: snd_hda_intel Device-3: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB API: ALSA v: k6.9.5-1-default status: kernel-api Server-1: PipeWire v: 1.0.7 status: active Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 8.02 TiB used: 6.99 TiB (87.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSC2BB300G4 size: 279.46 GiB ID-3: /dev/sdb vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB ID-4: /dev/sdc vendor: Kingston model: DataTraveler 3.0 size: 7.22 GiB type: USB Partition: ID-1: / size: 39.08 GiB used: 11.01 GiB (28.2%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 155.8 MiB used: 7 MiB (4.5%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 426.88 GiB used: 374.59 GiB (87.7%) fs: ext4 dev: /dev/nvme0n1p4 Swap: ID-1: swap-1 type: partition size: 2.01 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p2 Sensors: System Temperatures: cpu: 35.0 C pch: 38.5 C mobo: N/A Fan Speeds (rpm): N/A Info: Memory: total: 64 GiB note: est. available: 62.76 GiB used: 2.34 GiB (3.7%) Processes: 271 Uptime: 0h 5m Shell: Bash inxi: 3.3.34
I am a bit confused: Was this an upgrade or an fresh installation? If it was an upgrade, HOW did you upgrade? With the zypper method or booting into an installation ISO and then doing a YaST-based upgrade? I suspect that there was a short while where the NVidia drivers were not available.
(In reply to Stefan Hundhammer from comment #1) > I am a bit confused: Was this an upgrade or an fresh installation? > > If it was an upgrade, HOW did you upgrade? With the zypper method or booting > into an installation ISO and then doing a YaST-based upgrade? On beforehand I had LP15.5 installed, but had replaced the previous Nvidia card with another Nvidia gpu model. 1. I booted from from a USB stick (with openSUSE-Leap-15.6-DVD-x86_64709) with a Display port cable connected to the current Nvidia gpu and the monitor. The boot menu displayed OK, I tried first an "Upgrade" from this menu, but the signal disappeared with a black monitor after a while (possibly before the green progress bar started). I thought an upgrade was not possible, due to the replaced Nvidia card (new hardware) and that I had to do a new Installation. > I suspect that there was a short while where the NVidia drivers were not > available. 2. I rebooted the USB iso again and selected "Install" from the menu. The same thing happened, with a black monitor after a while. Not a short time, because I waited several minutes, and I got the impression the installation had terminated (not sure). 3. Then I replaced the DP cable with a DVI-D cable, booted the USB installation menu again and did a new Install from here. The installation went as it should and displayed continuous without loss of monitor signal. (Later on I replaced LP15.6 with a new Slowroll installation on this disk, installed LP15.6 on another disk in dual boot, quite ok with the DVI-D cable connected.) I don't understand why the DP connection did work work up to and included the boot menu, while the whole installation went fine continuously only with a DVI-D connection. With another monitor without DVI-D port, this would not have been possible.
OK; now it begins to make sense. So you had a working Display Port connection in Leap 15.5 because there you had working proprietary NVidia drivers that support this setup. And since you could see the boot menu, your machine's BIOS obviously also supports it. But when you select "install" from that menu, a Linux kernel (with kernel modules from an initrd) from the installation ISO takes over, and that one obviously does not have support for DP on this NVidia graphics card. So the screen went black. I don't know which driver we are currently using at that stage when booting from the installation media; but for sure it's something much simpler than a proprietary NVidia driver.
Let's get the kernel experts involved here.
(In reply to Stefan Hundhammer from comment #3) > OK; now it begins to make sense. > > So you had a working Display Port connection in Leap 15.5 because there you > had working proprietary NVidia drivers that support this setup. And since > you could see the boot menu, your machine's BIOS obviously also supports it. > I cannot confirm it was the DP connection that was used in Leap 15.5. Because also a DVI-D was connected to the monitor, it is well possible it really was the latter that was used also previously. What I noticed after the Slowroll new installation, was that the Nouveau driver was installed. And because it seemingly offered only low VGA resolution in this case, I added the Nvidia repositories and these drivers supported the true 2560x1440 resolution. This is a Asus PB278Q monitor with specifications https://www.asus.com/us/commercial-monitors/pb278q/specifications/
Do you ever use this Asus with any other computer, such as one that has DVI output but no DP output? Do you keep a DVI cable connected to this Asus whether or not it is also connected to any computer? Does the Asus have a firmware update available? When trying to install, were you cold booting the installation media into installation with no interruptions for cable switching or display control button pushing? Some monitors can be quirky when their connectivity is inconsistent. Yours has 4 video inputs from which to select, and a wealth of features, a formula for a normally dormant firmware defect to cause inexplicable behavior.
(In reply to Felix Miata from comment #6) > Do you ever use this Asus with any other computer, such as one that has DVI > output but no DP output? Do you keep a DVI cable connected to this Asus > whether or not it is also connected to any computer? I have now this Asus connected to the normal, rebuild and upgraded computer with quite new hardware (Z790 mobo, i12 and Arc A750 gpu). A750 does have HDMI and DP ports, but no DVI-D. Asus receives input from HDMI connected, which also wakes up the monitor with a bip at boot. With only a Display Port connection, Asus receives no signal from this gpu/computer, neither when I select this manually. The other MSI/Nvidia computer is relocated and connected to its normal, simpler monitor Philips 244E. It works as it should with DVI-D connection, and I have also tested it with the same USB boot installation session. However, I posted this bug because as long as the USB boot installation menu displayed ok over DP to Asus, I found it illogical it should loose this connection during the selected install or upgrade session. Does the Asus have a > firmware update available? When trying to install, were you cold booting the > installation media into installation with no interruptions for cable > switching or display control button pushing? Some monitors can be quirky > when their connectivity is inconsistent. Yours has 4 video inputs from which > to select, and a wealth of features, a formula for a normally dormant > firmware defect to cause inexplicable behavior. I don't remember if Asus ever has had a firmware upgrade, possibly not via Linux I would guess. The benefit with the Asus connections is its flexibility with new and old hardware and for multimedia work. I use also testing my authored and burned BD/DVD discs in standalene players connected via HDMI,
So the DP output doesn't work with nouveau driver? If so, it won't work on the installer image, either. In that case, the best would be to fix nouveau driver for the DP output on your machine. Report it to the upstream devs, e.g. gitlab.freedesktop.org issues DRM/Nouveau.