balbes150

To enable BT. You need to perform two steps. 1. Add to /etc/modules to list the module hci_uart 2. Add to the end of the initialization script (/boot/amlogics905x_init.sh) string su -c 'hciattach /dev/ttyS1 any' After a reboot should turn on BT. Information taken from this instruction The remaining steps in this manual you do NOT need to, everything you need is already in all desktop images Armbian. http://forum.khadas.com/t/add-bluetooth-support-for-ubuntu/593

As it turned out, with Odroid C2 works perfectly dtb file meson-gxbb-p200-lan (it's on the website, along with files of images). This dtb file works USB , wired network and video output (all three essential ingredients for successful start and run the desktop version).

For owners Odroid C2 , which have a fine-tuned system (any) on the SD card or eMMC module and want to try option Armbian with kernel 4.11+ (MATE\XFCE or server) without risk to the existing system. There is the option of running the system from USB stick (available at SD or eMMC system remains unchanged). 1. To download the correct image to the link https://yadi.sk/d/kZHc0uQE34z5jR 2. Unpack 3. To record on a USB flash drive (the size of the flash drive of 4 GB, the parameters of any). 4. Download and add on the USB flash drive file dtb for the Odroid (file in the place where site the images) 5. Rename the recorded file dtb to the "dtb.img" meson-gxbb-odroidc2.dtb 6. To add to the run settings file u-boot (for SD or eMMC media boot.ini) the second line in this string. --------------------------------------------------- ODROIDC2-UBOOT-CONFIG # Add run USB script s905_autoscript if usb start; then setenv dtb_mem_addr "0x1000000"; if fatload usb 0 1020000 s905_autoscript; then autoscr 1020000; fi; fi; ######################################################################## # Changes made to this are overwritten every time there's a new upgrade --------------------------------------------------- 7. Off Odroid C2 to connect the SD \ eMMC media with the main system and USB flash drive with the test system 8. To turn the power on. If done correctly, and 5-7 minutes on the screen you should see a standard login prompt for initial setup Armbian. When you turn on Odroid C2 without the Usb stick will automatically start a regular system. If desired, you can modify the line to boot.ini under run multiple systems with USB and SD\eMMC media. For example, to have the main system on the eMMC and run the same test with the SD card. p.s. During the test, I found a periodic problem with the dtb file on the website. If the dtb file from the website will be error, you need to try to use the dtb from the image from the catalog dtb. He's working with wired network (you can connect via SSH), but there is no video output on the monitor.

If You are using the image Armbian, need to replace u-boot. Now all images Armbian uses u-boot for S905X (it is not suitable for S905). There is infa, how to replace u-boot. You need to use u-boot to s905. https://github.com/150balbes/Amlogic_s905/wiki/s905_Unbrik_Amlogic_S905

Describe in detail what steps were done to start the image Armbian. PS If You have a console UART, I think you can run an external system.

I have my doubts that for Your card to get the standard version activation multi-download. It is designed to use u-boot, which is located in the internal memory. You have u-boot to be on an external drive, I'm not sure that this u-boot (which is located on external drive) you can add the desired variables to multi-boot. Typically, the uboot that is on external media that has no variables you can change (all variables as fixed in itself, u-boot and can not be changed). That's why I asked about the console UART, to check if there's a way in uboot to remember Your new variables. For u-boot which is used You need to collect a new version (with support for multi-boot). I tried to open the source code of u-boot from Your Board - it is not available.

What specific image did You try ?

Tested on Odroid C2 system startup from the USB stick (via script s905_autoscript, I prefer to run existing images without any modification). If add the script to the boot.ini a few lines, you can run images from a USB drive. This can be useful if there is on eMMC or on a SD card configured with the system and felt the need to run temporarily another system (without overwriting the existing SD\eMMC media). For example, for temporary checks new images, when unknown , to like this system or not, or for testing settings\software-that-be not to destroy the already set up working system. Process start automatically if the connected USB drive and it has a script that starts the system with the USB. When no USB media run regular system with SD\eMMC.

You have connected to the console UART ?

You have written the SD card with Android ? What files are in the first section (if you connect SD card to PC and see its contents on a PC) ?

I don't know what principle is download the uses on this Board. So what I say may be incorrect. You can try dual boot. To install the factory system (Android) to SD\eMMC card. Armbian to record to a USB stick. If on the media with regular Android, there is an external control script (similar like in C2 there is the Odroid boot.ini), add a line with the start of the script s905_autoscript (as is done in the multiboot).

What's stopping You to try the existing options to S905 ? p/s I don't know how compatible the hardware of this Board with other platforms.

Without these settings on my Vega S95 does not work wired network. As far as I know, there no full support for WiFi in this kernel version. When building image automatically are going to need a dtb packages. If needed, I can additionally download. But keep in mind that the images appear changes that can't pass through the packets. The best option to test - build your version of the image in place or build the kernel. For this you need to build binary files with support for acceleration. In a regular network reach such packages no. All threads in this section dedicated to this.

You need to use the dtb files only part of the image (from a catalog dtb). There is a file to s905 (meson-gxbb-) and for s905x (meson-gxl-). All the old files (from the firmware) or version 3.14 - new kernel not working.

In the file /etc/modules describes what to load at startup. It can be edited to suit your needs. To remove unnecessary modules or add new ones. If the module is loaded automatically - you can make it to the block list (how to do it is described on the Internet for the desired distribution).

This dtb file only applies to version the latest test images (test\20170423). In these images the latest kernel version 4.11.0+ (source from Neil Armstrong). These images are based on kernel contains a working version of HDMI (the monitor). The original boxes with S905 (Vega S95 , MXQ ) is a complete desktop, USB works (mouse and keyboard), running a wired network. The system successfully starts from USB drives and SD cards. Thus, I believe that it is almost working system kernel 4.x for office and server use. While there is one (for me) the problem is not working USB chips S905X and S912, which does not allow to use these images as desktop. By the way. I have a request to all is to try to run those images on their TV boxes and write results. This will help to accelerate the development of a new kernel on Amlogic platform. Obtained information I will give Neil Armstrong and the rest of the kernel developers.

How justified are the costs of time creating this image ? I will look at them. Try the latest test images, there are different variants of the dtb. And you can try to add Your patches.

Added to the website for more dtb file with fixes to work wired network 1 GB S905. For image kernel 4.11.0+ (dir Test) meson-gxbb-p200-lan.dtb

1. Try using the image Ubuntu. 2. Disable the download of WiFi module in Debian and try with dtb n200. We must look at the source code, I don't know what is there.

Added a new image test\20170423 kernel 4.11 (a link to the discussion of the kernel on the forum Khadas VIM). http://forum.khadas.com/t/state-of-linux-mainline-opengl-on-s905x/497/13 It has an output on the monitor. Pay attention that s905x USB not working yet, so the picture is there, but mouse and keyboard do not work, can only be controlled via ssh or UART and the launch is possible only with SD card. When choosing dtb recommend to check all the options files (for your platform). S905 works on USB so you can run a full desktop with mouse and keyboard and USB drives. Details and other images will come later (as long as there is Assembly, testing and loading).

This image contains more settings and files that cannot be obtained through an update.

Image update 20170421. Added to the library libMali (for fbdev). Please check the Firefox browser with file playback at resolution of 1080p. I have to check we have an odd situation, tried full screen youtube videos , like playable, but only if choose the 720p (screen resolution is set to 1080p). The temperature in armbianmonitor shows about 50 Degrees. I'm not well versed in matters of videoscoralie. I'm not clear whether acceleration is working, whether this effect is from something else. For work acceleration in the video (mpv vlc etc) it is necessary to recompile with support for Mali r5p1-01rel0 . I have not yet figured out how this is done in Ubuntu (something to build the package). I would be very grateful if you could drop links to instructions on how to do it. test link I found a video which offers a 1080p

Thanks, I will check the use of these patches. test image server 20170414.

Try that does not change in the TV box (leave activated universal multiboot from Armbian) and write to card LE and try to start the system from the card LE. If the LE to start , run fw_printenv via SSH and show me the output.

An updated version of the images 20170414. In these images added the ability to automatically use the built-in dtb out of internal memory. If no existing media file "dtb.img", the system tries to load the dtb from the internal memory. This feature is only being tested. Please to those who have the opportunity to check this option. Note that due to the fact that in the last image is the latest version of the kernel, dtb built-in data can not work properly. For example, I have on Tronsmart MXIII Plus when using built-in dtb data from the LE, the system starts normally, but the monitor does not display a picture (in this version I run via ssh and UART). It is important for me to clarify how to work this feature on other models with different firmware. The important thing is that we could start the total system (that you could connect via SSH or UART). If this function is startup dtb data from the internal memory, will be able to work on all models, then there is a chance to have a universal system.