balbes150

 
 
hi  it is my test armbian kernel 4.17 with my device wetek play 2  is  work  fine
 
 
hdmi work fine
ubuntu speeder
The graphics interface is running
wired network work
h/w video is Very heavy
sound not work
h

Image update Armbian kernel next 4.17-rc1 20180420 (directory “test” on the website). Now in the mainline kernel works HDMI, USB, wired network.

Test image Debian + KODI-18.
 
https://yadi.sk/d/goZiDfto3UV8UU
 
To run KODI-18 , you need to perform additional configuration of the system.
1. you need to remove the package “pulseaudio”
2. Switch to the test repository (disable all other repositories and enable "test" in the sourceslist file). Then install a new version of libc6-2.27 from the test repository).
After these steps, you can use KODI-18 as usual.

Test image Debian + KODI-18.
 
https://yadi.sk/d/goZiDfto3UV8UU
 
To run KODI-18 , you need to perform additional configuration of the system.
1. you need to remove the package “pulseaudio”
2. Switch to the test repository (disable all other repositories and enable "test" in the sourceslist file). Then install a new version of libc6-2.27 from the test repository).
After these steps, you can use KODI-18 as usual.

Test image Debian + KODI-18.
 
https://yadi.sk/d/goZiDfto3UV8UU
 
To run KODI-18 , you need to perform additional configuration of the system.
1. you need to remove the package “pulseaudio”
2. Switch to the test repository (disable all other repositories and enable "test" in the sourceslist file). Then install a new version of libc6-2.27 from the test repository).
After these steps, you can use KODI-18 as usual.

Test image Debian + KODI-18.
 
https://yadi.sk/d/goZiDfto3UV8UU
 
To run KODI-18 , you need to perform additional configuration of the system.
1. you need to remove the package “pulseaudio”
2. Switch to the test repository (disable all other repositories and enable "test" in the sourceslist file). Then install a new version of libc6-2.27 from the test repository).
After these steps, you can use KODI-18 as usual.

When started from the eMMC , the system uses the value "hdmimode" from the variable ENV (u-boot). You can change this variable using the "fw_setenv" utility (you can use the "fw_printenv" utility to read the variable), or you can use the UART console.

In this survey discussed the use of u-boot that goes into the composition of the image Armbian, which is recorded on the SD card. When i'm create an Armbian image, the build system automatically adds the u-boot image. This u-boot (from the SD card) is used to start the system only when there is no u-boot loader in the TV box itself or it is corrupted. In all other cases, u-boot is not used on the SD card. There are several variants of u-boot for different platforms (s905 s905x s912). On the SD card when building the image (in the image Armbian)  can only include one option. To use other options, you need to write it manually (replace the current one). Now, when i'm  create an image, it gets a variant of u-boot for s912. This option can only work on models with s912. Therefore, I want to exclude from the u-boot image. If the user needs (when he has a serious problem with his TV box, when the regular u-boot does not work from the internal memory), he will be able to download the desired option (just for his platform) and write it to the SD card.
 
 
In this embodiment, is used a regular u-boot from internal memory. This means your answer to question 2.

Have you downloaded the modules for WiFi ? Maybe your whole problem is solved with one command " modprobe ssv6051"

Image update Armbian 20180323 kernel 4.14.11 .
Works wired network, USB, monitor (you can change the screen resolution on the fly). The images are in the "test"directory.

Perhaps someone will be interested-a new version of Volumio 0.7_20180325  for S9xxx. It has audio output via a standard HDMI output. To use this feature, you must use one of two dtb files. For VIM1 (S 905 X) - "kvim_android.dtb" for the VIM2 (S912) - "kvim2_android.dtb". For those who use other dtb files, please write the names of the dtb files that you use. They need to make a number of changes to make them earned HDMI output.
 
https://yadi.sk/d/xbesnjYG3PETk5
 
details
 
https://volumio.org/forum/volumio-for-box-amlogic-s905-s905x-s912-s802-s812-t8028.html

Image update Armbian 20180323 kernel 4.14.11 .
Works wired network, USB, monitor (you can change the screen resolution on the fly). The images are in the "test"directory.

Image update Armbian 20180323 kernel 4.14.11 .
Works wired network, USB, monitor (you can change the screen resolution on the fly). The images are in the "test"directory.

Image update Armbian 20180323 kernel 4.14.11 .
Works wired network, USB, monitor (you can change the screen resolution on the fly). The images are in the "test"directory.

To run kernel 4.9 successfully, you need
1. New u-boot (it is used in firmware from Android-7).
2. The correct dtb.

Update image kernel 4.9.40 20180315

Update image kernel 4.9.40 20180315

Image works with SD cards and USB drives. Regular firmware in the device is NOT CHANGED. When you replace the dtb file can be run on any device with Amlogic chip S905 s905x s912   When you first start the system, the root user password is 1234   The minimum media size - 4 GB   https://yadi.sk/d/pHxaRAs-tZiei     Option how to start (Activation multi-boot).  
****************************************** Manual run Systems ******************************************

Now all images Armbian and LE has all the files for activate the multi-boot. Anything in addition to download and copy to media is not required.

1. Download the desired image
2. Unpack
3. Record an image on the medium
4. to run Android
5. open the app "Update&Backup"
6. Select local update and an archive on removable media (aml_update.zip)
7. Run update
8. System twice to reboot and start running the system from external media.
9. If after 7-10 minutes on the monitor not to receive any messages on system startup. Turn off TV box and add in manual in the first partition (FAT) the file "dtb.img". On the media there is a directory dtb from where you can take the files and copy them to the root of the renaming of "dtb.img".

Need to pick up the option for the file system will run. Pay attention, after you add\change the dtb file, you need to try to run the system and waiting to run 7-10 minutes. If not happened, repeat with a different dtb file.


Attention !!!! On models with S802 S805 S812. Activation multi-boot is possible ONLY with SD card (activation of the USB stick is NOT WORKING). After a one-time activation procedure is multi-boot, run a variety of systems is possible from ANY storage media (SD cards and USB storage devices).

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/606133-linux-images-for-s802-s805-s812-s905-s905x-s912-sd-usb-emmc   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  
************************************************** ************************************************** *******
 
The choice of shell to start (Mate\XFCE or KODI).
 
On the screen enter username and password (in lightdm) in the upper right corner of the screen there is a menu where you choose which GUI to run. The list will be three items (two rows with kodi) and the last line mate. Select mate (something opposite mate was the point), then enter the username and password. The system remembers the last selected mode. If at the next login or what not to choose in this menu, system at the entrance will trigger the option that was turning off in the previous session.
 
 
Install to eMMC (NAND)
 
    To install Armbian in the internal memory, you must execute multiple commands. We strongly recommend TO PreRUN create a full backup of the entire contents of the internal memory. This will allow you to return to the current state of the firmware at any time. To create a complete backup you need to execute commands.
 
su -
(enter passwd root)
ddbr
 
The running tip backup script
 
After creating the backup, to install to internal memory (eMMC) of the command being executed
Pay attention, if you not are sure that you will be able to solve possible problems from the installation of the internal memory (eMMC), do NOT PERFORM these commands.
 
su -
(enter passwd root)
./install.sh
or
nand_sata_install
 
 
Setup HDMI out.
 
The configure script video output hdmi.sh reside in a directory on a FAT partition (on a running system, this partition is automatically mounted to the /boot directory). This script can be changed. To change the screen resolution from 720p to 1080p, you need to uncomment the line "#mode=1080p60hz" and comment out the line "mode=720p60hz". Similarly, you can change the color depth from the default 24 to 32 (bpp=24). Note that with 32 bit color significantly changes the desktop. In this script you can place the commands you want to run WebMin , Doker, ask line to run the USB port (if necessary), configure, sound card, etc.
 
On Wifi.
 
run as root user one of these commands in the terminal
An example command to load module “dhd” or “wifi_dummy”
 
modprobe dhd
 
or
 
modprobe wifi_dummy
 
After verification of the selected module, if everything is working correctly, you can add it to the autorun list (add string name of the module in the file /etc/modules).
 
 
Remote control.
 
Added support for remote control. To use it you need to add the correct file “remote.conf” in the /boot directory or /etc/amremote. By default, a part of the image includes several predefined files (in the /boot directory). To use it you need to rename one of the files in “remote.conf”. Additionally uploaded the site to the directory the deb package “amremote.deb” , which can be installed in the old system (do not download the whole image). After installing this package you need to run service “amlogic-remotecfg” and add (rename) the correct file 'remote.conf".
 
Auto login
 
Add line to /etc/lightdm/lightdm.conf.d/11-armbian.conf
 
[SeatDefaults]
autologin-user=username
autologin-user-timeout=delay
 
 
Additional information
http://forum.khadas.com/t/armbian-kodi-ubuntu-debian-for-sd-usb-emmc/825
 
 
 
Wiki Information to enable multi-boot on the WiKi is outdated, use to activate the multi-boot description from this post in the beginning. https://github.com/150balbes/Amlogic_s905/wiki  
 Other versions of images with different Linux systems.
 
https://yadi.sk/d/5_32km_EsCV2A

fixed for image Armbian Ubuntu Mate 20180307
The remote works in the image 20180305, you need to use the correct dtb file.
 
 
 
It is a complex system (DE + KODI). To change the screen resolution ONLY in the file /boot/hdmi.sh.
 
I don't have s905w.
 
 
TO ALL
fix system menu for aml-kodi-ubuntu_5.41.deb

Thanks @balbes150. Tried your last images. Running 5.41 20180305 (Mate) on a s905x device (Mini M8SII) from internal storage and found the following problems:
IR remote doesn't work anymore. Placed remote.conf in /boot/ and /etc/amremote without any effect. The amlogic-remotecfg service is not running, because /dev/amremote cannot be found. There are also no LIRC devices in case you've moved to LIRC for IR support. Adjusting screen resolution in /boot/hdmi.sh (1080p60hz to 720p60hz) is partially failing. Case scenario: Running 1080p out of the box without adjustments after flashing: everything works fine. Kodi and desktop environment are running in 1080p. Changing 1080p to 720p after flashing and first boot: KODI works fine and runs in 720p, desktop environment shows artifacts and seems to be running in 1080p. Changing 1080p to 720p after flashing and before first boot: everything works fine. Kodi and desktop environment are running in 720p. Same effect when running the image from SD and USB stick.
 
//edit
Maybe I'm doing something wrong. Can't get remote working on mate 20171226 either (which worked fine before). Perhaps I'm forgetting something.

Update image Armbian 3.14 20180305
 
Updated the KODI-17.6 package for Ubuntu and added the KODI-17.6 package for Debian. Now these packages can be installed on any system (Server, ICEWM MATE\XFCE etc).
 
If install KODI-17.3, remove all old packages starting with “aml -*”.
 
Download and install the command "dpkg -i " new packages
(aml-amremote_5.41_arm64.deb aml-codec_5.41_arm64.deb aml-mali6_5.41_arm64.deb).
To install the new version KODI-17.6 aml-kodi-debian\ubuntu package, use the command
 
for Debian
 
apt install -f /full_patch/aml-kodi-debian_5.41_arm64.deb
 
for Ubuntu
 
apt install -f /full_patch/aml-kodi-ubuntu_5.41_arm64.deb
 
to install all the dependencies.

The test version of the KODI-17.6 (for s905\s905x). Important warning. This version is built on Ubuntu, so when you try to install on Debian libraries may not be suitable and you will have to manually install the necessary packages and create the necessary links to these libraries. In the future, I hope to build a deb version of the package for Debian as well. The order of installing the new version on the previous images.
 
1. To remove all packages with for version 17.3 names that start in aml-* (amremote, mali, kodi).
2. Remove the package "libasound2-plugins" with all its dependencies (**this is important**). Corrected. This item does not need to perform.
3. Restart the system.
4. Install a set of new packages at this link (aml-remote aml-codec aml-mali6 aml-kodi).
 
https://yadi.sk/d/NoKnDPJL3SxzbK
 
5. Restart the system.
 
After these steps, you can test the new version of KODI-17.6.
Please note-this is a test version and there may be errors. You can go back to the previous version of KODI-17.3 (remove the new packages and install old versions of packages).
 
 
Update Armband images for s9xxx 20180303 .
In the image with Ubuntu Mate now uses a new version of KODI 17.6 (for s905\s905x).
 
https://yadi.sk/d/7iYtTCRh3SyBZT

Fix Boot Wifi with some hacks and a Init.d Script
The Problem : Cant boot with Wifi Kernel Module
 
After many hours of try and fail (almost fail),
I resolve the problem of Boot with Wifi with lots of pacience and despair,
and the precious help of @balbes150 and @guidol, and Armbian Forum
 
The above "solution works" with
+ AlfaWise H96 Pro+ and
+ 3.14 Kernel Based` image (thank for the tip @balbes150) > Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_server_20180225.img.xz,

belive me its not pretty/elegant solution, is more a despair solution........
 
First remove all modules from `/etc/modules` to leave it initialization for `init.d` script clean,
I leave the comments, just has a note of my adventure in /etc/modules file LOL

 
$ cat /etc/modules #aml_nftl_dev #wifi_dummy #cfg80211 #dhd #wlan Next Create a `init.d` hacked script, with some magic and optimized sleeps, without that sleep times or with lower times it wont work,
Its very strange, I must load and unload module, and reload again, but its seems the only way to put this working,
I know its too strange, and hard to find, maybe someone has a better ways, I believe with some knowledge its easy,
 
Why its working only that way? 
don't ask me why, I don't care, for me its not pretty, but its ugly and working,
I'm happy with it, who cares, I don't waste more time for an elegant and pretty solution......
 
move on.....the `init.d` script
 
$ sudo nano /etc/init.d/wlan #! /bin/sh # /etc/init.d/wlan # ### BEGIN INIT INFO # Provides: wlan # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: AlfaWise H96 Pro+ Wireless Boot Script # Description: This file should be used to construct scripts to be # placed in /etc/init.d. This example start a # single forking daemon capable of writing a pid # file. To get other behavoirs, implemend # do_start(), do_stop() or other functions to # override the defaults in /lib/init/init-d-script. ### END INIT INFO # Some things that run always touch /var/lock/wlan # Carry out specific functions when asked to by the system case "$1" in start) echo "Starting Wlan Script" echo "modprobe wlan" /sbin/modprobe wlan echo "modprobe wlan -r in 28sec..." sleep 28 /sbin/modprobe wlan -r echo "modprobe lan in 28sec..." sleep 28 echo "modprobe wlan..." /sbin/modprobe wlan ;; stop) echo "Stopping script wlan" /sbin/modprobe wlan -r ;; *) echo "Usage: /etc/init.d/wlan {start|stop}" exit 1 ;; esac exit 0  
After boot inspect unload/load driver with
 
sudo tail -f /var/log/syslog | grep wlan  
Install systemd service
 
$ sudo systemctl enable wlan  
reboot to test if work
 
$ sudo reboot  
in other pc ping the wifi ip and wait it responds without do anything, here it starts respond after 2minutes, not bad since reboot, shutdown and boot
 
I tested with a lots of combinations, modules, timers, I don't know the things I try,
but for me it only work that way on boot, maybe someone with knowledge can explain why this driver don't boot, or boot in a state that is faulty, and useless, and must be up, down and up again with this sleep times......
 
some info after login

 
$ lsmod Module Size Used by wlan 3435325 0 zram 8953 8 cfg80211 415017 1 wlan ch341 5434 0 I anybody has questions, say so

thanks to all 

Will this help???
 
 

Better way. You can count on me to try with S905X in MXQ Pro and pro plus.