SteeMan

Moved the post to the correct sub-forum.

Moved

https://www.armbian.com/amlogic-s9xx-tv-box/

Some basic information would be very helpful. What image are you using (exact file name for the image please). What install steps did you perform? Can you include a screen shot/picture of what exactly you are seeing on screen? A capture of the boot log (either via uart or pictures of what is on screen can be helpful too).

You really should create a device tree overlay that just changes that attribute. The biggest downside of what you have done, is that every time you upgrade the linux kernel your change will be lost (as the new dtb file from that kernel will be installed) and you will need to redo this work with each upgrade.

moved

I'm sure it is AI powered, so if you asked it to, I'm sure it would

@arboniid Can you provide the exact filename of the image you are using? Also the name of the SBC you have that you are working with.

You need to make sure that any disk IDs get updated to the new values for you target media. Look in your armbianEnv.txt file and possibly your /etc/fstab files. But in general to solve booting issues you will need a USB uart adapter to see what is happening during the boot process that is failing.

Have you tried installing the armbian-firmware-full package? (By default armbian ships with a slimmed down set of device firmwares, but the -full package includes all the ones from mainline)

Yes I had thought of that, that should work.

yes

All of this information is very helpful. Here is what you need to try. Look at the file aml_autoscript in your armbian /boot folder. This is the script that should get run when the reset button is pressed during poweron on a regular amlogic based android tv box. But since you now have access to the uboot console, you can enter these environment commands directly. If you start with the 'setenv bootcmd... and end with the 'saveenv' you will have modified the uboot environment to run armbian from sd or usb first, and then fall back to your other os on emmc. In looking at your current uboot environment, the only command that will be modified from what you have is the 'bootcmd'. In looking at what you have both the armbian and your current bootcmd fall back to run 'storeboot'. But by installing the armbian version you will loose the abiltiy to boot osmc from sd or usb, which you probably don't care about, but I thought I would mention it.

I'd recommend looking at the script /root/install-aml.sh. This is the script that would copy from SD to emmc (if that was supported with your CPU). It is a pretty simple script and you can see the logic it uses to copy the root partition to another medium.

From the Installation Instructions post ( https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus) "Note: It is not possible to install into emmc on boxes with the s905 cpu"

u-boot-s905x-s912

That isn't the correct uboot to be using, and have you tried all of the s905w-* drb files?

You are using the minimal image which as the name implies has the bare minimum set of packages installed.

The appropriate place for this question is in the existing thread for rk3328 tv boxes:

Per the documentation: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-login

@orlando mendez Those aren't Armbian official images. You would need to ask whomever produced those images for that information.

It this really is amlogic based, then start here: https://www.armbian.com/amlogic-s9xx-tv-box

I believe the G11 Pro has an Amlogic s905x3 processor, so moving to the appropriate forum.

I'm not sure there is a problem. It looks like this may be expected behavior. I think your board is a community supported device which means that by default it will be on the beta apt repository. There are new packages deployed to the beta apt repository daily. So depending on the settings you have for your apt updates if you have automatic updates enabled and reboot on kernel updates you will get a daily reboot. Some of this functionality for auto updates in armbian-config was just recently introduced.

moved to correct forum and added the proper tag