balbes150

5.34

Almost all deb packages version 5.37, such as 5.34 on the website. The difference is in the packages. firmware-aml linux-dtb-amlogics905x linux-image-amlogics905x linux-xenial-root-amlogic-s905x But they are not significant changes. If needed, I can upload at a time (I have limited space).

Package fbset installed ? What program watch the video ? Activation of the monitor (script /boot/hdmi.sh) running ?

You know how can add new version and idesk idesk-set in a network repository Debian ?

To replace the firmware or try to add encryption support to kernel and system (but not the fact that it will help to use an encrypted system). Thank you for the test, I got some info. There are options on how to make a image for all tests. Write system on SD card or USB flash drive 4-8 GB, perform all necessary settings and adding in a real system on your TV box. Remove from the system unnecessary files, and personal settings. Repack the rootfs and boot received in the archives. Zero media (dd if=/dev/zero of=/dev/sda). Create a clean file system\partitions (BOOT and ROOTFS) on the media. Unzip archives and copy files to the media. Copy the image from media using dd. This is the image that other users can easily record on media to use. To create an image with clean sections, instead of real media, you can use created on PC image file onto your mounted via loop. I would be interested to get your version of the image with IceWM for the test (even in a plain tar archive of a rootfs). You may not exactly define the type of processor s905 or s905x or s905w. Try all the options dtb.

Oh, we think about the same .... I downloaded your image with icewm, look at VirtualBox. I have been working with Icewm. There is a part of the work. By the way, for Khadas have a build system Fenix, which can be supplemented with Assembly of IceWM, look at her. https://github.com/150balbes/fenix

Have you tried the latest test image Armbian Mate 20180116 ? I added a large number of new dtb (which are used in LE Kszaq). I have images with this kernel with IceWM\server and so on until they are uploaded to the site, I forward to feedback from users, something to learn how does a new set of dtb files on different machines. I received only one answer in a new way. Describing the problem with shutting down. By the way, I checked this message, the system shuts down, but sometimes it takes up to 10-15 minutes (I have not yet found a dependency, why it happens). I understand that you, like me, are a fan of IceWM ? Have you tried the latest test image Armbian Mate 20180116 ?

To study the output of the command "help" and explore the options of the received command with the "-help". Either contact the manufacturer requesting information.

You TV box not standard partition table, perhaps it uses encryption. Partition table get from SPL is : name offset size flag ================================================================================ 0: bootloader 0 400000 0 1: reserved 400000 800000 0 2: cache c00000 10000000 2 3: env 10c00000 400000 0 4: logo 11000000 300000 1 5: encrypt 11300000 100000 1 6: recovery 11400000 2000000 1 7: tee 13400000 800000 1 8: crypt 13c00000 2000000 1 9: misc 15c00000 2000000 1 10: boot 17c00000 1400000 1 11: system 19000000 60000000 1 12: persist 79000000 800000 4 13: panic 79800000 400000 4 14: data 79c00000 158400000 4

The installation of u-boot that depends on how it's done in u-boot (source code). For example, for models Khadas VIM u-boot has a special team (sdc_update bootloader u-boot.bin), which I will install u-boot in eMMC\SPI. I don't know which team has your u-boot.

Only disconnecting the USB media. Either learn how to do selective start of the system.

Show the output of "printenv" from u-boot and log run Armbian.

Perhaps your model does not have eMMC memory used an old version of NAND. Need a connected console UART.

What dtb file are you using ?

Enough to wait up to 10 minutes. Try all the dtb for your group (gxm* amd kvim2* ).

This requires access to source code and information from the manufacturer. Maybe you need to contact the manufacturer of your TV box.

I recommend to verify that u-boot steps strictly in this order. 1. To erase the u-boot in eMMC (TV box will not start this is normal, it is easy to fix in the future). 2. Record on SD card of your new (made by you) u-boot. 3. To check out the launch of a new u-boot from SD card on your TV box. 4. If your new u-boot will normally be run from SD card, you can try to burn it to eMMC.

+ need to wait for the first run (until the moment when you see the image on the monitor) can take up to 10 minutes.

Record your u-boot to eMMC - possible. You need to know, or what teams laid the manufacturer of u-boot, or to have an image of /dev/bootloader , something to record it with the dd command.

Start Armbian external media equivalent startup LE. So if LE did not kill the TV box, Armbian also won't hurt her (unless you're not perform the right commands in the running Armbian).

The log shows that the file is loaded (but the download is too slow) and the engine is running. Try to start the system manually. Using different dtb. Try checking two options (with different data for the used RAM). 1. options usb start setenv condev "console=ttyS0,115200n8 console=tty0 no_console_suspend consoleblank=0" setenv bootargs "root=LABEL=ROOTFS rootflags=data=writeback rw ${condev} fsck.repair=yes net.ifnames=0 mac=${mac}" fatload usb 0 0x14000000 uImage fatload usb 0 0x15000000 uInitrd fatload usb 0 0x11800000 dtb.img fdt addr 0x11800000 bootm 0x14000000 0x15000000 0x11800000 2. options usb start setenv condev "console=ttyS0,115200n8 console=tty0 no_console_suspend consoleblank=0" setenv bootargs "root=LABEL=ROOTFS rootflags=data=writeback rw ${condev} fsck.repair=yes net.ifnames=0 mac=${mac}" fatload usb 0 0x21000000 uImage fatload usb 0 0x22000000 uInitrd fatload usb 0 0x21800000 dtb.img fdt addr 21800000 bootm 0x21000000 0x22000000 0x21800000

1. See the first post of the topic about s905, it has all the links to the desired images. 2. The dtb file you need to use from the image Armbian (take from directory /dtb)

You need to have a number of elements with reference to the model of the TV box, which is going the way 3in1. 1. The source code u-boot version which has the command you want (u-boot must be able to start the any system from partitions of internal drive). 2. Access to source code dtb data. 3. A working version of Android with a built-in mode reboot into the desired system. 4. Real hardware for testing.

Any way to use a dtb file from the group gxm_q200_2g

Connect the flash drive with Armbian (don't forget to add correct dtb file) and run the UART in the console these commands. usb start fatload usb 0 11000000 aml_autoscript autoscr 11000000 The execution result of the show here.