Hardware-damaged eDP cable forcing 144Hz - Hard-locking 60Hz and Killing Wayland (Asus TUF F15)
06:01 09 May 2026

The Situation: I have an Asus TUF F15 with a physically damaged display cable. The 144Hz signal causes the screen to flicker and go black immediately, but the hardware works fine at 60Hz. I need a way to completely blacklist 144Hz at the system level so it never even attempts to probe that frequency.

The Issue: I am trying to force X11 because Wayland keeps defaulting to the hardware's 144Hz EDID profile. Even after uncommenting WaylandEnable=false in /etc/gdm3/custom.conf**, the system is STILL booting into Wayland.** I don't know who designed this, but the standard "off switch" isn't working, and I can't see the screen to change it manually.

What I have already tried:

  1. GRUB: Added video=eDP-1:1920x1080@60D and GRUB_GFXMODE=1920x1080@60 to /etc/default/grub. Ran update-grub.

  2. GDM3 Config: Set WaylandEnable=false (ignored by system).

  3. Display Cache: Deleted ~/.config/monitors.xml.

What I need help with:

  1. Scorched Earth Wayland Kill: Since the config file is being ignored, how do I manually mask or move the Wayland session files so the OS is physically forced into Xorg?

  2. Xorg Hard-Lock: What is the exact xorg.conf.d syntax to lock eDP-1 to 60Hz and ignore all other modes?

  3. BIOS/Boot: The BIOS splash screen is 144Hz and flickering. Is there any way to force 60Hz during POST or force the BIOS to HDMI without seeing the internal screen?

Specs:

  • Laptop: Asus TUF Dash F15

  • Distro: Lubuntu / GNOME

  • Status: Screen is unusable unless 60Hz is forced via terminal.

linux ubuntu wayland asus