Update image ArchLinux + KODI (S9xxx_ArchLinux_20170914_3_14_29_KODI.img.xz).
After unzip and write the image, copy the correct dtb file. The new image is used KODI-17.4. Added support for remote control. To use the remote control to rename the file “remote.conf.vim” in “remote.conf”. Pay attention, as it is a ready image, there is no automatic extension of the second section on the entire media, it has to be done manually (e.g. using gparted on a PC). After system startup, KODI starts automatically (in manual start or what not required). All the network settings and WiFi needs to be run in a production system (exit KODI, login as “root” password “root” and run the setup, restart the system or through an SSH connection).
hello I wanted to ask you if having the remix os mini sources you can conpilarne one for the vim?
in the positive case the remix sources mini - remix os 2.0 are here
github.com3
JideTechnology/remixos-kernel
remixos-kernel - linux kernel source used in Remix OS
VIM-3 ???
Such a model exists ?
This image is only for model VIM-1 (chip S905X). If it is about the VIM-2 (chip S912), the image will not be on the VIM-2 to work.
The extension of the secondary section - for this you need the PC to run a special program (for Linux, you can use the GPARTED program) and increase the size of the second partition on the media in the available space.
Updated kernel, now works HW when playing video. If artifacts appear on the image, you need to move your mouse. These artifacts are from the output to the console of service information. I have not yet found a way to disable the display of this service information. Please ask those who have 4K equipment to check how 4K playback works.
Hi, balbes150! I’m quite new in this, so would you mind explaining step-by-step how to install your image of Arch Linux MATE onto Khadas VIM Pro? I tried using USB-C cable and windows USB burning tool with no luck. When it checks image it says that image is not valid (or something like that).
I’m using Arch Linux on my desktop, my son is on windows.
These images are not for the USB Burn Tool. To run them, you need to use an external media (SD card or USB flash drive). Download, unzip the archive, write it to the media (note, do not copy the file, write the image to the media). Add the correct dtb file. Activate multi-boot once (and the system will automatically start any systems from external media). Details of running different systems from external media and video activation of multi-boot you can find in the topic about Armbian. The principles of use are the same. Option with KODI-18 I’ll look (if not removed it).
If you have a UART console, you can try to replace the system in eMMC with ArchLinux. Or return a full-time Android and complete the setup procedure using the script “install.sh”.
Start with restore the regular firmware and run ArchLinux with external media. For simple (without using the UART console) installation of ArchLinux in eMMC, you need to change the script “install.sh” (under the features of the ArchLinux directory structure, I will write how to do it), add the package “abootimg” to the system (make and install “abootimg” it in the ArchLinux System running from external media on VIM) and add a file option “fstab” to work from eMMC. By the way, after that, you can make an image for all users with a simple installation procedure (as it is used in Armbian) from the system received from you on the external media.
