You are not logged in.

Pages: 1

#1 2020-12-03 17:09:13

Zeioth
Member
Registered: 2016-01-04
Posts: 7

xrandr --addmode fails with X Error of failed request: BadMatch

I've been following several arch wiki documents. But none of them seem to work on nvidia closed drivers.

METHOD 1: Using a custom EDID FILE

description: I got an EDID file from nvidia and edited it with aw-edid-editor as described  here https://forum.level1techs.com/t/overclo … nux/109323 . Then I use it like this and reboot.

    Section "Monitor"
        Identifier     "Monitor0"
        VendorName     "Unknown"
        ModelName      "Philips PHL 288E2"
        HorizSync       30.0 - 140.0
        VertRefresh     40.0 - 60.0
        Option         "DPMS"
    EndSection

    Section "Device"
        Identifier     "Device0"
        Driver         "nvidia"
        VendorName     "NVIDIA Corporation"
        BoardName      "GeForce GTX 1070"
        Option         "UseEDID"           "false"
        Option         "UseEDIDFreqs"      "false"
        Option         "NoBandWidthTest"   "true"
        Option         "ModeValidation"    "AllowNonEdidModes,NoEdidMaxPClkCheck,NoMaxPClkCheck"
        Option         "AllowDDCCI"        "true"
    EndSection

    Section "Screen"
        Identifier     "Screen0"
        Device         "Device0"
        Monitor        "Monitor0"
        DefaultDepth    30
        Option         "Stereo" "0"
        Option         "nvidiaXineramaInfoOrder" "DFP-6"
        Option         "CustomEDID" "DP-4: ~/tweaks/os-configure/misc/edid-profiles-for-screens/edid-right-4k-71hz.bin;HDMI-0: ~/tweaks/os-configure/misc/edid-profiles-for-screens/edid-left-4k-71hz.bin"
        Option         "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On}, DP-4: nvidia-auto-select +3840+0 {ForceCompositionPipeline=On, AllowGSYNCCompatible=On}"
        Option         "SLI" "Off"
        Option         "MultiGPU" "Off"
        Option         "BaseMosaic" "off"
        SubSection     "Display"
            Depth      30 
        EndSubSection
    EndSection

Then I press alt+F2 and launch xstart -- -logverbose 6 and check /var/log/xorg.0.log and there's nothing about the EDID profile.

    [   213.225] (II) event0  - Power Button: device removed
    [   213.257] (II) event6  - Blue Microphones Yeti Stereo Microphone Consumer Control: device removed
    [   213.310] (II) event7  - Kingsis Peripherals ZOWIE Gaming mouse: device removed
    [   213.364] (II) event9  - SONiX USB DEVICE: device removed
    [   213.390] (II) event10 - SONiX USB DEVICE Keyboard: device removed
    [   213.430] (II) event11 - SONiX USB DEVICE System Control: device removed
    [   213.457] (II) event2  - foostan H4ck3r k3yBo4rd (crkbd): device removed
    [   213.497] (II) event3  - foostan H4ck3r k3yBo4rd (crkbd) Mouse: device removed
    [   213.550] (II) event4  - foostan H4ck3r k3yBo4rd (crkbd) System Control: device removed
    [   213.617] (II) event12 - SONiX USB DEVICE Consumer Control: device removed
    [   213.644] (II) event5  - foostan H4ck3r k3yBo4rd (crkbd) Consumer Control: device removed
    [   243.249] (--) NVIDIA(GPU-0): DFP-0: disconnected
    [   243.249] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
    [   243.249] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
    [   243.249] (--) NVIDIA(GPU-0): 
    [   243.278] (--) NVIDIA(GPU-0): Philips PHL 288E2 (DFP-1): connected
    [   243.278] (--) NVIDIA(GPU-0): Philips PHL 288E2 (DFP-1): Internal TMDS
    [   243.278] (--) NVIDIA(GPU-0): Philips PHL 288E2 (DFP-1): 600.0 MHz maximum pixel clock
    [   243.278] (--) NVIDIA(GPU-0): 
    [   243.278] (--) NVIDIA(GPU-0): DFP-2: disconnected
    [   243.278] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
    [   243.278] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
    [   243.278] (--) NVIDIA(GPU-0): 
    [   243.278] (--) NVIDIA(GPU-0): DFP-3: disconnected
    [   243.278] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
    [   243.279] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
    [   243.279] (--) NVIDIA(GPU-0): 
    [   243.279] (--) NVIDIA(GPU-0): DFP-4: disconnected
    [   243.279] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
    [   243.279] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
    [   243.279] (--) NVIDIA(GPU-0): 
    [   243.279] (--) NVIDIA(GPU-0): DFP-5: disconnected
    [   243.279] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
    [   243.279] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
    [   243.279] (--) NVIDIA(GPU-0): 
    [   243.279] (--) NVIDIA(GPU-0): Philips PHL 288E2 (DFP-6): connected
    [   243.279] (--) NVIDIA(GPU-0): Philips PHL 288E2 (DFP-6): Internal DisplayPort
    [   243.279] (--) NVIDIA(GPU-0): Philips PHL 288E2 (DFP-6): 1440.0 MHz maximum pixel clock
    [   243.279] (--) NVIDIA(GPU-0): 
    [   243.280] (--) NVIDIA(GPU-0): DFP-7: disconnected
    [   243.280] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
    [   243.280] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
    [   243.280] (--) NVIDIA(GPU-0): 
    [   243.296] (II) NVIDIA(0): Setting mode "DP-4:3840x2160_60+3840+0{ForceCompositionPipeline=On,AllowGSYNCCompatible=On},HDMI-0:nvidia-auto-select+0+0{ForceCompositionPipeline=On}"
    [   243.523] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [   243.523] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
    [   243.523] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
    [   243.523] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
    [   243.524] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
    [   243.524] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
    [   243.524] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
    [   243.524] (II) NVIDIA(0):     Config Options in the README.
    [   243.592] (II) event1  - Power Button: is tagged by udev as: Keyboard
    [   243.592] (II) event1  - Power Button: device is a keyboard
    [   243.593] (II) event0  - Power Button: is tagged by udev as: Keyboard
    [   243.593] (II) event0  - Power Button: device is a keyboard
    [   243.594] (II) event6  - Blue Microphones Yeti Stereo Microphone Consumer Control: is tagged by udev as: Keyboard
    [   243.594] (II) event6  - Blue Microphones Yeti Stereo Microphone Consumer Control: device is a keyboard
    [   243.595] (II) event7  - Kingsis Peripherals ZOWIE Gaming mouse: is tagged by udev as: Mouse
    [   243.595] (II) event7  - Kingsis Peripherals ZOWIE Gaming mouse: device set to 800 DPI
    [   243.595] (II) event7  - Kingsis Peripherals ZOWIE Gaming mouse: device is a pointer
    [   243.597] (II) event9  - SONiX USB DEVICE: is tagged by udev as: Keyboard
    [   243.597] (II) event9  - SONiX USB DEVICE: device is a keyboard
    [   243.598] (II) event10 - SONiX USB DEVICE Keyboard: is tagged by udev as: Keyboard
    [   243.598] (II) event10 - SONiX USB DEVICE Keyboard: device is a keyboard
    [   243.599] (II) event11 - SONiX USB DEVICE System Control: is tagged by udev as: Keyboard
    [   243.599] (II) event11 - SONiX USB DEVICE System Control: device is a keyboard
    [   243.601] (II) event12 - SONiX USB DEVICE Consumer Control: is tagged by udev as: Keyboard
    [   243.601] (II) event12 - SONiX USB DEVICE Consumer Control: device is a keyboard
    [   243.602] (II) event2  - foostan H4ck3r k3yBo4rd (crkbd): is tagged by udev as: Keyboard
    [   243.602] (II) event2  - foostan H4ck3r k3yBo4rd (crkbd): device is a keyboard
    [   243.603] (II) event3  - foostan H4ck3r k3yBo4rd (crkbd) Mouse: is tagged by udev as: Mouse
    [   243.603] (II) event3  - foostan H4ck3r k3yBo4rd (crkbd) Mouse: device is a pointer
    [   243.604] (II) event4  - foostan H4ck3r k3yBo4rd (crkbd) System Control: is tagged by udev as: Keyboard
    [   243.604] (II) event4  - foostan H4ck3r k3yBo4rd (crkbd) System Control: device is a keyboard
    [   243.606] (II) event5  - foostan H4ck3r k3yBo4rd (crkbd) Consumer Control: is tagged by udev as: Keyboard
    [   243.606] (II) event5  - foostan H4ck3r k3yBo4rd (crkbd) Consumer Control: device is a keyboard

The profile is not applied, nvidia seems to ignore it. (why?)

METHOD 2:
description: I try to add an unsuported resolution like described here https://wiki.archlinux.org/index.php/Xr … esolutions. So I run

    cvt 3840 2160 70
    xrandr --newmode "3840x2160_70.00"  839.00  3840 4160 4584 5328  2160 2163 2168 2250 -hsync +vsync
    xrandr --addmode DP-4 "3840x2160_70.00"

This last line fails with the error https://wiki.archlinux.org/index.php/Xr … is_invalid :
`X Error of failed request: BadMatch`

At this point arch wiki basically recommends you to use nouveau drivers instead.

So... I'm out of options. ideas?

Last edited by Zeioth (2020-12-03 17:09:30)

Offline

#2 2020-12-03 22:29:34

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,030

Re: xrandr --addmode fails with X Error of failed request: BadMatch

You can't use "~" in the xorg conf - it's a bash alias, not a path (at the very least it would be resolved for the user that runs X11 - in doubt root)

Also manjaro isn't supported here, https://forums.developer.nvidia.com/t/w … nux/161069
Your system is btw. using /etc/X11/xorg.conf.d/90-mhwd.conf AND /etc/X11/xorg.conf

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB