I loaded the “display-dp.dtbo” , and when connecting the screen, it could display normally and enter the system. But when I unplugged the screen and then restarted the device, the boot process got stuck.
When I load display-edp-4k.dtbo, the same issue occurs.
The UART logs for both scenarios got stuck at:
[ 25.006413] cloud-init[1348]: Cloud-init v. 25.2-0ubuntu1~24.04.1 running 'modules:config' at Tue, 25 Nov 2025 18:52:16 +0000. Up 24.95 seconds.
cloud-config.service
gdm.service
run-user-120.mount
user-runtime-dir@120.service
user@120.service
rtkit-daemon.service
run-user-120-doc.mount
run-snapd-ns.mount
tmp-snap.rootfs_8vokyr.mount
[ 26.297325] DL0_FE: ASoC: no backend DAIs enabled for DL0_FE, possibly missing ALSA mixer-based routing or UCM profile
run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount
colord.service
systemd-localed.service
packagekit.service
upower.service
geoclue.service
systemd-timedated.service
When the screen is reconnected, it will continue：
[ 31.140600] mediatek-drm-dp-v2 11b60000.dp-tx: [DPTX] find encoder, found dp_intf[0] bridge node:/soc/disp-dvo1@14018000
[ 31.142055] mediatek-drm-dp-v2 11b60000.dp-tx: [DPTX] [0] fail to find property dp_dsc_enable
[ 31.143169] mediatek-drm-dp-v2 11b60000.dp-tx: [DPTX] [0] fail to find property dp_dsc_cfg
fprintd.service
[ 31.742369] mt8189-mt6359p soc:sound: ASoC: DAPM unknown pin DP
Ubuntu 24.04.4 LTS ubuntu ttyS0
ubuntu login:
It seems to be waiting for some kind of signal. However, when loading the display-dsi.dtbo file, this phenomenon will not occur. Is this a problem? Is there a way to achieve the effect that even when the DP screen is not connected, the boot process can still be completed fully, just like when loading the display-dsi.dtbo? The screen could also turn on normally after detecting the DP device signal.
Hi Jenkin,
Can you share the image version and the boot assets version that you are using? Thanks.
Hi，Mei_Yong
image version: genio-classic-desktop-noble-emmc-20260506-41.tar.xz
boot assets version: genio-g720-evk-boot-assets-20260506-50.tar.xz
Hi Jenkin, our team will try to reproduce the issue and will reach out if we need further information or have any update. Thanks and appreciate your patience.
Hi Jenkin,
I have been testing with my G720 and I can’t reproduce your failure with display-dp.dtbo enabled. My system completes the boot process with or without a display connected. I have had a colleague conform my results on their machine.
We are using:
91837802d4752d86c6dd8758cb8fdd57 genio-classic-desktop-noble-emmc-20260506-41.tar.xz
988d4f6271e74fbd8a798585ea62bb6e genio-g720-evk-boot-assets-20260506-50.tar.xz
Are you able to confirm you have the correct downloads, and share your flash command(s) with us?
Hi Adam,
We are using the same version:
jenkin@cbc051cf6dd6:~$ md5sum genio-classic-desktop-noble-emmc-20260506-41.tar.xz
91837802d4752d86c6dd8758cb8fdd57 genio-classic-desktop-noble-emmc-20260506-41.tar.xz
jenkin@cbc051cf6dd6:~$ md5sum genio-g720-evk-boot-assets-20260506-50.tar.xz
988d4f6271e74fbd8a798585ea62bb6e genio-g720-evk-boot-assets-20260506-50.tar.xz
We only modify the u-boot-initial-env：
list_dtbo= emmc.dtbo video.dtbo apusys.dtbo display-edp-4k.dtbo
（or list_dtbo= emmc.dtbo video.dtbo apusys.dtbo display-dp.dtbo)
then flash the image ( PC OS is WIndows11):
PS Z:\ubuntu-env\genio-classic-desktop-noble-emmc-20260506-41> genio-flash
Genio Tools: v1.7.1
Ubuntu Image:
edition: Ubuntu classic/core images
version: 24.04
codename: noble
After flashing, reboot G720 and observe the UART0 log:
[ OK ] Started gdm.service - GNOME Display Manager.
gdm.service
run-user-120.mount
user-runtime-dir@120.service
user@120.service
rtkit-daemon.service
run-user-120-doc.mount
run-snapd-ns.mount
tmp-snap.rootfs_C3K1ia.mount
run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount
colord.service
systemd-localed.service
packagekit.service
upower.service
geoclue.service
The expected phenomenon should be that one can input the account and password. Just like when enabling display-dsi.dtbo. Instead of being unable to input any further commands as was the case above.
The above experiment was also replicated on the Genio 720 EVK P2V3. Did you test it on the same platform?
hi jenkin,
could you remove the “quiet” option in kernel command line and provide the full log to us? you should be able to edit this in grub menu. thanks.
hi jenkin,
could you try to compress the text file and share the file to us? that would help us understand more. thanks.
Hi jianhui,
I tried to attach the full boot log, but it seems the system only accepts image files (jpg, png, etc.) – I couldn’t find an option to upload .txt or .zip.
So I’ve uploaded the log to Baidu Cloud Drive instead. You can download it from the following link:
ubuntu_edp_boot.log
link: https://pan.baidu.com/s/1rEnEjaBzN4WlX6d00xeMig
code: piuh
hi jenkin,
i didn’t see any obvious errors blocking the boot process. once you are able to log in to the device, could you provide the full dmesg and journalctl -b logs?
Hi jianhui,
I waited for a very long time before I could log in to the device. Here are the full dmesg and journalctl -b logs I captured:
ubuntu_edp_dmesg_journalctl .log
link: https://pan.baidu.com/s/1Jetr9HVIzBhgz0pEAywnkQ
code: bp4a
hi jenkin,
i can reproduce the case that display-edp.dtbo is loaded but not connected. plymouth-quit-wait.service starts waiting until it is timeout because there is no output. then serial-getty.service starts after.
there is no connected/disconnected status in edp right now, i think it is not a hotplug peripheral by design. a quick way to fix your case is disable plymouth service:
- add in kernel command line: plymouth.enable=0
or
- sudo systemctl mask plymouth-quit-wait.service; sudo systemctl daemon-reload
please check if it helps.
Hi jianhui,
We convert DP to HDMI, so hotplug is involved. And the method you provided is effective and we will adopt it. Really appreciate your help!