Jump to content


  • Posts

  • Joined

  • Last visited

Reputation Activity

  1. Like
    g00d got a reaction from Igor in auto-shutdown and wake-on-lan ( WOL )   
    I understand now.
    thanks for clarification
  2. Like
    g00d got a reaction from Igor in [ODROID-HC2] where does u-boot look for necessary files and what filesystem type is needed ?   
    Me again. I figured out what the problem was and I was able to solve this like that:
    the original /boot structure contains three symbolic links, in my case on the ODROID-HC2 (which is equal to odroidxu4):
    dtb -> dtb-5.4.151-odroidxu4
    uInitrd -> uInitrd-5.4.151-odroidxu4
    zImage -> vmlinuz-5.4.151-odroidxu4
    The default boot.ini is seeking for that link names but on the fat system it's not possible to have symbolic links. I just renamed (or one can simply copy) the existing three files like that:
    dtb-5.4.151-odroidxu4 ---to---> dtb
    uInitrd-5.4.151-odroidxu4 ---to---> uInitrd
    vmlinuz-5.4.151-odroidxu4 ---to---> zImage
    I also found out that /boot folder is NOT being red by boot process, it looks at the root folder for those files. So I "mv /boot/* /" moved the complete content of the /boot folder into the root. That way the boot process works like a charm.
    Thank you Igor for assistance. Have a nice weekend

  3. Like
    g00d reacted to phelum in Full root filesystem encryption on an Armbian system (NEW, replaces 2017 tutorial on this topic)   
    In one of your previous posts you listed some U-Boot code that changed the fdtfile variable depending on the board name and you noted that your board wasn't mentioned.  The U-Boot log shows it is loading a flattened device tree file that is 88701 bytes long.  Can you check in your /boot/dts directory and check if the .dts file for your board is 88701 bytes ?  Somefile.dts files provide hardware details for the drivers and using the wrong one might cause all sorts of problems.  What I.m checking here is that U-Boot is loading the correct .dts file for your board.
    -- Steven
  4. Like
    g00d reacted to NicoD in How to debug boot issues on ODROID-HC2   
    You need to use ssh to login to it, and then configure everything like that.
    This video shows how to install headless(without hdmi).

    I'm not sure, but I think OMV can do full disk encryption easily. For that you need a Debian (buster, bullseye) image and OMV can be installed with armbian-config.
    Here how to install OMV. Search google for full disk encryption on OMV.
  5. Like
    g00d reacted to phelum in How to debug boot issues on ODROID-HC2   
    I think you need a serial cable connected to the UART0 port (try 115200 8N1).  This will show you the U-Boot output.  The U-Boot output should end with "Starting kernel ...".  If you see nothing after this then either the kernel isn't starting or its bootargs are specifying the wrong console for output.  The primary console in the bootargs should be "ttyS0,115200".
    I hope this helps.  I don't know the board and are assuming it uses the standard Armbian boot script.
  6. Like
    g00d reacted to Werner in How to debug boot issues on ODROID-HC2   
    Perhaps increase boot verbosity like suggested in the documentation.
  • Create New...