As far as I know, there are no working images for the Khadas VIM.

Does mainline u-boot support your device? This is a crucial step to easily enable your device.

Regards, Matthias

Hi Matthia Yes, you are right, now no ready-made image to run on VIM. I just want to try to build a test version of the universal image of openSUSE to run on the platform of the s9xxx (similar as done in Armbian). What version of u-boot You mean ? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

Unfortunately not. I barely just sent a patch for a second S905 device, no signs of S905X or S912 yet. The biggest question I am unclear about (and which needs testing/review) is whether new pinctrl drivers will be needed, or whether we might just ignore those drivers initially for at least serial.

The second issue is that my amlbootsig tool does not support S905X yet, so we couldn't build images in OBS, even if there were a U-Boot package. Both S905X and S912 seem to use aml_encrypt_gxl (haven't seen any _gxm), whereas the current state is based on aml_encrypt_gxb, and there was at least an initial @AML header not present on S905X. Even for S905 there's input differences between Hardkernel and FriendlyARM. amlbootsig does not block local testing with aml_encrypt_gxl of course.

Oleg, you can download a JeOS-rootfs tarball from http://download.opensuse.org/ports/aarch64/tumbleweed/images/ but it doesn't contain an initrd for its kernel; other images such as JeOS-efi or JeOS-odroidc2 do contain both. If you use your own e.g. linux-next kernel with built-in drivers you can circumvent the initrd.

Regards, Andreas

I checked the possibility to build and run from external media openSYSE on TV boxes with S905\S905X\S912. As it turned out, it is quite simple. You need to download one of the server images Armbian (you can use the desktop images, but they are bigger and there is no difference which image to take for the original). The choice can be used either with kernel 3.14 or 4.11. The difference in support additional items (USB, GPU, etc.). On s905X and s912 , for example Khadas VIM when using kernel 3.14 everything works, but when using 4.x will not work USB, ie you can use the control either via UART or SSH (although the graphics will be displayed on the screen, but you cannot type with keyboard or mouse). In S905 (e.g. at Tronsmart Vega S95), you can use the full both the kernel 3.14 and 4.11 (USB works). After you unpack and burn the image to media, you need to copy\save with the written medium, from the second section (ROOTFS) on the PC the directory /lib/firmware and /lib/modules and the file /bin/fbset. Then remove all directories and files from that partition on the storage media and write the contents the root of the archive openSUSE. Next, copy (to return back to the media) the previously stored two directories /lib/firmware and /lib/modules and the file /bin/fbset. When you use the 4.11 kernel, after copying all files, you can immediately begin to use the prepared medium as usual in multi-boot mode (details of how to activate multiboot on TV boxes, there are many forums and here). When using kernel 3.14 need to register in the autostart script run amlogics905x_init.sh (chmod 755). This script performs configuration and activation monitor-3.14 (without this, the screen will appear the image in this version of the kernel). Soon I will upload the finished images where everything is already done for you for system start up. Further set up and use openSUSE, you need to perform the instructions of the openSUSE WiKi. The user - root , password linux . -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org