# Enabling higher resolution in wayland

**URL:** <https://discuss.kde.org/t/enabling-higher-resolution-in-wayland/19410>\
**Category:** Help\
**Tags:** wayland\
**Created:** [July 31, 2024, 7:18am UTC](https://discuss.kde.org/t/enabling-higher-resolution-in-wayland/19410 "2024-07-31T07:18:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![josealberto4444](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/j/2bfe46/32.png) [@josealberto4444](https://discuss.kde.org/u/josealberto4444)\
**Post date:** [July 31, 2024, 7:18am UTC](https://discuss.kde.org/t/enabling-higher-resolution-in-wayland/19410/1 "2024-07-31T07:18:10Z")

</div>

I have a Philips 245E1 monitor. It doesn’t seem to send the correct edid or something, so it was a struggle to get it to work properly on Linux when I bought it some years ago (I’m currently using Manjaro). In system settings, I can only choose resolutions up to 1920x1080, but it supports a resolution of 2560x1440 at 60 Hz, as I was using it like that on X11 with this custom modeline in /etc/X11/xorg.conf.d/10-monitor.conf

```auto
Modeline "2560x1440" 241.5 2560 2608 2640 2720 1440 1443 1448 1481 +hsync +vsync

```

However, I want to use wayland and I cannot get it to work. I tried without success:

1. Generating an edid bin from that modeline, putting it in /usr/lib/firmware/edid and adding drm\_kms\_helper.edid\_firmware=edid/2560x1440.bin to grub.
2. Adding video=HDMI-A-1:2560x1440@60 to grub.

I’m out of ideas for searching anything else. Can you help me? =)

---

<div class="post-metadata">

**Author:** ![meven](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/meven/32/1748_2.png) [@meven](https://discuss.kde.org/u/meven)\
**Post date:** [July 31, 2024, 7:47am UTC](https://discuss.kde.org/t/enabling-higher-resolution-in-wayland/19410/2 "2024-07-31T07:47:43Z")

</div>

Can you share the output of the command `kscreen-doctor -o`

And maybe also the output of `drm_info -j`

Please tell us your distro and Plasma version (just to complete the context).

KWin does add common modes (that’s resolution+frequency) for screen that miss it obviously in their edid. I know about 1920x1080@60, if we can guess your screen is supposed to support 2560x1440, we might be able to adjust this.

Please report a bug for KWin on [https://bugs.kde.org/](https://bugs.kde.org/) with the details I asked.

---

<div class="post-metadata">

**Author:** ![josealberto4444](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/j/2bfe46/32.png) [@josealberto4444](https://discuss.kde.org/u/josealberto4444)\
**Post date:** [July 31, 2024, 8:19am UTC](https://discuss.kde.org/t/enabling-higher-resolution-in-wayland/19410/3 "2024-07-31T08:19:53Z")

</div>

I am using Manjaro and plasma 6.0.5.

> KWin does add common modes (that’s resolution+frequency) for screen that miss it obviously in their edid. I know about 1920x1080@60, if we can guess your screen is supposed to support 2560x1440, we might be able to adjust this.

According to the page www [dot] edid [dot] tv/edid/1959/ (I can’t post links, sorry), the maximum available for this screen is 2560x1440@74.97Hz, but my laptop only support up to 60 Hz, so I cannot check. In that page you can also download the edid provided for the TV (allegedly), in case it helps.

> Please report a bug for KWin on with the details I asked.

OK, I’m on it now, but I’ll leave also the details here just in case it helps someone.

`kscreen-doctor -o`

```auto
Output: 2 HDMI-A-1
        enabled
        connected
        priority 1
        HDMI
        Modes: 0:1920x1080@60* 1:1920x1080@60 2:1920x1080@60 3:1920x1080@60! 4:1920x1080@60 5:1920x1080@50 6:1920x1080@50 7:1280x1440@60 8:1680x1050@60 9:1280x1024@75 10:1280x1024@60 11:1440x900@60 12:1280x960@60 13:1280x720@60 14:1280x720@60 15:1280x720@60 16:1280x720@50 17:1024x768@75 18:1024x768@70 19:1024x768@60 20:832x624@75 21:800x600@75 22:800x600@72 23:800x600@60 24:800x600@56 25:720x576@50 26:720x576@50 27:720x576@50 28:720x480@60 29:720x480@60 30:720x480@60 31:720x480@60 32:720x480@60 33:640x480@75 34:640x480@73 35:640x480@67 36:640x480@60 37:640x480@60 38:640x480@60 39:720x400@70 
        Geometry: 0,0 1280x720
        Scale: 1.5
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: Automatic
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none

```

The output of `drm_info -j` does not fit here, but I’ll put it in the bug report.

---

<div class="post-metadata">

**Author:** ![josealberto4444](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/j/2bfe46/32.png) [@josealberto4444](https://discuss.kde.org/u/josealberto4444)\
**Post date:** [July 31, 2024, 10:08am UTC](https://discuss.kde.org/t/enabling-higher-resolution-in-wayland/19410/4 "2024-07-31T10:08:11Z")

</div>

Done, it’s the bug with id=491054 (I cannot post the link).

---

<div class="post-metadata">

**Author:** ![meven](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/meven/32/1748_2.png) [@meven](https://discuss.kde.org/u/meven)\
**Post date:** [July 31, 2024, 10:23am UTC](https://discuss.kde.org/t/enabling-higher-resolution-in-wayland/19410/5 "2024-07-31T10:23:57Z")

</div>

I have some privileged as a regular known contributor, posting links 😆: [491054 – No resolution higher than Full HD in wayland](https://bugs.kde.org/show_bug.cgi?id=491054)

---

<div class="post-metadata">

**Author:** ![guss77](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/guss77/32/2599_2.png) [@guss77](https://discuss.kde.org/u/guss77)\
**Post date:** [March 8, 2026, 10:32am UTC](https://discuss.kde.org/t/enabling-higher-resolution-in-wayland/19410/6 "2026-03-08T10:32:59Z")

</div>

**Update:** as reported in bug 456697 (not the one linked above, the one linked from that), as of December 2025 (in git) and Plasma 6.6 (released), KDE supports custom modelines that will let you add custom resolutions and refresh rates to the ones reported by your display.

The full details are in the [merge request libkscreen MR!266](https://invent.kde.org/plasma/libkscreen/-/merge_requests/266), but it generally goes like this:

To add a custom _full screen_ 1920x1080 with 75Hz refresh:

```auto
kscreen-doctor output.1.addCustomMode.1920.1080.75000.full

```

You can then see the result in the output of `kscreen-doctor -o`:

 ![image](https://discuss-cdn.kde.org/uploads/default/original/3X/5/3/53df7e0ff669538411f76ed686b65b2c468612cc.jpeg)  
(The refresh rate is “not accurate” because things like actual display bandwidth, etc)

You can remove such custom mode by using the index number of the custom mode (the first one is 0, as can be seen in the screenshot) like so:

```auto
kscreen-doctor output.1.removeCustomMode.0

```

The `full` at the end of the `addCustomMode` command means that the new mode is stretched to fit the screen. The other option is `reduced` which will leave black bars on the aspect that doesn’t fit when kwin matches resolution and aspect ratio for your screen - this could be top and bottom black bars if you set the height “too low” or right and left black bars if you set the resolution not wide enough.
