SteeMan

Please provide some basic information. What build are you using? What u-boot.ext? Screen shots of what you are seeing during the boot process would help. From your post it seems the system is booting, so I'm not sure what problems you are reporting without more details.

Based on the link you posted, you are not using Armbian. You are using builds from a fork of armbian for which the owners of that fork continue to use the Armbian name without permission (which causes confusion). We can't help you here as those are not armbian builds. You need to go to the site you downloaded from for help with their builds.

@Energokom Thank you for your contributions to the forum and welcome. I appreciate your comments and apparent knowledge. As for your question, I am going to direct you to this thread: I have been planning on getting this documented better as it is a bit complex sorting through hexdump's source code and notes, but the information is all there. I think you have the skills to sort it out. I inherited the existing u-boot-* files as binary blobs. It really bothers me to be including these in the builds without source code and instructions on how to recreate them. That is one of my next tasks on the aml-s9xx-box build is to make that better. So I have spent some time with hexdump's code rebuilding what is currently shipped, but I haven't really moved forward from there yet.

It depends on the native uboot installed on the box if it will support booting from a usb device. So some do and some don't. Your earlier post would indicate you have a faulty sd card and you may need to get a new one to continue down that path as it appears your device doesn't support booting from usb.

Are you asking if the armbian build will see all 4gb on this box? Or are you asking how to get it to see all 4gb?

The focus of armbian is supporting mainline linux. There really isn't any interest in supporting the legacy kernels. The legacy kernels are not supported and because of their age are full of known security vulnerabilities. However the build framework will let you build one if you need to.

You say you have tried many versions, can you be more specific? There are only the versions linked in the FAQ post instructions: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus If you are trying other builds then you may need to reinstall the original android firmware before trying the armbian community builds as mentioned in the instructions.

On a fresh install, the ssh daemon is running and listening on port22. You should be able to get the dynamically assigned ip address from your router and then log in as root with the default armbian root password. Then since this would be the first login, it will run through the initial setup in your ssh session, and prompt to the new root password, setup initial user, etc.

ssh in

Yes, I know that. I was just pointing out that you said: and he said: So it sounded like you were only planning on running one of the three commands he instructed you to run.

but what about version 5.88? I don't know what you mean.

I don't know what the problem is because as I said, you didn't capture the important part of the install-aml.sh script run. But I also did say the following: If you want a valid test of installing to emmc you need to restore the box to the original android firmware and start from there. And it may still not work, but that is the starting state the script expects and the only thing that is tested.

You need to follow *all* of the commands you were instructed to follow, not just one of them:

The error has nothing to do with internet. After the boot can't detect the emmc, then it falls back to trying to do a network boot, which is what you are seeing at the end of the log.

The messages are saying that the boot process can't find valid partitions on the emmc to boot from. Your video doesn't show the full log of the install-aml.sh (especially the partition creation which occurs at the beginning, so I don't know if the script had errors or not doing that part of the process.). Also, did you start from a clean android firmware on the emmc? That is what the script is expecting. If this is a box where you already had something else on the emmc, that may be causing the errors.

@jock @Igor I have been thinking along the same lines for the aml-s9xx-box builds. While having the weekly builds is great, they are very unstable, being built on current master with edge kernel and the unstable debian and ubuntu userlands. While that is all good for testing purposes, it is far from desirable for running anything in a production environment (yes there are crazy people like me that use TV boxes for production servers). Now that current has moved to 6.1 for meson64 and I suspect rockchip current will try to get to 6.1 soon, it would be nice to have stable builds based on a stable master, current kernel and supported userspace (i.e. jammy currently for ubuntu) for the TV Box targets, IMHO.

@Luis_D That installation guide doesn't apply to the Amlogic tv box builds (aml-s9xx-box) as they have their own procedures documented in the TV Box forum FAQ.

I thought you said that you were running the latest version from the sd card and that was the version that didn't go through the setup. Thus I am asking you to try the latest CLI/server version on SD to see if it goes through the initial setup. And then separately if you could try a fresh copy of the desktop version on SD and see if you can reproduce the issue with the setup being skipped.

Can you explain what you mean by this? what screen are you talking about?

No that wouldn't impact anything as the two environments are separate. Does it go through the initial configuration if you are using the cli/server version? Can you reproduce the issue by starting with a new image on the sd card and trying again? Also on the failure to run the install-aml.sh, does the script have execute permission set?

@HITCHER Your post was not allowed as it linked to external sites with non-armbian content. The answer to your question is no, it is not possible to combine the two.

You are typing the command wrong. There is a space after sudo, but if you are already logged in a root, you don't need the sudo at all. And in the case you did the command without sudo you didn't include the ./ Also note that you can't install on emmc if the box has an s905 cpu (you need an s905x or newer for emmc support). There was a recent thread that talked about this in the forums.

The s905w2 is a new cpu from amlogic. As far as I know no one has tried to get mainline linux running on tv boxes containing that cpu Generally when a manufacturer comes out with a new cpu it takes the main line linux community a couple of years to get a stable system working on it (if there is enough community support). So I would suggest you use your box as an android box and come back in a year or so to see if there has been any movement to support this cpu. Or if you have the skills work on bringing support for the cpu into mainline linux.

@Serkan Polat You don't mention what kind of board/box you are using. However I am assuming you are using some sort of android TV box (since your post mentions coreelec and a random tv box dtb file). You should note that TV Boxes are not supported by armbian. I should move your post to the TV Box community forum, but I will leave it here since you are offering to pay someone for help and this forum is where you are more likely to find someone with the skills that might be able to help. (The TV box forums generally only have end users reading the posts).

There is no mainline linux support for the s905x4 so you are out of luck. And from the threads I have read, no one seems interested in ever making that happen, especially amlogic.