Nofan Tasi

Update images (3.14.29 20170201).
 
Changes.
 
1. Updated kernel (frequency range limited to 500 - 1536)
2. Added the package gparted in the desktop version
3. Fixed setting in the inner memory
4. Fixed auto-using dtb from the internal memory
5. Added dtb file for VIM Khadas
6. Fixed reboot mode

Hi all
 
Here is recipe I use to natively build S905/ordroid kernel. Note this is on gentoo so initramfs details differ from ubuntu practice.
**** BACKUP /boot /lib/modules /lib/firmware **** **** choose 4.9 gcc **** gcc-config aarch64-unknown-linux-gnu-4.9.4 . /etc/profile export ARCH=arm64 git clone https://github.com/150balbes/Amlogic_s905-kernel.git cd Amlogic_s905-kernel git checkout S905X  or git checkout odroid make clean make mrproper # S905X wget https://raw.githubusercontent.com/150balbes/lib/master/config/kernel/linux-amlogics905x-default.config cp -p linux-amlogics905x-default.config .config # odroid cp -p ../config-3.14.79-vegas95 .config make oldconfig make -j3 Image make -j3 modules make -j3 dtbs cp -p arch/arm64/boot/dts/*.dtb /boot/dtb/ make modules_install make install make firmware_install # S905X dracut --kernel-cmdline "root=LABEL=ROOTFS boot=LABEL=BOOT" initramfs-dracut-arm64-3.14.29 3.14.29 cp -p initramfs-dracut-arm64-3.14.29 initrd.img mkimage -A arm64 -O linux -T ramdisk -C none -a 0 -e 0 -n uinitrd -d initrd.img uInitrd # odroid dracut --kernel-cmdline "root=LABEL=ROOTFS boot=LABEL=BOOT" initramfs-dracut-arm64-3.14.79+ 3.14.79+ cp -p initramfs-dracut-arm64-3.14.79+ initrd.img mkimage -A arm64 -O linux -T ramdisk -C none -a 0 -e 0 -n uinitrd -d initrd.img uInitrd # install them in /boot unset ARCH=arm64 **** restore previous gcc **** gcc-config aarch64-unknown-linux-gnu-6.3.0 . /etc/profile  
depends on S905x or odroid your boot could look like
 
 S905x
aml_autoscript      amlogics905x_init.sh  config-3.14.29  dtb.img             s905_autoscript      s905.start          uInitrd aml_autoscript.zip  boot.bmp              dtb             initrd.img-3.14.29  s905_autoscript.cmd  System.map-3.14.29  zImage  odroid aml_autoscript        boot.bmp         dtb.img              s905_autoscript.cmd  uInitrd           zImage aml_autoscript.zip    config-3.14.79+  initrd.img-3.14.79+  s905.start           uInitrd-3.14.79+ amlogics905x_init.sh  dtb              s905_autoscript      System.map-3.14.79+  vmlinuz-3.14.79+ The script files come from Balbes distributions.
 

Hi all
 
Here is recipe I use to natively build S905/ordroid kernel. Note this is on gentoo so initramfs details differ from ubuntu practice.
**** BACKUP /boot /lib/modules /lib/firmware **** **** choose 4.9 gcc **** gcc-config aarch64-unknown-linux-gnu-4.9.4 . /etc/profile export ARCH=arm64 git clone https://github.com/150balbes/Amlogic_s905-kernel.git cd Amlogic_s905-kernel git checkout S905X  or git checkout odroid make clean make mrproper # S905X wget https://raw.githubusercontent.com/150balbes/lib/master/config/kernel/linux-amlogics905x-default.config cp -p linux-amlogics905x-default.config .config # odroid cp -p ../config-3.14.79-vegas95 .config make oldconfig make -j3 Image make -j3 modules make -j3 dtbs cp -p arch/arm64/boot/dts/*.dtb /boot/dtb/ make modules_install make install make firmware_install # S905X dracut --kernel-cmdline "root=LABEL=ROOTFS boot=LABEL=BOOT" initramfs-dracut-arm64-3.14.29 3.14.29 cp -p initramfs-dracut-arm64-3.14.29 initrd.img mkimage -A arm64 -O linux -T ramdisk -C none -a 0 -e 0 -n uinitrd -d initrd.img uInitrd # odroid dracut --kernel-cmdline "root=LABEL=ROOTFS boot=LABEL=BOOT" initramfs-dracut-arm64-3.14.79+ 3.14.79+ cp -p initramfs-dracut-arm64-3.14.79+ initrd.img mkimage -A arm64 -O linux -T ramdisk -C none -a 0 -e 0 -n uinitrd -d initrd.img uInitrd # install them in /boot unset ARCH=arm64 **** restore previous gcc **** gcc-config aarch64-unknown-linux-gnu-6.3.0 . /etc/profile  
depends on S905x or odroid your boot could look like
 
 S905x
aml_autoscript      amlogics905x_init.sh  config-3.14.29  dtb.img             s905_autoscript      s905.start          uInitrd aml_autoscript.zip  boot.bmp              dtb             initrd.img-3.14.29  s905_autoscript.cmd  System.map-3.14.29  zImage  odroid aml_autoscript        boot.bmp         dtb.img              s905_autoscript.cmd  uInitrd           zImage aml_autoscript.zip    config-3.14.79+  initrd.img-3.14.79+  s905.start           uInitrd-3.14.79+ amlogics905x_init.sh  dtb              s905_autoscript      System.map-3.14.79+  vmlinuz-3.14.79+ The script files come from Balbes distributions.
 

Image update kernel from Hardkernel. Armbian_5.24_Vegas95_Ubuntu (the Test directory) note that these images can only run on a S905. The images that will be able to work on s905x s912 will be later (need to significantly patch the kernel). Features images-3.14.79. Problems with WiFi and sound. To change the screen resolution, you need to use a certain procedure.
 
1. marking the desired resolution in the file /boot/vegas95_init.sh
2. insertion of the selected permission to the file s905_autoscript.cmd (instead of the current parameter setenv m= "  ")
3. Precompiled script autostart system s905_autoscript. In this-you can select any standard solution available.
command
 
# mkimage -A arm -O linux -T script -C none -d s905_autoscript.cmd s905_autoscript
 
 
The existing problems are not working properly shutdown the TV box. After switching off, to enable, disable the power supply from the network.
 
 
 
As Docker is in the network repo Ubuntu, removed from the Assembly the old binaries. In-3.14.79 has support for Docker. Anyone can install it and use in this manner.
 
--------------------- translation  user Shimon -----------------
Here's the promised translation:
 
1. Look inside the /boot/vegas95_init.sh script:   Here's a sample: https://github.com/1...vegas95_init.sh   2. Find the desired resolution. For example, 1024x768p60hz https://github.com/1...s95_init.sh#L70   3. Replace the current value of the (setenv m) parameter in the /boot/s905_autoscript.cmd file with the new one. For example, the current value https://github.com/1...as95_720.cmd#L2   setenv m "720p60hz"   needs changing to   setenv m "1024x768p60hz"   4. recompile the binary version of the s905_autoscript with:   mkimage -A arm -O linux -T script -C none -d s905_autoscript.cmd s905_autoscript   On next reboot the selected resolution wil be used. Be sure to choose an exact value from the available list in vegas95_init.sh. Do not include the *) part. ---------------------

You can add a loop, for example as indicated in this thread, with the selected interval, and you can monitor the temperature in the terminal or the console UART.
 
http://forum.khadas.com/t/thermal-reading-wrong/168
 


while true; do sleep 1; cat /sys/class/thermal/thermal_zone0/temp ; done

 

The kernel sources for S905\S905X\S912 are in this GIT. The compliance branch in GIT the names of images and kernel versions.
 
1. images, the title of which stated "3.14.29" use - collected from branches S905X (universal - for the entire line of chips S9xxx).
2. Images - "3.14.79" - the branch odroid (this thread is only for chips S905)
3. Branch "armbian" - universal plan - for entire line S9xxx in an attempt to collect all positive elements   branches (Amlogic + Hardkernel + LE).
 
Pay attention to Assembly and installation\kernel for TV boxes is specific and different from the usual. I hope Marc (user Nofan Tasi) to share its successful experience build the kernel from source for TV boxes (including their details).

Tuned multiverse containing 5  desktop environments ICEWM XFCE, LXDE LXQT MATE.
Minimum media size of 4 GB. The user password is "user", "1", password "root", "1q2w3e4r".
By default, the system starts with MATE DE. To change the GUI you need to edit the file .xinitrc in the home directory of user "user".
Uncomment the line and comment out the current shell.

S9xxx_4G_ICEWM_MATE_XFCE_LXDE_LXQT_20170122.img.xz

https://yadi.sk/d/5_32km_EsCV2A
 
 
 
 
Request to those who try this system, write, run a different DE. Preferably, at least briefly to describe the speed of the graphical shells, indicating the model of the TV box (and brief parameters of iron). If possible, make a video recording of system response to user actions. It is important for me to understand what shell is better suited for systems with minimal resources. It is advisable to add screenshots of the output of the command "free -m" to the running shells.

For those who want to use MATE instead of XFCE.
 
1. Run synaptic
2. To install MATE packages (mate-desktop-environment-extras)
3. To create the user directory file .xinitrc
4. Add the line "exec mate-session"
5. After restarting, automatically start a GUI MATE.
 

Update images.
Ubuntu fixed activation ssh (now works fine on initial startup when configuring).
I decided to release these images before switching to a new version of the Assembly environment from which the removed Assembly of images with Debian.

IMHO TV boxes models MXQ - huge variety. They are very often counterfeited. So it is very easy to purchase a TV box, which looks normal, has excellent performance and low price. But in the end You get headache with high probability - a waste of money. To me many times appealed to different individuals, who have bought similar cheap TV boxes and who or what they are unable to run, and in the course of the trial , get a brick. That's very difficult to recover, because the manufacturer collected the TV box as a hodgepodge (of different components), has not provided any supporting drivers or codes. On these TV boxes can often only work with one exclusive stitching (from the seller). When you try to use others - get part is not working equipment (WiFi or BT or eth network or remote control, etc.). Therefore I can recommend only those models that are already tested in work. List of models You can find in this topic or in topics on freaktab.
 
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
 
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905x/598320-a95x-s905x-emmc-boot-for-ubuntu
 
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players

Setting the internal memory is possible. Before installing you need to check how much space system on an external drive and compare with what size does the partition /dev/data. Can be uninstalled from the system (on an external drive) part is not used packages and to clean from unnecessary files. This will reduce the required size of the internal memory. You can use the server version of the image, it requires less space to copy the internal memory. There is another extreme option to install to the internal memory. To change the distribution of internal (eMMC) memory in the dtb file. To unite all unused Linux partitions into one and install them Armbian.

Try to install in the eMMC option console image. Judging by the output of "df-h" the data size and the amount of free space close. Formatting creates a service directory "lost+" which can take a lot of space and not enough space for a full backup of the system. Alternatively, you can check install to eMMC, to start the system from external media , mount the partition /dev/data, delete all data, copy manually all the directories and files on /dev/data.
 
 
 
To add commands to the fdt in the script, you can use only the mistake of a script s905_autoscript. These commands must be executed on the processing stage u-boot.
 
 
 
You want to know, is possible to install in internal memory ?
 
 
 
 
Generate a new uInitrd needed when changing kernel or changing the composition of the modules required to run the system.

I've just given the latest Ubuntu image a test drive and I'm delighted to report it's much better compared to the one I've been using so far (20160625):

- the temp sensor as well as WiFI works out of the box
- no problem with ZRAM swapping, I was able to go up to 3G without any OOM kills whatsoever (@balbes150, you can safely make ZRAM the default, dispensing with that puny swapfile)
- persistent eth0 MAC address
- the kernel still only supports 1.5GHz max clock (instead of 1.6GHz)
- I was unable to free the reserved memory which used to work with the old kernel

For now, I've copied the new kernel to my own image and love the benefits

@balbes150 Could you suggest a proper way of integrating the fdt commands via the s905x_init.sh script perhaps?
 

This will probably sound pretty dumb question, but why can't we use the official kernel for arm64 ?
For exemple from here : http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.1/
And deb packages from here : https://launchpad.net/ubuntu/xenial/arm64 
(Not for kodi, it seems that we need version 17 https://launchpad.net/~team-xbmc/+archive/ubuntu/xbmc-nightly?)

Compiled a test version uInitrd in which activation of the screen occurs in two stages. Checked, according to my observations, in the spreading of the pictures (when failure of synchronization) this option allows you to normalize uInitrd image. Please to those who have the picture falls apart to check what happens to the image when you replace the FAT section of the uInitrd file in the new version. Note that in the spreading of the pictures at the time of system start-up, you need to wait for the full run that would have completed the second stage of activation.
 
https://yadi.sk/d/3mYLzUis34FwHz

mkimage -A arm -O linux -T script -C none -d s905_autoscript.txt "path_for_new_file"

just check this link: https://github.com/150balbes/Amlogic_s905

boot resolution in  s905_autoscript change txt file, then build binary... in my case this problem disappears after login...

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.

HI,
 
 
I would like to report that  the images Ubuntu 16.04.1  amlogic-S905x (server and desktop 18.12.2016 from balbes150)) are working on  Bqeel T12 (S912 2G/16GB). The system is booted , networking is working , wifi is activated. Xwindows is started, Firefox is OK There is no Kodi yet.
 
However, docker is not working due to the fact that aufs is not compiled (modprobe aufs failed) in the kernel. The source from In the /lib/modules/3.14.29 does not include fs/aufs. Given the fact that dokcer is working well with  Odroid C2 based  Ubuntu  image ( for example MiniMx S905 with the same kernel 3.14.29) , i tried to compile the support for aufs based on the source of this one. Unhappily there were too many errors (missing modules,..)
 
I would be grateful if the support of aufs could be integrated in the Armbian S905x/S912 version.
 
Thanks in advance.

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.
 
 
 

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

Last month, I have been Un Brick my TV Box, after i apply the sofware update notification, it make the TV Box only show Blank Black.... and its make me panic....
I never do Sofware Update anymore, and disable or cancel it when the notification is showed.
for now, if the current system or software doesn't have problem, i will not update it.