SteeMan

Igor, could you point me to a description and/or the fix for this issue? This is an issue that I am having with meson64 based TV boxes and it has also been reported by others in the TV Box club. I want to see if this fix addresses the issues we have been seeing - or if we have a different issue.

@Mohammad Shami Please read the two posts in the TV Box Club's FAQ forum

@andress187267If you think docker is essential for your use cases, we welcome your contributions to the armbian community to make that happen. That is what open source is all about. We certainly need many more volunteers to do all the work around here.

@zaqwsx12 Please read the FAQ post in the TV boxes FAQ forum: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Note that balbes150 no longer supports Amlogic CPUs. There are other posts in the TV box forums that describe building your own kernel. Please search the archives.

Moved thread to the TV box club forum for Amlogic boxes.

@lary I move your post to the appropriate forum. There are two items in the TV box club FAQ and you should read both of them. The first is about status of support of TV boxes and the second talks about how to install on Amlogic boxes like you apparently have.

@Slackstick The image name you have quoted doesn't resemble any armbian build I am aware of. Where did you find this image you are trying to install? If it isn't armbian based then this is not the correct place to be asking your question.

Moved to a new thread as this was posted in a thread dealing with a different box.

It wasn't dropped, it was never added. The legacy 3.x kernels are the vendor supplied kernels which take a base kernel and add a bunch of customizations on top (some with and some without source code). The mainline kernels are the kernels that have the hardware support integrated into the mainline code base. Because the vendors don't provide much if any support for their hardware/software, they generally don't care about getting their proprietary code/features into the mainline kernel tree. Thus while moving from the vendor kernel to the mainline kernel you end up loosing functionality. I wouldn't personally use a legacy vendor kernel. There is no support, no bug fixes, no security fixes.

I am closing this thread. With balbes no longer working on a unified single kernel/build for all CPU architectures (rockchip, amlogic, allwinner) (especially with his no longer supporting amlogic cpus), further questions or issues would better be created in the cpu family specific subforums: Rockchip CPU Boxes, Amlogic CPU Boxes, or Allwinner CPU Boxes.

Moved your post to the Rockchip CPU Box forum. I do not work with rockchip based boxes myself, but there are a few people who do in this forum that may be able to provide you some guidance. The RK3188 is an older 32bit cpu. A lot of the effort recently around here is support for more recent 64 bit based cpus. This post was originally posted to the mega thread: https://forum.armbian.com/topic/14232-single-armbian-image-for-rk-aml-aw-armhf-armv7

Moved your post to the Rockchip CPU Box forum. I do not work with rockchip based boxes myself, but there are a few people who do in this forum that may be able to provide you some guidance. The RK3188 is an older 32bit cpu. A lot of the effort recently around here is support for more recent 64 bit based cpus. Having said that, I will point for reference to: https://forum.armbian.com/topic/14232-single-armbian-image-for-rk-aml-aw-armhf-armv7/page/6/?tab=comments#comment-117335 which appears to be the latest builds referencing the 3188. I am not aware of general instructions for using the balbes 32bit builds, but I haven't read the whole thread regarding them (https://forum.armbian.com/topic/14232-single-armbian-image-for-rk-aml-aw-armhf-armv7)

@Youness Bouamal welcome to the Armbian forums. First off I want to point you to the following TV Box FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first As you will see in that FAQ, wifi is not something that generally works on the TV boxes. And even if it does work, the cheap built in antennas don't provide good coverage. To get better wifi support you likely would need the more expensive TV boxes with external antennas. So while you might be able to get something to work, most likely using external usb wifi adapters, you probably would be better off buying a purpose built device that would likely cost less. If your goal is to just experiment and see if it can be done, we would love to hear back on your findings for your specific box. . Finally you mention X96Q box. From what I know the X96Q uses the Allwinner H313 cpu not the Amlogic S905W. And those Allwinner chips (H313 and H616) are new chips that don't yet have armbian support, so that would be a non-starter. But the manufactuers are all the time reusing box names for different hardware, so you certainly could have something labeled X96Q that contains an amlogic cpu. (That is one of the problems supporting TV boxes with armbian is that two identical looking boxes can have completely different components).

@as400 I was going to point you to read the TV Box club FAQ entry on overall status (https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first) Honestly you have more working than most users as wifi and ir are not something I would expect to be working for you. Since you are running Amlogic boxes, you should be aware that balbes150 stopped his support of that CPU back in October. While he is still involved in Armbian he has mostly gotten out of supporting end users of the TV boxes. You were actually fortunate to get a response from him directly as that is rare these days in the TV box forums. I however have a question for you. Your original post didn't mention which boxes you have running. If you could take the time, it would be appreciated if you could post your results for others. I have recently started gathering information of working boxes in a consistent standardized format: https://forum.armbian.com/topic/16814-template-to-report-a-working-tv-box

To answer your questions, please go to the TV Boxes FAQ and read both: Status of Armbian on TV Boxes - Please Read First Installation Instructions for TV Boxes with Amlogic CPUs

These instructions are for balbes150's builds supporting Amlogic CPUs for TV Boxes. Note1: As of October 14th, 2020 balbes150 is no longer supporting Amlogic CPUs (and no one else has yet stepped up to continue his efforts). Therefore if you install using these builds/instructions you will have a 5.9.0 linux kernel with no upgrade path for the kernel. You will get updates from your chosen distribution (debian or ubuntu) just no kernel updates, unless someone else in the community picks up the ball and begins building/maintaining amlogic kernels for TV Boxes. 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. Download link: https://users.armbian.com/balbes150/arm-64/ or https://yadi.sk/d/_rQgn_FosYuW0g/20.10/20201014 In the downloads directory you will find builds for debian (buster and bullseye) and ubuntu (bionic and focal), with both desktop and non-desktop versions. Once you download your chosen build (for example https://users.armbian.com/balbes150/arm-64/Armbian_20.10_Arm-64_focal_current_5.9.0.img.xz - ubuntu focal non-desktop build), you need to burn the image to an SD card. Generally balenaEtcher is recommended as it does a verification of the burn. Also be sure to use high quality SD cards. Once you have the SD card with your chosen build, then you need to edit the boot configuration file on the SD card. In the BOOT partition of the SD card there will be a file /boot/extlinux/extlinux.conf, that you need to edit. (In earlier builds this was done in the /boot/uEnv.txt file, so a lot of comments you may find in older threads talk about that file, but in later builds it was changed to the extlinux.conf file) Your extlinux.conf file should look like: LABEL Armbian LINUX /zImage INITRD /uInitrd # aml s9xxx #FDT /dtb/amlogic/meson-gxbb-p200.dtb FDT /dtb/amlogic/meson-gxl-s905w-tx3-mini.dtb #FDT /dtb/amlogic/meson-gxm-q200.dtb #FDT /dtb/amlogic/meson-g12a-x96-max.dtb #FDT /dtb/amlogic/meson-g12b-odroid-n2.dtb APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 Basically you need to have the correct dtb for your box and the correct boot command for your box, along with the top three environment variables set. *Everything* else needs to either be deleted or commented out. This is a common mistake where people uncomment out what they need, but leave other lines in the file not uncommented and thus they fail to boot. The extlinux.conf file above is directly from my TX3 mini box. Note that if you were using a different box than a TX3 mini, you would attempt to use different dtb files until you found the one that works the best for you boxes hardware (there are a bunch of dtb files in /boot/dtb/... to try depending on your cpu architecture and hardware). It is unlikely that there will be a matching dtb file for your TV box. The idea is to find the one that works best for your box. This may mean that you try booting with different dtb files until you fine one that works good enough for your needs. By searching the forums you will find information about what dtbs other users have found work best for different boxes. Next you need to copy the correct uboot for your box. This is needed for how these builds boot on amlogic boxes. There are three different u-boot files located in the /boot directory: u-boot-s905, u-boot-s905x-s912, u-boot-s905x2-s922 You need to copy (note copy not move) the u-boot file that matches your cpu to a new file named: u-boot.ext So for example with a TX3 mini box that has an s905w cpu you would copy u-boot-s905x-s912 to u-boot.ext Note that for x905[w,d,l], and other variants use u-boot-s905x-s912; for s905x3 use u-boot-s905x2-s922 Once you have your SD card prepared you need to enable multiboot on the box. There are different ways documented to do this, but the most common is the "toothpick" method. The "toothpick" method means to hold the reset button while applying power to the box. The reset button is often hidden and located at the back of the audio/video jack connector. By pressing that button with a toothpick or other such pointed device you can enable multiboot. What you need to do is have the box unpluged, have your prepared sd card inserted, then press and hold the button while inserting the power connector. Then after a bit of time you can release the button. (I don't know exactly how long you need to hold the button after power is applied, but if it doesn't work the first time try again holding for longer or shorter times). You should now be booting into armbian/linux. Note that the first boot takes longer as it is enlarging the root filesystem to utilize the entire SD card. After you are satisfied that your box is working correctly for your needs you can optionally copy the installation from the SD card to internal emmc storage (assuming your box has emmc). You do this by running the appropriate shell script in /root, which is either /root/install-aml-s905-emmc.sh for s905 cpus or /root/install-aml.sh for all others: s905[x,w,l,x2,x3],s912,s922. Note that it is recommended that you make a backup of emmc first (use the ddbr tool that should be installed on your sd card). Also be prepared if anything goes horribly wrong with your emmc install to reinstall the armbian firmware using the Amlogic USB Burning Tool to unbrick your device. It is generally easy to find original android firmwares on the internet and you can generally recover a bricked box using the Amlogic tool and an original firmware file.

Moved to correct forum

Please describe what steps you are performing. The log would indicate you are booting with dtb/amlogic/meson-g12b-odroid-n2.dtb, not the dtb you think you are.

@Joel Mercedes First I want to draw your attention to the following information so that your expectations are properly set: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Second, what build did you install and where did you download it from? I am not aware of a build for amlogic TV boxes that has kernel 5.9.7 in it.

Moved post into its own thread as this is not related to the thread it was originally posted in.

Moved post to the correct forum. If you want help, please provide information on what exactly you have tried, what build you are working with, what dtb's you have tried, what installation steps you are following, etc. Also please read the following post to set proper expectations: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

Adding a link to the following thread that talks about hardware differences on some newer? x96 mini models that require changes to the dtb: https://forum.armbian.com/topic/15665-new-x96mini-hardware-upgraded-but-no-emmc-found

@robertoenr FYI, the information in this thread: https://forum.armbian.com/topic/8728-s905w-boot-process is helpful in learning the boot process (see especially Jock's post). Jock maintains the builds for rk3228/rk3229 based TV boxes. His approach is more of a 'pure' armbian environment than the balbes approach of reusing the android boot loader, but his explanation of the process is good.

@robertoenr FYI. I just installed into emmc on my Tx3 mini and it boots fine using u-boot-s905x-s912 copied to u-boot.ext along with meson-s905w-tx3-mini.dtb

@robertoenr That wasn't at all clear from your posts that that was the case. So you have a working SD install, and when you run install-aml.sh to move that install to emmc, that is when you are seeing this issue?