Which version of system do you use? Khadas official images, self built images, or others?
vim4-ubuntu-24.04-server-linux-5.15-fenix-1.7.3
Please describe your issue below:
Hi everyone,
I installed [vim4-ubuntu-24.04-server-linux-5.15-fenix-1.7.3] on my VIM4 via OOWOW, but it doesn’t boot at all—there’s not even the Khadas logo on the screen.
I’m booting from eMMC.
After trying different versions, I found that the device boots successfully when using a Fenix 1.6.x image, but any version 1.7 or later seems to fail.
Unfortunately, I’m not sure where or how to check for error messages or logs in this situation.
Could anyone advise me on:
How to troubleshoot this kind of boot issue?
How to access logs or debug information during early boot (e.g., via serial console)?
Whether this is a known issue with Fenix 1.7.x and VIM4?
Any help would be greatly appreciated. Thanks in advance!
Thank you very much for the suggestion about checking via serial connection.
I tried it, and I found that the system is booting properly—I can see the login screen through the serial console.
So, the issue seems to be that nothing is shown on the display.
I’m using the standard HDMI port (not the mini HDMI) on the VIM4.
Here is a trimmed portion of the boot log that may be related to HDMI or display output:
Error getting FEAT_DISABLE_HDMI_TX_3D: 101
vpp: vpp_init, chip_id=54
vpp: set_osd1_rgb2yuv rgb2yuv on = 0
...
lcd: [0]: use panel_type=mipi_0
lcd: load dts config: TS050, lcd_type: mipi(3)
lcd: [0]: lcd_set_connector: connector_type: MIPI_A
lcd: error: can't find node: /reserved-memory/linux,lcd-cma
...
outputmode=panel
connector_type=MIPI_A
...
vout_hdmi_hpd: lcd no need hpd detect
vout_hdmi_hpd: hdmimode=none
vout_hdmi_hpd: colorattribute=444,8bit
...
not find mapped vic
the resolveResolution mode [1280x768p60hz] is not valid
...
set HDMI to highest edid mode: 2160p60hz
support current mode:[2160p60hz], deep color:[420,10bit]
...
outputmode[2160p60hz420] is invalid
...
EDID version: 1.3
Manufacturer: NEC Model 2dd7 Serial Number [redacted]
Monitor name: EA271U
At this point, I’m not sure whether the display is being handled correctly or not.
This is not a major issue for me personally, since I can access the system via serial.
However, if it’s useful for improving support for Fenix 1.7.x, I’d be happy to share more logs or test further.
Please let me know if there’s anything specific I should check or provide.
I am a newly registered user and have encountered an issue where I am currently unable to attach files to my emails. Could you please advise on what steps I should take or what alternative method you recommend in order to successfully send you the requested log files?
Thank you very much for your prompt response and assistance. I’m pleased to inform you that I am now able to attach files with my messages—thanks to your efforts.
Please find attached the requested logs and configuration files:
kernel.txt (output of dmesg)
display-mode.txt (output of cat /sys/class/display/mode)
drm-modes.txt (output of cat /sys/class/drm/card0-HDMI-A-1/modes)
disp_cap.txt (output of cat /sys/class/amhdmitx/amhdmitx0/disp_cap)
edid.txt (output of edid-decode < /sys/class/amhdmitx/amhdmitx0/rawedid)
For privacy and security reasons, sensitive information (such as serial numbers and MAC addresses) has been redacted.
Thank you again for your support and for enabling the file attachment capability. Please let me know if you require any additional information or further testing.
