Igor

Try rather this build - it's testing, which means no support - but wireless drivers should be in better shape. And remember, this is not Raspberry Pi.

It should look like this: Than: iwconfig wlan0 power off results in: Most likely kernel configuration also need some work.

Anyone is better than this. Stick to AMPAK/Broadcomm AP6212 Why not XR819? https://forum.armbian.com/search/?&q=xr819 It is performing very bad and even many people tried to fix this, not much success was made.

Even after you run apt update && apt upgrade ? (you need a working network connection)

I guess we will meet up at least on sunxi dinner

You both forgot to provide the most important info: Which kernel/system version do you use? We have a utility which helps to debug. Do update and run armbianmonitor -u

This chip is actually quite reliable. Is perhaps power management turned on? This has huge impact. Type: iwconfig

Please provide the output of: armbianmonitor -u

Probably module does not have power/wrong few config. But this chip is so bad that it is perhaps better to stay powered off

Probably the only way to bring it back to life is to reflash it with a stock Phoenix tools/firmware. A80 is not very well supported so there aren't any alternatives ... some very basic mainline support exists, but that's all.

You need to adjust numbers according to: http://linux-sunxi.org/GPIO#Accessing_the_GPIO_pins_through_sysfs_with_mainline_kernel

This is a community project and you can and should add it on your own. It is prepared to be simple: https://docs.armbian.com/Process_Contribute/#collaborate-on-the-project Edit this line: https://github.com/armbian/build/blob/master/config/kernel/linux-rockchip-next.config#L788 Wait up to a day for kernel automated build at beta.armbian.com repository.

This means BT is not up and operational. We just put this image out even few things are not fully operational since it can be used for most cases. BT will eventually be solved, but it's functioning is not our top priority. Unfortunately. This is the case on other boards as well. This comes usually when we have nothing else to do or somebody just provides a fix for it. I thought it was. Unfortunately, 4.14 has for sure broken and afaik also up. The current image is probably the best whats out there for this board.

If branch="default" then branch="" and fix double "-"

Just do apt-get update and upgrade. I'll also add new images in next days.

Yes, with one exception - the default is empty.

Check packages naming: https://www.armbian.com/kernel and make a script. Fixed armbian naming ($LINUXFAMILY) is stored in /etc/armbian-release

We have daily beta updates. It should be there by now.

Yes, reading documentation first would save both of us some time: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-connect-to-wireless

If you are new to this ... I replace images in download section (get Xenial desktop) - they have the same name - download them again. They have this fix implemented, but they are not tested.

Armbian desktop is currently available only on desktop images. Working on it to provide a package which would transform CLI image into our desktop. Still some work: https://github.com/armbian/build/blob/master/lib/desktop-ng.sh Only Xenial based desktop is available at the moment, while Stretch you need to build on your own. It looks and acts more or less the same. https://dl.armbian.com/cubieboard2/archive/Armbian_5.37_Cubieboard2_Ubuntu_xenial_next_4.14.14_desktop.7z

Two days ago a fix was submitted, but I haven't tested it yet. On self-made image it might just work. https://github.com/armbian/build/commit/c9dcb99b93cbd6373b6db1d3bbf90a5c256bd185

Strange. I booted Stretch CLI image on my Cubietruck, connected with eth0 ... nmtui-connect and connect to wireless. No problems. http://ix.io/EBc

Unfortunately, I don't have Cubieboard 2 while my Cubietruck (very similar) boots fine. Can you try this image: https://dl.armbian.com/cubieboard2/archive/Armbian_5.37_Cubieboard2_Debian_stretch_next_4.14.14.7z

Why don't you simply(!) use our build tools which creates a .deb package by using a proven(!) compiler and you only need to install it with dpkg? It limits problems. If you need to make changes, use a parameter CREATE_PATCHES="yes" ... if you are creating a patch for def_config, you need to compile twice since .config was already made.