• Edited

Hello guys, as of last update (week 9 2025) the laptop's hdmi port cannot get signal to a second screen (TV).

linux-driver-management status
╒ Hardware Platform
╞ Platform Vendor : LG Electronics
╘ Platform Model : 13Z980
Simple GPU configuration
╒ Primary GPU
╞ Device Name : UHD Graphics 620
╞ Manufacturer : Intel Corporation
╞ Product ID : 0x5917
╞ Vendor ID : 0x8086
╞ X.Org PCI ID : PCI:0:2:0
╘ Boot VGA : yes

xrandr --listactivemonitors
Monitors: 1
0: +*eDP-1 1920/294x1080/165+0+0 eDP-1

xrandr -q
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 294mm x 165mm
1920x1080 60.02*+ 60.01 59.97 59.96 59.93
1680x1050 59.95 59.88
1400x1050 59.98
1600x900 59.99 59.94 59.95 59.82
1280x1024 60.02
1400x900 59.96 59.88
1280x960 60.00
1440x810 60.00 59.97
1368x768 59.88 59.85
1280x800 59.99 59.97 59.81 59.91
1280x720 60.00 59.99 59.86 59.74
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
1024x576 59.95 59.96 59.90 59.82
960x600 59.93 60.00
960x540 59.96 59.99 59.63 59.82
800x600 60.00 60.32 56.25
840x525 60.01 59.88
864x486 59.92 59.57
700x525 59.98
800x450 59.95 59.82
640x512 60.02
700x450 59.96 59.88
640x480 60.00 59.94
720x405 59.51 58.99
684x384 59.88 59.85
640x400 59.88 59.98
640x360 59.86 59.83 59.84 59.32
512x384 60.00
512x288 60.00 59.92
480x270 59.63 59.82
400x300 60.32 56.34
432x243 59.92 59.57
320x240 60.05
360x202 59.51 59.13
320x180 59.84 59.32
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)

I've tried to boot with the hdmi cable connected and disconnected but still does not work. HDMI cable is fine, as other devices give signal. I can't rollback as update took a long time (due to the necessary change to linux-firmaware) and this is as of now my only usable machine (computer is stuck with the black screen after login). Before the update it worked flawlessly, There is no other GPU in the laptop, just the integrated intel one.

    7 days later

    Last update didn't fix the issue, tried every xandr tutorial on the internet and saw many user having problems with budgie/solus and HDMI years ago, but never posting the fix, if they fixed it.
    It was working flawlessly before, just plug and got TV signal.

      ASDTT Hello guys, as of last update (week 9 2025) the laptop's hdmi port cannot get signal to a second screen (TV).

      ASDTT Last update didn't fix the issue,

      Generally speaking, I can't agree or disagree with you.

      Speaking specifically for myself, I connected my Solus to a beamer via HDMI cable just yesterday and had no problems.
      Solus Gnome on HP Elite Book with Intel Graphic

      Have you tried a DE other than Budgie (possibly Live System)?

        AlphaElwedritsch I'm on solus budgie and I haven't tried another DE, as I said never had issues before, from one day to the other just stopped working and I couldn't find any fix on the forums and the issues on the dev tracker are either open but on systems with either dedicated or hybrid GPUs configurations.

        I don't know how helpful this would be but here it goes.
        I used to have Manjaro with kde and it often forgot my display settings, which were at the time: laptop, internal display off (lid closed all the time) and LG TV with HDMI (through display port adapter) as primary monitor and Hewlett Packard side monitor with VGA.
        When I started to have problems with Manjaro messing up this configuration , I decided to try piece of software called arandr. It helped very much, temporarily.
        Eventually something changed with some update and it was all wrong configuration again. When I tried to fix it I managed somehow get Manjaro's "control panel" and arandr out of sync!: Marjaro's (native control panel)settings seemed complete opposite from arandr's settings, and changing settings at the other end resulted opposite settings at the other. I don't remember the details but it was crazy spiral or "loop of madness". Somehow I got out of that loop by rebooting, diconnecting extra monitors and defaulting to internal display or something along those lines.
        That said, I've had no problems with arandr with Solus Budgie, so I blame Manjaro and I suppose I could suggest that you should check out arandr. For what I understand it's "just" a graphical interface for xrandr. I find it very easy to use and very informative and it has helped me with display problems.

          ASDTT

          Based on the xrandr output, the monitor isn't being detected at the OS level, so this may be a kernel issue
          If you look at the last few eopkg updates via eopkg history, was the kernel updated?
          You might try booting into the LTS kernel if you usually use the current kernel (or vica versa) to see if the HDMI monitor is detected.

            qk4-li3 arandr didn't do anything, as you say is just a graphical interface for xrandr so it won't solve anything.

            TraceyC This where the updates. Tried 6.6.83-266.lts kernel and the problem persists. xrandr output being the exact same as on the first post.

            Fecha: 2025-03-02 08:41
            
                * laszip 3.4.4-2-1-x86_64 fue eliminado.
                * appstream-data está actualizado de 58-59-1-x86_64 a 59-60-1-x86_64.
                * lutris está actualizado de 0.5.18-79-1-x86_64 a 0.5.19-80-1-x86_64.
                * gdal está actualizado de 3.8.5-47-1-x86_64 a 3.10.2-48-1-x86_64.
                * postgresql-libpq está actualizado de 17.2-54-1-x86_64 a 17.4-55-1-x86_64.
                * postgresql está actualizado de 17.2-54-1-x86_64 a 17.4-55-1-x86_64.
                * linux-firmware-intel-graphics 20250211-89-1-x86_64 está instalado.
                * packagekit está actualizado de 1.3.0-33-1-x86_64 a 1.3.0-34-1-x86_64.
                * linux-current está actualizado de 6.12.12-313-1-x86_64 a 6.12.17-314-1-x86_64.
                * nvidia-470-glx-driver-modaliases está actualizado de 470.256.02-107-1-x86_64 a 470.256.02-108-1-x86_64.
                * nvidia-glx-driver-modaliases está actualizado de 565.77-556-1-x86_64 a 565.77-557-1-x86_64.
                * linux-firmware-libertas 20250211-89-1-x86_64 está instalado.
                * breeze-cursor-theme está actualizado de 6.2.5-132-1-x86_64 a 6.3.2-135-1-x86_64.
                * leafpad está actualizado de 0.8.19-4-1-x86_64 a 0.8.19-5-1-x86_64.
                * linux-firmware-qcom 20250211-89-1-x86_64 está instalado.
                * kdecoration está actualizado de 6.2.5-113-1-x86_64 a 6.3.2-116-1-x86_64.
                * breeze está actualizado de 6.2.5-132-1-x86_64 a 6.3.2-135-1-x86_64.
                * linux-firmware-mlxsw-spectrum 20250211-89-1-x86_64 está instalado.
                * linux-firmware-amdgpu 20250211-89-1-x86_64 está instalado.
                * linux-firmware está actualizado de 20250211-88-1-x86_64 a 20250211-89-1-x86_64.
                * curl está actualizado de 8.11.1-104-1-x86_64 a 8.12.1-105-1-x86_64.
                * pdal está actualizado de 2.5.6-8-1-x86_64 a 2.8.4-9-1-x86_64.
            
            Operación #326: Actualización de repositorio
            Fecha: 2025-03-02 08:41
            
                * Repositorio Solus está actualizado.
            
            Operación #325: Actualización de repositorio
            Fecha: 2025-03-01 10:21
            
                * Repositorio Solus está actualizado.
            
            Operación #324: eliminar
            Fecha: 2025-02-28 11:36
            
                * webrtc-audio-processing03 0.3.1-1-1-x86_64 fue eliminado.
            
            Operación #323: Actualización de repositorio
            Fecha: 2025-02-28 08:29
            
                * Repositorio Solus está actualizado.
            
            Operación #322: actualizar
            Fecha: 2025-02-26 08:19
            
                * mesalib está actualizado de 24.3.4-260-1-x86_64 a 24.3.4-261-1-x86_64.
                * xorg-server está actualizado de 21.1.15-106-1-x86_64 a 21.1.16-107-1-x86_64.
                * mesalib-32bit está actualizado de 24.3.4-260-1-x86_64 a 24.3.4-261-1-x86_64.
                * xorg-xwayland está actualizado de 24.1.5-33-1-x86_64 a 24.1.6-34-1-x86_64.

            To rule out or confirm it's something with Solus, can you try booting with a live USB of another distro, and see if you can get signal over HDMI with that? Fedora would be a good choice, since they have robust hardware support. Let us know!

              Just throwing this out there... I've had an HDMI cable just stop working before. I've also had several TV HDMI ports quit working over the years. Might try a different cable/different monitor/port just to rule out the easier hardware potentials.

              Lastly, and I hope it's not the case, I've had laptop video begin to go bad... It would work with the laptop, but it could no longer push an external display. Sometimes it would magically work, most of the time it wouldn't. Laptops are not known for having great heat management, CPU and GPU fans get plugged and thermal paste just doesn't seem to work as well. That heat over time can damage both CPU and GPU. I have had luck replacing both fans on multiple laptop brands over the years along with new thermal paste and have gotten some of them to work again. Fans are typically super cheap on Ebay and Youtube usually will have a guide.

                • Edited

                TraceyC So this is going to be complicated. Tried fedora xfce live and didn't get signal on HDMI-1 port of my TV (that gets signals when other device, a console, is connected), tried fedora xfce on HDMI-2 port and got signal from laptop. Rebooted to solus budgie on 6.12.19-315-current and no signal on either port.

                zmaint I'd already said in the first post cable and tv port were on working conditions, and now can confirm both ports on TV are woking and port on laptop is working.

                Edit: Forgot to add I tried to rollback, but laszip isn't in the repo anymore, so couldn't go back to before de week 9 update.

                  ASDTT I tried to rollback

                  But it's also not a good idea to stay on an outdated system...

                    First, a general request to everyone. Please read prior replies before asking something that's already been answered. I get that people want to be helpful, but this is not helpful. Nothing is more frustrating when you're having a problem than to be asked something you already stated, or to be told something completely unrelated.

                    Also, rolling back is a standard part of troubleshooting that can help narrow down the cause of a problem. It's use is detailed in our Help Center. No one has said to keep the system rolled back, or not to update it after this issue has been resolved.

                    Thanks.

                    ASDTT I'd already said in the first post cable and tv port were on working conditions, and now can confirm both ports on TV are woking and port on laptop is working.

                    OK, you've eliminated the cable and ports (both on laptop and the TV) as the cause of the problem. That's good.
                    So, Fedora on the laptop will send signal to HDMI2 on your TV but not HDMI1 (which is known working with other hardware).

                    That says the kernel or something in the video stack is happening.

                    • You said the kernel on Budgie was 6.12.19-315-current (which is up to date). What kernel was running on the Fedora live ISO?

                    Unfortunately, the display stack and drivers aren't something I'm very familiar with, so hopefully someone who is can also chime in.

                      5 days later

                      ASDTT

                      That does point to this likely being an issue with kernel drivers. I recommend opening a bug report on our issues tracker.