SteeMan
-
Posts
2021 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by SteeMan
-
-
You say you have followed the instructions. Have you explicitly followed this note from the instructions:. Note2: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attemping the install. coreelec changes the boot environment in ways that are incompatible with these armbian builds.
-
@RicardoSA What instructions are you following? No current instructions have a step that requires you to copy any file to root. Look at the instructions in the FAQ section of the TV box forum.
-
Moved your post to the appropriate forum.
Please read the TV Box forum FAQ items:
https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus
-
While there are other differences, based on what you have described the biggest difference for you is that the "arm-64" builds are no longer maintained. Those builds from October 2020 are the last that will be made. Whereas the "aw-h6-tv" builds are being currently maintained by balbes150 and are current with the latest kernel patch releases.
-
@extremeaudio both of your questions are answered by the FAQ posts in the TV Box forums: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus
-
Moved post to the correct location in the TV Boxes forum
-
@Tanmay Saha You didn't indicate what build you were using or what steps you were using. I would recommend starting with the TV box FAQ: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
and https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus
-
moved topic to the proper forum
-
@supersmurfs Since above you state that your box is an Allwinner H616 box, the following thread is tracking the base Armbian development for supporting the H616 cpu. While support is progressing, it is a way from being stable/supported.
-
This comment is likely superceeded by balbes and jock's posts, but I wanted to just provide my thoughts on the android dtb issues.
The way I like to think about dtbs is they are glue code between the kernel and the hardware. We often think of them only from the perspective of the hardware, which once a box is built the hardware doesn't change (although boxes can change over the course of different manufacturing runs providing different board revisions). But the kernel is an evolving code base and even though the hardware may be fixed, the dtb glue may need to change over time as the kernel code changes. Thus technically dtbs are kernel version specific (but in practice the changes in the kernel generally are not significant over smaller periods of time).
However.... When it comes to android kernels two factors come into play, one is that android kernels tend to be highly forked/patched from mainline kernels and second, android kernels tend to be based off very old kernels. So for example an android 4.4 based kernel is really a 5 year old kernel, and a lot has changed in the kernel over a 5 year period.
Also, making this more complex is that fact that sbc/tv box support has only been added to mainline kernels fairly recently. So older android or legacy kernels that were supported were highly patched kernels.
Armbian is generally focused on current mainline kernels (after all that is where the future support will all take place), and therefore a 5.10/5.12 kernel is very different in how it supports sbc/tv box hardware than a 4.4/4.x legacy/android kernel.
The end result is to not expect an android dtb to work with a mainline kernel. That doesn't mean that there isn't a lot to be learned from an older dtb file, but the process is much more complicated than simply getting the old andoird dtb and using it on a mainline kernel and expecting it to work.
-
@supersmurfs Welcome to the Armbian TV box forums. I want to thank you for your interest and apparent willingness to dig in and learn.
-
Most of my TV boxes are amlogic based. I just bought an H6 box but haven't had time to do much with it other than to boot an armbian build on it. Armbian booted on the box but networking didn't work, so I need to find some time to look into that when I get a chance. I may be reaching out to you once you get your allwinner boxes up and running
-
The first place to start is by reading the documentation: Armbian Developer Guide. The developer guide walks you through the armbian build process. The entire armbian build process may be more than you are looking for (not knowing what changes you are looking to make), but with an overall understanding of the armbian build process (simply being able to rebuild the image you are already running) you will likely be able to figure out a path forward for your needs, or at least be able to come back to the forums with a more specific question based on greater understanding of the system.
-
@Clonazepunk Welcome to armbian. I was just reading your recent posts and it sounds like you have some good technical skills and a desire to help others. A combination that is in limited supply. As you are new to armbian, if there is anything I can do to help your learning curve please reach out to me. The TV Box community needs people like you willing to help others. It seems that you have an interest in both rockchip and allwinner TV boxes. While Jock and other provide great support for rockchip there really isn't anyone currently supporting allwinner. So if you are looking for a challenge...
Again if you have any questions for me please reach out to me either in the forums or through PM.
-
-
-
Your question was already answered the first time you posted your question.
There is an entire thread dedicated to discussing how to install armbiian on an rk322x tv box: https://forum.armbian.com/topic/17979-help-can-i-install-armbian-on-tv-box-with-r329q-v30-board/?tab=comments#comment-123847
This is now the third the you are asking the same question. It you ask a fourth time, I will consider you as spamming the forum and proceed accordingly.
-
Moved to proper forum for a TV box question.
Please read the FAQ entry: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
Then search the forums for previous discussions on this topic.
-
@Wizzard In searching through this thread and the forums, I can't see anyone reporting to have tried installing on your model. Since no one has responded to your post, it is unlikely anyone around here has your model of box and therefore unlikely to be able to help you out. There are hundreds of different TV box models each with different components which makes support for the vast majority nearly impossible. There is likely information in this thread that could help you, but unfortunately you are likely on your own to sort through it and try out potential solutions to get your box working. One thing I noticed in this thread that may be helpful to your case is a comment that mentioned replacing the uboot on the armbian image with a libreelec uboot. Since you indicate you can boot libreelec that path sounded relevant to your situation. Unfortuantely I don't own any rockchip boxes and therefore am of little help beyond providing pointers to others efforts.
-
Your question is off topic for these forums as we deal with running armbian on SBCs and TV Boxes. Not with apks and android.
-
14 minutes ago, masteripper said:
OK...restoring means flash ?
yes
-
1 hour ago, masteripper said:
Thanks @SteeMan for the assistance.. given the fact that I switch MicroSDs and the one holding the Manjaro each time boots multiboot is enabled... what do you think ?
The manjaro version of multiboot is enabled but that has nothing to do with the armbian version of multiboot. Each distro does multiboot differently and they are not compatible. You must restore the base android firmware to get a good known environment before attempting armbian. I don't know how many times I have to say the same thing. If you want help, you need to follow the instructions.
-
33 minutes ago, masteripper said:
what about the subquestion...if the multi boot persists
Enabling multiboot is something that only should need to be done once, assuming it is done correctly. It is persisted in the uboot environment stored on emmc.
Having said that, I have experienced cases where for some reason on some boxes the uboot environment gets reset to the default and multiboot does need to get re-enabled, but that is a rare occurrence, nothing I have ever seen happening on every boot.
-
29 minutes ago, masteripper said:
I assume that when you run a - whatever - distribution from if you stay on the microsd no charges to the underlying system is performed...am I wrong ?
Your assumption is incorrect. The 'multiboot' changes the uboot environment stored on the emmc, even if you are trying to run something on sd. The is the whole point of 'enabling multiboot' without the changes to the base uboot environment the board doesn't know how to boot from the sd card. Those changes to the base uboot environment are different across different distributions and therefore the requirement to restore back to a known base with the original android firmware.
Help needed with S905X3 Ninkbox N8 plus
in Amlogic CPU Boxes
Posted
Also, dtd files are kernel/kernel version specific,. You can't assume a dtb from a vendor kernel will work on a mainline kernel.