Odroid C1 wrong kenel image on package upgrade?

Troubleshooting
21

Thanks @MichaIng! I would be happy to do it, the only problem on my side is that now I will not have physical access to the board (and as a consequence to the HDMI connection) for a while, possibly even for some months.
Is there another way to test it remotely? I guess not. :frowning:

22

Since we don’t know a clear kernel error that indicates whether HDMI works or not, no way to test remotely. And it would be risky anyway without physical access, in case some kernel build breaks boot or network.

It is not that urgent IMO: The DKMS issue is likely a rare one, specific to your particular driver sources, and now that we found the unintentionally missing RTW88 backport patch, that WiFi chip is generally supported already. And there is always the possibility to downgrade to package version 26.02.0-trunk-dietpi4.

23

I’ll test HDMI as soon as I can connect a display to the board. Iit’s currently running headless. I’ll report back soon.

24

Following MichaIng’s request on GitHub issue #8144, I tested HDMI on kernel 6.12.33-current-meson on my Odroid C1.

Setup

  • Device: Odroid C1 (Amlogic S805, armv7l)
  • DietPi: v10.3.3 (Trixie)
  • Kernel: 6.12.33-current-meson (linux-image-current-meson 26.05.0-trunk-dietpi5)
  • Display: 4K monitor connected via HDMI

Result: HDMI works correctly ✓

The display initialized at 1920x1080 without any errors. Console output was visible on screen immediately after boot. Relevant dmesg entries:

[3.390489] meson-drm d0100000.vpu: meson_vclk_setup(target: 1, phy: 1485000, dac: 148500, venc: 148500, hdmi_use_enci: 0)
[3.498634] Console: switching to colour frame buffer device 240x67
[3.549942] meson-drm d0100000.vpu: [drm] fb0: mesondrmfb frame buffer device

No DRM/VPU errors in dmesg. The HDMI pipeline (meson-drm / VPU) initializes cleanly and produces a stable image on screen.

This confirms that the HDMI regression introduced somewhere above 6.12.33 is not present in this kernel version, which should be a good basis for MichaIng’s planned v6.12.34 with the faulty commit re-implemented. Looking forward to eventually getting the kernel version unfrozen and tracking latest 6.12.y again.

25

Great, many thanks for testing! I’ll start working on a v6.12.34 next week, after the DietPi release this weekend.