Usb-c dp stopped working after apt update

Edge2
1

Which system do you use? Android, Ubuntu, OOWOW or others?

Ubuntu Jammy 22.04

Which version of system do you use? Khadas official images, self built images, or others?

Khadas official from OOWOW, I don’t remember the exact option.

Please describe your issue below:

After I recently updated the system, including the kernel, my monitor attached to usb-c display port stopped working. Before it was working fine, as the only screen, from boot.

I still have access with ssh, the system is running fine.

Post a console log of your issue below:

It is hard to tell for me where to look, however in the output of journalctl I find the following, which might be relevant:

Apr 25 16:18:18 kukudh kernel: rockchip-vop2 fdd90000.vop: Adding to iommu group 17
Apr 25 16:18:18 kukudh kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x5, primary plane phy id: 2
Apr 25 16:18:18 kukudh kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp1 assign plane mask: 0xa, primary plane phy id: 3
Apr 25 16:18:18 kukudh kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x140, primary plane phy id: 8
Apr 25 16:18:18 kukudh kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp3 assign plane mask: 0x280, primary plane phy id: 9
Apr 25 16:18:18 kukudh kernel: [drm] failed to init overlay plane Cluster0-win1
Apr 25 16:18:18 kukudh kernel: [drm] failed to init overlay plane Cluster1-win1
Apr 25 16:18:18 kukudh kernel: [drm] failed to init overlay plane Cluster2-win1
Apr 25 16:18:18 kukudh kernel: [drm] failed to init overlay plane Cluster3-win1
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: bound fdd90000.vop (ops 0xffffffc008e97298)
Apr 25 16:18:18 kukudh kernel: dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: bound fde80000.hdmi (ops 0xffffffc008ea5d48)
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: bound fde50000.dp (ops 0xffffffc008ea8958)
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: route-dsi0: failed to get logo,offset
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: route-hdmi0: failed to get logo,offset
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: can't not find any logo display
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: failed to show kernel logo
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
Apr 25 16:18:18 kukudh kernel: rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
Apr 25 16:18:18 kukudh kernel: [drm] Initialized rockchip 3.0.0 20140818 for display-subsystem on minor 0

In /boot I find:

initrd.img-5.10.198
initrd.img-5.10.160
initrd.img-5.10.66

So I guess I was on kernel 5.10.160 before uname -a gives

Linux kukudh 5.10.198 #1.6.5 SMP PREEMPT Fri Mar 1 10:24:40 CST 2024 aarch64 aarch64 aarch64 GNU/Linux

What would be the best way to downgrade the kernel back to 5.10.160 to test my assumption that the breaking appears between kernel versions?

Do you know a possible fix using the latest kernel?

Thanks, cheers, Lasse.

2

@graphicore
Try this firmware
https://dl.khadas.com/products/edge2/firmware/ubuntu/emmc/edge2-ubuntu-22.04-gnome-linux-5.10-fenix-1.6.2-240110-emmc.img.xz

3

@ivan.li, thanks. I installed that image. I used the OOWOW tool, as I don’t use Ubuntu which is required for the burn-tools, I’m on openSUSE Tumbleweed. I tried but it had a segmentation fault.

My screen is working again!

The journalctl output above seems to be irrelevant as it’s the same still.

I’m not keen to being unable to ever update again. Should I file an issue on GitHub - khadas/fenix: One-stop script set to build Ubuntu/Debian images to get this tracked and resolved? Otherwise, what would be the correct issue tracker?

4

Hi @graphicore
Thank you for your feedback, I will try to reproduce and solve it, and will update here later.

5

Hello @graphicore

I used the lastest official firmware, but can’t reproduce the problem. Please make sure the cable and screen are ok.
By the way, when connecting usb-c port to dp-screen, the screen don’t need to require additional power supply.

Regards.