External monitor not working after update

General system Newbie
1

Updated after about 1.5 months now external monitor doesnt connect and screen freezes when external monitor is plugged in.

Intel laptop to thunderbolt 4 hub. hub’s hdmi to monitor.

Plugging in hdmi freezes laptop screen and no image goes to monitor. unplugging hdmi only

unfreezes laptop, hub’s usb devices work.

I’ve checked /var/log/pacman.log and there is no errors related.

I ran -S linux-firmware as seen in another recent post but still doesnt fix the issue.

I restarted both laptop and monitor multiple times, did not resolve the issue.

Any ideas?

here’s the inxi -Gaz (disconnected from monitor)

Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: ASUSTeK
    driver: i915 v: kernel alternate: xe arch: Xe process: Intel 7 (10nm)
    built: 2022+ ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1
    bus-ID: 0000:00:02.0 chip-ID: 8086:a7a0 class-ID: 0300
  Device-2: Shinetech USB2.0 FHD UVC WebCam driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-8:2 chip-ID: 3277:0033
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: Samsung 0x416d built: 2021 res: 2880x1800 dpi: 234
    gamma: 1.2 size: 312x195mm (12.28x7.68") diag: 368mm (14.5") ratio: 16:10
    modes: 2880x1800
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.3-arch1.3
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Iris Xe Graphics (RPL-P)
    device-ID: 8086:a7a0 memory: 14.88 GiB unified: yes display-ID: :1.0
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor x11: xprop,xrandr
2

Before digging too deep, I’d first suggest testing another kernel (if available), e.g. LTS.

This really looks like a typical rolling-release regression in the graphics stack. I’ve seen similar issues before (in my case even a weeks-long shutdown hang on a Surface Pro, only hard power-off worked).

Switching kernels is quick, reversible, and often enough to confirm whether this is a regression or a hardware/config issue.

1 Like
4

Huge thanks man.

This resolved it.

Since this is a rolling-release thing.

I should wait until a later version of the kernel is released then test again on that?

5

Yes — wait for the next kernel in the same branch, install it and test again. That may fix it, but it’s not guaranteed.
Knowing the exact GPU helps narrowing it down — NVIDIA is often the usual suspect on rolling releases.

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.