So you don't have a problem with the installer, but with X11 or with the kernel.

First of, there is no such thing as a zypper installer. We have the NCurses (text) based "linuxrc" as the precursor to the installation, and we have an NCurses UI for the installation as well. The latter is the fallback if X11 cannot be started, and it can be detected that it couldn't be started.

If the output just can't be redirected to another port of the graphics card, very likely X11 did start, and it still sends its output to the default graphics port which may not be connected to a display.

You can select text mode from the installation ISO's boot menu. Did you try that? This is meant specifically for cases such as yours when you have trouble with the GUI for some reason. There is also a troubleshooting guide in the documentation what to do when that happens, mentioning some kernel parameters that can help to overcome the problem.

If it only happens with DP-HDMI and a projector setup, and it worked before with Leap (which is always inherently somewhat older; TW is bleeding edge), this points to the general direction of kernel or X11.

Please attach the output of "hwinfo", and if you can, please also paste the output of "inxi -b" (from any working SUSE or Ubuntu).


Trying the X11 maintainers first for further investigation. This might also be a case for the kernel maintainers.

I'm pretty sure this is a kernel issue with gerneric modesetting X driver running during installation. Reassigning.

After installing the system with DP-to-DP, reconnect again to DP-to-HDMI.  Then the problem reappears?  If yes, it's easier to gather the log.

Created attachment 868248 [details]
hwinfo results.

Results from inxi
```
System:
  Host: tc01 Kernel: 5.15.0-76-generic x86_64 bits: 64 Console: pty pts/2
    Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish)
Machine:
  Type: Desktop System: HP product: HP t630 Thin Client v: N/A serial: 8CN9500DPY
  Mobo: HP model: 8158 v: A01 serial: 8CN9500DPY UEFI: AMI v: M40 v01.11
    date: 06/25/2019
CPU:
  Info: quad core AMD Embedded G-Series GX-420GI Radeon R7E [MT MCP] speed (MHz):
    avg: 900 min/max: 900/2000
Graphics:
  Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] driver: amdgpu v: kernel
  Display: server: X.org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu tty: 88x31
  Message: GL data unavailable in console for root.
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
  Device-2: Intel Wireless 8260 driver: iwlwifi
  Device-3: Intel Bluetooth wireless interface type: USB driver: btusb
Drives:
  Local Storage: total: 119.24 GiB used: 8.61 GiB (7.2%)
Info:
  Processes: 198 Uptime: 22h 7m Memory: 6.73 GiB used: 1022.8 MiB (14.8%)
  Init: systemd runlevel: 5 Shell: Sudo inxi: 3.3.13
```

@Stefan Hundhammer, I did not see text mode from the installation ISO's boot menu.
If I recall, I had 4 options: 
- boot from disk
- installation
- upgrade
- more...

I'll check what options I have under more and get back.

@Takashi Iwai, I will try text mode suggestion from above first, then do DP-DP installation.

(In reply to Samuel Conway from comment #6)
> @Stefan Hundhammer, I did not see text mode from the installation ISO's boot
> menu.
> If I recall, I had 4 options: 
> - boot from disk
> - installation
> - upgrade
> - more...
> 
> I'll check what options I have under more and get back.

It's in the bottom status line where you can select the video mode with the F3 key. "Text mode" is one of the options for the video mode.

See

  https://github.com/yast/yast-installation/issues/914

(first screenshot)

@ Stefan Hundhammer,

I don't have those F1 etc options, I only have c: Command line and e: Edit entry

Under More..
I have 
Rescue System
Boot Linux System
Check installation media

I have written openSUSE-Tumbleweed-DVD-x86_64-Snapshot20230712-Media.iso to usb with:
`sudo dd if=./openSUSE-Tumbleweed-DVD-x86_64-Snapshot20230712-Media.iso of=/dev/sdi bs=4M status=progress && sync`

(In reply to Samuel Conway from comment #8)
> I don't have those F1 etc options, I only have c: Command line and e: Edit
> entry

The Fn row does not exist when booting in UEFI mode. With the menu entry you wish to boot selected, strike the "E" key to put Grub into edit mode, navigate to the end of the line that begins linu, which usually is wrapped, then append textmode=1 to start the installation in text mode. Any other cmdline options you wish to test are done in same manner booted in UEFI mode. Other such options can be found on https://en.opensuse.org/SDB:Linuxrc

Ah, right; in that case, a kernel parameter

  textmode=1

is the equivalent.

Added to textmode=1 then saved with ctrl+x on installation entry but issue still persists.


I get to initializing udev... then black screen.

I'm now doing install with DP-to-DP.

What I notice:
- initializing udev...
- black screen for a second
- initializing udev... ok
- green bar loading  drivers status


While with DP-to-HDMI
- initializing udev...
- black
- searching for input
- hdmi connected (but screen is black)

Created attachment 868330 [details]
hwinfo but now with opensuse

(In reply to Stefan Hundhammer from comment #2)
> Please attach the output of "hwinfo", and if you can, please also paste the
> output of "inxi -b" (from any working SUSE or Ubuntu).
> 
> 
> Trying the X11 maintainers first for further investigation. This might also
> be a case for the kernel maintainers.

Have sshed into device then ran commands again inxi -b and hwinfo (attached): 
inxi -b:
System:
  Host: tc01 Kernel: 6.4.3-1-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE
    Tumbleweed 20230717
Machine:
  Type: Desktop System: HP product: HP t630 Thin Client v: N/A serial: <superuser required>
  Mobo: HP model: 8158 v: A01 serial: <superuser required> UEFI: AMI v: M40 v01.11
    date: 06/25/2019
CPU:
  Info: quad core AMD Embedded G-Series GX-420GI Radeon R7E [MT MCP] speed (MHz): avg: 900
    min/max: 900/2000
Graphics:
  Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] driver: amdgpu v: kernel
  Display: x11 server: X.org v: 1.21.1.8 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: radeonsi gpu: amdgpu tty: 101x23 resolution: 1920x1080
  API: OpenGL Message: GL data unavailable in console. Try -G --display
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
  Device-2: Intel Wireless 8260 driver: iwlwifi
  Device-3: Intel Bluetooth wireless interface driver: btusb type: USB
Drives:
  Local Storage: total: 119.24 GiB used: 3.33 GiB (2.8%)
Info:
  Processes: 168 Uptime: 0h 51m Memory: available: 6.72 GiB used: 594.7 MiB (8.6%) Init: systemd
  Shell: Bash inxi: 3.3.27

So, now you could install the system with DP-DP?  And on the running system, try to switch to DP-HDMI.  Do you see the same problem?  When you reconnect back to DP-DP, does it recover again?

If all yes, please try like the following:
- Boot with DP-DP, go up to GUI desktop
- Enable the debugging of drm, run below as root
    echo 0x1e > /sys/module/drm/parameters/debug
- Re-connect to DP-HDMI, and you'll see a buggy screen
- Re-connect back to DP-DP, screen recovered
- Save the output "dmesg" command, and attach the output to Bugzilla

Created attachment 868621 [details]
output of  dmesg

(In reply to Takashi Iwai from comment #14)
> So, now you could install the system with DP-DP?  And on the running system,
> try to switch to DP-HDMI.  Do you see the same problem?  When you reconnect
> back to DP-DP, does it recover again?
> 
> If all yes, please try like the following:
> - Boot with DP-DP, go up to GUI desktop
> - Enable the debugging of drm, run below as root
>     echo 0x1e > /sys/module/drm/parameters/debug
> - Re-connect to DP-HDMI, and you'll see a buggy screen
> - Re-connect back to DP-DP, screen recovered
> - Save the output "dmesg" command, and attach the output to Bugzilla

Did as as requested, had video output for both DP-DP and DP-HDMI. output of dmesg  is attached.

(In reply to Samuel Conway from comment #16)
> (In reply to Takashi Iwai from comment #14)
> > So, now you could install the system with DP-DP?  And on the running system,
> > try to switch to DP-HDMI.  Do you see the same problem?  When you reconnect
> > back to DP-DP, does it recover again?
> > 
> > If all yes, please try like the following:
> > - Boot with DP-DP, go up to GUI desktop
> > - Enable the debugging of drm, run below as root
> >     echo 0x1e > /sys/module/drm/parameters/debug
> > - Re-connect to DP-HDMI, and you'll see a buggy screen
> > - Re-connect back to DP-DP, screen recovered
> > - Save the output "dmesg" command, and attach the output to Bugzilla
> 
> Did as as requested, had video output for both DP-DP and DP-HDMI. output of
> dmesg  is attached.

I powered off device and took to room with projector, first booting with DP-DP monotor, successful video output, swapped to DP-HDMI for projector projector, but again no video output, just black screen.

Rebooted again with DP-DP, still no output. Swapped again to DP-HDMI (still nothing) so I created a new dmesg export: dmesg-20230803-1 and attached it.
Also swapped adapters since I have two, but no success.

let me know if I can test anything else.
regards

Created attachment 868623 [details]
dmesg when attaching to projector

FWIW, I updated another device (laptop) to version="20230804" release="2430.1", which also had DP-HDMI output issues.

I needed to Rollback to previous snapshot (20230801) to fix.

Through a quick glance at logs, I didn't see anything particular.

I suppose the best would be to report the issue to the upstream, gitlab.freedesktop.org, DRM/AMDGPU.

Not sure this is related to the root cause: In the first dmesg (comment#15), there are too many failed attempts to access DP AUX channel 

[  211.387106] [drm:link_set_dpms_on [amdgpu]] link_set_dpms_on pipe_ctx dispname=S24E650 signal=20
[  211.422003] amdgpu 0000:00:01.0: [drm:drm_dp_dpcd_access [drm_display_helper]] AMDGPU DM aux hw bus 1: Too many retries, giving up. First error: -5

05 is -EIO.

Do you know if the DP-HDMI cable used is active or passive? Perhaps that would make a difference.

Agreed that the best option is to report this at: https://gitlab.freedesktop.org/drm/amd/-/issues