Okay so I ordered the more on spec ZMI zPower Turbo 65W USB-C PD power adapter (5V @ 3A, 9V @ 3A, 12V @ 3A, 15V @ 3A, and 20V @ 3.25A) but still no dice. Using only the pi-top Display Cable (from the pi-top Display Port direct to the FHD Touch Display and Bluetooth Keyboard) and the ZMI PSU connected to the pi-top USB-C port the pi-top shows charging. Before powering on the pi-top the pi-top Touch Display shows no power (power and brightness buttons not lit up) and when turning on the pi-top the pi-top FHD Touch Display power and brightness buttons only turn on near the end of the loading stage (near end of OLED screen displaying 4 with rotating dashes) but the pi-top FHD Touch Display itself never displays anything and the backlight never even comes on (just black screen). Unplugging the pi-top Display Cable and replugging in and/or using the HDMI refresh from the OLED Settings area on the pi-top does nothing. In addition to the pi-top FHD Touch Display power and brightness buttons lighting up the Bluetooth Keyboard power light also lights up… but again the FHD Touch Display never displays anything. Again, it seems like this should be the happy path but doesn’t work at all. Would welcome any additional ideas. Seems to be an issue with the pi-top itself (maybe firmware) or the pi-top Display Cable and not the raspberry pi or pi-top FHD Touch Display and Bluetooth Keyboard (unless related to the proprietary protocol over the pi-top Display Cable as the pi-top Display Adapter seems to work fine)
Also, I’m assuming someone actually has a working pi-top + pi-top Display Cable + pi-top FHD Touch Display and Bluetooth Keyboard. If this is true would you mind sharing your /boot/config.txt file contents. Mine are the defaults from the OS install which I was also assuming would support the happy path by default (with pi-top FHD Touch Display and Bluetooth Keyboard connected via the pi-top Display Cable) as this is called a pi-top (like laptop) and not pi-box (as in… just a box with no screen or keyboard)
Can you send us a picture of your setup? I’ll send over my config.txt when I get home, but I dont recommend using my overclock haha. It isnt for the feint of heart.
This is my complete non-working setup. The pi-top Display Cable is plugged in to match the notch on both the pi-top and the pi-top FHD Touch Display. Also plugged in is the USB-C cable from the ZMI PSU. If I use the display adapter and a separate PSU for the pi-top and a separate PSU for the display adapter and then plug in the micro hdmi and micro usb cable then it all works but this is way too many cables and adapters to justify using this on the go (or at all) especially considering the loss of a usb port for the touch and now only having the option for a single display. 
Haha, I know what you mean about being on the go 
I’m still using the display adapter and the mini-hdmi on mine. Just a jumble of wires haha.
Yeah, some other people have been having issues and they are trying to track down the problem. I dont have the display cable so I dont know if my configuration will actually help you in this case 
Just to document, after making the EEPROM changes my bootconf.txt contains the following:
[all]
BOOT_UART=0
WAKE_ON_GPIO=0
POWER_OFF_ON_HALT=1
DHCP_TIMEOUT=45000
DHCP_REQ_TIMEOUT=4000
TFTP_FILE_TIMEOUT=30000
ENABLE_SELF_UPDATE=1
DISABLE_HDMI=0
BOOT_ORDER=0xf41
And my /boot/config.txt (minus comments) is as follows:
max_framebuffers=1
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
dtoverlay=dwc2
hdmi_force_hotplug:1=1
[all]
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
dtparam=i2c_arm=on
enable_uart=0
start_x=1
gpu_mem=128
dtparam=audio=on
disable_splash=0
dtparam=spi=off
I’m very curious how this all stacks up against a pi-top [4] Complete (with Raspberry Pi 4 4GB pre-installed) with a working pi-top FHD Touch Display and Bluetooth Keyboard (connected over the pi-top Display Cable… not using the pi-top Display Adapter). Or even how this stacks up to a pi-top [4] DIY Edition like mine if anyone has a working one (again with the pi-top FHD Touch Display and Bluetooth Keyboard connected over the pi-top Display Cable).
It would strike me as extremely odd if this made it all the way to production and no one has a working system or has ever tested this happy path default configuration.
Looking at /var/log/syslog I see the following (line of interest in bold) which seems related to displays not working on other OSes:
Mar 8 22:06:48 pi-top kernel: [ 5.260802] input: ILITEK ILITEK-TP Touchscreen as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/$
Mar 8 22:06:48 pi-top kernel: [ 5.261828] hid-generic 0003:222A:0001.0003: input,hiddev96,hidraw2: USB HID v1.10 Device [ILITEK ILITEK-TP] on$
Mar 8 22:06:48 pi-top kernel: [ 5.685493] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x0001$
Mar 8 22:06:48 pi-top kernel: [ 5.686091] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0$
Mar 8 22:06:48 pi-top kernel: [ 5.686626] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x0001$
Mar 8 22:06:48 pi-top kernel: [ 5.687211] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x000100$
Mar 8 22:06:48 pi-top kernel: [ 5.692786] g_ether gadget ptusb0: renamed from usb0
Mar 8 22:06:48 pi-top kernel: [ 6.003472] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
Mar 8 22:06:48 pi-top kernel: [ 6.028209] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
Mar 8 22:06:48 pi-top kernel: [ 6.028236] checking generic (3eace000 12c000) vs hw (0 ffffffffffffffff)
Mar 8 22:06:48 pi-top kernel: [ 6.028253] fb0: switching to vc4drmfb from simple
Mar 8 22:06:48 pi-top kernel: [ 6.029233] Console: switching to colour dummy device 80x30
Mar 8 22:06:48 pi-top kernel: [ 6.030337] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1
Mar 8 22:06:48 pi-top kernel: [ 6.045606] vc4-drm gpu: [drm] HDMI-A-1: EDID is invalid:
Mar 8 22:06:48 pi-top kernel: [ 6.045632] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Mar 8 22:06:48 pi-top kernel: [ 6.045648] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Mar 8 22:06:48 pi-top kernel: [ 6.045663] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Mar 8 22:06:48 pi-top kernel: [ 6.045679] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Mar 8 22:06:48 pi-top kernel: [ 6.045694] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Mar 8 22:06:48 pi-top kernel: [ 6.045709] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Mar 8 22:06:48 pi-top kernel: [ 6.045724] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Mar 8 22:06:48 pi-top kernel: [ 6.045739] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Mar 8 22:06:48 pi-top kernel: [ 6.154730] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
Mar 8 22:06:48 pi-top kernel: [ 6.157254] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Mar 8 22:06:48 pi-top kernel: [ 6.157287] [vc_sm_connected_init]: start
Mar 8 22:06:48 pi-top kernel: [ 6.162710] mc: Linux media interface: v0.10
Mar 8 22:06:48 pi-top kernel: [ 6.203702] [vc_sm_connected_init]: installed successfully
Mar 8 22:06:48 pi-top kernel: [ 6.221163] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Mar 8 22:06:48 pi-top kernel: [ 6.245704] Console: switching to colour frame buffer device 80x30
Mar 8 22:06:48 pi-top kernel: [ 6.250321] bcm2835_audio bcm2835_audio: card created with 4 channels
@hogank interesting that you don’t get a valid EDID, this might mean there is an issue with the HDMI I2C lines between the pi and the FHD display. Could you try forcing the HDMI resolution in config.txt by adding these lines:
hdmi_force_hotplug:0=1
hdmi_group=1
hdmi_mode=16
also try:
hdmi_force_hotplug:0=1
hdmi_group=2
hdmi_mode=82
also, what do you get if you run this:
/opt/vc/bin/tvservice -d edid.dat; /opt/vc/bin/edidparser edid.datThis will be good to troubleshoot in the future. @duwudi, are you going to go back and ask people to check their syslog as well? Maybe other people are having g similar issues?
Both edits to /boot/config.txt did not produce any changes when booting up (although of course the screen resolution changed in VNC viewer as expected). The pi-top FHD Touch Display still did not show anything and the backlight didn’t even turn on (although its power and brightness buttons lit up and the Bluetooth Keyboard light turned green as well). The output in /var/log/syslog still showed EDID is invalid in both cases. Following is the ouput of the commands:
root@pi-top:~# /opt/vc/bin/tvservice -d edid.dat; /opt/vc/bin/edidparser edid.dat
Nothing written!
Enabling fuzzy format match…
Failed to open edid.dat
/opt/vc/bin/edidparser exited with code -1
If it helps to clarify, this appears to be solely display related. Switching from VNC to the FHD Touch Display (unplugging the pi-top Display Cable from my Macbook and plugging into the FHD Touch Display and Bluetooth Keyboard) I can in fact use the keyboard and the touch screen as switching back to the VNC viewer shows/reflects the touches and keystrokes I took. So its purely the display that isn’t functioning over the display cable.
Other tvservice outputs for status, name, and list:
pi@pi-top:~ $ /opt/vc/bin/tvservice -s
state 0xa [HDMI DMT (82) RGB full 16:9], 1920x1080 @ 60.00Hz, progressive
pi@pi-top:~ $ /opt/vc/bin/tvservice -n
[E] No device present
pi@pi-top:~ $ /opt/vc/bin/tvservice -l
2 attached device(s), display ID’s are :
Display Number 2, type HDMI 0
Display Number 7, type HDMI 1
Just for your information, when you VNC in, unless you’ve set it up to do screen mirroring, it will start a new session, even if it is the same account. In a way, this makes it possible to have 3+ screen running simultaneously on the same user, if the displays after the second one, are connected via the network on VNC. By default, it wont mirror anything between sessions.
Also, the FHD display wont turn on the backlight unless it receives a valid signal. It goes to sleep immediately after power up. So it still could be ok, but not sending a valid signal through.
This is what I get going down the EDID rabbit hole (this was with micro hdmi going from pi-top to pi-top Display Adapter and into pi-top FHD Touch Screen). I’m not an expert here, just digging through everything I can trying to find anything remotely related and get this to work.
pi@pi-top:~ $ ls -1 /sys/class/drm/*/edid
/sys/class/drm/card1-HDMI-A-1/edid
/sys/class/drm/card1-HDMI-A-2/edid
pi@pi-top:~ $ edid-decode < /sys/class/drm/card1-HDMI-A-2/edid
No header found
pi@pi-top:~ $ edid-decode < /sys/class/drm/card1-HDMI-A-1/edid
EDID version: 1.3
Manufacturer: NCS Model 0 Serial Number 0
Made in week 13 of 2016
Digital display
DFP 1.x compatible TMDS
Maximum image size: 121 cm x 68 cm
Gamma: 2.50
Undefined display color type
Default (sRGB) color space is primary color space
First detailed timing is preferred timing
Display x,y Chromaticity:
Red: 0.6396, 0.3300
Green: 0.2998, 0.5996
Blue: 0.1503, 0.0595
White: 0.3125, 0.3291
Established timings supported:
640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
Standard timings supported:
Detailed mode: Clock 148.500 MHz, 1214 mm x 683 mm
1920 2008 2052 2200 hborder 0
1080 1084 1089 1125 vborder 0
+hsync +vsync
VertFreq: 60 Hz, HorFreq: 67500 Hz
Detailed mode: Clock 74.250 MHz, 1214 mm x 683 mm
1280 1390 1430 1650 hborder 0
720 725 730 750 vborder 0
+hsync +vsync
VertFreq: 60 Hz, HorFreq: 45000 Hz
Monitor name: NCS HDMI
Monitor ranges (GTF): 24-120Hz V, 12-154kHz H, max dotclock 340MHz
Has 1 extension blocks
Checksum: 0xb7 (valid)
CTA extension block
Extension version: 3
21 bytes of CTA data
Video data block
VIC 16 1920x1080@60Hz 16:9 (native) HorFreq: 67500 Hz Clock: 148.500 MHz
VIC 4 1280x720@60Hz 16:9 HorFreq: 45000 Hz Clock: 74.250 MHz
VIC 5 1920x1080i@60Hz 16:9 HorFreq: 33750 Hz Clock: 74.250 MHz
VIC 34 1920x1080@30Hz 16:9 HorFreq: 33750 Hz Clock: 74.250 MHz
VIC 19 1280x720@50Hz 16:9 HorFreq: 37500 Hz Clock: 74.250 MHz
VIC 20 1920x1080i@50Hz 16:9 HorFreq: 28125 Hz Clock: 74.250 MHz
Audio data block
Linear PCM, max channels 2
Supported sample rates (kHz): 48
Supported sample sizes (bits): 24 20 16
Speaker allocation data block
Speaker map:
FL/FR - Front Left/Right
Vendor-specific data block, OUI 000c03 (HDMI)
Source physical address 1.0.0.0
Underscans PC formats by default
Basic audio support
1 native detailed modes
Detailed mode: Clock 74.250 MHz, 1214 mm x 683 mm
1920 2008 2052 2200 hborder 0
540 542 547 562 vborder 0
+hsync +vsync interlaced
VertFreq: 60 Hz, HorFreq: 33750 Hz
Detailed mode: Clock 74.250 MHz, 1214 mm x 683 mm
1920 2008 2052 2200 hborder 0
1080 1084 1089 1125 vborder 0
+hsync +vsync
VertFreq: 30 Hz, HorFreq: 33750 Hz
Detailed mode: Clock 74.250 MHz, 1214 mm x 683 mm
1280 1720 1760 1980 hborder 0
720 725 730 750 vborder 0
+hsync +vsync
VertFreq: 50 Hz, HorFreq: 37500 Hz
Detailed mode: Clock 74.250 MHz, 1214 mm x 683 mm
1920 2448 2492 2640 hborder 0
540 542 547 562 vborder 0
+hsync +vsync interlaced
VertFreq: 50 Hz, HorFreq: 28125 Hz
Checksum: 0x1d (valid)@hogank would you mind if I ask support to replace your screen, pi-top and Display Cable? I’d like to get them back to my office to fully test the whole system.
Hey sorry for the late response. I’ve been traveling and just ended up returning the pi-top setup. By all appearances it’s a well designed and put together platform. Hopefully some of these issues can get ironed out, I’d love to give it a shot again in the future. Thanks for taking the time to check into the issues I was experiencing.
Hi @hogank, no worries thanks for the update. Did you buy directly from us or through a reseller? Just want to make sure I can get your units back for testing 
They were ordered through Amazon, so reseller I believe unless you stock them directly for Amazon to fulfill. The display cable and its two adapters came in a bag so a bit tough to identify if they were brand new or a previous defective return, but they looked new. The display, keyboard, and pi-top DIY case were all definitely brand new and never opened or returned prior to me, in my opinion.
Sounds like you bought it used. My pi-top came in a box from Amazon. I’ve bought used as well and it also came in a bag.
Sounds like it was a previous return and went though Amazon’s warehouse deals dept. Something I know all to well about as I work in Amazon in customer returns till I can get back to my normal work.
@duwudi getting that exact suit back from Amazon for testing will be a little difficult, they will more likely turn it on to check it’s working and put it up for resale again