[SOLVED] Second display (DP-1) not rendering properly on Hyprland

treqo · 2025-12-08 05:59:12

Hi all,

I'm new to Arch, coming from Ubuntu and am currently facing an issue with what seems to be some sort of display corruption on my secondary internal display. My computer is ASUS ROG Zephyrus Duo 15 GX550. I'll start off by providing some info on my system and current configs:

fastfetch output for system overview

                  -`                     treqo@arch-ROG-Zephyrus
                 .o+`                    -----------------------
                `ooo/                    OS: Arch Linux x86_64
               `+oooo:                   Host: ROG Zephyrus GX550LXS_GX550LXS (1.0)
              `+oooooo:                  Kernel: Linux 6.17.9-arch1-1
              -+oooooo+:                 Uptime: 10 mins
            `/:-:++oooo+:                Packages: 635 (pacman)
           `/++++/+++++++:               Shell: bash 5.3.8
          `/++++++++++++++:              Display (BOE085F): 1920x550 @ 2.5x in 14",]
         `/+++ooooooooooooo/`            Display (AUO31EB): 3840x2160 @ 2.5x in 15"]
        ./ooosssso++osssssso+`           WM: Hyprland 0.52.2 (Wayland)
       .oossssso-````/ossssss+`          Cursor: Adwaita
      -osssssso.      :ssssssso.         Terminal: kitty 0.44.0
     :osssssss/        osssso+++.        Terminal Font: FreeMono (11pt)
    /ossssssss/        +ssssooo/-        CPU: Intel(R) Core(TM) i9-10980HK (16) @ 5z
  `/ossssso+/:-        -:/+osssso+-      GPU 1: NVIDIA GeForce RTX 2080 SUPER Mobil]
 `+sso+:-`                 `.-/+oso:     GPU 2: Intel UHD Graphics @ 1.25 GHz [Inte]
`++:.                           `-/+/    Memory: 2.92 GiB / 31.12 GiB (9%)
.`                                 `/    Swap: 0 B / 4.00 GiB (0%)
                                         Disk (/): 7.71 GiB / 936.84 GiB (1%) - ext4
                                         Local IP (wlan0): 10.0.0.158/24
                                         Battery (ASUS Battery): 100% [AC Connected]
                                         Locale: en_US.UTF-8

Output of inxi (Graphics part)

Graphics:
  Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: ASUSTeK driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: DP-1,eDP-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:9bc4
    class-ID: 0300
  Device-2: NVIDIA TU104BM [GeForce RTX 2080 SUPER Mobile / Max-Q]
    vendor: ASUSTeK driver: nvidia v: 580.105.08 alternate: nouveau,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
    arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none empty: DP-2, DP-3, HDMI-A-1, eDP-2 bus-ID: 01:00.0
    chip-ID: 10de:1ed3 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: Hyprland v: 0.52.2 driver: X: loaded: intel,nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: i965 gpu: i915
    display-ID: 1
  Monitor-1: DP-1 model: BOE Display 0x085f built: 2019 res: 3840x1100
    dpi: 284 gamma: 1.2 size: 344x99mm (13.54x3.9") diag: 358mm (14.1") modes:
    max: 3840x1100 min: 1920x550
  Monitor-2: eDP-1 model: AU Optronics 0x31eb built: 2017 res: 3840x2160
    dpi: 284 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5")
    ratio: 16:9 modes: 3840x2160
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
    inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.3.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
    device-ID: 8086:9bc4 memory: 30.39 GiB unified: yes
  Info: Tools: api: eglinfo,glxinfo gpu: nvidia-smi x11: xprop,xrandr

hyprctl monitors all (the problematic display is DP-1)

Monitor eDP-1 (ID 0):
3840x2160@60.00200 at 0x0
description: AU Optronics 0x31EB
make: AU Optronics
model: 0x31EB
physical size (mm): 340x190
serial:
active workspace: 1 (1)
special workspace: 0 ()
reserved: 0 0 0 0
scale: 2.50
transform: 0
focused: yes
dpmsStatus: 1
vrr: false
solitary: 0
solitaryBlockedBy: windowed mode,missing candidate
activelyTearing: false
tearingBlockedBy: next frame is not torn,user settings,missing candidate
directScanoutTo: 0
directScanoutBlockedBy: user settings,software renders/cursors,missing candidate
disabled: false
currentFormat: XRGB8888
mirrorOf: none
availableModes: 3840x2160@60.00Hz
colorManagementPreset: srgb
sdrBrightness: 1.00
sdrSaturation: 1.00
sdrMinLuminance: 0.20
sdrMaxLuminance: 80

Monitor DP-1 (ID 1):
1920x550@60.05600 at 0x2160
description: BOE 0x085F
make: BOE
model: 0x085F
physical size (mm): 340x100
serial:
active workspace: 2 (2)
special workspace: 0 ()
reserved: 0 0 0 0
scale: 2.50
transform: 0
focused: no
dpmsStatus: 1
vrr: false
solitary: 0
solitaryBlockedBy: windowed mode,missing candidate
activelyTearing: false
tearingBlockedBy: next frame is not torn,user settings,missing candidate
directScanoutTo: 0
directScanoutBlockedBy: user settings,software renders/cursors,missing candidate
disabled: false
currentFormat: XRGB8888
mirrorOf: none
availableModes: 3840x1100@60.02Hz 3840x1100@48.02Hz 1920x550@60.06Hz 1920x550@48.08Hz
colorManagementPreset: srgb
sdrBrightness: 1.00
sdrSaturation: 1.00
sdrMinLuminance: 0.20
sdrMaxLuminance: 80

hyprland.conf (Monitors section)
For context, I have it set at 1920x550@60.06 since it's one of the available modes, and hyprland freezes whenever I have it set at 3840x1100 and the config is reloaded (I have a feeling this is related somehow). To unfreeze, I go to TTY then go back to Hyprland and it unfreezes – my guess is that it falls back to 1920x550, since the moment it freezes the secondary screen looks different* (images attached at the bottom of post)

monitor = desc:AU Optronics 0x31EB, 3840x2160@60.00, 0x0, 2.5
monitor = desc:BOE 0x085F, 1920x550@60.06, 0x2160, 2.5, transform, 0

Additionally, I took some pictures and a screencapture:

The default look with DP-1 at 1920x550

The updated look with DP-1 at 3840x1100 – screen frozen

Running grim ~/Pictures/Screenshots/screenshot.png to get a screenshot of the whole screen. This is actually one image with a transparent background separating the two screens. After taking this screenshot, I realized that I need to take into account the 2.5 times scaling, so I changed the offset of 0x2160 to 0x864 for the same result without the gap. Also tried changing it to 3840x1100 but it still causes hyprland to freeze. You can see that the top screen is 3840x2160 and the secondary screen is 1920x550.

screenshot before offset fix
screenshot after offset fix

Any help would be greatly appreciated!

Edit: Changed embedded images to links

Last edited by treqo (2025-12-13 08:34:40)

seth · 2025-12-08 10:07:58

Please replace the oversized images w/ links (and optionally thumbnails) to keep the posts concise.

What happens if you disable the scale? (ie. set it to 1)
Are you running hyprland on the inte or the nvidia GPU and does that make a difference?
https://wiki.hypr.land/Configuring/Multi-GPU/

Is the DP wired to the intel or the nvidia chip?

for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done

You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/
You can also test the behavior of X11 and the org log will conveniently expose the wiring of the outputs

treqo · 2025-12-09 10:39:19

Hi Seth, thanks for the reply

I followed along with the advice you gave, here are the results so far.

When I set scale to 1, the issue still occurs, all that happens is the text becomes really small (tested with res 1920x550 and 3840x1100).

I followed the guide and confirmed that Hyprland is running on Intel. I added this to my config, but when testing the nvidia gpu I used nvidia-dgpu which I also created a symlink to (and commented out EGL_VENDOR).

env = AQ_DRM_DEVICES,/dev/dri/intel-igpu 
env = __EGL_VENDOR_LIBRARY_FILENAMES,/usr/share/glvnd/egl_vendor.d/50_mesa.json

Also just for completeness

$ lspci -d ::03xx; ls -l /dev/dri/by-path/ ;echo "---------------"; ls -l /dev/dri
00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation TU104BM [GeForce RTX 2080 SUPER Mobile / Max-Q] (rev a1)
total 0
lrwxrwxrwx 1 root root  8 Dec  9 00:28 pci-0000:00:02.0-card -> ../card1
lrwxrwxrwx 1 root root 13 Dec  9 00:28 pci-0000:00:02.0-render -> ../renderD128
lrwxrwxrwx 1 root root  8 Dec  9 00:28 pci-0000:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Dec  9 00:28 pci-0000:01:00.0-render -> ../renderD129
---------------
total 0
drwxr-xr-x  2 root root        120 Dec  9 00:28 by-path
crw-rw----+ 1 root video  226,   0 Dec  9 00:50 card0
crw-rw----+ 1 root video  226,   1 Dec  9 00:50 card1
lrwxrwxrwx  1 root root          5 Dec  9 00:28 intel-igpu -> card1
lrwxrwxrwx  1 root root          5 Dec  9 00:28 nvidia-dgpu -> card0
crw-rw-rw-  1 root render 226, 128 Dec  9 00:28 renderD128
crw-rw-rw-  1 root render 226, 129 Dec  9 00:28 renderD129

Also based on the output of your provided bash command, both displays (eDP-1 and DP-1) are wired to card1 – the intel GPU.

Doing some digging into the log – full log here – with the hyprland debug option, it's a bit surprising that a bunch of the errors come from eDP-1 (the main display). Also, still not going to rule out this being an NVIDIA drm issue, getting a weird result using modetest on card1/card0.

I got i3 to work with both displays without any hassle, so I might just go with that for the time being.

Thanks for the suggestions and help so far!

seth · 2025-12-09 15:53:14

[LOG] Applying monitor rule for eDP-1
[ERR] Monitor eDP-1: REJECTED available mode 3840x2160@60.00Hz!
[ERR] Monitor eDP-1: REJECTED preferred mode!!!
[ERR] Monitor eDP-1: REJECTED available mode 3840x2160@60.00Hz!
[ERR] Monitor eDP-1: REJECTED preferred mode!!!
[ERR] Monitor eDP-1: REJECTED custom mode 3840x2160@60.00Hz!
[ERR] Monitor eDP-1 has NO FALLBACK MODES, and an INVALID one was requested: 3840x2160@60.00Hz
[LOG] [AQ] drm: Modesetting eDP-1 with 3840x2160@60.00Hz
[LOG] Added new monitor with name eDP-1 at [-1, -1] with size [0, 0], pointer 56358eff6230
[LOG] checking if we have seen this monitor before: eDP-1
[LOG] Monitor eDP-1 was not on any workspace
[LOG] [IWaylandProtocol] Registered global [WLOutput (eDP-1)]
[LOG] arrangeMonitors: eDP-1 explicit [0, 0]
[LOG] arrangeMonitors: eDP-1 xwayland [0, 0]
[LOG] New output with name DP-1
[LOG] Applying monitor rule for DP-1
[ERR] Monitor DP-1: REJECTED available mode 3840x1100@60.02Hz!
[ERR] Monitor DP-1: REJECTED preferred mode!!!
[ERR] Monitor DP-1: REJECTED available mode 3840x1100@48.02Hz!
[LOG] Monitor DP-1: requested 3840x1100@60.00Hz, using available mode 1920x550@60.06Hz
[LOG] output DP-1 succeeded basic test on format DRM_FORMAT_XRGB8888
[LOG] [AQ] drm: Modesetting DP-1 with 1920x550@60.06Hz
[LOG] Monitor DP-1 -> destroyed all render data
[LOG] Monitor DP-1 data dump: res 1920x550@60.06Hz, scale 2.50, transform 0, pos -1x-1, 10b 0

Can you post the edid decodes and your Xorg log, https://wiki.archlinux.org/title/Xorg#General ?
Does it work w/ sway or weston (ie. hyprland/configuration issue)?

treqo · 2025-12-13 08:32:35

Hi thanks for all the help. I tried sway like you suggested, and after it worked completely fine I assumed it wasn't a wayland issue, but a Hyprland specific issue. Luckily I stumbled upon this post and found a simple fix by adding AQ_NO_MODIFIERS=1 to the hyprland config file.

Cheers

Last edited by treqo (2025-12-13 08:35:48)

seth · 2025-12-13 09:03:18

For context, https://wiki.hypr.land/0.46.0/FAQ/#my-e … nal-laptop

Arch Linux

#1 2025-12-08 05:59:12

[SOLVED] Second display (DP-1) not rendering properly on Hyprland

#2 2025-12-08 10:07:58

Re: [SOLVED] Second display (DP-1) not rendering properly on Hyprland

#3 2025-12-09 10:39:19

Re: [SOLVED] Second display (DP-1) not rendering properly on Hyprland

#4 2025-12-09 15:53:14

Re: [SOLVED] Second display (DP-1) not rendering properly on Hyprland

#5 2025-12-13 08:32:35

Re: [SOLVED] Second display (DP-1) not rendering properly on Hyprland

#6 2025-12-13 09:03:18

Re: [SOLVED] Second display (DP-1) not rendering properly on Hyprland

Board footer