System freezes after connecting second monitor

English Hardware
1

I have fresh installation of Opensuse Tubleweeb on my Notebook HP Elitbook 860, and I have a following problem:

When I’m connecting second monitor, or beamer, by HDMI, the system freezes, becoming totally irresponsible. The system works well, however, if the second monitor was connected from the start. But even in this case the system is freezing randomly after screensaver logout.

This problem occurs both with X.11 and Wayland.

Here is inxy -GS:

System:
Kernel: 6.8.1-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
Desktop: GNOME v: 46.0 tk: GTK v: 3.24.41 wm: gnome-shell
tools: gsd-screensaver-proxy avail: xscreensaver dm: GDM v: 46.0
Distro: openSUSE Tumbleweed 20240326
Machine:
Type: Laptop System: HP product: HP EliteBook 860 16 inch G10 Notebook PC
v: SBKPF serial: Chassis: type: 10
serial:
Graphics:
Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Hewlett-Packard
driver: i915 v: kernel alternate: xe arch: Gen-13 process: Intel 7 (10nm)
built: 2022+ ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:a7a1 class-ID: 0300
Device-2: Cheng Uei Precision Industry (Foxlink) HP 5MP Camera
driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
bus-ID: 3-1:2 chip-ID: 05c8:0613 class-ID: fe01 serial:
Display: x11 server: X.org v: 1.21.1.11 with: Xwayland v: 23.2.4
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
alternate: intel dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1200 s-size: <missing: xdpyinfo>
Monitor-1: eDP-1 model: LG Display 0x0702 built: 2022 res: 1920x1200 hz: 60
dpi: 141 gamma: 1.2 chroma: red: x: 0.596 y: 0.369 green: x: 0.365 y: 0.553
blue: x: 0.153 y: 0.102 white: x: 0.314 y: 0.329
size: 345x215mm (13.58x8.46") diag: 407mm (16") ratio: 16:10
modes: 1920x1200
EDID-Warnings: 1: parse_edid: unknown flag 2
API: OpenGL v: 4.6 vendor: intel mesa v: 24.0.3 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel Graphics (RPL-U) device-ID: 8086:a7a1
memory: 30.26 GiB unified: yes
API: EGL Message: EGL data requires eglinfo. Check --recommends.

Thank you for signaling if I can provide any additional helpful information to solve this problem.

Cordially.

2

@Sprn Hi and welcome to the Forum :smile:
Since your gpu supports the Xe driver, have you tried that?

3

@malcolmlewis Thank you, my pleasure!

To be honest, I’m not sure. I haven’t change the default driver anyway.

Here is the lspci VGA info:

lspci -nnk | grep VGA -A 3 | grep -E “VGA|driver”
00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04)
Kernel driver in use: i915

4

@Sprn If you look at the inxi output I see driver: i915 v: kernel alternate: xe as well as;

 /sbin/modinfo xe | grep A7A1
alias:          pci:v00008086d0000A7A1sv*sd*bc03sc*i*

At grub if you press the ‘e’ key to edit grub and arrow down to the line linux/linuxefi and press the end key and add module_blacklist=i915 and press F10 to boot, does that switch or just get a black screen? That entry is only a test, so next boot it won’t be there.

5

@malcolmlewis : Thank you for the hint.
I did as you said, it switched and loaded normally. Although the graphics was weird (somewhat stretched vertically), with eventual flickering.
Unfortunately, I cannot check if this option works with HDMI before Tuesday, as I am using second monitor at my workplace only. I’ll tell you though Tuesday.
Thank you once again.

6

@Sprn so it did switch to the xe driver inxi -Gxxz?

So, with either the i915 or xe module there are a plethora of options that can be set;

/sbin/modinfo i915 | grep "parm:"

/sbin/modinfo xe | grep "parm:"

So you might need to read up on those…

7

@Sprn so it did switch to the xe driver inxi -Gxxz?

I’m not sure, this is inxi -Gxxz with i915 blacklisted:

Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Hewlett-Packard
    driver: N/A arch: Gen-13 bus-ID: 00:02.0 chip-ID: 8086:a7a1

Thank you, I will search and read about the options of i915!

8

@Sprn so it didn’t use the xe driver, likely just a modesetting one… so if you use that command again to boot, then when in the system switch to root user and run the command modprobe xe might need to logout/login, does it show xe in the output of the inxi command?

I would probably just stick with the default i915 and see what parameters may be usefully.