balbes150

New version 5.71 with kernel 5.0.0-rc2. Works in SERVER mode (text console). Until not start X11, need to understand. Works USB, LAN on both models MVR9 (1000Mb LAN) MX10 (100Mb LAN).

Starting from version 5.71 , you don't need to change anything in the image after recording to run on MX10. All settings and the DTB file are already there. I opened the case of my MX10. It is the chip SSV6051. Perhaps in other options can be used another version of. Or people run the firmware (system) from MX10 on other models, such as the A5X max, which differ only in the WiFi chip.

Not mounted root. Perhaps any problem with eMMC or wrong DTB.

https://yadi.sk/d/3dNcIyJC_Pet6A Only the reason is not in the core. By the way, with the kernel 4.4.154 by my tests, the system works faster with video. Perhaps because it uses sources from LE (where working with video is better optimized).

Write in detail what you did, what settings you used, what image was used, what is happening now.

I read that there are programs for RK under Windows that allow you to immediately pull out all the firmware from eMMC and disassemble it into components. If you can pull the DTB off the MX10, share it, I want to learn it. I haven't opened the case for my MX10 yet, but I've seen internet that this model uses ssv6051. The module and firmware I have in the image, but need the correct settings for the dtb.

Have you implemented these guidelines ? There can be no identical label. The installation script specifically changes the eMMC label and uses its eMMC value in the settings. Using UUID is a bad solution that is often used by those who do not want to properly design the installation system.

Good news Update version NEXT kernel 5.0.0-rc2 20190118. Khadas VIM1 has WiFi And BT without any patches. Perhaps some of the other models Wi-Fi will work.

Tell me, do you create problems on purpose ? I wrote you what you need to do on TV box, where you have already created a problem. And only after you find the right solution for the spoiled TV box, you can start experimenting with others. What DTB did you use on the second TV box ? Show the full contents of the "uEnv.ini " and " extlinux.config" after you have edited them.

The new version 5.71 20190118. Updated kernel to 4.20.2.

If Armbian starts and even shows you the login window-Your TV box is easy to restore. Write the image to the Sd card. Specify in "/extlinux/extlinux.conf" which dtb to use. I recommend starting with the file for Khadas VIM2. Uncomment the line with its instructions and delete (or comment out) the line from Khades VIM1. The result of the launch of write here. And do not rush to do something without advice.

MVR9 -> rk3328-box-trn9.dtb MX10 -> rk3328-mx10.dtb Just change the comment on the desired line:) by the way, MVR9 works with the file for MX10 (but no LAN Wifi BT). On the contrary-does not work, because MVR9 uses the best iron (similar to Renegade). Perhaps the dtb from MVR9 will also work on Renegade https://github.com/150balbes/Build-Armbian/blob/master/packages/bsp/rk3328-tv/extlinux.conf

So far it is only a guess and there are no files.

1. The structure that gparted shows is correct. The installation script is specially written so that it is as safe as possible to put the system in the eMMC. It keeps all the important data structure of the standard firmware in eMMC (u-boot env recovery boot etc). This allows you to use regular tools to restore native Android firmware in any TV box at any time. 2. When you renamed the file " s912-u-boot.img", you took the risk (I warned about this earlier in this topic) of replacing the regular u-boot-2015 with a new version of u-boot-2018. New version assembled and tested only on Khadas VIM2 (it I told). So when you replaced your u-boot-2015 with a new one, you got a problem. The new u-boot-2018 cannot work with standard firmware tools. It is not known whether the new u-boot is compatible specifically with your TV box model or not. 3. You may now have to perform special steps to restore the health of your TV box. 4. All new versions are specially launched from external media to check if everything works on your hardware correctly. Only then is the installation done on the eMMC. For example, in core 4.x there is no support for many Wi-Fi on some models does not work USB, etc. 5. If USB does not work, to restore the ability to control the system , you have to use either SSH through the network or UART. At that moent when you installed the new version into eMMC, but it is not working USB, have you had the opportunity small means to restore the system to its previous level, but again you hurried and did not wait for advice on how to do it. 6. I do not understand what the current state of the system in eMMC is. What happens if turn on the TV box, which messages appear on the screen ?

The first test I did on the image SERVER (choose a full installation of all components). KODI runs without problems there. I didn't have time to check the rest. If necessary, I can repeat this check of the other components on the SERVER.

I have for MVR9, browser and other programs (used in the script) are noticeably better than the MX10 (it's the same A5X max). Perhaps the reason is that another dtb is used, without optimization.

Try running the script again and selecting the second version of GLAMOUR drivers for x11 to install.

It looks like you have the same problem as the Z28 , the manufacturer has made it impossible to run other systems easily. The topic Z28 is infa, how can you try to solve it, but it requires some training.

Try to change the options used DTB. If this does not help, you should try to take the boot loader from the images that are running.

Why are you in a hurry and do not wait for an answer, as you had to do after the first run of the installation script from version 5.71 ? You already have a version with kernel 3.14 installed, and the transition to the new kernel should be done differently. Now you will have to perform many other steps to restore the TV box.

For all I know the models rk33xx not need to press anything. The system itself should automatically start from the SD card.

All software (mpv gstreamer KODI) are collected using system libraries from Ubuntu. Therefore, Ubuntu packages will not work in Debian. We need to rebuild all the components for Debian. I came across this when building KODI versions with HW for AML.

1. Universal multi-loading is a prerequisite. 2. The installation process is simplified, now it is enough to run one installation script, it contains all the steps (which were previously in two scripts). I left until the previous version of the steps, perhaps someone will use the first versions of the images.

Test media-script to MX10 http://forum.puppyrus.org/index.php?topic=21337.msg153103#msg153103 Mode 1080 (used TV \ monitor with Full HD) desktop-MPV and Gstreamer (and player based on it) twist all the videos in full screen without problems. The main advantage of Gstreamer - it can be scaled in arbitrary proportions directly on the desktop, MPV - only full screen on the entire desktop and control only buttons (or remote control if it has support in the system) KODI-works without problems with any formats. Playing in the browser-there is something strange and do not understand what the reason. Full-screen playback mode. If you select the parameters in the YouTube more than 720-begin braking and regular friezes with a spinning white circle in the center. I have the feeling that not enough channel speed Internet. Desktop mode on a 4K TV with 4K. Video. A strange glitch on my TV 4K-when you try to run any video software with any video format - green horizontal chaotic flat on video and brakes when playing, the only thing that if you run KODI, then it will be the video itself is normal, but it is necessary to move the mouse or try to display the video reference information on the "O" button - immediately appear the same green bars and video slows sharply. And it does not matter what the resolution of the desktop to set at 720 and 1080 exactly the same kanitel. I don't know what the reason is. You'll have to check MVR9. But if you run a clean LE-4K TV, everything works without interference, any video turns in full screen (including 4K). I tried to install the YouTube plugin in LE and watch the video in IT, there you can set only 720, and the video works without problems with the desktop format 4K. I think the reason in software or settings or banal heating, it is necessary to understand. Test to MVR9 http://forum.puppyrus.org/index.php?topic=21366.msg153162#msg153162 Checked on MVR9 on TV 4K-everything works in MPV gstreamer KODI without glitches, which described about MX10. So the reason in something on the MX10, most likely in dtb or kernel. A pleasant surprise, it turned out that MVR9 in KODI, MPV and on the desktop Armbian (in the file Manager and other things) out of the box working remote, though not all of the buttons (not the main "Ok"). With video playback in the browser at 4K screen resolution and video playback in YouTube and MVR9 there are problems (but better than MX10) - very slow, have to put a very low resolution in YouTube and oddly enough to switch to full screen, then works better than in a normal window in the browser. I think the reason is that HW somehow doesn't work correctly with the browser at 4K screen resolution. The desktop itself while 4K resolution works quickly, the Windows drags fast, the menus are not slow.

You need to build your version of s805_script (the name can be any), specify where to load the kernel, initrd and DTB. Write it in NAND. To edit variables of u-boot, add after the check run the script with USB and SD, run your new script. Then when you run u-boot, it will run a new script from NAND, and the script will already run the system from NAND with the specified parameters.