pi-top fails to boot with EDID enabled

My pi-top fails to boot with EDID enabled (tested with 16-11-18 5.27 build)

The resolution set in CONFIG.TXT doesn’t appear to matter, it boots to a black screen that slowly fades to white.

I suspect this is on your pi-top one whose display is 1366 pixels wide. i.e. not divisible by 8
As I’m sure you know, using an MDF with 1360×768 works.

p.s. pi-top 2’s EDID defaults to 1920×1080 and that works o.k. but it also offers a 720 mode, selecting it results in no display

I suspect this is on your pi-top one whose display is 1366 pixels wide. i.e. not divisible by 8

Correct. I would expect this to be handled now the OS supports padding to fix the “not divisible by 8” issue.

I would expect this to be handled now the OS supports padding to fix the “not divisible by 8” issue.

Mmm I am duly disabused. I wonder though if there is a bug in that new feature and a copy of the EDID block might help Jeffrey fix it?
Though I’m probably going off half cock!

If it’s the same EDID from here then it seems to work OK for me with the latest ROM (although I’m testing with a regular monitor, using hdmi_edid_file in config.txt to get the firmware to load EDID.DAT).

Did it used to work in the past? (although I added support for automatic row padding about a year ago, I don’t remember seeing anyone report back that the pi-top was now working correctly). In particular, if specifying disable_mode_changes makes it work, then that points to a problem with how we’re reprogramming the GPU.

Also, what does *Status show for the configured mode?

I don’t remember seeing anyone report back that the pi-top was now working correctly

So:

• It never did work

Or:

• It worked great but nobody bothered to say so

Given this is the internet, I’m leaning towards the second choice…

It worked great but nobody bothered to say so

Given this is the internet, I’m leaning towards the second choice…

I’ve just finished a day full of that option, mixed with a large helping of us not changing anything and magically fixing things for a service involving a third party who “didn’t do nuffin honest guv it must have been your change”
So, perfectly normal.

If it’s the same EDID from here then it seems to work OK for me

It’s not quite the same, there’s a few bytes that are different:

0x00 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x00 0x26 0xCF 0x33 0x05 0x00 0x00 0x00 0x00
0x00 0x16 0x01 0x03 0x80 0x1D 0x11 0x78 0x0A 0x12 0x30 0x91 0x56 0x53 0x92 0x28
0x1E 0x50 0x54 0x00 0x00 0x00 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01
0x01 0x01 0x01 0x01 0x01 0x01 0xD5 0x1C 0x56 0xA6 0x50 0x00 0x23 0x30 0x28 0x20
0x3C 0x00 0x25 0xA5 0x10 0x00 0x00 0x19 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xFE 0x00 0x49
0x6E 0x66 0x6F 0x56 0x69 0x73 0x69 0x6F 0x6E 0x0A 0x20 0x20 0x00 0x00 0x00 0xFE
0x00 0x4D 0x31 0x33 0x33 0x4E 0x57 0x4E 0x31 0x20 0x52 0x33 0x20 0x0A 0x00 0x5F

Did it used to work in the past?

I’ve never got EDID to work on my pi-top.

what does *Status show for the configured mode?

“Auto”. Configure is also set to “Auto”. Obviously that’s with EDID disabled, I don’t know if either of those change when it is enabled.