Closed alexvnesta closed 20 hours ago
@alexvnesta, I just checked 0.3.5 Jummy Current (Armbian-unofficial_24.2.0-trunk_Mkspi_jammy_current_6.6.17.img.xz) and everything looks fine.
My configuration:
Some extra info:
cat /boot/armbianEnv.txt
lsmod | grep -i "fb\|drm\|gpu"
[ 0.093835] platform ff3c0000.hdmi: Fixed dependency cycle(s) with /vop@ff370000/port/endpoint@0
[ 3.345724] rockchip-drm display-subsystem: bound ff370000.vop (ops vop_component_ops)
[ 3.345903] dwhdmi-rockchip ff3c0000.hdmi: supply avdd-0v9 not found, using dummy regulator
[ 3.346320] dwhdmi-rockchip ff3c0000.hdmi: supply avdd-1v8 not found, using dummy regulator
[ 3.347020] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2)
[ 3.348976] dwhdmi-rockchip ff3c0000.hdmi: registered DesignWare HDMI I2C bus driver
[ 3.349926] rockchip-drm display-subsystem: bound ff3c0000.hdmi (ops dw_hdmi_rockchip_ops)
[ 3.351730] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[ 3.519833] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device
[ 17.308315] [drm] Initialized lima 1.1.0 20191231 for ff300000.gpu on minor 1
[ 20.905456] systemd[1]: Starting Load Kernel Module drm...
[ 21.117802] systemd[1]: modprobe@drm.service: Deactivated successfully.
[ 21.125509] systemd[1]: Finished Load Kernel Module drm.
verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=eea90f05-b8de-46b1-adfa-bf0fc3de8ac0
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
fb_st7796 12288 0
fbtft 49152 1 fb_st7796
gpu_sched 49152 1 lima
drm_shmem_helper 24576 1 lima
and
total 0
lrwxrwxrwx 1 root root 0 Jan 21 2016 card0 -> ../../devices/platform/display-subsystem/drm/card0
lrwxrwxrwx 1 root root 0 Jan 21 2016 card0-HDMI-A-1 -> ../../devices/platform/display-subsystem/drm/card0/card0-HDMI-A-1
lrwxrwxrwx 1 root root 0 Jul 27 13:45 card1 -> ../../devices/platform/ff300000.gpu/drm/card1
lrwxrwxrwx 1 root root 0 Jul 27 13:45 renderD128 -> ../../devices/platform/ff300000.gpu/drm/renderD128
-r--r--r-- 1 root root 4.0K Jan 21 2016 version
mkspi:~:% cat /sys/class/drm/card0-HDMI-A-1/status
connected
mkspi:~:% cat /sys/class/drm/card0-HDMI-A-1/modes
800x480
800x480
720x480
720x480
720x480
720x480
640x480
640x480
640x480
What happened?
I haven't had the time to check older trunk releases - can someone please confirm this is a real regression on 0.3.5?
On both the Debian bookworm edge (Armbian-unofficial_24.2.0-trunk_Mkspi_bookworm_edge_6.7.5.img.xz) and the ubuntu jammy current (Armbian-unofficial_24.2.0-trunk_Mkspi_jammy_current_6.6.17.img.xz) my genuine Makerbase ips50 display is not working.
Specifically - The backlight illuminates, but there is no display output. I have all three cables connected - Usb, 24v power, and HDMI. Just the backlight illuminates, nothing more. I just got this display, so I can't confirm if it worked on a previous build.
My display does work when plugged into a normal windows pc.
Here is some info - when I only specify extraargs=video=HDMI-A-1:e or no extra args at all.
Boot takes forever and keeps trying to resolve the below errors.
When I add the resolution and hotplug to my /boot/armbianEnv.txt, the startup does not throw any errors and is fast, but I still get no display out, just backlight.
HDMI-A-1:800x480@60e hdmi_force_hotplug=1
How to reproduce?
Flash emmc with either of the two images and hook up all three cables.
Branch
main (main development branch)
On which host OS are you observing this problem?
Jammy
Relevant log URL
No response
Code of Conduct