SteeMan

That list of dtbs you provided are not from official builds. I don't know what code you are using and therefore can't provide help. But the s905x3 would use a meson-sm1-* dtb.

What box do you have, and what download do you have installed?

I believe the driver for this is already in the Armbian builds with the exception of the meson64-edge kerne, and I think that is an oversight and I have a question in to confirm.

Also going back to a very basic question. What do you intend to use the TV box for? Why do you even want to use the desktop version?

One thought I have for you to try is to go back to the clu version, and use armbian-config to install/enable desktop support on it.

I am on vacation this week. So I can't really offer much support as I don't have access to my boxes to test any suggestions.

So you were successful with the cli build, but the xfce build isn't booting?

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.

Yes

Also have you tried installing the desktop build on emmc? It should work. You shouldn't care what size it takes on the SD card, as that doesn't impact how it is installed on emmc. Most of the space on the SD card is unused empty space.

Have you run the desktop version from SD card? No reason to worry about emmc install if the performance isn't going to meet your needs. I personally find the performance on most TV boxes to be too slow for real use desktop use. They in my opinion are best for usage as servers.

What build did you download from the armbian servers? I assume you are looking for a desktop build, it looks like you installed a server/command line build.

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.

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

Can you attach the file instead of cut/paste?

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.

I just noticed this from your post above. If this is from your extlinux.conf, you have a typo. It should be "meson-gxl-s905x-p212.dtb" (note - not . )

That thread has a different error (/dev/mmcblk1p1 does not exist) and he is using different hardware. Also his issue is that it works fine running from sd card until after he does an update/upgrade. You can't get it running at all from the sd card. So most likely very different problems.

Also, I'm assuming your video was from you booting from an sd card the 23-02 build you downloaded, correct?

That was helpful. I can make out some of the information. What I would like you to try is to get a clearer picture/video of the information in the attached screenshot (the stuff before "Starting kernel") What I can see from this screenshot is the problem is with the kernel running, not the u-boot, I need to see the arguments that u-boot is passing to the kernel, which I can't make out from the video you sent.

I don't know. The safest would be to flash android again and install. I'm still waiting for this requested information.

@Thinvent What TV Box are you using? What build are you using (filename and where you downloaded from)?

Which ever you want (CLI = command line, i.e. server no gui; minimal = cli with minimal pre installed packages; xfce = gui desktop with xfce) I will need you to post the beginning part of the boot process you see, not the end. Also, what dtb file are you using? did you reenable multiboot? what u-boot.ext? Finally, I'm assuming the output above is from you attempting to boot 23-02 from sd card not from emmc, correct?

@nettings Moved your last post back to your original thread as I think that makes the most sense, instead of having your comments spread across two different threads.

Since I don't know what previous version you had installed in emmc (i.e. where it came from, who built it, etc). That means from my perspective you are trying to run the emmc install script on top of an unknown environment. So i'm left to guessing what your issues might be. The cleanest solution would be to flash android back to the emmc so you have a known starting point and then reinstalling the current armbian build. This assumes you have/can find a copy of android firmware for your box, or that you made a backup before you installed to emmc. If that doesn't work, I suspect the problem is that you are trying to 'reinstall' into emmc. The script is only tested for installing into a fresh environment that has android on it, not an environment that already has linux. So you may need to look at the script and only do the portions that are involved in the copying over of the files from the sd card, but omit that part that is creating the partitions and other work on the disk. To verify this is what is happening, I would need you to capture the entire output of your running of the install-aml.sh script for me to review.