Investigate Clock Frequency (w/ EDID) of ScreenPad Plus

[Qonfused]

Continue investigating ScreenPad Plus 'scrambled display-out' issue, potentially involving a custom WEG patch or edited EDID data injection.

[Qonfused]

For reference, this is the dumped EDID data from windows for the BOE087F display (ScreenPad Plus):

Hex data (8 rows):

00 FF FF FF FF FF FF 00 09 E5 7F 08 00 00 00 00
01 1D 01 04 A5 1F 08 78 02 D2 2D 93 51 57 8D 28
18 4E 52 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 94 1B 80 A0 70 03 32 20 30 20
55 00 35 53 10 00 00 1A 12 16 80 A0 70 03 32 20
30 20 55 00 35 53 10 00 00 1A 00 00 00 FE 00 42
4F 45 20 48 46 0A 20 20 20 20 20 20 00 00 00 FE
00 4E 56 31 32 36 42 35 4D 2D 4E 34 31 0A 00 ED

(one row):

00 FF FF FF FF FF FF 00 09 E5 7F 08 00 00 00 00 01 1D 01 04 A5 1F 08 78 02 D2 2D 93 51 57 8D 28 18 4E 52 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 94 1B 80 A0 70 03 32 20 30 20 55 00 35 53 10 00 00 1A 12 16 80 A0 70 03 32 20 30 20 55 00 35 53 10 00 00 1A 00 00 00 FE 00 42 4F 45 20 48 46 0A 20 20 20 20 20 20 00 00 00 FE 00 4E 56 31 32 36 42 35 4D 2D 4E 34 31 0A 00 ED

[Qonfused]

Below was the attempted EDID patch in the 0x2 device block (PciRoot(0x0)/Pci(0x2,0x0)):

Key	Type	Value
AAPL01,override-no-connect	Data	00FFFFFF FFFFFF00 09E57F08 00000000 011D0104 A51F0878 02D22D93 51578D28 184E5200 00000101 01010101 01010101 01010101 0101941B 80A07003 32203020 55003553 1000001A 121680A0 70033220 30205500 35531000 001A0000 00FE0042 4F452048 460A2020 20202020 000000FE 004E5631 32364235 4D2D4E34 310A00ED

[Qonfused]

Will investigate possible hot-plug issue w/ HDMI fix in a separate PR.

[Maleficent-Magik]

from now until the end of the month I'm on vacation ^^' so I don't have access to my Zenbook anymore, I wish you good luck! don't hesitate to share your progress

[Qonfused]

I also found the display under the linux hw EDID repo: https://raw.githubusercontent.com/linuxhw/EDID/master/DigitalDisplay.md MFG	Model	Name	Res	Inch	Made	ID
BOE	BOE087F	HF NV126B5M-N41	1920 x 515	12.6	2019	46E74341751E

edid-decode (hex):

00 ff ff ff ff ff ff 00 09 e5 7f 08 00 00 00 00
01 1d 01 04 a5 1f 08 78 02 d2 2d 93 51 57 8d 28
18 4e 52 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 94 1b 80 a0 70 03 32 20 30 20
55 00 35 53 10 00 00 1a 12 16 80 a0 70 03 32 20
30 20 55 00 35 53 10 00 00 1a 00 00 00 fe 00 42
4f 45 20 48 46 0a 20 20 20 20 20 20 00 00 00 fe
00 4e 56 31 32 36 42 35 4d 2d 4e 34 31 0a 00 ed

[Maleficent-Magik]

excellent idea ! (btw, before going on vacation, I had tested a method which consisted in putting an edid file in System/Library/Displays/Overrides but it did not bring any change.so the problem is not related to the edid I think)Le 12 août 2022 05:15, Cory Bennett @.***> a écrit : I also found the display under the linux hw EDID repo: https://raw.githubusercontent.com/linuxhw/EDID/master/DigitalDisplay.md MFGModelNameResInchMadeIDBOEBOE087FHF NV126B5M-N411920 x 51512.6201946E74341751E edid-decode (hex): 00 ff ff ff ff ff ff 00 09 e5 7f 08 00 00 00 00 01 1d 01 04 a5 1f 08 78 02 d2 2d 93 51 57 8d 28 18 4e 52 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 94 1b 80 a0 70 03 32 20 30 20 55 00 35 53 10 00 00 1a 12 16 80 a0 70 03 32 20 30 20 55 00 35 53 10 00 00 1a 00 00 00 fe 00 42 4f 45 20 48 46 0a 20 20 20 20 20 20 00 00 00 fe 00 4e 56 31 32 36 42 35 4d 2d 4e 34 31 0a 00 ed

Will probably do more testing in Linux as well to verify whether it's actually a eDP or DP interface connected.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[Qonfused]

Yeah I have the same display EDID in macOS still:

<00 ff ff ff ff ff ff 00 09 e5 7f 08 00 00 00 00 01 1d 01 04 a5 1f 08 78 02 d2 2d 93 51 57 8d 28 18 4e 52 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 94 1b 80 a0 70 03 32 20 30 20 55 00 35 53 10 00 00 1a 12 16 80 a0 70 03 32 20 30 20 55 00 35 53 10 00 00 1a 00 00 00 fe 00 42 4f 45 20 48 46 0a 20 20 20 20 20 20 00 00 00 fe 00 4e 56 31 32 36 42 35 4d 2d 4e 34 31 0a 00 ed>

I do notice that it's IODisplayConnectFlags is 00 00 00 00 w/ only the framebuffer patch (in spite of power data, etc in IORegistryExplorer showing it is enabled and using the correct display type).

[Qonfused]

There's also a 48 Hz profile (reminds me that an old hack during the Mojava Beta days was to patch 4k@60 displays as 48 Hz):

Detailed Timing Descriptors:
    DTD 1:  1920x515    60.074881 Hz 384:103   33.942 kHz     70.600000 MHz (309 mm x 83 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    5 Vsync   5 Vback   40 Vpol N
    DTD 2:  1920x515    48.076923 Hz 384:103   27.163 kHz     56.500000 MHz (309 mm x 83 mm)
                 Hfront   48 Hsync  32 Hback   80 Hpol P
                 Vfront    5 Vsync   5 Vback   40 Vpol N

^ If that timing works that might be indicative of a clock-data issue. Reconnecting the internal DP connector for the screenpad plus could test for a possible hot-plug issue instead.

[Qonfused]

I worry that there is some kind of DP -> eDP adapter logic (given the datasheet shows a eDP connector) that I've somehow looked over in the schematic. That would make it easy to revisit #1.

[Qonfused]

There doesn't appear to be any evidence of invalid clock data, or anything related to some kind of OEM patch to the display's EDID data.

Will open up a new pull request to investigate HDMI hot-plug.