Odroid C2: kernel panic "Failed to execute /init (error -2)" when trying to load custom EDID

cosmos · March 11, 2024 at 11:59 AM

This is related to Odroid C2 on 11.0.1: switching tv to 24fps? where I was trying to get my C2 switch to 1080p24, even though it is not normally detected by EDID? Followed the Intel-related instructions in https://wiki.libreelec.tv/configuration/edid#intel however during boot the boot process is stopped with the error message specified in the subject and described in length in my older thread.

Has anyone on C2 been able to successfully use these instructions, in order to boot with a modified EDID file? If not, then there's obviously something different on C2 boots, otherwise I'll need some help figuring what I'm doing differently here...

**chewitt** · March 11, 2024 at 12:53 PM

Bash

#!/bin/bash

# SPDX-License-Identifier: GPL-2.0
# Copyright (C) 2022-present Team LibreELEC (https://libreelec.tv)

do_install(){
  # create the persistent firmware dir
  mkdir -p "/storage/.config/firmware/edid"

  # capture the raw edid file
  if [ ! -e /storage/.config/firmware/edid/edid.bin ]; then
    cat "/sys/class/drm/card0-HDMI-A-1/edid" > "/storage/.config/firmware/edid/edid.bin"
  else
    echo "info: using existing edid.bin"
  fi

  # create the cpio file
  mkdir -p "/storage/cpio/lib/firmware/edid"
  cp "/storage/.config/firmware/edid/edid.bin" "/storage/cpio/lib/firmware/edid/"
  cd "/storage/cpio" || echo "error: cannot find /storage/cpio .. exiting!" && exit 1
  find . -print | cpio -ov -H newc > "/storage/.config/firmware/edid/edid.cpio"

  # mount /flash rw
  mount -o remount,rw /flash

  # copy the cpio file
  cp "/storage/.config/firmware/edid/edid.cpio" "/flash/edid.cpio"

  # cleanup cpio dir
  rm -rf "/storage/cpio"

  # determine boot method and set params
  if [ -f "/flash/extlinux/extlinux.conf" ]; then
    FILE="/flash/extlinux/extlinux.conf"
    if grep -q "initrd=/edid.cpio" "${FILE}" ; then
      echo "error: ${FILE} already contains edid.cpio, aborting!"
      exit 1
    else
      cp "${FILE}" "${FILE}.backup"
      sed -i "/ APPEND/s/$/ drm.edid_firmware=edid\/edid.bin video=HDMI-A-1:D/" "${FILE}"
      echo "info: edid setup complete!"
      exit 0
    fi
  else
    FILE="/flash/uEnv.ini"
    if grep -q "initrd=/edid.cpio" "${FILE}" ; then
      echo "error: ${FILE} already contains edid.cpio info .. aborting!"
      exit 1
    else
      cp "${FILE}" "${FILE}.backup"
      sed -i "/ bootargs/s/$/ drm.edid_firmware=edid\/edid.bin video=HDMI-A-1:D/" "${FILE}"
      echo "info: edid setup complete!"
      exit 0
    fi
  fi
}

do_cleanup(){
  rm "/storage/.config/firmware/edid/edid.bin"
  rm "/storage/.config/firmware/edid/edid.cpio"
  mount -o remount,rw /flash
  rm "/flash/edid.cpio"
  if [ -f "/flash/extlinux/extlinux.conf" ]; then
    FILE="/flash/extlinux/extlinux.conf"
  else
    FILE="/flash/uEnv.ini"
  fi
  cp "${FILE}.backup" "${FILE}"
  mount -o remount,ro /flash
}

do_usage(){
  echo "usage: getedid {create|delete}"
  exit 0
}

case $1 in
  create)
    do_install
    ;;
  delete)
    do_cleanup
    ;;
  *)
    do_usage
    ;;
esac

exit

Display More

I created ^ that some time ago to replicate the "edid-create" process for other boards (which never seemed to quite work) but it's not something that I was able to test easily so it hasn't been upstreamed.

Copy to /storage, make it executable, then run "./script.sh create" and see what happens.

cosmos · March 11, 2024 at 7:32 PM

Just ran it: displayed a "using existing edid" but nothing more. Upon closer inspection, it seems the script exits at line 20 for some reason (even though the script enters /storage/cpio succesfully). Modified that line to do a cd alone.

Now the script produced:

Code

info: using existing edid.bin
info: edid setup complete!

... and /flash/extlinux/extlinux.conf:

Code

LABEL LibreELEC
 LINUX /KERNEL
 FDT /meson-gxbb-odroidc2.dtb
 APPEND boot=LABEL=LIBREELEC disk=LABEL=STORAGE systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0 drm.edid_firmware=edid/edid.bin video=HDMI-A-1:D

And it worked!!!! Cheers mate!!!

cosmos · March 12, 2024 at 6:46 AM

If it might help someone, checking what is different from the wiki (and what I basically followed) for the C2 case, it seems that the instructions for intel-based installations need a couple of modifications for C2 systems:

1) An addition perhaps should be made that extlinux.conf might be available as /flash/extlinux/extlinux.conf instead of /flash/extlinux.conf

2) Most importantly, contents of extlinux.conf should not include the initrd=/edid.cpio part, otherwise the system will panic at boot.

**chewitt** · March 12, 2024 at 10:06 AM

I'll probably just add the script (with an edit to L20) and see what issues are unearthed.