balbes150

1. In current versions of LE (at startup LE from the media) in the shutdown menu, it is possible to choose to reload the system, which is located in the internal memory ("Rebot from NAND flash\Android"). Ie if you set Armbian in eMMC and when you run the LE from external media, you can choose a LE to restart the system , which is in the eMMC. 2. What version of LE are you using ? In image Stretch not use a test repository.

I apologize for the delay in response. Before upgrading, I recommend doing a full backup (utility ddbr). 1. Then you can try updating via apt. If the system fails to start, you will have to perform a clean installation. 2. I haven't tested the packs mount in x86. The start order of systems in the presence of external media. If you have a bootable system on a USB , it runs first USB -> if USB is no system (or no USB), checks the system on the SD and if there is, it runs SD -> if there is no system on the SD card , run system from eMMC.

You can use unlimited number of systems on external media. When you connect together several media, always run the same system in order of priority - USB -> SD. To run from SD card, you need to be sure to turn the system off USB.

1. Start Armbian from SD card. 2. Open a terminal and run the command "sudo ddbr", then follow the prompts. Select the mode for creating a compressed backup. Ddbr utility creates a full backup (on the SD card in the directory /ddbr) of the system that you are now in the internal memory of the TV box. 3. After that you can write on the USB flash drive system Libreelec and connect to the TV box. Notice - to activate the multi-boot is not necessary. Libreelec should automatically start up with USB stick. Check the LE (all devices on your TV box) and if everything is working correctly, you can run the installation LE in the inside memory.

1. If you use advanced features KODI, I recommend using Libreelec. You can install one of these systems (LE or Armbian) to eMMC , and the second to run from external media. If you have a model VIM2, you can install in eMMC universal system MultiOS_3in1 (Android+LibreELEC+Armbian or any other variant of Linux). 2. To use a USB stick with KODI you can try to mount it via SSH. Look for information about using the libraries MALI. I have no specific information on this issue. As far as I know, KODI uses x11 in a limited way, so no x11 is not necessary. You can try to view the source code for Amlogic on the subject of how they use gstreamer to work with the framebuffer and libamcodec.

I already replied earlier to this question. At the time of assembling the images in the standard repositories Jessi didn't have the right versions of packages. Now there have been many changes in the repositories (test disabled) and now I am collecting images of Debian using the official branches Stretch. By the way, to all , I will repeat for the, at the moment (when I checked last time) in the thread Jessi broken packages, which are responsible for mounting a label, so when you try to upgrade from Jessi you risk to not run from external media system. Video hardware acceleration is only in KODI. Therefore, any other program (including browsers) use softbuy processing, which need all the resources of the processor (the more powerful the processor, the better the video quality). If you want to get a full-screen video in the browser - it can be assembled using the library libMali.

All packages that begin at aml-* https://yadi.sk/d/09xzoZ3Y3PSYBb To add user to all groups that are required to run KODI and its libraries. Probably need to install and configure additional packages that have default images of the desktop (I have not studied for a full list of packages).

sudo modprobe wifi_dummy or sudo modprobe dhd ******************************************* su - (enter the root password) modprobe wifi_dummy or su - (enter the root password) modprobe dhd

Wrapped in a warm hat is one of my TV boxes (Tronsmart Vega S96) . Run test for a couple of hours. Here is the result at the end of the second hour. Such a conclusion in the console, no change for end hours, so stopped the test.

I'll look and I'll check with the pillow ...

The images with the kernel 4.9.40 is only for those TV boxes, where set a new u-boot (Nougat-Ubuntu). Today, this model Khadas VIM and VIM2.

I added the info in the first post, look at it, there is an answer to your question.

Probably possible to port OpenWRT. But who will do this ? I know that the user Tasinofan is working to create a option system that can turn TV box into the router.

I took this direction at the request of one user from the forum Khadas (the audio). It seemed to me that you can try to combine the positive of both projects and benefit for both directions. I know of many users who are "obsessed" with high-quality sound and TV boxes can be quite simple and not expensive "means to play".

Maybe someone interested in the direction of Volumio platform Amlogic S9xxx (S905 S905X S912). At the same time, savvy users can tell the direction, to fix the problem with sound through HDMI in this way. https://volumio.org/forum/volumio-for-box-amlogic-s905-s905x-s912-t8028.html

The pillow I not used. When testing I covered the board of a plastic bag (there were no ventilation).

Turned off the fan. Launched this version of the script. Waited 30 minutes, the temperature rose slowly during this time to 80 degrees. In all lines the result is around 3.7-3.8 . How long should I wait ? 1512 @ 80: execution time (avg/stddev): 3.8009/0.01 1512 @ 80: execution time (avg/stddev): 3.8009/0.01 1512 @ 80: execution time (avg/stddev): 3.8032/0.01 1512 @ 79: execution time (avg/stddev): 3.8145/0.01 1512 @ 79: execution time (avg/stddev): 3.7967/0.01 1512 @ 80: execution time (avg/stddev): 3.8084/0.01 1512 @ 79: execution time (avg/stddev): 3.7900/0.01 1512 @ 80: execution time (avg/stddev): 3.8060/0.01 1512 @ 80: execution time (avg/stddev): 3.8063/0.01 1512 @ 80: execution time (avg/stddev): 3.8029/0.01 1512 @ 80: execution time (avg/stddev): 3.8110/0.01 1512 @ 80: execution time (avg/stddev): 3.8076/0.01 1512 @ 80: execution time (avg/stddev): 3.7976/0.01 1512 @ 79: execution time (avg/stddev): 3.8038/0.01 1512 @ 80: execution time (avg/stddev): 3.7911/0.01 1512 @ 80: execution time (avg/stddev): 3.8022/0.01 1512 @ 79: execution time (avg/stddev): 3.7961/0.01 1512 @ 79: execution time (avg/stddev): 3.8046/0.00 1512 @ 80: execution time (avg/stddev): 3.8247/0.01 1512 @ 80: execution time (avg/stddev): 3.8106/0.01 1512 @ 80: execution time (avg/stddev): 3.7978/0.00 1512 @ 80: execution time (avg/stddev): 3.8035/0.01

Yes, I have installed the cooling system (heatsink + fan) which at maximum load when compiling to maintain the temperature above 60 Degrees. I didn't do any special settings. Copied code into the script and ran. For reference, the system itself Armbian installed in eMMC.

Khadas VIM2 Basic (S912) Armbian Ubuntu Xenial root@amlogic:~# ./1.sh -e 100: execution time (avg/stddev): 43.1555/0.00 -e 250: execution time (avg/stddev): 38.6359/0.00 -e 500: execution time (avg/stddev): 36.7715/0.00 -e 667: execution time (avg/stddev): 36.7342/0.00 -e 1000: execution time (avg/stddev): 36.6605/0.00 -e 1200: execution time (avg/stddev): 36.6654/0.00 -e 1512: execution time (avg/stddev): 25.8857/0.00 -e 100: execution time (avg/stddev): 12.2133/0.01 -e 250: execution time (avg/stddev): 11.1908/0.00 -e 500: execution time (avg/stddev): 10.4857/0.00 -e 667: execution time (avg/stddev): 10.0522/0.00 -e 1000: execution time (avg/stddev): 9.1695/0.00 -e 1200: execution time (avg/stddev): 8.5308/0.00 -e 1512: execution time (avg/stddev): 7.5821/0.00 -e 100: execution time (avg/stddev): 8.8878/0.01 -e 250: execution time (avg/stddev): 7.9328/0.01 -e 500: execution time (avg/stddev): 6.6367/0.01 -e 667: execution time (avg/stddev): 5.8735/0.00 -e 1000: execution time (avg/stddev): 4.7245/0.01 -e 1200: execution time (avg/stddev): 4.1828/0.01 -e 1512: execution time (avg/stddev): 3.7980/0.01

So for this hardware has no support (source and firmware).

When writing a message at the top of the window there are buttons, third from the right in the "eye" is the creation of a spoiler. modprobe dhd or modprobe wifi_dummy This information was discussed many times in this thread and added to the first page of the topic. I have not tested X92, don't know how it will behave. I can write about those models that were compared. Khadas VIM2 (S912) and Khadas VIM (S905X). The system starts with the same USB stick, the only difference in the different dtb files. The difference in the desktop is quite noticeable (for me). Test video 720p (in the box using mpd without changing the size of the video) on S905X has a noticeable micro-frize. At S912, the video goes smoothly. The overall performance of same better. A prerequisite. The presence of a good cooling system (radiator + fan + proper case). All TV boxes, regardless of processor type, suffer from one problem - poor cooling. For Linux this is a very important point, because it uses all CPU power. I think that even on the TV box, which you have now, not much to improve Linux, if you make the right cooling.

In my models of TV boxes wired network works on DHCP. Perhaps you are not correct dtb file (there are options for the network card 100Mb, or 1Gb). The module loaded for the Wifi ?

rus eng Spent the time. I took from website the latest image of Ubuntu server. Recorded on the medium and started on VIM (s905x). I looked on the DHCP server which address is assigned to the TV box. With the PC running the SSH session connecting to the TV box. When connecting the system asked for the initial password immediately after the opening session was required to enter the current password. We need to introduce new (especially write the password option, which usually enter tests, if You yourself can not come up with a working version password for root). Here is a variant of password "1q2w3e4r" , to the system request enter it again. be prompted to enter a name for the new user (enter the "user") , after a couple of seconds, receive a request for a password for the created user, enter "1" and repeat the password. For other requests, the parameters are a new user, just pass Enter (5 times) and final confirmation to go on the restart. So, if you do it right, no Ctll+C is not required. I don't believe You are so cunning equipment that it does not allow to correctly perform such a trivial sequence of actions. As long as You follow the basic instructions for initial configuration of Armbian, I see no reason to respond to Your questions.

Scripts s905_autoscript only work with u-boot. To ensure that work team hdmi.sh - the system must be properly configured and running, it is a system service. Without a full system startup it doesn't work. Next week I'll try to check the work of BT on Telos.

As activated universal multiboot ? 1. Read carefully, that says system. It's not looping, and the requirement to use the correct password for user "root" (which does not pass the security requirements). Until then, until you enter the correct password, the system will not continue the setup. 2. Any partitions "system" is not used in Armbian. If everything was done correctly in the initial settings, subsequent runs of the system twice to activate the monitor and the image itself is normalized for correct start. This means that the system is not configured and not configured properly passwords and logins. Council. If you want to achieve something, learn to study the documentation. For Armbian there are detailed instructions on how and what to perform. https://docs.armbian.com/ KODI will only work in images with kernel 3.14.29.