Jump to content

SteeMan

Moderators
  • Posts

    1460
  • Joined

  • Last visited

Posts posted by SteeMan

  1. 48 minutes ago, spirake said:

    What should I do to use the same custom dtb all the time?

     

    I tried to already answer that question, but perhaps I wasn't specific enough:

    16 hours ago, SteeMan said:

    If you are going to use a custom dtb you need to put it in the /boot directory and make the extlinux.conf point to it there.

    You need to place the custom dtb outside the /boot/dtb directory in /boot directly. Then you extlinux.conf reference would look like: FDT /<custom file>.dtb

  2. @VN-HCM_dung  Here is what you would need to do.  1) perform a new clean install on the new tv box on the emmc.  This will create the partitions in the correct location, preserving the android uboot environment.  2) Assuming that you have the same linux kernel installed on the old and new boxes, you can simply replace the contents of the root partition (you don't need to touch the boot partition /boot) with those from your original box.  You can use /root/install-aml.sh as a guide on what needs to be copied over. (If you have a different kernel version then you also need to preserve /lib/modules/(your kernel version) on the root partition.

  3. Can you help even a little bit.  How about you start with telling what you have done?  Give context to the screen shot.  Showing a random screen shot is of no help.  List the exact steps you have done, and what you are trying to do.

    Also you need to answer my questions when I ask, if you want help.  You still haven't answered the question I asked if you have successfully tested running the desktop build from the SD card?  Because you were able to run the cli version from sd only based on prior reports.

    I've taken hours of my time to help you.  You need to try harder to make it easier to help you.

     

  4. You maybe have already done this, but please try with the instructions and downloads from here:

    https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus

     

    Your box should have an s912 amlogic cpu.  Which means you should be trying the meson-gxm-* dtb files (of which there are 11 in the latest builds).

     

    Since you say you have tried different downloads/instructions, you may need to reflash the android firmware so that you are starting from a known environment.  Who knows what boot environment is currently on your box.

     

     

  5. OK, as I suspected, your file has windows carriage returns (^M) at the end of each line.  So I'm guessing you used a windows editor to edit the file, which automatically added these characters. 

    I have attached your file with those characters removed.  Please try it.

    I'm surprised I haven't seen this issue before as I would think it would be quite common to do exactly what you did.

    I'm not 100% sure these extra carriage returns are the problem, and I won't be around my tv boxes to test this until tomorrow morning, but I'm pretty sure that is your issue.

    extlinux.conf

  6. This helps a lot, thanks.

    It would appear that there is something wrong with your extlinux.conf file.  Please attach the file you are using for me to review.

    The log you posted shows:

     

    Retrieving file: /extlinux/extlinux.conf

    ...

    Ignoring unknown command: FDT

    Ignoring unknown command:

    Ignoring unknown command:   append

    ...

    SCRIPT FAILED: continuing...

    Found U-Boot script /boot.scr

    ...

    Current fdtfile after armbianEnv: amlogic/meson-gxl-s905x-libretech-cc.dtb

    Mainline bootargs: root=/dev/mmcblk1p1 ...

     

    So the log shows that it can't correctly read the extlinux.conf file, specifically the two important lines (the FDT and append lines, which are the dtb and kernel boot parameters).

    So then it falls back to using some default stuff and ends up trying to boot with the wrond dtb and the wrong kernel bootargs.  Which is why the boot process is then failing.

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines