SteeMan
-
Posts
1654 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by SteeMan
-
-
I believe the brand name of this box is: MXQ 4k which is a rk322x based box. Moving the post to the rockchip tv box forum
-
5 minutes ago, Raulin said:
Tengo una caja Tv Box, con esta placa queria saber si es posible instalar armbian...y si es asi como es el precedimiento de instalacion......gracias por su ayuda...
"I have a Tv Box, with this board I wanted to know if it is possible to install armbian ... and if this is how the installation procedure is ...... thanks for your help ..."
The armbian forums are in english. Please use google translate.
-
Use the "toothpick" method instead of trying the update app from android.
-
31 minutes ago, wperw said:
Hi, I've this one but thelabel say H616 4 + 32,.
The H616 version is also supported?
No, there is no current Armbian support for the H616 CPU variant. Work is being done, but the general guidance is that support for this may be a year or so in the future.
-
@drookie Welcome to the world of impossible to support tv boxes. As you mention the hardware of these two otherwise similarly labeled tv boxes is different. /The dtb file is what provides the mapping from the hardware to the linux kernel. So what you really need are two different dtb files for the two different boxes. But without the support of the tv box manufacturer providing the necessary information on their hardware it is very difficult to figure out the correct dtb for a box (let alone a hundred different boxes from different manufacturers all with slight differences in their hardware). There isn't really anyone currently involved in this project that has the skills/time/desire to work on this nearly impossible problem. This is why the TV Box FAQ item (https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first) says to set your expectations low. It sounds like you do have a mostly functioning box so consider yourself better than many. We could always use more contributors around here. If you have the skills and time, you could learn a lot by trying to research and update the dtb for your hardware and contribute back to the community your work.
-
If you want help (and both jock and I are here to help you), you do need to provide some more information. Things that would be helpful include:
1) What are you trying to accomplish? (people don't just change kernel config files and rebuild kernels for no reason)
- what changes do you want to make and why?
2) What experience do you have in building kernels? Have you built an x86 kernel before?
- knowing where you are starting from experience wise helps us give you the appropriate level of information
I started a year or so ago about where I think you are. My goal was to get more regular kernel updates following the linux mainline sources. I spent a couple of months reading a lot of threads in these forums about others who had done similar things and over time built up my knowledge so that I am now able to build mainline kernels for both my test and production boxes. (I just this morning updated one of my test boxes to the just release 5.12.0 kernel).
As jock mentioned above the overall process is more than just compiling and building a kernel image. You also need to understand the boot process so that your kernel is correctly invoked by the boot process and then you also need to understand enough about dtb files so the kernel knows how to interact with your hardware.
From some of my notes from last year here is a thread I found useful in my learning process:
-
@cuker Some of the amlogic u-boots that were in balbes150 builds come from the work of hexdump. (I don't know if balbes150 further enhanced them or not). Look at the following thread for hexdump's repositories and building instructions
; https://forum.armbian.com/topic/16753-chainloaded-uboot-images-for-amlogic
I have rebuilt some of these from source to see if I could, as I don't generally like using binary code that I don't know the origin of.
-
I would recommend starting with mainline kernel sources - they work well on s905x devices (that is what I am running on all my devices). You could also look at the standard armbian meson64 kernel (mainline plus some patches) in the armbian/build tree.
-
Your post has nothing to do with the topics of this site - Armbian on TV Boxes. We don't have anything to do with rooting andoird in these forums.
-
@jacinto69 Please read the two TV Box Club FAQ items: 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
.
Then after being sure you are following the correct installation steps, please provide more details on your installation, like what dtb files you have tried, what u-boot.ext file you are using, etc.
-
I moved the original post to a new thread as this doesn't appear related to the thread it was originally posted in.
-
1 hour ago, Jackchen said:
Hello, I am currently using your armbian 3.10.108 image, but I want to build Retroarch in it, and found that the Mali GPU driver is missing, I want to ask, is there any way to solve it
Please read the FAQ entry: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
There are a couple of comments in that post that are relevant to your question. 1) balbes is no longer working on amlogic cpus, 2) the current state of the TV box code (espeucally for amlogic) is suitible for server use only, don't expect much graphical support to be working. Also in a comment just a few posts ago, balbes expressed his opinion that he doesn't work with proprietary binary closed source code (like the legacy mali drivers). The open source drivers are only becoming available on current kernels, so there isn't anything except closed source support for your 3.10 ancient kernel.
-
Moved to new topic. This question has nothing to do with kernel recompilation which was the topic this was originally posted in.
-
@vice I suggest you repost your question in the thread https://forum.armbian.com/topic/12656-csc-armbian-for-rk322x-tv-boxes
as @jock is very good at helping, but he likes to focus his efforts on posts in that thread. Something else that would be helpful is to provide more information about what build you are attempting to use and where you downloaded it from.
-
-
I split this out into its own topic. Even though the information is all derived from the thread "Armbian for TV box rk3328" I think it makes it easier from a forum search perspective if someone is looking for rk3318 information in a search to have a separate thread.
-
The short answer is you can't. The boot process for armbian and libreelec uses the native uboot installed on emmc to start the boot process. So if your emmc isn't working you can't boot these from an sd card. Theoretically it is possible if you have a complete proper uboot installed on the sd card, but such a thing doesn't exist around here as that hasn't been the approach to how we have supported amlogic based tv boxes.
Are you sure your emmc is broken? Have you tried to restore your android firmware to emmc?
-
There are many posts in the forums talking about this same issue. Please search the forums for an answer, If you still are not able to find a solution, then please post more information about what you have tried including what you mean by 'I have already found a way' in your last post.
-
On 4/8/2021 at 3:52 PM, Daniel Cagarrinho said:
I have successfully connected wifi, but wen I reboot the box the os cannot start properly!!! I have followed the instructions from this topic
I have been focused on the wifi changes that I perhaps have overlooked something else. Do you have armbian installed on emmc? The reason I ask is that I have multiple boxes where if armbian is installed on emmc, they sometimes will not reboot. The work around is to install an sd card (with a bootable version of armbian installed, including the correct dtb configured), boot once from the sd card and then remove the sd card and the system will then boot normally from emmc.
-
@Thang First off since you are working with coreelec you will need to restore the box to a clean android firmware before attempting to work with the armbian builds that are out there. The coreelec install changes things in incompatible ways to how the armbian builds expect the system to be in order to work correctly.
I have two of these boxes (don't know if they are the exact same hardware as you have reported as I haven't opened them up recently)
One of these boxes I am running as a production web server and the other I use for testing.
I am currently using the meson-g12a-sei510.dtb but have in the past used the meson-g12a-x96-max-rmii.dtb
But it seems that on newer kernels the meson-g12a-x96-max-rmii.dtb isn't working anymore.
Note that these boxes only have 100mbit ethernet and therefore the regular meson-g12a-x96-max.dtb won't work for networking as it is for 1gbit ethernet, you need meson-g12a-x96-max-rmii.dtb or meson-g12a-sei510.dtb that I am currently using.
You mention a couple of things in your original post that I want to explain to you, specifically that the formats of the dtb files between coreelec and armbian are different. That is because coreelec uses legacy kernels and armbian uses mainline kernels. Legacy kernels are kernels where the cpu vendor/board designer added support for the cpu and board to a fork of the linux kernel. Mainline kernels are where the support for the cpu has been officially integrated into the kernel source tree and supported by the official linux kernel. Those two processes have led to different ways of the code being structured and thus make the dtbs incompatible between the two code lines.
-
Also moved this post to the correct forum as this related to TV Boxes not a supported Armbian board.
-
First please read the following FAQ item in the TV Box FAQ: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
In that FAQ post you will see that no one is any longer supporting amlogic s9xx TV boxes. So you have the following hurdles: TV boxes are not supported by Armbian. The developer (bables150) who was working on these boxes in his community fork no longer is (but he never supported the x905x3 even when he was working on amlogic), and this is such a low priority type of item, that it wouldn't likely get attential anyway (see the setting expectations part of the FAQ item).
Since you posted this same question three times in the forums, I will be deleting the duplicate posts, leaving this one.
-
Moved post to the correct forum
-
@Sevillano I'm not quite sure what steps/instructions you are following. But start by reading the two TV Box FAQ posts: 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
There aren't steps that require you to compile the entire system on a virtual machine. So I am assuming you are trying to perform a regular build of armbian, but armbian doesn't support TV boxes. That is why this forum exists and there are the forked builds that attempt to get a working environment on amlogic based boxes.
You will most likely need to find an original android firmware and restore your emmc to a good working android before moving forward.
Impossible to load aml_autoscript.zip in Android 6.0.1.
in Amlogic CPU Boxes
Posted
Moved to the appropriate forum.
Please read the following FAQ entries:
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