Jump to content

Kelvie Wong

Members
  • Posts

    6
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Kelvie Wong got a reaction from laibsch in HDMI doesn't work for radxa-zero 3 on "current" and "edge", but works on "vendor" (for the 4GB version)   
    So I have two boards, and two images, both built with armbian-build. I built `current` on March 24th 2025 and HDMI and everything works great
     
    I built one this week and there is no HDMI output.
     
    Logs of the non-working one:
     
    Apr 07 18:36:09 radxa-zero3 kernel: mmc2: new UHS-I speed SDR104 SDIO card at address 390b Apr 07 18:36:09 radxa-zero3 kernel: rk808-rtc rk808-rtc.4.auto: registered as rtc0 Apr 07 18:36:09 radxa-zero3 kernel: rk808-rtc rk808-rtc.4.auto: setting system clock to 2017-08-05T09:00:10 UTC (1501923610) Apr 07 18:36:09 radxa-zero3 kernel: rockchip-vop2 fe040000.vop: Adding to iommu group 0 Apr 07 18:36:09 radxa-zero3 kernel: rockchip-drm display-subsystem: bound fe040000.vop (ops vop2_component_ops [rockchipdrm]) Apr 07 18:36:09 radxa-zero3 kernel: dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY) Apr 07 18:36:09 radxa-zero3 kernel: dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver Apr 07 18:36:09 radxa-zero3 kernel: rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops dw_hdmi_rockchip_ops [rockchipdrm]) Apr 07 18:36:09 radxa-zero3 kernel: [drm] Initialized rockchip 1.0.0 for display-subsystem on minor 0 Apr 07 18:36:09 radxa-zero3 kernel: rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes Apr 07 18:36:09 radxa-zero3 kernel: rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes  
    Logs of the working one:
    Mar 24 21:17:04 radxa-zero3 kernel: mmc_host mmc2: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0) Mar 24 21:17:04 radxa-zero3 kernel: dwmmc_rockchip fe2c0000.mmc: Successfully tuned phase to 150 Mar 24 21:17:04 radxa-zero3 kernel: mmc2: new ultra high speed SDR104 SDIO card at address 390b Mar 24 21:17:04 radxa-zero3 kernel: rockchip-vop2 fe040000.vop: Adding to iommu group 0 Mar 24 21:17:04 radxa-zero3 kernel: rk808-rtc rk808-rtc.4.auto: registered as rtc0 Mar 24 21:17:04 radxa-zero3 kernel: rockchip-drm display-subsystem: bound fe040000.vop (ops vop2_component_ops [rockchipdrm]) Mar 24 21:17:04 radxa-zero3 kernel: rk808-rtc rk808-rtc.4.auto: setting system clock to 2017-08-05T09:00:10 UTC (1501923610) Mar 24 21:17:04 radxa-zero3 kernel: dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY) Mar 24 21:17:04 radxa-zero3 kernel: dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver Mar 24 21:17:04 radxa-zero3 kernel: rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops dw_hdmi_rockchip_ops [rockchipdrm]) Mar 24 21:17:04 radxa-zero3 kernel: [drm] Initialized rockchip 1.0.0 for display-subsystem on minor 0 Mar 24 21:17:04 radxa-zero3 kernel: Console: switching to colour frame buffer device 240x67 Mar 24 21:17:04 radxa-zero3 kernel: rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device  
    On the non-working one, I've tried both the same kernel version (6.12.20) as well as the most recent `current` (6.12.21), and edge (6.14.1).
     
    Buildling a vendor image on bookworm works fine. Given I have two systems where one works and one doesn't, what can I check between them (deb package versions maybe? DTB files?) to help debug this?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines