If the Wifi worked on the multi-DM, and then ceased to work in it, then the cause is most likely not in the software. Perhaps You changed something in the router settings or it ceased to work Wi-Fi. Have you tried to restart the router ?
Hi RDFTKV
I hope soon to write a small report about what I have done with VIM. My first impressions were rather interesting device, the first thing I liked - the design principle of the modular housing (its easy to change with minimal cost). The current design needs some work, but it’s easy to do.
I checked this running Mate - Armbian_5.24_S9xxx_mate_Ubuntu_xenial_3.14.29_desktop_20170205.img from SD card.
There does seem to be a problem.
The network manager sees the WiFi module(device wlan0) and shows a MAC, but does not see my networks.
Under the notification area, network connections, WiFi is greyed out.
After many attempts to setup the network manager, no go.
Also could not use the WiFi module as a hotspot, shows device wlan0(and MAC), but nothing actually happens
Also will not pickup an unsecured hotspot provided by another TV box.
Sometimes network notification reports eth0 connected, even when no Eth cable is connected.
I think I will download the image again and re-burn the card.
Checked the latest image. Downloaded from the website (something to make sure that the file on the website is not corrupted). Recorded on the flash drive. Launched on VIM. Then show a video of my actions. The system found the available network, I enter only a password to connect. Pay attention - I not change Android, I just added multi-upload (via UART console, it’s easier and immediately see the result). The dtb file is used from internal memory. Maybe you have to handle the case could disconnect the antenna or broke the contact. Or use the dtb that is different from the regular one. Either the router is spelled out binding to MAC to the address, and he changed. Ideas from me yet.
Pay attention, for those who use my images. I found the cause of the fall core at a temperature of 70 degrees in the images Armbian is a module “mali.ko”. Remove it from the system (for old images). On the website under Linux\Armbian\Test an updated version of the image MATE (20170228) with the correction (without the module “mali.ko”) and a few patches that improve the core.
p.s.
Image MATE 20170205. Removed the module “mali.ko” . Under load (without fan) the temperature reaches 80-82 degrees - the system does not fall, continues to work.
Images are downloaded from Debian. After some time they will be available. The version of the image with ArchLinux is on the site, but it has not been updated because no one asks about it. By the way, in the near future (after testing) images from the Test directory will be moved to the main directory, because I have limited place. If anyone needs the old version - download now in the future I will delete (to make room for new).
New image (Test 20170303) correction module mali. Checked on S905X - everything works, the temperature is over 70 degrees, the system is not falling. Please check at home. Please check the work WiFi network.
All images Armbian default has a built-in u-boot. If no eMMC in u-boot, the processor should use u-boot from SD card (from armbian).
You need to rename the file s905_autoscript in aml_autoscript (replace the existing file with this one).
I just keep getting
GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;LOOP:1;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;LOOP:2;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;LOOP:3;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;
ok it seems like the image contains uboot.bin and not uboot.sd.bin which is necessary for sdcard boot. flashing that and renaming the autoscript did the trick