http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 Malcolm Lewis changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |malcolmlewis@linuxmail.org -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c1 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS Flags| |needinfo?(kourosh@pourdanan | |deh.com) --- Comment #1 from Stefan Dirsch --- Please attach Xorg.0.log and journalctl. to this bugreport. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c3 Kourosh P. changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #854309|0 |1 is obsolete| | --- Comment #3 from Kourosh P. --- Created attachment 854310 --> http://bugzilla.opensuse.org/attachment.cgi?id=854310&action=edit journalctl Booting the system with monitor OFF since boot, leaving the monitor OFF and SSH into the system from another machine and run the commands from the SSH session -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c5 --- Comment #5 from Kourosh P. --- Created attachment 854312 --> http://bugzilla.opensuse.org/attachment.cgi?id=854312&action=edit journalctl Turning the monitor ON it shows DisplayPort NO Signal -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c7 --- Comment #7 from Kourosh P. --- Created attachment 854314 --> http://bugzilla.opensuse.org/attachment.cgi?id=854314&action=edit journalctl Changing to console 1, CTRL+ALT+F1 (tty1) to get to command line -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c9 --- Comment #9 from Kourosh P. --- Created attachment 854316 --> http://bugzilla.opensuse.org/attachment.cgi?id=854316&action=edit journalctl While in console 1 (tty1), login, starting X (startx) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 Kourosh P. changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kourosh@pourdanan | |deh.com) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c12 --- Comment #12 from Kourosh P. --- I would like to add the following for reference: My original NEW system had an Nvidia GeForce 3070 GPU with the nouveau drivers, when I started experiencing this issue. Then I installed the Nvidia .run file thinking it might help but it didn't. When I contacted my PC store where I bought the system, Canada Computers, they were kind enough to swap the GPU for the current one, i.e. AMD Radeon RX 6800 (I was lucky that I purchased the extended warranty at the time of purchase). To summarize, I don't think it is ONLY amdgpu driver issue in my humble opinion. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c13 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|amdgpu/nouveau: Monitor NO |amdgpu: Monitor NO signal |signal if it hasn't been on |if it hasn't been on since |since system boot |system boot --- Comment #13 from Stefan Dirsch --- Summary change is confusing. There is no nvidia GPU in this system any longer. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c15 --- Comment #15 from Stefan Dirsch --- Thanks. But in that case it's more confusing than helpful. ;-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c17 Nikolai Nikolaevskii changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kaykaykay123@gmail.com --- Comment #17 from Nikolai Nikolaevskii --- According to inxi output OP uses Intel Core i7-10700K + ASUSTeK PRIME Z490-A + AMD Navi 21 video card. With Intel Core i7-10700K he has 2 video cards: built-in Intel UHD 630 and discrete AMD (previously Nvidia). But inxi shows only AMD Navi 21. There are some settings in BIOS about video cards: disable/enable iGFX (i.e. built-in), and which video card BIOS will initialize first - built-in or discrete. So, if built-in video card is disabled, but is set to be initialized first, he may get observed behaviour. To OP: please provide full output for command: sudo inxi -aSCGImz -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c19 --- Comment #19 from Kourosh P. --- To @Nikolai In the BIOS Advanced > System Agent (SA) Configuration > Graphics Configuration

Primary Display > 'Auto' was selected. The other options were 'CPU Graphics', 'PEG', 'PCIE' and I changed it to 'PEG'. Advanced > System Agent (SA) Configuration > Graphics Configuration > iGPU Multi-Monitor is already set to 'Disabled'. I rebooted the system with monitor OFF and got the same result with DP NO Signal when monitor was turned on.

sudo inxi -aSCGImz System: Kernel: 5.3.18-59.34-default x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.34-default root=UUID=843c52a9-20ba-4694-abc3-a3988c2c354a splash=silent resume=/dev/disk/by-uuid/295c1286-73fd-42fa-9f7a-21fa1103e118 mitigations=auto quiet Console: tty 1 dm: SDDM Distro: openSUSE Leap 15.3 Memory: RAM: total: 15.53 GiB used: 733.7 MiB (4.6%) Array-1: capacity: 64 GiB slots: 4 EC: None max module size: 16 GiB note: est. Device-1: ChannelA-DIMM1 size: No Module Installed Device-2: ChannelA-DIMM2 size: 8 GiB speed: 2133 MT/s type: DDR4 detail: synchronous bus width: 64 bits total: 64 bits manufacturer: G-Skill part-no: F4-3000C16-8GISB serial: N/A Device-3: ChannelB-DIMM1 size: No Module Installed Device-4: ChannelB-DIMM2 size: 8 GiB speed: 2133 MT/s type: DDR4 detail: synchronous bus width: 64 bits total: 64 bits manufacturer: G-Skill part-no: F4-3000C16-8GISB serial: N/A CPU: Topology: 8-Core model: Intel Core i7-10700K bits: 64 type: MT MCP arch: N/A family: 6 model-id: A5 (165) stepping: 5 microcode: EC L1 cache: 512 KiB L2 cache: 16.0 MiB L3 cache: 16.0 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 121596 Speed: 800 MHz min/max: 800/5100 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 801 6: 800 7: 800 8: 800 9: 801 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Tul driver: amdgpu v: kernel bus ID: 04:00.0 chip ID: 1002:73bf Display: server: X.org 1.20.3 compositor: kwin_x11 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa tty: 208x57 Message: Advanced graphics data unavailable in console for root. Info: Processes: 338 Uptime: N/A Init: systemd v: 246 runlevel: 5 target: graphical.target Compilers: gcc: N/A Shell: bash (sudo) v: 4.4.23 running in: tty 1 (SSH) inxi: 3.1.00 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c21 --- Comment #21 from Kourosh P. --- Created attachment 854329 --> http://bugzilla.opensuse.org/attachment.cgi?id=854329&action=edit dmesg After No Signal at console 7 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c23 --- Comment #23 from Kourosh P. --- Created attachment 854331 --> http://bugzilla.opensuse.org/attachment.cgi?id=854331&action=edit ps ucx for user after switching to TTY1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c25 --- Comment #25 from Kourosh P. --- (In reply to Takashi Iwai from comment #16)

BTW, when you boot with another desktop environment (such as icewm), does the problem persist? I mean not to log out and switch from KDE, but login directly to icewm session (which should be available as fallback) at boot.

I enabled icewm to load instead of Plasma at boot, but still NO Signal when turning on monitor after boot I am afraid. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c27 --- Comment #27 from Kourosh P. --- (In reply to Nikolai Nikolaevskii from comment #26)

(In reply to Nikolai Nikolaevskii from comment #17)

...

According to inxi output OP uses Intel Core i7-10700K + ASUSTeK PRIME Z490-A + AMD Navi 21 video card. With Intel Core i7-10700K he has 2 video cards: built-in Intel UHD 630 and discrete AMD (previously Nvidia). But inxi shows only AMD Navi 21. There are some settings in BIOS about video cards: disable/enable iGFX (i.e. built-in), and which video card BIOS will initialize first - built-in or discrete. So, if built-in video card is disabled, but is set to be initialized first, he may get observed behaviour.

To OP: please provide full output for command: sudo inxi -aSCGImz

OK, theory was good, but failed.

New one: https://wiki.archlinux.org/title/AMDGPU#Issues_with_power_management_/ _dynamic_re-activation_of_a_discrete_amdgpu_graphics_card

[QUOTE] Issues with power management / dynamic re-activation of a discrete amdgpu graphics card

If you encounter issues similar to [9], you can workaround the issue by setting the kernel parameter amdgpu.runpm=0, which prevents the dGPU from being powered down dynamically at runtime. [/QUOTE]

Try to use parameter amdgpu.runpm=0.

I tried that kernel parameter on both my test SSD (runs vanilla Leap 15.3 without AMDGPU-PRO drivers) and my main m.2 (runs Leap 15.3 with AMDGPU-PRO drivers) and still the same results I am afraid. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c30 --- Comment #30 from Kourosh P. --- (In reply to Takashi Iwai from comment #29)

The log showed that DP-3 connector was detected while HDMI-A-1 connector was disconnected. Isn't this DP-3 corresponding to your monitor? Or is it a different output?

Thank you for your follow-up. When doing the test to get a log I don't remember physically disconnecting an HDMI cable. I have always performs the logs when on DisplayPort. I have tested to see if HDMI works in the past, but not unplugging while getting logs. I hope I understood your question. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c39 --- Comment #39 from Takashi Iwai --- Please report the problem at https://gitlab.freedesktop.org/drm/amd/-/issues -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://gitlab.freedesktop. | |org/drm/amd/-/issues/1952 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c42 --- Comment #42 from Kourosh P. --- (In reply to Felix Miata from comment #41)

(In reply to Kourosh P. from comment #40)

...

I have reported this matter at the following link: https://gitlab.freedesktop.org/drm/amd/-/issues/1952

I just made the following addition there:

# inxi -S System: Host: ab250 Kernel: 5.18.19-200.fc36.x86_64 arch: x86_64 bits: 64 Desktop: Trinity v: R14.0.12 Distro: Fedora release 36 (Thirty Six) #

If I keep my second display's cable disconnected, I get this: # grep onnec /var/log/Xorg.0.log [ 5.313] (II) modeset(0): Output DP-1 connected [ 5.313] (II) modeset(0): Output HDMI-1 disconnected [ 5.313] (II) modeset(0): Output HDMI-2 disconnected [ 5.313] (II) modeset(0): Output HDMI-3 disconnected [ 5.313] (II) modeset(0): Output DP-2 disconnected # Or this: # grep onnec /var/log/Xorg.0.log [ 5.544] (II) modeset(0): Output DP-1 disconnected [ 5.544] (II) modeset(0): Output HDMI-1 disconnected [ 5.544] (II) modeset(0): Output HDMI-2 connected [ 5.544] (II) modeset(0): Output HDMI-3 disconnected [ 5.544] (II) modeset(0): Output DP-2 disconnected #

It may surprise many that if I keep my second display's signal cable connected from the PC, but with it powered off, I get this on booting instead: # grep onnec /var/log/Xorg.0.log [ 5.412] (II) modeset(0): Output DP-1 connected [ 5.412] (II) modeset(0): Output HDMI-1 disconnected [ 5.412] (II) modeset(0): Output HDMI-2 connected [ 5.412] (II) modeset(0): Output HDMI-3 disconnected [ 5.412] (II) modeset(0): Output DP-2 disconnected # Or this: # grep onnec /var/log/Xorg.0.log [ 5.451] (II) modeset(0): Output DP-1 connected [ 5.451] (II) modeset(0): Output HDMI-1 disconnected [ 5.451] (II) modeset(0): Output HDMI-2 connected [ 5.451] (II) modeset(0): Output HDMI-3 disconnected [ 5.451] (II) modeset(0): Output DP-2 disconnected #

So, at "connection" time, the secondary display isn't providing any information about it's capability, only the cable connection is "reporting" something is connected. Some may want to rethink their definition of "connected", and not boot with an external display attached but un-powered.[/quote]

It would be nice to know what MX Linux is doing that it doesn't present the problem.

Thank you. -- You are receiving this mail because: You are on the CC list for the bug.