Setting "UseEDID" to false in X11 config results in out of range

olifurz · 2026-04-19 13:14:57

(note: i formerly used nouveau for a short time but found issues with GSP and opted to just try fix the issues i was having with nvidia)

Running on a RTX 3060, attempting to create any interlaced mode via xrandr --newmode then adding it with xrandr --addmode results in the following error
For example "xrandr --newmode "1280x1024i_60" 112.89 1280 1360 1496 1712 1024 1026 1032 1098 interlace" then finally "xrandr --addmode DP-0 1280x1024i_60"

X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  16 (RRCreateMode)
  Serial number of failed request:  38
  Current serial number in output stream:  38

Issue doesn't occur when creating progressive resolutions

Found a fix for this issue found here however after rebooting with this fix I get greeted with an "out of range" error on my monitor (hp 7550) when loading into lightdm. I'm able to switch to another tty and the error disappears however.

Upon retrying the command again I get

X Error of failed request:  BadName (invalid parameter attributes)
...

/etc/X11/xorg.conf is as follows

Section "Monitor"
    Identifier "DFP-1"
    # These match up with my monitor's specs in the user manual
    HorizSync 30.0 - 86.0
    VertRefresh 50.0 - 140.0
    Option "DPMS" "true"
    # When this is set to false, monitor goes out of range
    Option "UseEdid" "true" 
    # Removing these options just seems to remove a lot of resolutions that I can select in XFCE
    Option "ModeValidation" "AllowDpInterlaced,AllowInterlacedModes,NoDFPNativeResolutionCheck,AllowNonEdidModes,NoMaxPClkCheck,NoHorizSyncCheck,NoVertRefreshCheck"
EndSection

Section "Device"
        Identifier "NVIDIA"
        Driver "nvidia"
        Option "ConnectedMonitor" "DFP-1"
        Option "IgnoreEDIDChecksum" "DFP-1"
        # Doesn't appear to do anything despite the file being set, can't set the custom interlaced resolution I added
        Option "CustomEDID" "DFP-1:/etc/X11/edid.bin"    
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "NVIDIA"
    Monitor "DFP-1"
    DefaultDepth 24    
EndSection

Last edited by olifurz (2026-04-19 13:40:02)

seth · 2026-04-19 14:16:49

nvidia will not allow you to add random modelines and Option "ModeValidation" goes into the device or screen section, not the monitor one - actually completely remove that for now.

olifurz · 2026-04-19 15:32:41

seth wrote:

nvidia will not allow you to add random modelines.

Define random here, a friend who also happens to own a CRT monitor had a similar X/Nvidia config and managed to output things just fine with that modeline.

seth wrote:

Option "ModeValidation" goes into the device or screen section, not the monitor one - actually completely remove that for now

Completely remove the monitor section or the option?

seth · 2026-04-19 16:29:53

"Random" means anything that's not in the set of modes granted by the modevalidation. Stuff you just made up, no matter how valid or sensible the modeline itself is.
You might want to add a monitor section w/ a specific mode (though nvidia prefers the metamode option anyway) but you'll need to loosen the modevalidation - just not in that option, nvidia takes key from the device and screen sections, https://download.nvidia.com/XFree86/Lin … tions.html

olifurz · 2026-04-19 16:38:58

After some experimenting with the ModeLine option in the Monitor section, it seems that having an interlaced modeline reports out of range regardless of if UseEdid is enabled or not. I've tried using Video Timings Calculator to generate these modelines

How am I supposed to loosen the mode validation correctly? Moving the ones I already had such as AllowInterlacedModes to the Device section doesn't appear to solve the issue.

Last edited by olifurz (2026-04-19 16:44:59)

olifurz · 2026-04-19 17:01:49

The X config options I had bookmarked was out of date.. , cheers for the new one

Last edited by olifurz (2026-04-19 17:02:03)

seth · 2026-04-19 17:04:10

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Post you present xorg config and xorg log, the UseEDID option won't help you here at all, the ModeValidation option controls what is allowed.

olifurz · 2026-04-19 18:15:53

Xorg.0.log
xorg.conf
/etc/X11/edid.bin (can be analysed with a tool like edid-decode)
As a reminder, this is a HP 7550 passing through a VGA to DP converter

Last edited by olifurz (2026-04-19 18:21:52)

seth · 2026-04-19 19:15:31

Try

Option "ModeValidation" "NoMaxPClkCheck, NoHorizSyncCheck, NoVertRefreshCheck, NoDisplayPortBandwidthCheck, AllowDpInterlaced, AllowNonEdidModes"

Edit:

As a reminder, this is a HP 7550 passing through a VGA to DP converter

There's no guarantee that any modeline you test is actually working - the immediate goal is to be able to actually add one.

Last edited by seth (2026-04-19 19:16:25)

olifurz · 2026-04-19 19:36:53

seth wrote:

Try

Option "ModeValidation" "NoMaxPClkCheck, NoHorizSyncCheck, NoVertRefreshCheck, NoDisplayPortBandwidthCheck, AllowDpInterlaced, AllowNonEdidModes"

Interlaced modeline I added via the EDID does not show up still, not in xrandr or XFCE display settings.
Xorg.0.log

Edit: I attempted to run "xrandr --newmode "1280x480_120i" 105.91 1280 1360 1496 1712 480 481 484 515 interlace -hsync +vsync" and "xrandr --addmode DP-0 "1280x480_120i"" which matches the modeline configurated in the EDID and I still get thrown "BadMatch (invalid parameter attributes)"

xrandr --verbose outputs this

Last edited by olifurz (2026-04-19 19:47:27)

seth · 2026-04-19 19:47:14

Nvidia has an extra option to load an external edid, see the nvidia readme.
For now, does

◉ cvt12 1280 1024 60 -i                    
# 1280x1024 @ 60.000 Hz Interlaced (CVT) field rate 59.747 Hz; hsync: 31.875 kHz; pclk: 51.00 MHz
Modeline "1280x1024_60.00i"  51.00  1280 1312 1440 1600  1024 1027 1034 1045 Interlace  -hsync +vsync

=>

xrandr --newmode "1280x1024_60.00i"  51.00  1280 1312 1440 1600  1024 1027 1034 1045 Interlace  -hsync +vsync
xrandr --addmode DP-0 1280x1024i_60"

work?

Edit:

[  5371.819] (II) NVIDIA(0): Setting mode "DP-0: 1280x960 @1280x960 +0+0 {ViewPortIn=1280x960, ViewPortOut=1280x960+0+0}"

Try

◉ cvt12 1280 960 60 -i                    
# 1280x960 @ 60.000 Hz Interlaced (CVT) field rate 59.628 Hz; hsync: 29.844 kHz; pclk: 47.75 MHz
Modeline "1280x960_60.00i"  47.75  1280 1312 1440 1600  960 963 967 980 Interlace  -hsync +vsync

Last edited by seth (2026-04-19 19:49:32)

olifurz · 2026-04-19 19:50:18

seth wrote:

Nvidia has an extra option to load an external edid, see the nvidia readme.

You can see I did this in the xorg config. (or are we on about different options?)

seth wrote:

For now, does

◉ cvt12 1280 1024 60 -i                    
# 1280x1024 @ 60.000 Hz Interlaced (CVT) field rate 59.747 Hz; hsync: 31.875 kHz; pclk: 51.00 MHz
Modeline "1280x1024_60.00i"  51.00  1280 1312 1440 1600  1024 1027 1034 1045 Interlace  -hsync +vsync

=>

xrandr --newmode "1280x1024_60.00i"  51.00  1280 1312 1440 1600  1024 1027 1034 1045 Interlace  -hsync +vsync
xrandr --addmode DP-0 1280x1024i_60"

work?

Reports the same as my edited message earlier:

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  38
  Current serial number in output stream:  39

seth · 2026-04-19 19:55:42

Yeah, sorry - missed that.

[  5369.462] (**) NVIDIA(0): Option "CustomEDID" "DFP-1:/etc/X11/edid.bin"

Does the 1280x960 mode work?

Adding

Option "ModeDebug" "True"

will make the driver log what mode it rejects why.

olifurz · 2026-04-19 20:03:46

Xorg.0.log

[ 6869.399] (WW) NVIDIA(GPU-0): Validating Mode "1280x960_120i":
[ 6869.399] (WW) NVIDIA(GPU-0): Mode Source: EDID
[ 6869.399] (WW) NVIDIA(GPU-0): 1280 x 960 @ 120 Hz
[ 6869.399] (WW) NVIDIA(GPU-0): Pixel Clock : 105.91 MHz
[ 6869.399] (WW) NVIDIA(GPU-0): HRes, HSyncStart : 1280, 1360
[ 6869.399] (WW) NVIDIA(GPU-0): HSyncEnd, HTotal : 1496, 1712
[ 6869.399] (WW) NVIDIA(GPU-0): VRes, VSyncStart : 960, 962
[ 6869.399] (WW) NVIDIA(GPU-0): VSyncEnd, VTotal : 968, 1030
[ 6869.399] (WW) NVIDIA(GPU-0): Sync Polarity : -H +V
[ 6869.399] (WW) NVIDIA(GPU-0): Extra : Interlace
[ 6869.399] (WW) NVIDIA(GPU-0): Mode is rejected: Interlaced modes are not supported on
[ 6869.399] (WW) NVIDIA(GPU-0): this GPU.
[ 6869.399] (WW) NVIDIA(GPU-0): GPU extended capability check failed.
[ 6869.399] (WW) NVIDIA(GPU-0): Mode "1280x960_120i" is invalid.

Not good. All hope lost?
Edit: Appending "NoExtendedGpuCapabilitiesCheck" to the end of the ModeValidation option doesn't make any difference (strange?)

Last edited by olifurz (2026-04-19 20:09:34)

seth · 2026-04-19 20:13:49

Not sure how reliable https://www.reddit.com/r/GloriousCRTMas … t/idqlx0z/ is but your GPU is obviously way newer than that

olifurz · 2026-04-19 20:20:41

seth wrote:

Not sure how reliable https://www.reddit.com/r/GloriousCRTMas … t/idqlx0z/ is but your GPU is obviously way newer than that

Haven't got a second PCIe slot so can't do passthrough with an older GPU (& my CPU doesn't have integrated graphics, what a bummer)

Strange how NoExtendedGpuCapabilitiesCheck doesn't affect this since it's meant to bypass these checks. Might return to Nouveau sometime to see if I can get that working again, unless it's hardware-related?

seth · 2026-04-19 20:22:21

The GPU hardware might be unable to generate those modelines

olifurz · 2026-04-19 20:31:03

seth wrote:

The GPU hardware might be unable to generate those modelines

I'll have a try at Nouveau when I'm in the mood, many thanks for your help o7

olifurz · 2026-04-19 21:49:46

Had a try at nouveau, it may just be that my card doesn't support it cause while it does display the interlaced options, my GPU just cuts out entirely like you saw in my previous post

Apr 19 22:42:30 arch kernel: nouveau 0000:09:00.0: gsp: Xid:56 CMDre 00000000 00002008 00>
Apr 19 22:42:30 arch kernel: nouveau 0000:09:00.0: gsp: Xid:56 CMDre 00000000 00000200 00>
Apr 19 22:42:32 arch kernel: nouveau 0000:09:00.0: drm: core notifier timeout
Apr 19 22:42:34 arch kernel: nouveau 0000:09:00.0: drm: wndw-0: timeout
Apr 19 22:42:47 arch kernel: nouveau 0000:09:00.0: drm: core notifier timeout
Apr 19 22:42:49 arch kernel: nouveau 0000:09:00.0: drm: wndw-0: timeout
Apr 19 22:42:51 arch kernel: nouveau 0000:09:00.0: drm: core notifier timeout
Apr 19 22:42:53 arch kernel: nouveau 0000:09:00.0: drm: core notifier timeout
Apr 19 22:42:55 arch kernel: nouveau 0000:09:00.0: drm: core notifier timeout
Apr 19 22:42:57 arch kernel: nouveau 0000:09:00.0: drm: wndw-0: timeout
Apr 19 22:42:59 arch kernel: nouveau 0000:09:00.0: drm: core notifier timeout
Apr 19 22:43:01 arch kernel: nouveau 0000:09:00.0: drm: wndw-0: timeout
Apr 19 22:43:01 arch systemd[1]: Started Getty on tty2.
Apr 19 22:43:02 arch kernel: ------------[ cut here ]------------
Apr 19 22:43:02 arch kernel: nouveau 0000:09:00.0: [drm] vblank wait timed out on crtc 0
Apr 19 22:43:02 arch kernel: WARNING: drivers/gpu/drm/drm_vblank.c:1318 at drm_wait_one_v>
Apr 19 22:43:02 arch kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq>
Apr 19 22:43:02 arch kernel:  libphy snd i2c_smbus bluetooth k10temp iwlwifi ccp soundcor>
Apr 19 22:43:02 arch kernel: CPU: 3 UID: 0 PID: 328 Comm: kworker/3:2 Not tainted 6.19.11>
Apr 19 22:43:02 arch kernel: Hardware name: System manufacturer System Product Name/PRIME>
Apr 19 22:43:02 arch kernel: Workqueue: events drm_fb_helper_damage_work
Apr 19 22:43:02 arch kernel: RIP: 0010:drm_wait_one_vblank+0x179/0x220
Apr 19 22:43:02 arch kernel: Code: 0f 84 bc 00 00 00 48 8b 7b 08 4c 8b 67 50 4d 85 e4 75 >
Apr 19 22:43:02 arch kernel: RSP: 0018:ffffcdf0409e3da8 EFLAGS: 00010286
Apr 19 22:43:02 arch kernel: RAX: ffffffffc12b4729 RBX: ffff8c8141129800 RCX: 00000000000>
Apr 19 22:43:02 arch kernel: RDX: ffff8c8141bd3610 RSI: ffffffffc12b4729 RDI: ffffffff977>
Apr 19 22:43:02 arch kernel: RBP: 0000000000000000 R08: 00000020ac098126 R09: 00000000000>
Apr 19 22:43:02 arch kernel: R10: ffff8c814b191b00 R11: 0000000000000000 R12: ffff8c8141b>
Apr 19 22:43:02 arch kernel: R13: 0000000000002115 R14: ffff8c816a5f1830 R15: ffff8c814b2>
Apr 19 22:43:02 arch kernel: FS:  0000000000000000(0000) GS:ffff8c88b6d83000(0000) knlGS:>
Apr 19 22:43:02 arch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 19 22:43:02 arch kernel: CR2: 00005601536099b6 CR3: 0000000130930000 CR4: 00000000003>
Apr 19 22:43:02 arch kernel: Call Trace:
Apr 19 22:43:02 arch kernel:  <TASK>
Apr 19 22:43:02 arch kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Apr 19 22:43:02 arch kernel:  drm_client_modeset_wait_for_vblank+0x5b/0x70
Apr 19 22:43:02 arch kernel:  drm_fb_helper_damage_work+0x7e/0x1a0
Apr 19 22:43:02 arch kernel:  process_one_work+0x193/0x350
Apr 19 22:43:02 arch kernel:  worker_thread+0x1a1/0x310
Apr 19 22:43:02 arch kernel:  ? __pfx_worker_thread+0x10/0x10
Apr 19 22:43:02 arch kernel:  kthread+0xfc/0x240
Apr 19 22:43:02 arch kernel:  ? __pfx_kthread+0x10/0x10
Apr 19 22:43:02 arch kernel:  ? __pfx_kthread+0x10/0x10
Apr 19 22:43:02 arch kernel:  ret_from_fork+0x243/0x280
Apr 19 22:43:02 arch kernel:  ? __pfx_kthread+0x10/0x10
Apr 19 22:43:02 arch kernel:  ret_from_fork_asm+0x1a/0x30
Apr 19 22:43:02 arch kernel:  </TASK>
Apr 19 22:43:02 arch kernel: ---[ end trace 0000000000000000 ]---
Apr 19 22:43:03 arch kernel: ------------[ cut here ]------------
Apr 19 22:43:03 arch kernel: nouveau 0000:09:00.0: [drm] vblank wait timed out on crtc 0
Apr 19 22:43:03 arch kernel: WARNING: drivers/gpu/drm/drm_vblank.c:1318 at drm_wait_one_v>
Apr 19 22:43:03 arch kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq>
Apr 19 22:43:03 arch kernel:  libphy snd i2c_smbus bluetooth k10temp iwlwifi ccp soundcor>
Apr 19 22:43:03 arch kernel: CPU: 3 UID: 0 PID: 328 Comm: kworker/3:2 Tainted: G        W>
Apr 19 22:43:03 arch kernel: Tainted: [W]=WARN
Apr 19 22:43:03 arch kernel: Hardware name: System manufacturer System Product Name/PRIME>
Apr 19 22:43:03 arch kernel: Workqueue: events drm_fb_helper_damage_work
Apr 19 22:43:03 arch kernel: RIP: 0010:drm_wait_one_vblank+0x179/0x220
Apr 19 22:43:03 arch kernel: Code: 0f 84 bc 00 00 00 48 8b 7b 08 4c 8b 67 50 4d 85 e4 75 >
Apr 19 22:43:03 arch kernel: RSP: 0018:ffffcdf0409e3da8 EFLAGS: 00010286
Apr 19 22:43:03 arch kernel: RAX: ffffffffc12b4729 RBX: ffff8c8141129800 RCX: 00000000000>
Apr 19 22:43:03 arch kernel: RDX: ffff8c8141bd3610 RSI: ffffffffc12b4729 RDI: ffffffff977>
Apr 19 22:43:03 arch kernel: RBP: 0000000000000000 R08: 00000020e9126f7d R09: 00000000000>
Apr 19 22:43:03 arch kernel: R10: ffff8c814b191b00 R11: 0000000000000000 R12: ffff8c8141b>
Apr 19 22:43:03 arch kernel: R13: 0000000000002115 R14: ffff8c816a5f1830 R15: ffff8c814b2>
Apr 19 22:43:03 arch kernel: FS:  0000000000000000(0000) GS:ffff8c88b6d83000(0000) knlGS:>
Apr 19 22:43:03 arch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 19 22:43:03 arch kernel: CR2: 00000c1400e69980 CR3: 0000000130930000 CR4: 00000000003>
Apr 19 22:43:03 arch kernel: Call Trace:
Apr 19 22:43:03 arch kernel:  <TASK>
Apr 19 22:43:03 arch kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Apr 19 22:43:03 arch kernel:  drm_client_modeset_wait_for_vblank+0x5b/0x70
Apr 19 22:43:03 arch kernel:  drm_fb_helper_damage_work+0x7e/0x1a0
Apr 19 22:43:03 arch kernel:  process_one_work+0x193/0x350
Apr 19 22:43:03 arch kernel:  worker_thread+0x1a1/0x310
Apr 19 22:43:03 arch kernel:  ? __pfx_worker_thread+0x10/0x10
Apr 19 22:43:03 arch kernel:  kthread+0xfc/0x240
Apr 19 22:43:03 arch kernel:  ? __pfx_kthread+0x10/0x10
Apr 19 22:43:03 arch kernel:  ? __pfx_kthread+0x10/0x10
Apr 19 22:43:03 arch kernel:  ret_from_fork+0x243/0x280
Apr 19 22:43:03 arch kernel:  ? __pfx_kthread+0x10/0x10
Apr 19 22:43:03 arch kernel:  ret_from_fork_asm+0x1a/0x30
Apr 19 22:43:03 arch kernel:  </TASK>
Apr 19 22:43:03 arch kernel: ---[ end trace 0000000000000000 ]---

Arch Linux

#1 2026-04-19 13:14:57

Setting "UseEDID" to false in X11 config results in out of range

#2 2026-04-19 14:16:49

Re: Setting "UseEDID" to false in X11 config results in out of range

#3 2026-04-19 15:32:41

Re: Setting "UseEDID" to false in X11 config results in out of range

#4 2026-04-19 16:29:53

Re: Setting "UseEDID" to false in X11 config results in out of range

#5 2026-04-19 16:38:58

Re: Setting "UseEDID" to false in X11 config results in out of range

#6 2026-04-19 17:01:49

Re: Setting "UseEDID" to false in X11 config results in out of range

#7 2026-04-19 17:04:10

Re: Setting "UseEDID" to false in X11 config results in out of range

#8 2026-04-19 18:15:53

Re: Setting "UseEDID" to false in X11 config results in out of range

#9 2026-04-19 19:15:31

Re: Setting "UseEDID" to false in X11 config results in out of range

#10 2026-04-19 19:36:53

Re: Setting "UseEDID" to false in X11 config results in out of range

#11 2026-04-19 19:47:14

Re: Setting "UseEDID" to false in X11 config results in out of range

#12 2026-04-19 19:50:18

Re: Setting "UseEDID" to false in X11 config results in out of range

#13 2026-04-19 19:55:42

Re: Setting "UseEDID" to false in X11 config results in out of range

#14 2026-04-19 20:03:46

Re: Setting "UseEDID" to false in X11 config results in out of range

#15 2026-04-19 20:13:49

Re: Setting "UseEDID" to false in X11 config results in out of range

#16 2026-04-19 20:20:41

Re: Setting "UseEDID" to false in X11 config results in out of range

#17 2026-04-19 20:22:21

Re: Setting "UseEDID" to false in X11 config results in out of range

#18 2026-04-19 20:31:03

Re: Setting "UseEDID" to false in X11 config results in out of range

#19 2026-04-19 21:49:46

Re: Setting "UseEDID" to false in X11 config results in out of range

Board footer