balbes150

In this embodiment, the variables I see the setting. With some caution you can try to verify the installation to the internal memory. For this you need  be SURE to backup the internal memory. You can use the scripts included in the latest images. To register as a user "root" (su -) and execute one of the options backup "ddbr_backup_3g" or "ddbr_backup_full". The first script creates a minimal copy of the first 3 GB of emmc memory. The second script creates a complete copy of the entire memory. The media must have enough free space to create a selected option of the copy. After the copy, I recommend save it on PC in a safe place the backup file (from the directory /ddbr on the media). To install on internal memory. Start terminal and log in as the user "root" with the command "su -". Start the installation with the command "./install.sh". Avoid not understand the consequences of the script, don't use mode "sudo". The script will attempt to copy the working system to the internal memory. Therefore, before install need to perform all the necessary setup of the system on removable media and check that all the hardware would work as required (WiFi , sound, etc.). After copying is complete, you need to perform a logoff and try to start TV box without external media. Probably the first time the system fail to boot from the internal memory. You need to start the system from external media and reinstall. I when testing, the system started to work after the second reinstall.

Updated the deb packages (firmware and libmali) for manual installation in still images (5.24).
 
https://yadi.sk/d/LBA4bXk_32RGZ6
 
 
 
 
firmware/brcm/config.txt

In the near future I plan to publish the Linux images for s812 (they are being tested). TV set-top box on the basis of the s812 chip is very close with s802 (they all use the same kernel). So I hope that the images s812 will also work on s802.

Update. The Ubuntu image (20161218) test support HW libMali. Firefox works quite smoothly when playing video from youtube. Tried KODI from online repositories (version 15.2), with 720P video plays back. Not ideal, but not a slideshow . You can comment out the startup desktop (comment out the last line in the file .bashrc in your home directory) and run KODI with the command "startx kodi". To enable sound you need to change the settings.

Have not tested the version of the image to run from removable media to S805. Are you interested ?

1. you can use the dd command to create a copy and restore.
2. use simple scripts, which is already composed of all the images Armbian which I collect. A list of current scripts.
 
dd_backup - creates a complete copy of all internal memory.
 
dd_backup_3g - creates a copy of the first 3 GB of memory. Almost all firmwares I've seen are placed in the first 2-3 GB of memory. Next are user data.
 
dd_restore - restores content from a previously created backup.
 
Pay attention. Before using the scripts running system from SD card, be SURE to check what names are assigned to the internal memory is mmcblk0 or mmcblk1 (command "fdisk -l"). And depending on this to fix the scripts. By default, they use mmcblk0. This link has more information.
 
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/580062-s905_ddbr
 
We strongly recommend to use stream compression during the backup. Such copies do NOT work. Backup compression (to reduce size for storage) you need to perform after the backup is complete. Time backup can be significant (depending on the carrier speed). For example for TV box 16GB - about 15-30 minutes.

1. u-boot, which I wrote, recorded in the first megabyte of the image as the bootable part (for those cases when you need to start the system when NOT working or missing bootloader in the internal memory). During normal system start-up from external media (using multi-boot), the boot loader may not affect the startup process (as it uses a standard boot loader from internal memory).
2. As long as the installation process does not require fully debugged, I don't post a script for automatic installation Armbian in TV boxes. Now to debug the installation scripts Armbian the internal memory there is NO step replaces the regular u-boot. The problem of debugging the installation process Armbian the internal memory that you can not change the code to the regular bootloader. Have to use limited features (commands) to run and use Linux.
3. In a modified u-boot is already enabled multiboot (you can launch from portable media).
4. I no longer use the USB cable and windows software for firmware (for archiving and full recovery of the contents of the internal memory, including u-boot). I was completely satisfied with the ddBR (NOT TWRP). For this I use the loader from the SD card that would be free to start the system from external media when you killed the internal loader. By the way, to create a complete backup and restore "brick" the PC is not needed. Simply plug in the SD card (with the backup that you need to do TO experiments with the TV box), a keyboard, closing the contacts and it's easy to completely restore the state of the TV box to experiments with the internal memory (eMMC) , including the initial state of u-boot and all the env settings.
 
 
 

https://forum.armbian.com/index.php/topic/2419-armbian-for-amlogic-s905-and-s905x/?p=21058

Just as a reference:
H2+ and H5 'SDKs' available on this mirror: http://filez.zoobab.com/allwinner/ Xunlong's 'Debian Server' image from yesterday is mirrored here: https://transfer.sh/f7Eet/orangepih5-pc2.img.xz(login: debian:debian -- sudo enabled) Regarding development efforts in general simply watch linux-sunxi IRC log (no need to join conversations, everything available as log -- see above)

root@amlogic-s905x:~# fdisk -l p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff} p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Menlo; color: #000000; background-color: #ffffff; min-height: 13.0px} span.s1 {font-variant-ligatures: no-common-ligatures}   Disk /dev/mmcblk0: 7.4 GiB, 7969177600 bytes, 15564800 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00019380   Device         Boot  Start      End  Sectors  Size Id Type /dev/mmcblk0p1        2048   133119   131072   64M  e W95 FAT16 (LBA) /dev/mmcblk0p2      133120 15253503 15120384  7.2G 83 Linux   Disk /dev/mmcblk1: 7.2 GiB, 7752122368 bytes, 15140864 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk1rpmb: 128 KiB, 131072 bytes, 256 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@amlogic-s905x:~# Beelink Mini MX S905 1GB/8GB

Tomorrow I will upload the kernel packages and headers. They are not in network.

Ok, it was quite simple. Working sample s905_autoscript (static configuration, dhcp should also work):
setenv m "1080p50hz" setenv hpd "false" setenv mbpp "32" setenv bootargs "root=LABEL=rootfs rootwait ro console=ttyS0,115200n8 console=tty0 no_console_suspend hdmimode=${m} m_bpp=${mbpp} net.ifnames= 0 fsck.repair=yes elevator=noop disablehpd=${hpd} consoleblank=0 hdmitx=cecf" setenv boot_start booti 0x11000000 0x13000000 0x1000000 setenv ethaddr C0:12:34:56:78:90 setenv ipaddr 192.168.1.231 setenv serverip 192.168.1.248 tftp 0x13000000 uInitrd tftp 0x11000000 Image tftp 0x1000000 dtb.img run boot_start Now I can change kernel/initrd/dtb images without moving sd card to another device
I will probably change root to NFS too. 
It should be faster ans safer  than sd cards..

1. I understand that the system automatically used the correct dtb data (you not copied dtb) ?
2. It is the universal images, which are collected from my git if you select AmlogicS905X
3. The setup script in the internal memory is NOT working. It needs to be changed (I don't have time, something would have to change it and test). The main problem is that the script should NOT replace u-boot and should be able to embed the system into existing mtd-partitions without affecting functionality of an internal component (recovery env, etc).
4. For WiFi settings you need to perform several manual operations (I hope next versions will be added gradually need the infrastructure to support WiFi).
 
https://forum.armbian.com/index.php/topic/2419-armbian-for-amlogic-s905-and-s905x/?p=20730

Judging by the log, the system is running. Log in as the root user with the password 1234, change the root password, create new user and give the shutdown command "poweroff". After turning it off try to start the system the power button on the remote control. If You are using a version of the image Desktop, after system startup and login, you can give the command "startx" to start graphical desktop.

Yes, of course.
1. Download and burn image Armbian to the media.
2. Using prepared media to activate universal multiboot.
3. Try to start the system from external media without modifications.
If the system cannot start, try to copy the from the directory "dtb" in the root of the FAT partition dtb file with the name "dtb.img". And try to start the system with this file. For tests, recommended you have connected the console UART. This will significantly ease the debugging process, because will be immediately obvious where the error occurs run, will allow you to make adjustments to the testing process (to load the elements of the system separately , without the need of a long process of rebuilding). You can try to use files that have collected garyang (link above in this thread), just remember to rename the kernel Image to zImage.

1. I understand that the system automatically used the correct dtb data (you not copied dtb) ?
2. It is the universal images, which are collected from my git if you select AmlogicS905X
3. The setup script in the internal memory is NOT working. It needs to be changed (I don't have time, something would have to change it and test). The main problem is that the script should NOT replace u-boot and should be able to embed the system into existing mtd-partitions without affecting functionality of an internal component (recovery env, etc).
4. For WiFi settings you need to perform several manual operations (I hope next versions will be added gradually need the infrastructure to support WiFi).
 
https://forum.armbian.com/index.php/topic/2419-armbian-for-amlogic-s905-and-s905x/?p=20730

1. You can use ready-made images for s905x.
2. When you start the system from external media, the internal memory remains unchanged.
3. Activation multi-boot with interfere to receive the OTA update.
4. There is the option of running the system from external media without having to activate the multi-boot. For this you need to rename the file s905_autoscript in aml_autoscript (deleting the old version aml_autoscript). To run this option, you can use the toothpicks.

Hello i hear you balbes. I am on mobile so very bad writing here. Sorry.. I tried armbian librelec and amlogic images and modules. Amlogic works as described in the manual. Libreelec works. Balbes armbian desktop versions works after you put below files into directories and issue commands below.

I have mini m8s II which has ap6212 wifi module. I will try to remember file names. The chip is bcm43438.
 
Firmwares: /lib/firmware/brcm
fw_bcm43438a0.bin
fw_bcm43438a0_apsta.bin
fw_bcm43438a0_p2p.bin
nvram.txt
nvram_ap6212.txt
config.txt
 
Modules: /lib/modules   (check also /lib/modules/kernel/3.14.29/ folder..)
cfg80211.ko
dhd.ko

Balbes kernel has setting for broadcom chips to look for directory /lib/firmware/brcm

So copy original files from eMMC of your device.

sudo modprobe cfg80211
sudo modprobe dhd

If it does not work go to below files directories.

sudo insmod cfg80211.ko
sudo insmod dhd.ko

Armbian Dekstop version should work after above commands.

Headless is more difficult. Or I am lack of required knowledge. It requires to setup wpa_supplicant.conf  & /etc/network/interfaces   i belive. But never make it work reliably..
Hope this helps..
 
UPDATE:
check this:
 
https://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/
 

Thank you. So the main works. You can now remove the old files. Why ask about testing. The Assembly is using network repositories, where packages change, and how it changed is not known. I think that WiFi does not work not because of dtb data. While this is a common problem with images Armbian - I have not reached finish, but other users that have decided this question are silent and do not seek to share best practices, and what to change, something began to work.
 
 
СпаÑибо. Значит оÑновное работает. Теперь можно убирать Ñтарые файлы. Почему Ñпрашиваю про теÑтирование. Сборка идёт Ñ Ð¸Ñпользованием Ñетевых репозиториев, в которых пакеты изменÑÑŽÑ‚ÑÑ, что и как там изменили - не извеÑтно. Я думаю, что WiFi у Ð’Ð°Ñ Ð½Ðµ работает не из-за dtb данных. Пока Ñто Ð¾Ð±Ñ‰Ð°Ñ Ð¿Ñ€Ð¾Ð±Ð»ÐµÐ¼Ð° образов Armbian - у Ð¼ÐµÐ½Ñ Ð½Ðµ доходÑÑ‚ руки доделать, а другие пользователи, которые решили у ÑÐµÐ±Ñ Ñтот Ð²Ð¾Ð¿Ñ€Ð¾Ñ - молчат и не ÑтремÑÑ‚ÑÑ Ð¿Ð¾Ð´ÐµÐ»Ð¸Ñ‚ÑŒÑÑ Ð½Ð°Ñ€Ð°Ð±Ð¾Ñ‚ÐºÐ°Ð¼Ð¸, что и как нужно изменить, что-бы Ñтало работать.

Tested the new ubuntu img(cli and desktop), but only on Nexbox a95x, later i try it on several different device. All default functional works well(ethernet, audio, apt, etc) video play smooth test and my 720p sample(with x11 vo driver). Some trouble with wi-fi, it's not visible in Ifconfig, but i think problem in dtb and i need change dts in orde to fix it.
 
 

About official support, I don't know, it is a question of administration. As far as I can judge by the description model - last images Armbian Amlogic-s905x should work on this model.

1. https://yadi.sk/d/srrtn6kpnsKz2 
2. I'd say that the min size 4-gb(cli), better 8gb(desktop).
3. One image - one sd
4. raspbian based on debian and other open source component, so you can build 'you own raspbian'

https://yadi.sk/d/srrtn6kpnsKz2 - balbes150's ya.disk folders.

Yes, of course.
1. Download and burn image Armbian to the media.
2. Using prepared media to activate universal multiboot.
3. Try to start the system from external media without modifications.
If the system cannot start, try to copy the from the directory "dtb" in the root of the FAT partition dtb file with the name "dtb.img". And try to start the system with this file. For tests, recommended you have connected the console UART. This will significantly ease the debugging process, because will be immediately obvious where the error occurs run, will allow you to make adjustments to the testing process (to load the elements of the system separately , without the need of a long process of rebuilding). You can try to use files that have collected garyang (link above in this thread), just remember to rename the kernel Image to zImage.

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/565449-running-linux-from-sd-card-or-usb-flash-drive-using-balbes150-method-and-files?p=608502#post608502
 
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/565449-running-linux-from-sd-card-or-usb-flash-drive-using-balbes150-method-and-files?p=608542#post608542