[Bug 1213380] New: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output
https://bugzilla.suse.com/show_bug.cgi?id=1213380 Bug ID: 1213380 Summary: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: samcon@protonmail.com QA Contact: jsrain@suse.com Target Milestone: --- Found By: --- Blocker: --- I encountered a black screen issue while attempting to boot the openSUSE Tumbleweed ISO after the BIOS on my system. This issue specifically occurs when using a DP-HDMI video output. This problem does not arise when using the same video output with other operating systems like Leap, Fedora, and Ubuntu LTS. In those cases, I am able to get video output without any black screen problems. Steps to Reproduce: 1. Start the computer and access the BIOS. 2. Configure the boot order to prioritize booting from the openSUSE Tumbleweed ISO. 3. Save the changes and exit the BIOS. 4. The system attempts to boot from the ISO. 5. First I see the kernal or bootloader messages, then it jumps to a black screen - with waiting for source message on projector. Expected Behavior: Upon booting from the openSUSE Tumbleweed ISO, the system should display zypper installer instead of a black screen, just like other operating systems do when using the DP-HDMI video output. Additional Information: - Operating System: openSUSE Tumbleweed - Video Output: DP-HDMI - Other operating systems (Leap, Fedora, Ubuntu LTS) do not exhibit the black screen issue with the same video output. - When I connect the same system to the monitor using DP-to-DP instead of DP-to-HDMI, the video output is successfully displayed. - Have used tried with iso from few weeks back and latest Snapshot20230714-Media.iso Kind regards, Sam -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c5 --- Comment #5 from Samuel Conway <samcon@protonmail.com> --- Created attachment 868248 --> https://bugzilla.suse.com/attachment.cgi?id=868248&action=edit 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 ``` -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c6 --- Comment #6 from Samuel Conway <samcon@protonmail.com> --- @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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c8 --- Comment #8 from Samuel Conway <samcon@protonmail.com> --- @ 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` -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c9 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net --- Comment #9 from Felix Miata <mrmazda@earthlink.net> --- (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 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c11 --- Comment #11 from Samuel Conway <samcon@protonmail.com> --- Added to textmode=1 then saved with ctrl+x on installation entry but issue still persists. I get to initializing udev... then black screen. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c12 --- Comment #12 from Samuel Conway <samcon@protonmail.com> --- 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) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c13 --- Comment #13 from Samuel Conway <samcon@protonmail.com> --- Created attachment 868330 --> https://bugzilla.suse.com/attachment.cgi?id=868330&action=edit 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 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c15 --- Comment #15 from Samuel Conway <samcon@protonmail.com> --- Created attachment 868621 --> https://bugzilla.suse.com/attachment.cgi?id=868621&action=edit output of dmesg -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c16 --- Comment #16 from Samuel Conway <samcon@protonmail.com> --- (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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c17 --- Comment #17 from Samuel Conway <samcon@protonmail.com> --- (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 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c18 --- Comment #18 from Samuel Conway <samcon@protonmail.com> --- Created attachment 868623 --> https://bugzilla.suse.com/attachment.cgi?id=868623&action=edit dmesg when attaching to projector -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c19 --- Comment #19 from Samuel Conway <samcon@protonmail.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1213380 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mrmazda@earthlink.net | -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com