Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

0 votes
1 answers
111 views
Lenovo 4k60hz Monitor is stuck at 30hz on Linux+Windows. Is this Lenovo EDID the problem?
This EDID is from a Lenovo P32p-20 4k monitor connected to a ThinkPad P16v Gen 2 laptop (Intel 155H). On other laptops (older thinkpads and macbooks) it works at 4k@60hz but on newer Intel ThinkPads including P16vG2 & X1 Carbon Gen 12 it only works at 4k@30hz. On Windows 11 I can select 59.95hz but...
This EDID is from a Lenovo P32p-20 4k monitor connected to a ThinkPad P16v Gen 2 laptop (Intel 155H). On other laptops (older thinkpads and macbooks) it works at 4k@60hz but on newer Intel ThinkPads including P16vG2 & X1 Carbon Gen 12 it only works at 4k@30hz. On Windows 11 I can select 59.95hz but then the resolution drops to 2560x1440. Going back to 4k reverts to 30hz. I originally suspected a flakey EDID or Linux decoding it but now I suspect the Intel/ThinkPad hardware. I note it says "EDID conformity: FAIL". The laptop's built-in panel (eDP-1) correctly shows "3840x2400 59.98*" but the external Lenovo monitor (DP-4) only goes to 30hz according to xrandr. OS is OpenSUSE w/KDE + Wayland however I think the desktop environment is unrelated because it's a kernel issue decoding the available modes, right? edid-decode (hex): 00 ff ff ff ff ff ff 00 30 ae a2 62 00 00 00 00 1c 1e 01 04 b5 46 27 78 3a e5 a5 ae 4f 43 ab 26 0c 50 54 a1 08 00 d1 00 d1 c0 b3 00 81 c0 81 80 95 00 a9 c0 81 00 4d d0 00 a0 f0 70 3e 80 30 20 35 00 b9 88 21 00 00 1a 00 00 00 fd 00 17 4c 1e a0 3c 01 0a 20 20 20 20 20 20 00 00 00 fc 00 4c 45 4e 20 50 33 32 70 2d 32 30 0a 20 00 00 00 ff 00 56 4e 41 34 59 35 33 52 0a 20 20 20 20 01 b7 02 03 1b f1 4e 61 60 5f 10 1f 05 14 04 13 12 11 03 02 01 23 09 7f 07 83 01 00 00 a3 66 00 a0 f0 70 1f 80 30 20 35 00 b9 88 21 00 00 1a 56 5e 00 a0 a0 a0 29 50 30 20 35 00 b9 88 21 00 00 1a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0c ---------------- Block 0, Base EDID: EDID Structure Version & Revision: 1.4 Vendor & Product Identification: Manufacturer: LEN Model: 25250 Made in: week 28 of 2020 Basic Display Parameters & Features: Digital display Bits per primary color channel: 10 DisplayPort interface Maximum image size: 70 cm x 39 cm Gamma: 2.20 DPMS levels: Off Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2 First detailed timing includes the native pixel format and preferred refresh rate Color Characteristics: Red : 0.6826, 0.3105 Green: 0.2626, 0.6689 Blue : 0.1503, 0.0488 White: 0.3134, 0.3291 Established Timings I & II: IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz Standard Timings: DMT 0x45: 1920x1200 59.884600 Hz 16:10 74.556 kHz 193.250000 MHz DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz DMT 0x2f: 1440x900 59.887445 Hz 16:10 55.935 kHz 106.500000 MHz DMT 0x53: 1600x900 60.000000 Hz 16:9 60.000 kHz 108.000000 MHz (RB) DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz Detailed Timing Descriptors: DTD 1: 3840x2160 59.996625 Hz 16:9 133.312 kHz 533.250000 MHz (697 mm x 392 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront 3 Vsync 5 Vback 54 Vpol N Display Range Limits: Monitor ranges (Bare Limits): 23-76 Hz V, 30-160 kHz H, max dotclock 600 MHz Display Product Name: 'LEN P32p-20' Display Product Serial Number: 'VNA4Y53R' Extension blocks: 1 Checksum: 0xb7 ---------------- Block 1, CTA-861 Extension Block: Revision: 3 Underscans IT Video Formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 Native detailed modes: 1 Video Data Block: VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz VIC 96: 3840x2160 50.000000 Hz 16:9 112.500 kHz 594.000000 MHz VIC 95: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz VIC 31: 1920x1080 50.000000 Hz 16:9 56.250 kHz 148.500000 MHz VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz VIC 20: 1920x1080i 50.000000 Hz 16:9 28.125 kHz 74.250000 MHz VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz VIC 19: 1280x720 50.000000 Hz 16:9 37.500 kHz 74.250000 MHz VIC 18: 720x576 50.000000 Hz 16:9 31.250 kHz 27.000000 MHz VIC 17: 720x576 50.000000 Hz 4:3 31.250 kHz 27.000000 MHz VIC 3: 720x480 59.940060 Hz 16:9 31.469 kHz 27.000000 MHz VIC 2: 720x480 59.940060 Hz 4:3 31.469 kHz 27.000000 MHz VIC 1: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz Audio Data Block: Linear PCM: Max channels: 2 Supported sample rates (kHz): 192 176.4 96 88.2 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block: FL/FR - Front Left/Right Detailed Timing Descriptors: DTD 2: 3840x2160 29.980602 Hz 16:9 65.688 kHz 262.750000 MHz (697 mm x 392 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront 3 Vsync 5 Vback 23 Vpol N DTD 3: 2560x1440 59.950550 Hz 16:9 88.787 kHz 241.500000 MHz (697 mm x 392 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront 3 Vsync 5 Vback 33 Vpol N Checksum: 0x0c ---------------- Preferred Video Timing if only Block 0 is parsed: DTD 1: 3840x2160 59.996625 Hz 16:9 133.312 kHz 533.250000 MHz (697 mm x 392 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront 3 Vsync 5 Vback 54 Vpol N ---------------- Preferred Video Timings if Block 0 and CTA-861 Blocks are parsed: DTD 1: 3840x2160 59.996625 Hz 16:9 133.312 kHz 533.250000 MHz (697 mm x 392 mm) Hfront 48 Hsync 32 Hback 80 Hpol P Vfront 3 Vsync 5 Vback 54 Vpol N VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz Hfront 176 Hsync 88 Hback 296 Hpol P Vfront 8 Vsync 10 Vback 72 Vpol P ---------------- Native Video Resolution: 3840x2160 ---------------- edid-decode SHA: 84ddf9155376 2021-10-03 10:37:45 Warnings: EDID: Base EDID: Some timings are out of range of the Monitor Ranges: Horizontal Freq: 28.125 - 135.000 kHz (Monitor: 30.000 - 160.000 kHz) Failures: Block 1, CTA-861 Extension Block: Missing VCDB, needed for Set Selectable RGB Quantization to avoid interop issues. EDID conformity: FAIL $ xrandr Screen 0: minimum 16 x 16, current 10561 x 3780, maximum 32767 x 32767 eDP-1 connected primary 3840x2400+0+1379 (normal left inverted right x axis y axis) 344mm x 215mm 3840x2400 59.98*+ 2048x1536 59.95 1920x1440 59.97 1600x1200 59.96 1440x1080 59.99 1400x1050 59.98 1280x1024 59.89 1280x960 59.94 1152x864 59.96 1024x768 59.92 800x600 59.86 640x480 59.38 320x240 59.52 2560x1600 59.99 1920x1200 59.96 1680x1050 59.95 1440x900 59.89 1280x800 59.81 1152x720 59.97 960x600 59.96 928x580 59.88 800x500 59.50 768x480 59.90 720x480 59.71 640x400 59.95 320x200 58.96 3840x2160 60.00 3200x1800 59.99 2880x1620 60.00 2560x1440 59.96 2048x1152 59.98 1920x1080 59.96 1600x900 59.95 1368x768 59.88 1280x720 59.86 1024x576 59.90 864x486 59.92 720x400 59.55 640x350 59.77 DP-4 connected 6720x3780+3841+0 (normal left inverted right x axis y axis) 697mm x 392mm 6720x3780 29.99*+ 2048x1536 29.95 1920x1440 29.95 1600x1200 29.95 1440x1080 29.86 1400x1050 29.98 1280x1024 29.90 1280x960 29.82 1152x864 29.92 1024x768 29.89 800x600 29.55 640x480 29.85 320x240 27.50 2560x1600 29.99 1920x1200 29.95 1680x1050 29.95 1440x900 29.91 1280x800 29.83 1152x720 29.96 960x600 29.86 928x580 29.64 800x500 29.53 768x480 29.64 720x480 29.25 640x400 29.58 320x200 26.53 5120x2880 29.99 4096x2304 29.99 3840x2160 29.98 3200x1800 29.96 2880x1620 29.96 2560x1440 29.94 2048x1152 29.94 1920x1080 29.95 1600x900 29.92 1368x768 29.94 1280x720 29.93 1024x576 29.84 864x486 29.50 720x400 29.51 640x350 29.03 windows EDID enter image description here
Andrew (101 rep)
Dec 3, 2024, 12:29 PM • Last activity: May 25, 2025, 03:26 PM
1 votes
0 answers
29 views
Neither Win11 nor Manjaro pick or show the correct edid entry
I have an Acer CB382CUR ultrawide curved monitor which allows 75Hz at its native resolution of 3840x1600. Connecting my Dell 9310 (Intel Iris Xe) via USB-C and Displayport Alt Mode only allows setting the monitor to 60Hz no matter if I use Win11 or Manjaro. Using a Macbook M4 this works with 75Hz wi...
I have an Acer CB382CUR ultrawide curved monitor which allows 75Hz at its native resolution of 3840x1600. Connecting my Dell 9310 (Intel Iris Xe) via USB-C and Displayport Alt Mode only allows setting the monitor to 60Hz no matter if I use Win11 or Manjaro. Using a Macbook M4 this works with 75Hz with the same cable. In Manjaro, when running the following little script to get the edid entries: for f in find /sys/devices -name 'edid'; do echo "";echo $f;sudo cat $f| edid-decode;done I get this output: /sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-DP-4/edid EDID of 'stdin' was empty. /sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-HDMI-A-1/edid EDID of 'stdin' was empty. /sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-DP-2/edid EDID of 'stdin' was empty. /sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-eDP-1/edid edid-decode (hex): 00 ff ff ff ff ff ff 00 4d 10 f9 14 00 00 00 00 15 1e 01 04 a5 1d 12 78 0e de 50 a3 54 4c 99 26 0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30 20 36 00 20 b4 10 00 00 18 20 30 80 a0 70 b0 23 40 30 20 36 00 20 b4 10 00 00 18 00 00 00 fe 00 56 56 4b 38 59 81 4c 51 31 33 34 4e 31 00 00 00 00 00 02 41 03 32 00 12 00 00 0a 01 0a 20 20 00 7f ---------------- Block 0, Base EDID: EDID Structure Version & Revision: 1.4 Vendor & Product Identification: Manufacturer: SHP Model: 5369 Made in: week 21 of 2020 Basic Display Parameters & Features: Digital display Bits per primary color channel: 8 DisplayPort interface Maximum image size: 29 cm x 18 cm Gamma: 2.20 Supported color formats: RGB 4:4:4, YCrCb 4:4:4 Default (sRGB) color space is primary color space First detailed timing includes the native pixel format and preferred refresh rate Color Characteristics: Red : 0.6396, 0.3291 Green: 0.2998, 0.5996 Blue : 0.1494, 0.0595 White: 0.3125, 0.3281 Established Timings I & II: none Standard Timings: none Detailed Timing Descriptors: DTD 1: 1920x1200 59.950171 Hz 16:10 74.038 kHz 154.000000 MHz (288 mm x 180 mm) Hfront 48 Hsync 32 Hback 80 Hpol N Vfront 3 Vsync 6 Vback 26 Vpol N DTD 2: 1920x1200 47.960137 Hz 16:10 59.231 kHz 123.200000 MHz (288 mm x 180 mm) Hfront 48 Hsync 32 Hback 80 Hpol N Vfront 3 Vsync 6 Vback 26 Vpol N Alphanumeric Data String: 'VVK8Y.LQ134N1' Manufacturer-Specified Display Descriptor (0x00): 00 00 00 02 41 03 32 00 12 00 00 0a 01 0a 20 20 '....A.2....... ' Checksum: 0x7f /sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-DP-3/edid edid-decode (hex): 00 ff ff ff ff ff ff 00 04 72 63 09 02 a5 87 22 1c 20 01 04 b5 58 25 78 3b e4 05 ad 4f 45 ab 27 0e 50 54 bf ef 80 71 4f 81 40 81 80 81 c0 81 00 95 00 b3 00 d1 c0 50 9a 00 a0 f0 40 2e 60 08 20 08 08 70 6f 31 00 00 1a 00 00 00 ff 00 31 32 32 38 37 41 35 30 32 34 32 30 30 00 00 00 fd 00 30 4b 82 82 3c 01 0a 20 20 20 20 20 20 00 00 00 fc 00 43 42 33 38 32 43 55 52 0a 20 20 20 20 01 54 02 03 34 f1 4b 01 03 04 12 13 05 14 1f 90 07 5a 23 09 07 07 83 01 00 00 67 03 0c 00 10 00 38 78 68 1a 00 00 01 01 30 4b 00 e3 05 e0 00 e6 06 05 01 60 60 45 02 3a 80 18 71 38 2d 40 58 2c 45 00 70 6f 31 00 00 1e 18 4c 00 a0 f0 40 17 60 08 20 98 00 70 6f 31 00 00 1a 4c c2 00 a0 f0 40 3a 60 08 20 c8 08 70 6f 31 00 00 1a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 73 ---------------- Block 0, Base EDID: EDID Structure Version & Revision: 1.4 Vendor & Product Identification: Manufacturer: ACR Model: 2403 Serial Number: 579314946 (0x2287a502) Made in: week 28 of 2022 Basic Display Parameters & Features: Digital display Bits per primary color channel: 10 DisplayPort interface Maximum image size: 88 cm x 37 cm Gamma: 2.20 DPMS levels: Off Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2 First detailed timing includes the native pixel format and preferred refresh rate Display supports continuous frequencies Color Characteristics: Red : 0.6787, 0.3105 Green: 0.2705, 0.6679 Blue : 0.1523, 0.0546 White: 0.3134, 0.3291 Established Timings I & II: IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz Apple : 640x480 66.666667 Hz 4:3 35.000 kHz 30.240000 MHz DMT 0x05: 640x480 72.808802 Hz 4:3 37.861 kHz 31.500000 MHz DMT 0x06: 640x480 75.000000 Hz 4:3 37.500 kHz 31.500000 MHz DMT 0x08: 800x600 56.250000 Hz 4:3 35.156 kHz 36.000000 MHz DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz DMT 0x0a: 800x600 72.187572 Hz 4:3 48.077 kHz 50.000000 MHz DMT 0x0b: 800x600 75.000000 Hz 4:3 46.875 kHz 49.500000 MHz Apple : 832x624 74.551266 Hz 4:3 49.726 kHz 57.284000 MHz DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz DMT 0x11: 1024x768 70.069359 Hz 4:3 56.476 kHz 75.000000 MHz DMT 0x12: 1024x768 75.028582 Hz 4:3 60.023 kHz 78.750000 MHz DMT 0x24: 1280x1024 75.024675 Hz 5:4 79.976 kHz 135.000000 MHz Apple : 1152x870 75.061550 Hz 192:145 68.681 kHz 100.000000 MHz Standard Timings: DMT 0x15: 1152x864 75.000000 Hz 4:3 67.500 kHz 108.000000 MHz DMT 0x20: 1280x960 60.000000 Hz 4:3 60.000 kHz 108.000000 MHz DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz DMT 0x2f: 1440x900 59.887445 Hz 16:10 55.935 kHz 106.500000 MHz DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz Detailed Timing Descriptors: DTD 1: 3840x1600 60.000000 Hz 12:5 98.760 kHz 395.040000 MHz (880 mm x 367 mm) Hfront 8 Hsync 32 Hback 120 Hpol P Vfront 32 Vsync 8 Vback 6 Vpol N Display Product Serial Number: '12287A5024200' Display Range Limits: Monitor ranges (Range Limits Only): 48-75 Hz V, 130-130 kHz H, max dotclock 600 MHz Display Product Name: 'CB382CUR' Extension blocks: 1 Checksum: 0x54 ---------------- Block 1, CTA-861 Extension Block: Revision: 3 Underscans IT Video Formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 Native detailed modes: 1 Video Data Block: VIC 1: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz VIC 3: 720x480 59.940060 Hz 16:9 31.469 kHz 27.000000 MHz VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz VIC 18: 720x576 50.000000 Hz 16:9 31.250 kHz 27.000000 MHz VIC 19: 1280x720 50.000000 Hz 16:9 37.500 kHz 74.250000 MHz VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz VIC 20: 1920x1080i 50.000000 Hz 16:9 28.125 kHz 74.250000 MHz VIC 31: 1920x1080 50.000000 Hz 16:9 56.250 kHz 148.500000 MHz VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (native) VIC 7: 1440x480i 59.940060 Hz 16:9 15.734 kHz 27.000000 MHz VIC 90: 2560x1080 60.000000 Hz 64:27 66.000 kHz 198.000000 MHz Audio Data Block: Linear PCM: Max channels: 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block: FL/FR - Front Left/Right Vendor-Specific Data Block (HDMI), OUI 00-0C-03: Source physical address: 1.0.0.0 DC_36bit DC_30bit DC_Y444 Maximum TMDS clock: 600 MHz Vendor-Specific Data Block (AMD), OUI 00-00-1A: Version: 1 Feature Caps: 0x01 Minimum Refresh Rate: 48 Hz Maximum Refresh Rate: 75 Hz Flags 1.x: 0x00 Colorimetry Data Block: BT2020cYCC BT2020YCC BT2020RGB HDR Static Metadata Data Block: Electro optical transfer functions: Traditional gamma - SDR luminance range SMPTE ST2084 Supported static metadata descriptors: Static metadata type 1 Desired content max luminance: 96 (400.000 cd/m^2) Desired content max frame-average luminance: 96 (400.000 cd/m^2) Desired content min luminance: 69 (0.293 cd/m^2) Detailed Timing Descriptors: DTD 2: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (880 mm x 367 mm) Hfront 88 Hsync 44 Hback 148 Hpol P Vfront 4 Vsync 5 Vback 36 Vpol P DTD 3: 3840x1600 30.006161 Hz 12:5 48.700 kHz 194.800000 MHz (880 mm x 367 mm) Hfront 8 Hsync 32 Hback 120 Hpol P Vfront 9 Vsync 8 Vback 6 Vpol N DTD 4: 3840x1600 75.000000 Hz 12:5 124.350 kHz 497.400000 MHz (880 mm x 367 mm) Hfront 8 Hsync 32 Hback 120 Hpol P Vfront 44 Vsync 8 Vback 6 Vpol N Checksum: 0x73 Unused space in Extension Block: 21 bytes /sys/devices/pci0000:00/0000:00:02.0/drm/card1/card1-DP-1/edid EDID of 'stdin' was empty. As you can see the built-in laptop screen is the first entry at card1-eDP-1. All good with that. The external monitor is on card1-DP-3 and has two edid blocks. Both OSes only seem to see the first block as it contains the 60Hz setting only. However, the second block contains the correct 75Hz setting. DTD 4 to be precise. **How can I make Manjaro use this setting?** I'm on Wayland if it matters, but the issue is there with X as well. @editor: As this happens in Arch as well (had that previously installed), I'm changing the tags to just "linux". I assume the issue is distro-independent and probably an issue with the Intel provided driver which could explain the behaviour in both, Windows and Linux, as it is open source afaik.
8192K (111 rep)
May 21, 2025, 08:43 AM • Last activity: May 21, 2025, 09:36 PM
0 votes
1 answers
174 views
Samsung QN700B monitor loses 8k resolution (stuck 4k) when reconnected/turned back on, forgets settings
I'm having a problem with a Samsung TV as a monitor. Thank you for any insight: debian + xorg + RTX4090 + qn700b + (HDMI 2.1 cable seems good) Problem: when waking the TV and computer, I can't get it back to 8k again? It becomes stuck at 4k. --- Symptoms: - Initially, a black screen when TV/computer...
I'm having a problem with a Samsung TV as a monitor. Thank you for any insight: debian + xorg + RTX4090 + qn700b + (HDMI 2.1 cable seems good) Problem: when waking the TV and computer, I can't get it back to 8k again? It becomes stuck at 4k. --- Symptoms: - Initially, a black screen when TV/computer are turned back on (either order). - Ctrl-alt-f1/f2/etc wakes screen into 4k, and then I can ctrl-alt-f7 back to graphical tty, but I lost 8k and now it's stuck at 4k (tv correctly still in Samsung game mode). - sudo nvidia-settings doesn't allow 8k (only 4k appears in dropdown) - downloading EDID via nvidia-settings and forcing in xorg doesn't work? Not sure how to tell. - cvt and xrandr --newmode etc / --addmode "HDMI-0" 7680x4320at60 fails with BadMatch (invalid parameter attributes), major opcode 140 RANDR, minor opcode 18 RRAddOutputMode. (I know I can set Option "DPMS" "false" and various Options "fooTime" "off" in xorg or xset -dpms and keep the monitor on 24/7, or restart the window manager/X/etc as a workaround, but wish to otherwise fix this without losing WM state, without an irreversible firmware update if possible.) Thank you for any insight! Xorg.0.log: Validated MetaModes: "7680x4320+0+0{AllowGSYNCCompatible=On}" .. MetaMode "HDMI-0:7680x4320" could not be re-validated against the current hardware configuration; removing. .. Setting mode "DPY-0:7680x4320+0+0{AllowGSYNCCompatible=On}" .. Setting mode "DPY-0:nvidia-auto-select+0+0{AllowGSYNCCompatible=On}" xorg.conf: Section "Monitor" .. Option "DPMS" "false" Option "PreferredMode" "7680x4320" EndSection Section "Device" .. Option "ModeValidation" "AllowNonEdidModes" EndSection Section "Screen" .. Option "CustomEDID" "GPU-0.HDMI-0:/path/to/edid.txt" Option "metamodes" "7680x4320 +0+0 {AllowGSYNCCompatible=On}" Option "ConnectToAcpid" "False" # https://bbs.archlinux.org/viewtopic.php?id=262207 SubSection "Display" Virtual 7680 4320 Depth 24 EndSubSection EndSection
ninjagecko (199 rep)
Nov 30, 2023, 01:29 PM • Last activity: Oct 22, 2024, 02:01 PM
4 votes
2 answers
2672 views
How to set bytes of EDID on a i2c device
I have a monitor LG E2251 (monitor [details](https://www.lg.com/uk/monitors/lg-E2251VR-led-monitor)). My computer was connected to the monitor via DVI-I cable; after the power supply broke, the display went black. I rebooted the system and all seemed ok. I pass the POST as usual, however I cannot se...
I have a monitor LG E2251 (monitor [details](https://www.lg.com/uk/monitors/lg-E2251VR-led-monitor)) . My computer was connected to the monitor via DVI-I cable; after the power supply broke, the display went black. I rebooted the system and all seemed ok. I pass the POST as usual, however I cannot see the GUI nor CLI when connected with DVI-I. I believe the EDID code for DVI-I has been corrupted. I also tried with other 2 connections: whether HDMI doesn't present any damge,I get the following message for DVI-I
nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
[    9.292129] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    9.292133] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[    9.292135] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    9.292137] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000302 00020030
[    9.292139] nouveau 0000:01:00.0: DRM: DCB outp 01: 02000300 00000000
[    9.292141] nouveau 0000:01:00.0: DRM: DCB outp 02: 02011362 00020010
[    9.292143] nouveau 0000:01:00.0: DRM: DCB outp 03: 01022310 00000000
[    9.292145] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
[    9.292146] nouveau 0000:01:00.0: DRM: DCB conn 01: 00002161
[    9.292148] nouveau 0000:01:00.0: DRM: DCB conn 02: 00000200
[    9.296293] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    9.296294] [drm] Driver supports precise vblank timestamp query.
[    9.309393] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
 [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 185
[    9.449801] nouveau 0000:01:00.0: DVI-I-1: EDID block 0 invalid.
[    9.449803] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DVI-I-1
[    9.470675] nouveau 0000:01:00.0: No connectors reported connected with modes
[    9.470678] [drm] Cannot find any crtc or sizes - going 1024x768
[    9.472105] nouveau 0000:01:00.0: DRM: allocated 1024x768 fb: 0x70000, bo ffff9d41b8eafc00
[    9.472196] fbcon: nouveaufb (fb0) is primary device
[    9.474979] Console: switching to colour frame buffer device 128x48
[    9.476170] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[    9.508021] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
and a similar one for VGA
[drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 198
[   95.783329] nouveau 0000:01:00.0: VGA-1: EDID block 0 invalid.
[   95.783331] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for VGA-1
# MY APPROACH - installed i2c-tools on my debian machine. - found i2c-1 to be my DVI interface - with i2cdump -y 1 0x50 I can dump the EDID code. ## i2cset However, when I want to set a block of bytes with i2cset -y 1 0x50 0x00 0x00 0xff i EDID does not change. **How can I correct those EDID?** Is there a fast solution in the UserSpace, without assembly programming? I say I'm new to EDID, nouveau driver, I2C or SMBus communication. Any advice and correction is appreciated. It looks like I could send BLOCKs of bytes on that I2C BUS i2cdetect -F 1:
Functionalities implemented by /dev/i2c-1:
I2C Block Write                  yes
I2C Block Read                   yes
...
but I don't know what's wrong. ### LINKS + [wikipedia/EDID](https://en.wikipedia.org/wiki/Extended_Display_Identification_Data) + [read EDID](https://unix.stackexchange.com/q/7763/354095) + [i2cget](https://stackoverflow.com/q/44550692/11368129) + [i2cset](https://stackoverflow.com/q/50556657/11368129)
pathox (41 rep)
May 22, 2019, 11:14 AM • Last activity: Jul 6, 2024, 12:07 AM
3 votes
3 answers
18989 views
Second monitor not recognized - xorg.conf file
I'm trying to use this monitor Acer XB270H, with my Ubuntu laptop, but it is not recognized, appears cropped with incorrect resolution. *Note: I first was using the docking station with the monitor DP cable, and bought a mini DP to DP cable to be able to plug directly the computer to the monitor ins...
I'm trying to use this monitor Acer XB270H, with my Ubuntu laptop, but it is not recognized, appears cropped with incorrect resolution. *Note: I first was using the docking station with the monitor DP cable, and bought a mini DP to DP cable to be able to plug directly the computer to the monitor instead : but no change, it was not a hardware problem.* I tried to force a new configuration with xrandr : cvt 1920 1080 : # 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz Modeline "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync
xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync
xrandr --addmode DP1 "1920x1080_60.00"
**Here what shows up :** gsd-color: unable to get EDID for xrandr-DP1: unable to get EDID for output So, following command turns the second monitor black showing 'no signal' :
xrandr --output DP1 --mode 1920x1080_60.00
--- **SPECS** Linux 4.18.0-13-generic #14-Ubuntu SMP x86_64 GNU/Linux lspci -v | grep VGA : 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
inxi -Gxx :
Graphics: Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0166 Display: x11 server: X.Org 1.20.1 driver: i915 compositor: gnome-shell resolution: 1366x768~60Hz, 1024x768~60Hz OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.2.2 compat-v: 3.0 direct render: Yes
----

**UPDATE :**

I'm now trying to use a xorg.conf file as proposed.

To get the EDID I could not use read-edid, parse-edid : /sys/class/drm/card0-DP1/edid : Partial Read... Try again..., and could not find it on Internet.

I finally managed to get the EDID (256-bits) file from **Windows** with moninfo.exe tool :
ls -al /etc/X11/edid.bin -rwxr----- 1 root root 256 Feb 3 14:00 /etc/X11/edid.bin ``` I tried to follow some Xorg guides, but this error came up too many times : gsd-color: failed to get edid: unable to get EDID for output
DependencyHell (193 rep)
Jan 24, 2019, 09:18 PM • Last activity: Aug 25, 2023, 09:05 PM
1 votes
0 answers
488 views
Is there any persistent files of stored EDID information from previously plugged in monitors?
**TL/DR:** I have an ACER GN246HL monitor with HDMI port which stopped working properly, probably due to corrupted monitor EEPROM. As a work-around on my Ubuntu 22.10 machine I need to figure out the correct monitor EDID by retrieving and verifying the EDID data from sources other then the monitor i...
**TL/DR:** I have an ACER GN246HL monitor with HDMI port which stopped working properly, probably due to corrupted monitor EEPROM. As a work-around on my Ubuntu 22.10 machine I need to figure out the correct monitor EDID by retrieving and verifying the EDID data from sources other then the monitor itself (in it's defective state). Is there a process in UBUNTU 22.10 that persistently stores monitor EDID data on disk so it survives reboot? If the answer is yes, I hope I could potentially retrieve the EDID for my monitor as it was stored in the past when the monitor was still working correctly. **What I know/suspect so far:** The monitor is not recognized anymore by the BIOS or the kernel during boot up (both on Ubuntu and Win10, irrespective of GPU or GPU driver). I suspect the monitor EEPROM has somehow been corrupted or is malfunctioning so that either the monitor EDID is garbage or the DDC/I2C communication between PC and monitor is not working properly anymore. However, the monitor is not completely dead or unusable. On my Ubuntu 22.10 machine, despite staying 100% black during boot-up sequence, it comes back to live after boot-up by displaying the Ubuntu log-in page. From there, log-in and everything else works and the monitor performs (almost) as usual. The resolution is correct and there is no lag, image noise or stutter when playing videos, for example. While displayed colors seem basically OK, there is still some problem with the color gamut as manifested mainly by noticeably "burnt out" highlights in video playback. On Windows things are a bit worse, one machine with Win10 boots (without displaying anything) but fails to display any log-in page. On a second Windows10 box, the BIOS complains (most likely about a missing monitor) and refuses to boot. **What I think might be the solution (for Ubuntu):** All the above suggests the problem can be fixed by instructing the kernel to read correct monitor EDID from a file during boot-up instead of trying to get it from the monitor EEPROM. **What is still missing to fix the problem:** I need to find the correct EDID data for my monitor, but I cannot get it from the monitor itself. Tried various tools, but all seem to indicate that I2C bus address for the monitor is missing/not working. I found three potential routes to obtain EDID from other sources than the monitor: 1) A github [repository](https://github.com/linuxhw/EDID) has EDID data for the ACER GN246HL. But the EDID varies with manufacturing date and there is no EDID for the manufacturing date of my monitor in the repository. I don't know, maybe one of the existing EDID can be modified to suit my monitor but I have not yet tried to figure out if and how this could be done. 2) I have installed a tool called Monitor Asset Manager v9.2 on a Windows10 machine. It can read the EDID of attached monitors and potentially also create INF files to modify EDID data on Windows. Interestingly, the tool indicates that Windows stores EDID data permanently in registry. There are clearly registry entries with EDID data for all monitors that have been plugged into this Windows box in the past, including the ACER GN246HL. However, I don't know yet how to extract this EDID data (and convert it to a binary) and then how to make sure that extracted EDID is still from the time the monitor was working correctly and wasn't changed by accident when the same but now defective monitor was plugged in at a later point in time. 3) This is pretty much speculation, but given that there is persistent EDID data stored in registry on Windows machines I was wondering if something similar occurs on Linux machines. The answer is probably no, but how is it possible that the monitor comes back to life after boot-up and correctly displays the log-in page? **Finally, the question to the forum:** I think the EDID data is temporarily stored in a xorg.0.log file. But this does not work in my case since the kernel fails to access the EDID data of my ACER GN246HL monitor due to corrupted monitor EEPROM. Therefore my question, is there a process in UBUNTU 22.10 that persistently stores EDID data on disk? If the answer is yes, I assume I could potentially retrieve the EDID for my monitor that was stored in the past when the monitor was still working correctly. **Background or "Why did the monitor stop working properly?":** I do not know what exactly did happen. The monitor worked fine for years in single and dual monitor set-ups on Windows and Linux using a variety of GPUs and GPU drivers. It also worked in a set-up with two PC and a KVM switch. It seems like the circuitry of this monitor got corrupted when I recently swapped out one of the PC's in the KVM set-up to temporarily work on an SBC with an X86 intel processor. When I manually switched the KVM to the SBC machine the ACER monitor in the dual monitor set-up went immediately black and the second monitor changed resolution. I don't think I will ever find out what exactly went wrong, but it might be related to poor firmware on the SBC which I had only used in headless mode until then.
yesno (341 rep)
Apr 16, 2023, 06:02 PM
2 votes
0 answers
463 views
Centos 7 kernel loading custom monitor EDID file does not work
I want to load a custom EDID File with the Linux Kernel. I added `drm_kms_helper.edid_firmware=edid/myedid.bin` to `GRUB_CMDLINE_LINUX` in `/etc/defauls/grub`. Then I updated the grub.cfg with `grub2-mkconfig > /boot/grub2/grub.cfg` and added the EDID File to initrd with `dracut --force --include /u...
I want to load a custom EDID File with the Linux Kernel. I added drm_kms_helper.edid_firmware=edid/myedid.bin to GRUB_CMDLINE_LINUX in /etc/defauls/grub. Then I updated the grub.cfg with grub2-mkconfig > /boot/grub2/grub.cfg and added the EDID File to initrd with dracut --force --include /usr/lib/firmware/edid /usr/lib/firmware/edid I checked with lsinitrd if the files are there lsinitrd | grep edid Arguments: --force --include '/usr/lib/firmware/edid' '/usr/lib/firmware/edid' drwxrwx--- 2 root root 0 Oct 6 01:25 usr/lib/firmware/edid Then I restarted the computer and xrandr gives the old informations and not the infomations I defined in EDID File. DP1 disconnected (normal left inverted right x axis y axis) DP2 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.32 56.25 848x480 60.00 640x480 59.94 HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) This is what dmesg | grep drm prints out (I also tried out to change drm_kms_firmware to drm but this only removed the warning in the log. I am using kernelversion 3.10 so drm_kms_helper should be right): [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.10.0-1160.76.1.el7.x86_64 root=UUID=XXXXX ro drm_kms_helper.edid_firmware=edid/myedid.bin rhgb quiet mem=2G [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-1160.76.1.el7.x86_64 root=UUID=2df6baad-7c38-488e-8acd-14a461e72a99 ro drm_kms_helper.edid_firmware=edid/myedid.bin rhgb quiet [ 2.652804] [drm] drm_kms_firmware.edid_firmware is deprecated, please use drm.edid_firmware intead. [ 3.115696] [drm] Replacing VGA console driver [ 3.117295] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 3.117299] [drm] Driver supports precise vblank timestamp query. [ 3.179723] [drm] Initialized i915 1.6.0 20181204 for 0000:00:02.0 on minor 0 [ 3.198830] fbcon: inteldrmfb (fb0) is primary device [ 3.261252] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device This is my intel.conf inside /etc/X11/xorg.conf.d # /etc/X11/xorg.conf.d/01-intel.conf Section "Device" Identifier "intel(0)" Driver "intel" Option "TearFree" "true" Option "DRI" "2" Option "ReprobeOutputs" "true" Option "HotPlug" "false" EndSection And my Xorg log (grep drm) [ 96.089] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-1160.76.1.el7.x86_64 root=UUID=XXXXX ro drm_kms_helper.edid_firmware=edid/myedid.bin rhgb quiet [ 96.098] (II) xfree86: Adding drm device (/dev/dri/card0) [ 96.098] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0 Kernel Version: 3.10.0-1160.76.1.el7.x86_64 In Kernel config this is set CONFIG_DRM_LOAD_EDID_FIRMWARE=y
test123123123 (31 rep)
Oct 5, 2022, 02:20 PM
35 votes
5 answers
134690 views
How to get EDID for a single monitor?
Pending an answer to [xrandr detects amplifier as monitor][1] a possible workaround is to blacklist devices with specific [EDID][2]s. Unfortunately [`xrandr --verbose`][3] prints everything in a format which is cumbersome to parse and doesn't support querying single devices, and [`get-edid`][4]'s ou...
Pending an answer to xrandr detects amplifier as monitor a possible workaround is to blacklist devices with specific EDID s. Unfortunately xrandr --verbose prints everything in a format which is cumbersome to parse and doesn't support querying single devices, and get-edid 's output doesn't seem to be easy to map to xrandr's monitor IDs (for example DVI-1). **Is there some way to get an *easily parseable* EDID for a *single* monitor?**
l0b0 (53368 rep)
Feb 9, 2014, 12:01 PM • Last activity: Jan 7, 2022, 02:45 PM
1 votes
1 answers
823 views
Remove detected resolutions
There are many articles about how to add undetected resolutions. My problem is the opposite: *gnome-control-center* shows many resolutions I won't ever use. Here is my list with 33 entries on a 3840x2160 monitor: [![Example 3840x2160 screen][1]][1] [1]: https://i.sstatic.net/TMb5d.png **How to clean...
There are many articles about how to add undetected resolutions. My problem is the opposite: *gnome-control-center* shows many resolutions I won't ever use. Here is my list with 33 entries on a 3840x2160 monitor: Example 3840x2160 screen **How to clean up this list** (per monitor) **and only keep these 2 entries?** - 3840x2160 (native resolution) - 1920x1080
auipga (133 rep)
Jun 1, 2021, 11:05 AM • Last activity: Dec 22, 2021, 03:44 PM
1 votes
1 answers
236 views
Lower screen resolution 1600x1200 does not fill the area of the Dasung HD-F e-ink monitor in Fedora 34
I bought the Dasung HD-F 2019 e-ink monitor. The default screen resolution is 2200x1650 @ 40. Dasung also supports 1600x1200 @ 60 and I would like to use that. Unfortunately, the screen does not fill completely in Fedora 34. My notebook has Intel UHD Graphics 620. I don't know where the problem is,...
I bought the Dasung HD-F 2019 e-ink monitor. The default screen resolution is 2200x1650 @ 40. Dasung also supports 1600x1200 @ 60 and I would like to use that. Unfortunately, the screen does not fill completely in Fedora 34. My notebook has Intel UHD Graphics 620. I don't know where the problem is, but my guess is that the system thinks Dasung is 20x15 cm in size. In fact, it is 27x20 cm. Filled area is exactly 20x15 cm. I completely do not know how to configure monitors in Linux in an advanced way. I spent many hours reading and trying different ways. Photo of Dasung with 1600x1200 What I did (using some tutorials): I made hex dump of edid and replaced 20x15 cm with 27x20 cm (offset 0x15 and 0x16). Changed offset 0x7f to the new checksum. Copied file to /lib/firmware/edid/correct-edid.bin. Created Dracut configuration /etc/dracut.conf.d/00-dasung-hdf-edid.conf to copy the new EDID into initramfs: > install_items+=" /lib/firmware/edid/correct-edid.bin " Regenerated initramfs using Dracut: sudo dracut -f. Added drm.edid_firmware=HDMI-A-1:edid/correct-edid.bin to the end of GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub. At the end: sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg Unfortunately it didn't help. Result of xrandr --verbose:
Screen 0: minimum 320 x 200, current 2200 x 2730, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+1650 (0x47) normal (normal left inverted right x axis y axis) 309mm x 174mm
	Identifier: 0x42
	Timestamp:  242415
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       0
	CRTCs:      0 1 2
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	_MUTTER_PRESENTATION_OUTPUT: 0 
	EDID: 
		00ffffffffffff0006af3d3200000000
		101c0104a51f117802fc15a055509b27
		0c505400000001010101010101010101
		010101010101143780b8703824401010
		3e0035ae100000180000000f00000000
		00000000000000000020000000fe0041
		554f0a202020202020202020000000fe
		004231343048414e30332e32200a00bd
	scaling mode: Full aspect 
		supported: Full, Center, Full aspect
	Colorspace: Default 
		supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
	max bpc: 12 
		range: (6, 12)
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	panel orientation: Normal 
		supported: Normal, Upside Down, Left Side Up, Right Side Up
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 95 
		supported: 95
	non-desktop: 0 
		range: (0, 1)
  1920x1080 (0x45) 141.000MHz -HSync -VSync +preferred
        h: width  1920 start 1936 end 1952 total 2104 skew    0 clock  67.02KHz
        v: height 1080 start 1083 end 1097 total 1116           clock  60.05Hz

    



HDMI-1 connected 2200x1650+0+0 (0x7b2) normal (normal left inverted right x axis y axis) 200mm x 150mm
	Identifier: 0x43
	Timestamp:  242415
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       1
	CRTCs:      0 1 2
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	_MUTTER_PRESENTATION_OUTPUT: 0 
	EDID: 
		00ffffffffffff001263010000000000
		0a1d0103801b14782a08a5a2574fa228   <--- 1b14 (27 x 20 cm) is my own change
		0f505400000001010101010101010101        using custom edid file, before
		010101010101c13e98a880722e603820        it was 140f (20 x 15 cm)
		3600c8960000001e0000001000000000
		00000000000000000000000000fc0050
		617065726c696b6520482044483f4030
		62b0324040c013006d552100001e00c5
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	max bpc: 12 
		range: (8, 12)
	content type: No Data 
		supported: No Data, Graphics, Photo, Cinema, Game
	Colorspace: Default 
		supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater
	aspect ratio: Automatic 
		supported: Automatic, 4:3, 16:9
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 103 
		supported: 103
	non-desktop: 0 
		range: (0, 1)
  2200x1650 (0x7b2) 160.650MHz +HSync +VSync *current +preferred
        h: width  2200 start 2256 end 2288 total 2368 skew    0 clock  67.84KHz
        v: height 1650 start 1653 end 1659 total 1696           clock  40.00Hz
  1600x1200 (0x7b3) 162.000MHz +HSync +VSync
        h: width  1600 start 1664 end 1856 total 2160 skew    0 clock  75.00KHz
        v: height 1200 start 1201 end 1204 total 1250           clock  60.00Hz
Result of edid-decode < /sys/class/drm/card0-HDMI-A-1/edid:
edid-decode (hex):

00 ff ff ff ff ff ff 00 12 63 01 00 00 00 00 00
0a 1d 01 03 80 1b 14 78 2a 08 a5 a2 57 4f a2 28   <--- 1b14 (27 x 20 cm) is my own change
0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01        using custom edid file, before
01 01 01 01 01 01 c1 3e 98 a8 80 72 2e 60 38 20        it was 140f (20 x 15 cm)
36 00 c8 96 00 00 00 1e 00 00 00 10 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 fc 00 50
61 70 65 72 6c 69 6b 65 20 48 20 44 48 3f 40 30
62 b0 32 40 40 c0 13 00 6d 55 21 00 00 1e 00 c5

----------------

Block 0, Base EDID:
  EDID Structure Version & Revision: 1.3
  Vendor & Product Identification:
    Manufacturer: DSC
    Model: 1
    Made in: week 10 of 2019
  Basic Display Parameters & Features:
    Digital display
    Maximum image size: 27 cm x 20 cm    <--- before my changes it was 20x15
    Gamma: 2.20
    DPMS levels: Off
    RGB color display
    First detailed timing is the preferred timing
  Color Characteristics:
    Red  : 0.6328, 0.3398
    Green: 0.3105, 0.6328
    Blue : 0.1582, 0.0605
    White: 0.3134, 0.3291
  Established Timings I & II: none
  Standard Timings: none
  Detailed Timing Descriptors:
    DTD 1:  2200x1650   40.001 Hz   4:3    67.842 kHz  160.650 MHz (200 mm x 150 mm)
                 Hfront   56 Hsync  32 Hback  80 Hpol P
                 Vfront    3 Vsync   6 Vback  37 Vpol P
    Dummy Descriptor:
    Display Product Name: 'Paperlike H D'
    DTD 2:  1600x1200   60.000 Hz   4:3    75.000 kHz  162.000 MHz (621 mm x 341 mm)
                 Hfront   64 Hsync 192 Hback 304 Hpol P
                 Vfront    1 Vsync   3 Vback  46 Vpol P
Checksum: 0xc5
In Windows 10 everything works fine. I will be grateful for your help.
amarel (21 rep)
Jul 7, 2021, 09:56 PM • Last activity: Aug 1, 2021, 05:39 PM
1 votes
0 answers
296 views
Build custom EDID with several modelines
I would like to build custom EDID using [kernel sources][1]. But I need to use several modelines - more refresh rates for same resolution. Is it possible using method in kernel sources? Could you please show me how my `1920x1080.S` file should look like? [1]: https://git.kernel.org/pub/scm/linux/ker...
I would like to build custom EDID using kernel sources . But I need to use several modelines - more refresh rates for same resolution. Is it possible using method in kernel sources? Could you please show me how my 1920x1080.S file should look like?
Ales (11 rep)
Mar 22, 2016, 11:40 AM • Last activity: May 17, 2021, 07:08 AM
1 votes
0 answers
1274 views
NVIDIA G-SYNC 'unvalidated' for officially validated monitor?
I'm looking at a green NVIDIA G-SYNC sticker on the bezel of my monitor, yet the NVIDIA driver tells me 'G-SYNC Unvalidated', and I can only get G-SYNC working when I specifically set 'Allow G-SYNC on monitor not validated as G-SYNC Compatible'. Why? I've read this article: https://www.phoronix.com/...
I'm looking at a green NVIDIA G-SYNC sticker on the bezel of my monitor, yet the NVIDIA driver tells me 'G-SYNC Unvalidated', and I can only get G-SYNC working when I specifically set 'Allow G-SYNC on monitor not validated as G-SYNC Compatible'. Why? I've read this article: https://www.phoronix.com/scan.php?page=article&item=gsync-compatible-linux&num=1 which states that the whitelist for validated monitors is the same one used for Windows. It includes a link to the official NVIDIA list of supported monitors: https://www.nvidia.com/en-us/geforce/products/g-sync-monitors/specs/ My monitor is listed, it's a Dell AW3420DW (it also show this in nvidia-settings), and I'm driving it through the DisplayPort, per the requirement. The graphics card is a RTX 3090 FE. I've been looking at the EDID of the monitor, that looks OK too. So I'm puzzled as to why it insists my display is 'unvalidated'... Any ideas?
kasimir (455 rep)
Apr 15, 2021, 09:41 AM
1 votes
2 answers
2794 views
Custom EDID for specfic physical monitor, not output
I have a setup where I connect to two different displays depending on where I am. I would like to use a mode which one of the monitors doesn't allow, but that won't be loaded when any other display is connected. To be more concrete, the I would like to overclock the external display at home to 120hz...
I have a setup where I connect to two different displays depending on where I am. I would like to use a mode which one of the monitors doesn't allow, but that won't be loaded when any other display is connected. To be more concrete, the I would like to overclock the external display at home to 120hz, but not overclock a different display at work that I connect to the same HDMI port. Is this possible using nvidia? I can't seem to be able to override EDID with xrandr, at the same time using the EDID settings by default.
Materia Gravis (31 rep)
Nov 13, 2019, 11:32 PM • Last activity: Mar 23, 2021, 03:40 PM
1 votes
1 answers
320 views
Philips 275E1 2560x1440 with nVidia GT730 (EDID problem) not working
I would like to run QHD (2560x1440) resolution with the above setup (under Fedora 33, nvidia 390.141) via DVI output (connected via a DVI KVM-Switch and a DVI-HDMI adapter), but ran into problems because of conflicting EDID information. (I might add, that the same config works under Windows 10 with...
I would like to run QHD (2560x1440) resolution with the above setup (under Fedora 33, nvidia 390.141) via DVI output (connected via a DVI KVM-Switch and a DVI-HDMI adapter), but ran into problems because of conflicting EDID information. (I might add, that the same config works under Windows 10 with a GT610) During X startup, I see: [ 1246.824] (--) NVIDIA(GPU-0): Philips PHL 275E1 (DFP-0): connected [ 1246.824] (--) NVIDIA(GPU-0): Philips PHL 275E1 (DFP-0): Internal TMDS [ 1246.824] (--) NVIDIA(GPU-0): Philips PHL 275E1 (DFP-0) Name Aliases: [ 1246.824] (--) NVIDIA(GPU-0): DFP [ 1246.824] (--) NVIDIA(GPU-0): DFP-0 [ 1246.824] (--) NVIDIA(GPU-0): DPY-2 [ 1246.824] (--) NVIDIA(GPU-0): DVI-I-1 [ 1246.824] (--) NVIDIA(GPU-0): DPY-EDID-d8924ab7-3fc5-1d05-8925-b0246b2fb6b2 [ 1246.824] (--) NVIDIA(GPU-0): DVI-I-1 [ 1246.824] (--) NVIDIA(GPU-0): Philips PHL 275E1 (DFP-0): 230.0 MHz maximum pixel clock and [ 1246.824] (--) NVIDIA(GPU-0): --- EDID for Philips PHL 275E1 (DVI-I-1) --- [ 1246.824] (--) NVIDIA(GPU-0): EDID Version : 1.3 [ 1246.824] (--) NVIDIA(GPU-0): Manufacturer : PHL [ 1246.824] (--) NVIDIA(GPU-0): Monitor Name : Philips PHL 275E1 [ 1246.824] (--) NVIDIA(GPU-0): Product ID : 0xc20c [ 1246.824] (--) NVIDIA(GPU-0): 32-bit Serial Number : 0x0000a609 [ 1246.824] (--) NVIDIA(GPU-0): Serial Number String : [ 1246.824] (--) NVIDIA(GPU-0): Manufacture Date : 2020, week 51 [ 1246.824] (--) NVIDIA(GPU-0): DPMS Capabilities : Active Off [ 1246.824] (--) NVIDIA(GPU-0): Input Type : Digital [ 1246.824] (--) NVIDIA(GPU-0): Prefer first detailed timing : Yes [ 1246.824] (--) NVIDIA(GPU-0): Supports GTF : No [ 1246.824] (--) NVIDIA(GPU-0): Maximum Image Size : 600 mm x 340 mm [ 1246.824] (--) NVIDIA(GPU-0): Valid HSync Range : 30.0 kHz - 114.0 kHz [ 1246.824] (--) NVIDIA(GPU-0): Valid VRefresh Range : 48.0 Hz - 75.0 Hz [ 1246.824] (--) NVIDIA(GPU-0): EDID maximum pixel clock : 300.0 MHz As a consequence, X sorts out the detailed timings for 2560x1440 provided by EDID: [ 1246.826] (II) NVIDIA(GPU-0): --- Building ModePool for Philips PHL 275E1 (DFP-0) --- [ 1246.826] (WW) NVIDIA(GPU-0): Validating Mode "2560x1440_60": [ 1246.826] (WW) NVIDIA(GPU-0): Mode Source: EDID [ 1246.826] (WW) NVIDIA(GPU-0): 2560 x 1440 @ 60 Hz [ 1246.826] (WW) NVIDIA(GPU-0): Pixel Clock : 241.50 MHz [ 1246.826] (WW) NVIDIA(GPU-0): HRes, HSyncStart : 2560, 2608 [ 1246.826] (WW) NVIDIA(GPU-0): HSyncEnd, HTotal : 2640, 2720 [ 1246.826] (WW) NVIDIA(GPU-0): VRes, VSyncStart : 1440, 1443 [ 1246.826] (WW) NVIDIA(GPU-0): VSyncEnd, VTotal : 1448, 1481 [ 1246.826] (WW) NVIDIA(GPU-0): Sync Polarity : +H +V [ 1246.826] (WW) NVIDIA(GPU-0): Mode is rejected: PixelClock (241.5 MHz) too high for [ 1246.826] (WW) NVIDIA(GPU-0): Display Device (Max: 230.0 MHz). [ 1246.826] (WW) NVIDIA(GPU-0): Mode "2560x1440_60" is invalid. Any idea what I can do about this?
Andreas Spengler (81 rep)
Feb 19, 2021, 09:50 AM • Last activity: Feb 25, 2021, 09:28 AM
0 votes
1 answers
704 views
size of display connected via HDMI was'nt automatically detected correctly (xUbuntu)
I have xUbuntu 18.04.4 LTS (XFCE 4.12 + 4.15.0-111 Linux kernel) on the Dell Vostro 3360 laptop. When I connected the external display (Samsung SyncMaster T240) via VGA cable - all is good and I got such xrandr output: ``` xrandr -q *** VGA-1 connected 1920x1200+1366+0 (normal left inverted right x...
I have xUbuntu 18.04.4 LTS (XFCE 4.12 + 4.15.0-111 Linux kernel) on the Dell Vostro 3360 laptop. When I connected the external display (Samsung SyncMaster T240) via VGA cable - all is good and I got such xrandr output:
xrandr -q
***
VGA-1 connected 1920x1200+1366+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
***
But when I connected this one via HDMI cable the size of this display isn't detected correcltly (in the XFCE Display window it shows as Samsung 7") and I got such output:
***
xrandr -q
HDMI-1 connected 1920x1200+1366+0 (normal left inverted right x axis y axis) 160mm x 90mm
   1920x1200     59.95*+
***
Accordingly, some apps such as Viber or Caliber are displayed with "huge controls". How I can fix this problem (desirable - not only for this display, but for HDMI-connections at all)? UPDATED. for now looks like problem is in EDID-information that is sending by external-display via HDMI (and NO, xrandr --fbmm doesn't works...)
Sergej Matsypa (101 rep)
Jul 19, 2020, 12:51 PM • Last activity: Jul 21, 2020, 08:47 AM
4 votes
0 answers
1165 views
How to drive an external monitor that does not send hotplug info over HDMI?
Since a few days I have the Dasung `Paperlike HD` device and after using it for one day I'm afraid the utility that comes with it, did something it shouldn't have done. **Hot-plug events** First, of all, it doesn't seem to receive hot-plug information over HDMI (anymore). The so-called `HPD` (hot-pl...
Since a few days I have the Dasung Paperlike HD device and after using it for one day I'm afraid the utility that comes with it, did something it shouldn't have done. **Hot-plug events** First, of all, it doesn't seem to receive hot-plug information over HDMI (anymore). The so-called HPD (hot-plug detect) signal carried through pin 19 (see [wikipedia](https://en.wikipedia.org/wiki/HDMI)) does not seem to arrive. **Manually enable** We can override this (our interface is DP-1):
echo 'on-digital' | sudo tee /sys/class/drm/card0-DP-1/status
Now we can read the EDID information through edid-decode /sys/class/drm/card0-DP-1/edid
edid-decode (hex):

00 ff ff ff ff ff ff 00 12 63 01 00 00 00 00 00 
0a 1d 01 03 80 14 0f 78 2a 08 a5 a2 57 4f a2 28 
0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01 
01 01 01 01 01 01 c1 3e 98 a8 80 72 2e 60 38 20 
36 00 c8 96 00 00 00 1e 00 00 00 10 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 fc 00 50 
61 70 65 72 6c 69 6b 65 20 48 20 44 48 3f 40 30 
62 b0 32 40 40 c0 13 00 6d 55 21 00 00 1e 00 d1 

----------------

EDID version: 1.3
Manufacturer: DSC Model 1 Serial Number 0
Made in week 10 of 2019
Digital display
Maximum image size: 20 cm x 15 cm
Gamma: 2.20
DPMS levels: Off
RGB color display
First detailed timing is preferred timing
Color Characteristics
  Red:   0.6328, 0.3398
  Green: 0.3105, 0.6328
  Blue:  0.1582, 0.0605
  White: 0.3134, 0.3291
Established Timings I & II: none
Standard Timings: none
Detailed mode: Clock 160.650 MHz, 200 mm x 150 mm
               2200 2256 2288 2368 ( 56  32  80)
               1650 1653 1659 1696 (  3   6  37)
               +hsync +vsync
               VertFreq: 40.001 Hz, HorFreq: 67.842 kHz
Dummy Descriptor
Display Product Name: Paperlike H D
Detailed mode: Clock 162.000 MHz, 621 mm x 341 mm
               1600 1664 1856 2160 ( 64 192 304)
               1200 1201 1204 1250 (  1   3  46)
               +hsync +vsync
               VertFreq: 60.000 Hz, HorFreq: 75.000 kHz
Checksum: 0xd1
The checksum is correct. We use the indicated modelines to manually configure the interface
xrandr --newmode "Low-res" 162.000 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
xrandr --addmode DP-1 "Low-res"
xrandr --output DP-1 --mode "Low-res"
# Bug This leads to the following trace (with dmesg -w):
[  760.510138] ------------[ cut here ]------------
[  760.510140] WARN_ON(len  0b b8 d0 78 02 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5
[  760.510316] RSP: 0018:ffffacbf40ebbb40 EFLAGS: 00010286
[  760.510318] RAX: 0000000000000000 RBX: ffff98275e83a000 RCX: 0000000000000000
[  760.510319] RDX: 0000000000000011 RSI: ffffffff88f945b1 RDI: 0000000000000246
[  760.510320] RBP: ffffacbf40ebbb40 R08: ffffffff88f945a0 R09: 0000000000000011
[  760.510321] R10: ffffffff88f94980 R11: 0000000088f9459f R12: ffff9826fda56800
[  760.510322] R13: 00000000000a4cb8 R14: ffff982766680000 R15: 00000000000278d0
[  760.510324] FS:  00007f8f40701a80(0000) GS:ffff98276b300000(0000) knlGS:0000000000000000
[  760.510325] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  760.510326] CR2: 00007f0bb409b703 CR3: 0000000228540002 CR4: 00000000003606e0
[  760.510329] Call Trace:
[  760.510369]  intel_dp_mode_valid+0xb6/0x240 [i915]
[  760.510383]  drm_helper_probe_single_connector_modes+0x412/0x740 [drm_kms_helper]
[  760.510406]  drm_mode_getconnector+0x47d/0x4b0 [drm]
[  760.510409]  ? radix_tree_lookup+0xd/0x10
[  760.510428]  ? drm_connector_property_set_ioctl+0x60/0x60 [drm]
[  760.510440]  drm_ioctl_kernel+0xae/0xf0 [drm]
[  760.510451]  drm_ioctl+0x234/0x3d0 [drm]
[  760.510471]  ? drm_connector_property_set_ioctl+0x60/0x60 [drm]
[  760.510476]  ? __fsnotify_parent+0x9f/0x140
[  760.510478]  do_vfs_ioctl+0x407/0x670
[  760.510482]  ksys_ioctl+0x67/0x90
[  760.510484]  __x64_sys_ioctl+0x1a/0x20
[  760.510487]  do_syscall_64+0x57/0x190
[  760.510490]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  760.510491] RIP: 0033:0x7f8f40a6137b
[  760.510493] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05  3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48
[  760.510494] RSP: 002b:00007ffd3eb26108 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
[  760.510497] RAX: ffffffffffffffda RBX: 00007ffd3eb26150 RCX: 00007f8f40a6137b
[  760.510498] RDX: 00007ffd3eb26150 RSI: 00000000c05064a7 RDI: 000000000000000e
[  760.510499] RBP: 00000000c05064a7 R08: 0000000000000007 R09: 0000000000000190
[  760.510500] R10: 0000000000000140 R11: 0000000000003246 R12: 0000000000000001
[  760.510501] R13: 000000000000000e R14: 00007ffd3eb26150 R15: 0000000000000000
[  760.510503] ---[ end trace 706fd3d45f136b1f ]---
Apparently in the following function the i915 module does receive a value equal or smaller than 0 as return value of intel_dp_common_len_rate_limit.
int
intel_dp_max_link_rate(struct intel_dp *intel_dp)
{
	int len;

	len = intel_dp_common_len_rate_limit(intel_dp, intel_dp->max_link_rate);
	if (WARN_ON(len common_rates[len - 1];
}
I've also copied the edid data to /lib/firmware/edid/paperlike.bin and added the kernel commandline parameter drm_kms_helper.edid_firmware=edid/paperlike.bin. However, this doesn't make much of a difference. I think that's logical. It's not that the EDID information is not available. It's that the hot-plug pin is not set and so the entire screen is not considered to be connected. By manually setting it to be connected, the EDID information can be retrieved. However, actually sending data to it, doesn't work. My guess is that I've to do something else to override the hot-plug behaviour, but what? **Current situation** The current situation is that the Paperlike HD screen stays blank. Nothing happens. The USB part of it works though (it is a touchscreen). When setting the output with xrandr (as indicated above) it gives:
xrandr: Configure crtc 1 failed
It feels like I'm close to solving this riddle, however, I definitely need help here.
Anne van Rossum (1810 rep)
May 30, 2020, 03:12 PM • Last activity: May 30, 2020, 03:42 PM
1 votes
1 answers
779 views
Run an X program when a monitor is plugged in
I have a computer with a bizarre bug. When I turn off the monitor and turn it back on, the screen stays blank. This only happens while logged in under X (but not at the Gdm screen). I've found a way to cause the screen to turn on: ``` xset dpms force off xset dpms force on ``` How can I run these co...
I have a computer with a bizarre bug. When I turn off the monitor and turn it back on, the screen stays blank. This only happens while logged in under X (but not at the Gdm screen). I've found a way to cause the screen to turn on:
xset dpms force off
xset dpms force on
How can I run these commands automatically when the monitor is turned on? The monitor is connected over DisplayPort and reports EDID information. The operating system is Ubuntu 18.04. A polling-based solution is not acceptable. Turning the monitor on should react without waiting so polling would require a very short interval, but it's an infrequent action so it doesn't warrant keeping the CPU hot enough to run a task at subsecond intervals. I'm looking for a **trigger** when a monitor is plugged in, to run in the X session.
Gilles &#39;SO- stop being evil&#39; (862327 rep)
Jun 29, 2019, 09:11 PM
2 votes
1 answers
908 views
How can I get real-time information about monitor plug/unplug events?
When I connect or disconnect the USB device, udev shows/monitors that event. But udev is not enough smart to detect the plug-out or plug-in of the monitor. Is there any way/tool/utility from which I will get real-time information about the plug-out or plug-in of a monitor? (I know how to get [EDID i...
When I connect or disconnect the USB device, udev shows/monitors that event. But udev is not enough smart to detect the plug-out or plug-in of the monitor. Is there any way/tool/utility from which I will get real-time information about the plug-out or plug-in of a monitor? (I know how to get [EDID information](https://unix.stackexchange.com/questions/7622/edid-information) at some point in time, but not how to react when a monitor is plugged in.)
SHW (15376 rep)
Feb 21, 2011, 02:00 PM • Last activity: Jun 29, 2019, 07:50 PM
2 votes
1 answers
4103 views
How to load a modified EDID into RAM after boot to fix defective monitor's EDID report?
I've acquired a couple of HP L1750 monitors, which have VGA & DVI inputs. The VGA inputs work without issue. However, the DVI input only works until Kernel Mode Setting (KMS) occurs, after which it declares it isn't receiving a signal and enters sleep mode. I've tested two different HP L1750 monitor...
I've acquired a couple of HP L1750 monitors, which have VGA & DVI inputs. The VGA inputs work without issue. However, the DVI input only works until Kernel Mode Setting (KMS) occurs, after which it declares it isn't receiving a signal and enters sleep mode. I've tested two different HP L1750 monitors, with different DVI cables and different DVI source providers (i.e. different video cards) and the same behaviour obtains. I've also tried manually specifying the appropriate resolution via a kernel boot option, e.g.: video=DVI-D-0:1280x1024@60e As well as manually configuring xorg.conf (relying on the the output of hwinfo --monitor) to: Section "Device" Identifier "DefaultDevice" EndSection Section "Monitor" Identifier "DefaultMonitor" HorizSync 24-83 VertRefresh 50-77 Option "TargetRefreshRate" "60" Option "DDC" "off" Option "DPMS" "off" Option "DefaultModes" "on" Option "PreferredMode" "1280x1024" EndSection Section "Screen" Identifier "DefaultScreen" Device "DefaultDevice" Monitor "DefaultMonitor" EndSection The issue seems to be that the DVI of this monitor is defective without a special Windows driver to fix it . How do I determine what the appropriate EDID should be? And how do I go about loading it into RAM after boot? EDIT: Information about graphics card, kernel driver, X driver etc.: $ inxi -Gxxxxx Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: Micro-Star MSI driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:67df Display: x11 server: X.Org 1.20.4 driver: amdgpu unloaded: modesetting alternate: ati,fbdev,vesa compositor: kwin_x11 resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon RX 470 Graphics (POLARIS10 DRM 3.30.0 5.1.4-arch1-1-ARCH LLVM 8.0.0) v: 4.5 Mesa 19.0.5 direct render: Yes In terms of xrandr, it claims the DVI-D-0 is disconnected (even though it is connected and even though the monitor shows output via DVI-D-0 pre-KMS); I include here the modes it lists via VGA (note it's connected to VGA via a HDMI->VGA converter, so what shows up as HDMI-A-1 is actually the VGA connection) HDMI-A-1 connected 1280x1024+0+696 (normal left inverted right x axis y axis) 340mm x 270mm 1280x1024 60.02 + 75.02* 1920x1080 60.00 59.94 1280x800 60.02 1152x864 75.00 1280x720 60.00 59.94 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 720x480 60.00 59.94 640x480 75.00 72.81 60.00 59.94 720x400 70.08 DVI-D-0 disconnected (normal left inverted right x axis y axis) Trying to set the display manually with xrandr doesn't seem to work: $ xrandr --output DVI-D-0 --mode 1280x1024 xrandr: cannot find mode 1280x1024 Doing xrandr --output DVI-D-0 doesn't result in a "cannot find mode" message, but it doesn't turn the display on via DVI either. I tried xrandr --output DVI-D-0 --mode [...] for all of the resolutions listed above for the VGA connection, from 1280x1024 to 720x400, and all result in the "cannot find mode" message. EDIT2: Xorg.0.log information relevant to EDID: [ 45.594] (II) AMDGPU(0): EDID for output HDMI-A-1 [ 45.594] (II) AMDGPU(0): Manufacturer: HWP Model: 26e9 Serial#: 16843009 [ 45.594] (II) AMDGPU(0): Year: 2008 Week: 2 [ 45.594] (II) AMDGPU(0): EDID Version: 1.3 [ 45.594] (II) AMDGPU(0): Digital Display Input [ 45.594] (II) AMDGPU(0): Max Image Size [cm]: horiz.: 34 vert.: 27 [ 45.594] (II) AMDGPU(0): Gamma: 2.40 [ 45.594] (II) AMDGPU(0): DPMS capabilities: StandBy Suspend Off [ 45.594] (II) AMDGPU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 [ 45.594] (II) AMDGPU(0): Default color space is primary color space [ 45.594] (II) AMDGPU(0): First detailed timing is preferred mode [ 45.594] (II) AMDGPU(0): redX: 0.640 redY: 0.349 greenX: 0.284 greenY: 0.617 [ 45.594] (II) AMDGPU(0): blueX: 0.142 blueY: 0.067 whiteX: 0.313 whiteY: 0.329 [ 45.594] (II) AMDGPU(0): Supported established timings: [ 45.594] (II) AMDGPU(0): 720x400@70Hz [ 45.594] (II) AMDGPU(0): 640x480@60Hz [ 45.594] (II) AMDGPU(0): 640x480@72Hz [ 45.594] (II) AMDGPU(0): 640x480@75Hz [ 45.594] (II) AMDGPU(0): 800x600@60Hz [ 45.594] (II) AMDGPU(0): 800x600@72Hz [ 45.594] (II) AMDGPU(0): 800x600@75Hz [ 45.594] (II) AMDGPU(0): 832x624@75Hz [ 45.594] (II) AMDGPU(0): 1024x768@60Hz [ 45.594] (II) AMDGPU(0): 1024x768@70Hz [ 45.594] (II) AMDGPU(0): 1024x768@75Hz [ 45.594] (II) AMDGPU(0): 1280x1024@75Hz [ 45.594] (II) AMDGPU(0): 1152x864@75Hz [ 45.594] (II) AMDGPU(0): Manufacturer's mask: 0 [ 45.594] (II) AMDGPU(0): Supported standard timings: [ 45.594] (II) AMDGPU(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 [ 45.594] (II) AMDGPU(0): Supported detailed timing: [ 45.594] (II) AMDGPU(0): clock: 108.0 MHz Image Size: 340 x 270 mm [ 45.594] (II) AMDGPU(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0 [ 45.594] (II) AMDGPU(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0 [ 45.594] (II) AMDGPU(0): Ranges: V min: 50 V max: 77 Hz, H min: 24 H max: 83 kHz, PixClock max 145 MHz [ 45.594] (II) AMDGPU(0): Monitor name: HP L1750 [ 45.594] (II) AMDGPU(0): Serial No: CND8020JJG [ 45.594] (II) AMDGPU(0): Supported detailed timing: [ 45.594] (II) AMDGPU(0): clock: 27.0 MHz Image Size: 160 x 90 mm [ 45.594] (II) AMDGPU(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0 [ 45.594] (II) AMDGPU(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0 [ 45.594] (II) AMDGPU(0): Number of EDID sections to follow: 1 [ 45.594] (II) AMDGPU(0): EDID (in hex): [ 45.594] (II) AMDGPU(0): 00ffffffffffff0022f0e92601010101 [ 45.594] (II) AMDGPU(0): 0212010380221b8ceedc55a359489e24 [ 45.594] (II) AMDGPU(0): 115054adef8081800101010101010101 [ 45.594] (II) AMDGPU(0): 010101010101302a009851002a403070 [ 45.594] (II) AMDGPU(0): 1300540e1100001e000000fd00324d18 [ 45.594] (II) AMDGPU(0): 530e000a202020202020000000fc0048 [ 45.594] (II) AMDGPU(0): 50204c313735300a20202020000000ff [ 45.594] (II) AMDGPU(0): 00434e44383032304a4a470a202001b0 [ 45.594] (II) AMDGPU(0): 02031b61230907078301000067030c00 [ 45.594] (II) AMDGPU(0): 2000802d43908402e2000f8c0ad08a20 [ 45.594] (II) AMDGPU(0): e02d10103e9600a05a00000000000000 [ 45.594] (II) AMDGPU(0): 00000000000000000000000000000000 [ 45.594] (II) AMDGPU(0): 00000000000000000000000000000000 [ 45.594] (II) AMDGPU(0): 00000000000000000000000000000000 [ 45.594] (II) AMDGPU(0): 00000000000000000000000000000000 [ 45.594] (II) AMDGPU(0): 00000000000000000000000000000029 [ 45.594] (--) AMDGPU(0): HDMI max TMDS frequency 225000KHz [ 45.594] (II) AMDGPU(0): Printing probed modes for output HDMI-A-1 [ 45.594] (II) AMDGPU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP) [ 45.594] (II) AMDGPU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) [ 45.594] (II) AMDGPU(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e) [ 45.594] (II) AMDGPU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [ 45.594] (II) AMDGPU(0): Modeline "1280x800"x60.0 108.00 1280 1328 1440 1688 800 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 45.594] (II) AMDGPU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [ 45.594] (II) AMDGPU(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 45.595] (II) AMDGPU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) [ 45.595] (II) AMDGPU(0): EDID for output DVI-D-0 [ 45.595] (II) AMDGPU(0): Output DisplayPort-0 connected [ 45.595] (II) AMDGPU(0): Output DisplayPort-1 disconnected [ 45.595] (II) AMDGPU(0): Output HDMI-A-0 connected [ 45.595] (II) AMDGPU(0): Output HDMI-A-1 connected [ 45.595] (II) AMDGPU(0): Output DVI-D-0 disconnected [ 45.595] (II) AMDGPU(0): Using user preference for initial modes [ 45.595] (II) AMDGPU(0): Output DisplayPort-0 using initial mode 1280x1024 +0+0 [ 45.595] (II) AMDGPU(0): Output HDMI-A-0 using initial mode 1280x1024 +0+0 [ 45.595] (II) AMDGPU(0): Output HDMI-A-1 using initial mode 1280x1024 +0+0 [ 45.595] (II) AMDGPU(0): mem size init: gart size :ff973000 vram size: s:ff2e8000 visible:f2e8000 [ 45.595] (==) AMDGPU(0): DPI set to (96, 96) [ 45.595] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
emacsomancer (509 rep)
May 25, 2019, 10:03 PM • Last activity: May 26, 2019, 05:02 PM
1 votes
2 answers
9652 views
How to tell intel graphics to use my custom EDID file?
As the topic says: How to tell intel graphics to use my custom EDID file?
As the topic says: How to tell intel graphics to use my custom EDID file?
Rimfire (279 rep)
Jul 14, 2016, 05:00 AM • Last activity: May 4, 2019, 10:12 AM
Showing page 1 of 20 total questions