balbes150

The sound HDMI works in the core 4.20. Installation scripts are designed to run from the SD card. To run the installation from USB, you need to edit the scripts (change the name mmcblk1 to mmcblk0).

These DTB appeared in the images of the patch from Libreelec. But nobody checked them and there are no guarantees that they are working at all.

New image 5.73 kernel 4.4 and 5.0 20190131

still can be used armbianmonitor -m

Check this option and write the result. https://yadi.sk/d/6dGnDzxI9Zc6Dg

No need to copy and rename anything. Write the image to two media SD card and USB flash drive. Then connect both media at the same time to the TV box and turn on. It is recommended to check all variants of DTB (you only need to edit the file " extlinux.conf " on SD card).

Show the output of the fw_printenv command with kernel 3.14 running from this box.

This driver uses private binary blobs from ARM. LIMA is completely open data. I prefer to use the open version. What the dtb has been used and what exactly the version of the image. The 3.14 kernel is very outdated and no longer supported, so I don't use it anymore. LIMA drivers are in the image. Only the correct version of MESA with LIMA support is missing (and may need to build programs using LIMA \ MESA-LIMA). Write in detail all the steps that you did. Without this, there is no point in making assumptions. Very useful information. Thanks. Do you have a UART console on it ? The problem is not with the kernel, but with your hardware (the manufacturer's support for it). The manufacturer of your model doesn't want to do anything for it to work with the new kernel. You have a model with a network card 100Mb, it needs dtb p201 S11 Hardware: CPU: Amlogic S905 Quad-core A53 2.0GHz 64bits GPU: Penta(5) core Mali 450 Android Version: 5.1 RAM: 1G ROM: 8G WiFi: Built in 2.4G WiFi Ethernet: 10/100 mbps RJ45

Of different versions of the kernel and image version Armbian has its own rules adjusted to the correct DTB. Refer to the appropriate topics.

As long as you do not provide a log to start a new kernel from the UART console, no one will help you.

I figured out the FFMPEG build. Details in this post. Testing the decoder seems to work correctly (there is a noticeable difference with the soft mode), but so far there is an incomprehensible situation with the use of FFPLAY.

New Ubuntu Server image 5.73 for S812 with kernel 5.0-rc4. HDMI does not work. Control via UART or SSH. I checked on Tronsmart MXIII Plus running from SD card and USB flash drive. Installation in eMMC was not checked.

New version 5.73. 1. A separate section for images with the s905 LIMA driver has been added to the catalog. Notice is images in which there is only the kernel driver LIMA, HW support for DE until they do not. For HW you need to collect a special version of MESA-LIMA. I tried to build it, but I have a bug at the end of the build. May be there is a wish to collect the desired version of MESA-LIMA and help the process of the emergence HW to s905 ? 2. In the usual directory S905 Assembly for without driver LIMA. 3. I built an FFMPEG package with support for decoding using HW. To check, you can download the package and install it in the system with the command "dpkg". When checking the work I was able to run FFMPEG command decode test video. HW ffmpeg -c:v h264_v4l2m2m -i Test.mkv -f null /dev/null not HW ffmpeg -c:v h264 -i Test.mkv -f null /dev/null When you start to S905 , when using the decoder with HW h264 decoding speed is equal to 11.9 , without using HW decoding speed is equal to 4.3. When tested on S912-with HW speed 12 , without HW speed 7.9. I tried running the video using ffplay. HW ffplay -vcodec h264_v4l2m2m Test.mkv not HW ffplay -vcodec h264 Test.mkv It shows the test video, the sound is correct, but the video is played in the braked mode (as if the deceleration is enabled). Maybe there's something I'm doing wrong when building or testing. I would appreciate it if someone could find a reason why the video is stalled. https://yadi.sk/d/9igaopSIabKsjw

run SD + USB ?

Don't waste time on tests. eMMC is much faster than USB on all current s9xx, they use USB 2.0. Now begin to emerge S905X2 with USB 3.0 , but they have no support in Armbian. When you first start the installation in eMMC (when eMMC is Android firmware), there are no partitions yet and what you see in GPARTD is normal. For eMMC installation, it is important that eMMC (mmcblk) is visible (partitions are not required, they will be created by the installation system). Only after the initial installation of Armbian in eMMC will appear sections that can see GPARTED. The easiest way to find out if you can install to eMMC or not. Run the "ddbr" utility, if it can create a full backup of eMMC, then the installation in eMMC will work (but it does not guarantee 100% system health from eMMC).

Using " dd " to copy a system is a bad decision. This utility is intended for other purposes, but many began to use it incorrectly. And then get problems from such actions. You've seen somewhere, what would the system from the Live CD transferred to HDD utility "dd" ? To do this, use a special installation procedure that uses special steps to create a file system, specially designed for this utilities.

What for?

Judging by the message, it is information on emergence of new packages. This is not an update Armbian. You can get more information about the packages that will be updated if you run the "apt" command with the necessary options.

I am interested in decoding for S9xxx. You can write details, what kernel do you use, what kernel config do you use ? What are the FFMPEG source code and build option ?

@martos Did you manage to build your version of FFMPEG using v4l-m2m ?

Are you setting up the DTB correctly in the new versions ? I didn't understand the question. Write more about the problem. In new versions, the kernel has been updated and you need to check whether it will work on your hardware or not. Run from external media and see how it will work.

You need to add your DTS to the kernel sources and build a new DTB using the Armbian kernel sources.

Such things are almost impossible to evaluate remotely, there can be a lot of different reasons (hardware and software).

You have the same problems as the MX10. But MVR9 these problems there.

Uploaded to the site fixed version 5.72 for S905. Now in the kernel 4.20 has gxbb (S905) work sound HDMI. Additionally fixed DTB from Tronsmart Vega S95 (Pro Meta Telos). Now these files work. To the right of the button "Raw" View" etc