SteeMan

@vcmsptx with the new builds (i.e. the 6.0.x kernels) try changing the extlinux.conf file to use: LINUX /uImage I noticed an issue that the u-boot currently packaged (u-boot-s905x2-s922) doesn't boot the Image binary but will boot the uImage kernal binary. At least this is the case on my s905x2 based box. If you can confirm this same behavior on your box, that would be helpful.

@vcmsptx What build and instructions are you using?

The first place to start is with the following two FAQ posts: 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

The first place to start is with the following two FAQ posts: 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

Please read the following FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first (Short answer is: don't expect wifi to work on TV Boxes)

As an unsupported board, the 4C+ only exists on the Community Supported boards page: https://github.com/armbian/community

@Cliff There is no official Armbian software for this box as this is not a supported box by Armbian. If I may ask, where did you get this 'official' armbian from? The only reason I ask, is if there is something that leads people to believe something is supported when it isn't, that is an area that we can improve docs/website, etc to avoid future confusion.

Correct. This if from the Inovato website: IMPORTANT NOTE: If you have any questions or problems with this process, by all means use the Armbian Forums to search for information, but please DO NOT ask questions if you can't find your answer. They don't support the Quadra firmware: We do. So please use the Support category on this forum.

@Titus The software you have installed is not from Armbian. That developer has a fork of Armbian but does not participate in Armbian development nor these forums. In fact they use the Armbian name without permission. You will need to contact the developer who provided this software to you for your questions/support.

Please provide more information, I can't guess as to what you are doing/seeing. That is what is supposed to happen. Pressing the reset button during boot will cause the board to load the multiboot setup from an sd card. This is something you should only need to do once. You mention usb, do you mean sd card? What happens after you release the reset button?

Read the TV Box FAQ items on this forum: 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

@wapins The build you are using is a fork of Armbian. That developer has no association with armbian and does not interact with armbian developers or these forums. They use the armbian name without permission. You need to post your question in their forums as we can't help you here.

Lets start by explaining what build you are using? What installation instructions are you following? What dtb are you trying?

You don't provide any specific details on what you have installed. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

After a fix committed this past week, these builds now work on all the amlogic based boxes I have: TX3mini (s905w) X96mini (s905w) H96MaxX2 (s905x2) TX3 (s905x3)

@jiapei100 I think you are confusing cpu support and board support. While the rk3229 cpu has good support in modern linux kernels (good but not perfect yet) there is no support for your specific board. It is very different work to support the cpu than support a specific board using that cpu. It can take months of development effort to get a board to work well after the kernel supports the cpu. Board support entails support for all the other hardware on the board (memory chips, networking/wifi and whatever else may be on the board). That involves both making sure that the proper drivers are available for the hardware (often since there is generally no help from the board manufacturer, it is a guessing game to reverse engineer the hardware and try to find source code for the hardware componentes) and that the dtb file is created for that specific hardware. The dtb is the mapping between the hardware and the linux kernel. Generally to work well you will need a dtb specific to your board. And then finally all of this work also needs to be done with the u-boot code to again get the hardware mapped correctly so the device can boot. As jock stated you should read the armbian development documentation to understand what armbian is. For example your final question about which config file to use, doesn't make sense if you understand the armbian build system. 'current', 'edge' and 'legacy' are labels for specific kernel versions - legacy generally is the original 4.x kernel released by the manufacturer, current is the current stable version (i.e. 5.15), and edge is the bleeding edge development kernel (i.e 6.x).

Why are you expecting it to work? Armbian doesn't support TV Boxes. Please read the FAQ post: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first/ While there has been some effort by the community to support amlogic cpus that effort recently has only been toward the newer 64 bit s9xx series. No efforts recently that I am aware of to work on the old 32bit s8xx series.

What are you trying to accomplish? Are you looking for help porting Armbian to support this device? I ask because TV Boxes are not supported by Armbian (see https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first) and the RK3588 cpu is a very new chip that is only partially working on mainline linux currently. While there are people working on base support for the CPU, the significant additional work to support a specific box (with all its specific hardware) would still need to be done.

I'll start with a basic question. What are you trying to accomplish? Looking at the link you provided, you are dealing with a device that Armbian does not support (and I doubt anyone around Armbian has any knowledge of this particular device). You mention in your first post linux 6.0. So I therefore assume you are looking to add support to linux 6.0 and Armbian for this device??? If that is the case, I would first ask do you have the skills and experience to undertake such a task? Adding support for a new device into the mainstream kernel is a very difficult task, that often takes years of effort to get most of the features working (for someone experienced doing such tasks). As for this particular respeaker 2.0 sbc, what are your plans for using it? It would appear to be a specialized device for audio applications. Which would lead me to believe that there are specific components on this sbc that will need proper driver support in the mainline kernel as well. Which would likely make the task even more difficult to get these specialized features working on mainline. As a general rule I would say that usually for a new device the process is to first become familiar with the manufacturer provided legacy linux code base (i.e. be able to build the legacy code from source and start building an understanding of what specialized components the sbc has that may need to be supported in mainline). Then generally the next step would be to bring that legacy code base into the Armbian build framework to get it working there. Then start working on getting basic functionality working on mainline (by basic I mean things like getting the board to boot (building a mainline uboot and kernel that can boot the device)). Once you get the device to boot on mainline, then you start working on getting each feature working, hdmi, networking, usb, etc. Then finally getting any device specific features ported/working. In looking at the respeaker 2.0 legacy source code download, it looks like the legacy code is linux 4.4 base. There will be a significant effort necessary to bring a seven year old code base up to mainline. All this is easier if you have the help of the manufacturer, but that rarely is the case.

Armbian now has a community supported build target for amlogic TV Boxes (aml-s9xx-box). You can now build your own builds directly with the Armbian build system. This is now an opportunity for members of the community to move the support for amlogic TV boxes forward within the Armbian framework. If you are not familiar with the Armbian build system check out the Armbian developer documentation. If you have idea on how you would like to see things evolve/change please use this forum to share your thoughts and ideas and submit PRs for any code changes you would like to see. I am currently testing this code against the four different amlogic based boxes I own, but would appreciate others testing as well. Once I have completed my testing, I will be updating the FAQ amlogic install instructions with this information.

@bobjones58 Why does hardware feature XY work in old kernel but not in more recent one? - https://docs.armbian.com/User-Guide_FAQ

My guess would be "Chrome OS", or the linux kernel used for a chrome os install

@andersonpersan I am answering your other question that you had posted in a different thread here. First I would point out that your board says MX3mini and the board date is 2021. That is years newer than other TX3 mini boards I have. I suspect (as is common for tv box manufacturers) that this is really a completely different board but put in a TX3 mini case. This is likely due to the covid related chip shortages and they used whatever chips they could find to produce these boards. Therefore it is likely there isn't going to be any supported dtbs for your board. Since the cpu chip may be a amlogic s905w (although there are cases reported in the rockchip tv box forum where the manufacturers are faking the markings on the chips as well - cases where the chips say amlogic but are really rockchip or vice versa), I would recommend trying all the meson-gxl-* dtb files, to see if any are a good match for your hardware.

I had issues with an older intstall in this area and it was fixed by installing the latest /etc/default/armbian-motd file. I would compare your armbian-motd to the current version (https://github.com/armbian/build/pull/4096/commits/4767a1220ca3b836e15aa3c4bf034c8ef4a350c3)

@Byzor Check out this post: https://forum.armbian.com/topic/23632-mxq-max-4gb-32gb/?do=findComment&comment=147427 It has instructions on how to reset the environment after a coreelec install. I would always recommend reflashing original firmware as the best option, but when that isn't possible, this should work.