balbes150

Thanks for checking. I'll try to see what can be done with c2play.

Updated desktop images. Removed from the composition package "nodm". The order of use without package nodm. After creating a new user, exit from the root user (exit command, or you can reboot with reboot command) and authorization on behalf of the new user. After login give startx.

Thanks for the info.
I have tried mpv with vo=x11 in my current ubuntu mate, i can scale and full screen, but its make video playback slower, but with default window it smooth just like VLC.
 
What about c2play, can you make it work with your Armbian ?

Images 79 based on the kernel from Hardkernel. Images 29 based on the kernel from Amlogic (the same core used in the LE). By the way, I checked Ubuntu the behavior of the program "mpv" (this program is used by default for multimedia playback), video can be scaled. I repeat, just in case, download the new images not sure if the uninstall package "nodm" , the system begins to work normally in previous images. In the last images 29 updated the startup scripts of the system, they can be download separately (version v5) from my GIT and replace the FAT partition.
 
https://github.com/150balbes/Amlogic_s905/tree/master/script/S905_ARMBIAN

Updated desktop images. Removed from the composition package "nodm". The order of use without package nodm. After creating a new user, exit from the root user (exit command, or you can reboot with reboot command) and authorization on behalf of the new user. After login give startx.

I found the reason for the bad behavior of desktop latest desktop images. As a temporary solution - to disable the use of the package nodm to start the graphics. To do this, open the configuration file /etc/default/nodm and replace in the first line the value "true" to "false" . To run charts - after starting the system to enter the console username and password, after login give the command "startx". This method can be used on all previous images, where after starting the graphics screen becomes too dark.
 
 
Along the way, found that the system normally displays the color mode 32 and 24 (no previous problems when in 32 bit color desktop became very dark).
 
 
 
More good news, checked now in Ubuntu playback of normal video. If you do not change the scale of the image is reproduced smoothly. Debian - this video clip is playable slides. Although the sound is played correctly.

I found the reason for the bad behavior of desktop latest desktop images. As a temporary solution - to disable the use of the package nodm to start the graphics. To do this, open the configuration file /etc/default/nodm and replace in the first line the value "true" to "false" . To run charts - after starting the system to enter the console username and password, after login give the command "startx". This method can be used on all previous images, where after starting the graphics screen becomes too dark.
 
 
Along the way, found that the system normally displays the color mode 32 and 24 (no previous problems when in 32 bit color desktop became very dark).
 
 
 
More good news, checked now in Ubuntu playback of normal video. If you do not change the scale of the image is reproduced smoothly. Debian - this video clip is playable slides. Although the sound is played correctly.

In the latest version images (20161030) fixed the network card on the platform S905X. If You have everything working, update is not necessary.

Upload
 
https://yadi.sk/d/DXftuWpXx4zNt
 
 
 
 
If You used booldroot , you can try to compile the kernel and modules with support for mali (to go to booldroot folder and then give the make command menucobfig, mark the desired option and collect). Or download the source code and once in the system S912 to assemble and install. For use restarting the internal firmware, you can use the finalize script s912_autoscript (add check) and an extra script (on the desktop that will install any variable in u-boot, or create a file dummy in BOOT FAT). An example script can be found here.
 
https://github.com/150balbes/LibreELEC.tv/blob/Amlogic-S905-kszaq/projects/S905/install/s905_autoscript.src
 
https://github.com/150balbes/LibreELEC.tv/blob/Amlogic-S905-kszaq/projects/S905/filesystem/usr/sbin/rebootfromnand
 
 
To S905X
 
As it turned out, during the actual test, S905X works fine run from a USB flash drive. Ie S905X system can be used with SD card and USB flash drive.

When assembling the images, the system generates deb packages with kernel headers and other. Their size is not large. If you want, I can upload them to the website. And you will be able to easily download them to install into an existing system. But I warn you that I this option is not checked and how it works I do not know. Not the fact that it will, but there is a risk that when you update it can overwrite u-boot and have to restore it. You can try to remove the packages from u-boot, do they not fire when you update the kernel and check the update scripts of the kernel (where the generated initrd, etc.).

Gathered for a versatile look that can work on both platforms S905 and S905X. In the images used a new kernel. A side effect from the use of the new engine is not running the output to the console on the monitor\TV. Therefore, for the primary system configuration you must use either connect via SSH or UART console. After the initial setup begins to work normally the system and the system can be used normally using the keyboard and mouse. Positive nuance from the new kernel - it was OK to work off. Now after turning off, you can turn on the TV console as usual with the remote control. In the image included two ready-made startup script for different screen resolutions. To use them, it is necessary to rename the appropriate option in s905_autoscript. To use the image on the platform S905 - it is necessary to copy and rename "dtb.img" directory dtb file. On the platform S905X must work the startup dtb from the internal memory. If it does not work - must similarly copy the correct dtb file.
 
Armbian_5.21_Amlogic-s905x_Debian_jessie_3.14.29_desktop_20161016.img
 
Armbian_5.21_Amlogic-s905x_Ubuntu_xenial_3.14.29_desktop_20161016.img
 
 
Please note, for SSH access and the initial settings you must wait for a secondary reload. At the first start of the image created before the settings for the network and SSH, expanding the secondary section. Then restarts automatically. Only then can you start setting up via SSH or the console UART.

There is another option to get the files you need.
When building image LE, You will have a directory with collected ready files and source code. In these subdirectories You can find the files you need. Do not spend the time to build the entire image, You can specify the build command, only the desired packages.

U-boot for the boards, there are no command "autosrc usb mmc emmc bootp" ?
 
The tester, who does not know that it is happening in the system (which carriers and why they are used) ?????
Better not to have such testing.
 
About the pros and cons of LABEL. Suppose such a scenario. Recorded image on the SD card of 16 GB . Checked. Works. Decided to move on the USB flash drive of size 8 GB. When using LABEL. Simply copy all the directories and files (as is) to a new medium. And assign a LABEL. Made changes to the system during testing. Created archive. Then deployed on any medium, even smaller (considering the size of the files). Can be easily transferred to testing by other users of the entire system "as is" for any media. I do not impose. I just share information. By the way, if the console UART, write and debug the script  - not difficult. When you work (if using) on other boards it is rarely necessary to edit (console UART is not needed). Enough to rule the working scripts, which defines all the features of the system startup (which you can change). This algorithm is already well established.

Added a few new images from Ubuntu.
 
https://yadi.sk/d/5_32km_EsCV2A
 
https://yadi.sk/d/pHxaRAs-tZiei

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=586733#post586733

As it turned out, the images of workers.  
The download does not occur due to a failure in the procedure of the extension section. The procedure prescribed force /dev/mmcblk0. And when you start from SD card, this device indicates the internal memory (eMMC). Where you already have the partitions from Android. If you disable the extension root partition in the script, it works (without automatic extensions section).

Hi,

here is a short howto to boot Armbian on Mini M8S from SD Card.

You have to change the u-boot environment to check the SD-Card and then start a autoscript script.

To boot the Armbian image you have to change some files from Armbian, change all mmcblk0 to mmcblk1 in file /etc/fstab /etc/init.d/firstrun /etc/init.d/resize2fs

You need the file boot-s905.txt and have to convert it to autoscript, the Mini M8S u-boot can't work with Armbians u-boot boot.ini.
setenv cec "cecf" setenv mesontimer "0" setenv nographics "0" setenv condev "console=ttyS0,115200n8 console=tty0 consoleblank=0" setenv verbosity "255" setenv bootargs "root=/dev/mmcblk1p2 rootwait rootflags=data=writeback rw ${condev} no_console_suspend hdmimode=${hdmimode} m_bpp=${display_bpp} fsck.repair=yes loglevel=${verbosity} net.ifnames=0" setenv initrd_loadaddr "0x13000000" fatload mmc 0:1 ${initrd_loadaddr} uInitrd fatload mmc 0:1 ${loadaddr} zImage fatload mmc 0:1 ${dtb_mem_addr} dtb/meson8_Mini-M8S.dtb fdt addr ${dtb_mem_addr} if test "${mesontimer}" = "1"; then fdt rm /timer; fi if test "${nographics}" = "1"; then fdt rm /reserved-memory; fdt rm /aocec; fi booti ${loadaddr} ${initrd_loadaddr} ${dtb_mem_addr} Convert it with u-boot tools to autoscript.
mkimage -A arm -O linux -T script -C none -d boot-s905.txt s905_autoscript Copy it to SD-Card to the boot partition, and also copy the file "meson8_Mini-M8S.dtb" the Boot partition in folder "dtb".

Now open the case and connect the UART connector.
Read this Howto for more informations.
http://www.cnx-software.com/2015/12/06/how-to-run-headless-linux-on-amlogic-s905-devices-such-as-mini-mx-or-k1-plus/#
setenv preboot "run factory_reset_poweroff_protect;run upgrade_check;run bootmode_check;run init_display;run storeargs;run upgrade_key;run user_start;run switch_bootmode;" setenv user_start "if mmcinfo; then run linux_start_mmc;fi;" setenv linux_start_mmc "if fatload mmc 0 ${loadaddr} s905_autoscript; then echo ===[LINUX START from mmc]===;autoscr ${loadaddr};fi;" saveenv After reboot the Mini M8S should boot from SD-Card.
 
Please check the lines and be careful, an error can brake the possibility to interrupt the boot sequence.
 
UPDATE 2016/09/08:
after apt-get distupgrade, the uboot package was updated and this was rewriting the uboot data from emmc, but the Mini m8s is not working with the uboot from Hardkernels Ordroid uboot.
I got this after boot:
***** Warning!! ************************************************** ***
* This board have not been autorized or product keys are not valid. *
* Please contact with Hardkernel or your distributor *
************************************************** *******************
 
After shorten the emmc at boottime, I was able to recover the stockimage via OTG USB and amlogic's windows tool, thanks to balbes150, I found a info on freaktab.
 
So after first armbian boot from SD, you have to remove the uboot package with "apt-get remove linux-u-boot-odroidc2".
boot-s905.txt
s905_autoscript.gz
meson8_Mini-M8S.dtb.gz

Hi,
 
with the how-to from http://www.cnx-software.com/2015/12/06/how-to-run-headless-linux-on-amlogic-s905-devices-such-as-mini-mx-or-k1-plus/#it was possible to boot the Odroid C2 Image on a Mini M8S ( s905 2GB Ram).
 
The Mini M8S stock u-boot does not support CFGLOAD, so I had to change some parameter from the boot.ini to bring them to the ENV.
 
The Boot Priority is different from the Odroid C2, it will only check the EMMC, does someone knows if this is more a hardware or software configuration?
 
 
If someone has interest I will post a small how-to.
 
Thank you for your hard work for this open system.
 
br tpc010

In C2 use your Odroid u-boot, which added to the boot.ini as a startup script. You can use another option that uses standard features of u-boot. The script for the command autoscr. Not a lot of details can be seen here.  
http://amlinuxmedia.com/forum/index.php?topic=223.msg2117#msg2117

Information in this topic is very outdated see this topic.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Information in this topic is very outdated see this topic.