Include the complete command. It’s only one extra line, but it makes it clear what you are showing us.
Include the trailing shell prompt, to show us we are seeing complete command output.
Preserve the formatting of the input/output using one of two methods: a: Include a line containing only ``` directly ahead of and another directly after your paste; or b: Use the </> (PRE) icon above the input window to contain your paste.
Your command output fell short of providing enough troubleshooting information. From Xterm or Konsole or other GUI terminal, please provide inxi -GSaz following the above directions. If run from a vtty, inxi has limited access to useful data it would ordinarily provide.
Nomodeset is a troubleshooting parameter intended to enable a limited graphical running state for access to logs, package management and reconfiguration. It limits output to one display only, and a limited set of lowfi resolutions.
Does the problem remain running an X11 session instead of Wayland?
Does the problem remain running an IceWM session instead of Plasma?
You may try an alternative X driver. Ordinarily the driver provided by package xf86-video-amdgpu is optimum for your GPU class. By removing the package and restarting X or rebooting, X will switch to using an alternative display driver, “modesetting”, which could possibly be a solution, or at least a workaround.
Yes, there are 3 DMs installed, Plasma (X11), Plasma (Wayland), and IceWM Session,
the X11, one is the preferred option, the external monitor has no input signal from any.
kernels 5.17.3 and 6.8.1.1 have been tried without success.
–auto and --rotate normal should not be required for your primary output eDP. Usually --auto is employed alone to trigger a reset. “'” before and after output names are not necessary. I’ve never needed them. Usually, HDMI-A-0 is an output name used exclusively by the kernel. This is usually mapped to something else in X, depending on the X driver employed. It may be perfectly valid for X, but when not, its use is ignored, so a chicken and egg problem can arise in determining proper nom-de-plume for a device or output. Hence, my request for the three additional commands’ output.
The problem you have reported may be in the amdgpu driver provided by xf86-video-amdgpu, so we need to see what happens with it removed.
Still waiting to see whether HDMI appears after doing
sudo zypper rm xf86-video-amdgpu
and restarting X or rebooting. Ignore that zypper will remove other *video* packages along with xf86-video-amdgpu. Most installations install every GPU driver in existence when normally one or less is actually needed.
going back to original setup dmesg as follows,
[ 8.031143] [ T882] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[ 8.031159] [ T882] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[ 8.031272] [ T882] amdgpu: Virtual CRAT table created for GPU
[ 8.031778] [ T882] amdgpu: Topology: Add dGPU node [0x164c:0x1002]
[ 8.031784] [ T882] kfd kfd: amdgpu: added device 1002:164c
[ 8.031867] [ T882] amdgpu 0000:03:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 7
[ 8.031876] [ T882] amdgpu 0000:03:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 8.031883] [ T882] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 8.031890] [ T882] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 8.031896] [ T882] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 8.031902] [ T882] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 8.031909] [ T882] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 8.031915] [ T882] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 8.031922] [ T882] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 8.031928] [ T882] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 8.031935] [ T882] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[ 8.031941] [ T882] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
[ 8.031947] [ T882] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
[ 8.031954] [ T882] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
[ 8.031960] [ T882] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
[ 8.031966] [ T882] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
[ 8.033881] [ T882] amdgpu 0000:03:00.0: amdgpu: Runtime PM not available
Can you explain exactly what you did here? It does not make sense. What I was expecting to see was available firmware package versions, including the one installed.
Please ID the source of direction to employ this option. I’ve only ever previously seen the following (in addition to uninstalling) for disabling plymouth:
noplymouth
plymouth=0
plymouth.enable=0
Try any one or more of these to see if it makes any difference. I never have plymouth installed, so haven’t tested which is/are valid.
Try adding video=HDMI-A-0:e as an additional cmdline option. If it doesn’t change anything, try using D in place of e. Either should force the HDMI output to be enabled, at least until your DM loads, which might put the black back.