Igor

Forget about using this wifi. It could be the worst chip ever made The only real solution is to use some USB based wifi, Realtek 8811AU or 8812AU is recommended.

- booting modern kernel is not supported. But ... support for NAND exists in a modern kernel. I am not sure if this is true for u-boot and if things are production stable. In any case, rather get some solid SD card. Its more reliable and faster than NAND. - transferring system from NAND to SD card is also not implemented. Manually it is possible to move the system back to SD card, but again not recommended. Usually is better to start with a clean image and transfer your application+data there.

You can edit boot.cmd (and recompile to boot.scr), but it is not recommended if you are not confident in what you are doing. It is possible that this feature is broken for this board. Since this is nothing critical, I guess nobody pays attention. Thanks for pointing this out. Will be checked why is this so.

Login as root and run: apt install armbian-firmware-full or manually it that won't work - check this: http://mitchtech.net/realtek-wireless-dongle-rt3070-on-the-raspberry-pi/ Remember to reboot or reload the module.

DVFS part will receive some changes (AFAIK refactoring) since it is not working as it should yet. Nevertheless, a kernel is good enough for testing, perhaps even for use. Remember, it is a first "stable to be" build ... (not so big) problems are expected.

Done, default 4.4 kernel was also upgraded with upstream patches and tested.

Fixed upstream so now it's safe to update. Those who ended up on a dead board, this is the way to recover: 1. Get some older image and boot your C2 2. Download this file 3. Attach SD with card reader and make sure your SD is /dev/sda1 (disconnect other devices or check with dmesg too see where it was assigned to and adjust commands appropriately) 4. Write u-boot with command: DEVICE=/dev/sda dpkg -i linux-u-boot-odroidc2_5.40_arm64.deb 5. Boot with a previously dead SD card

Graphics driver is here for some time, first a simple one, now DRM, but it is still under development. If you mean video acceleration, then its what @gnasch pointed out. BTW. HDMI out is usually disabled on board that doesn't have it.

armbianmonitor -u for a start would really help in this case. USB ID will tell what driver to use.

eMMC support was recently added to this kernel and that could trigger this problem. Not sure ATM. When reporting a problem it saves time if people add their full logs, preferably with armbianmonitor -u .Sometimes a quick scan can already provide an answer.

Is this problem related to specific kernel, 4.4.y / 4.14.y?

This is far from kernel hacking or any serious involvement in electronics - it is only a serial console, 3 wires connected to board and USB to your desktop computer. This basic (debug) tool is sometimes the only way to proceed on boards without HDMI and a network. "Normal" users do accept advice and we just try to help them the best way we know.

Broken network or nothing at all?

Well, then setting $KERNELBRANCH="tag:v4.14.16" in userspace/lib.config might temporally solve this issue?

Unfortunately, Orangepi Zero wireless (check our frustration with forum search) is half broken and there is nothing to do about. We lost hope that this crappy chip will ever be fully usable. Stay away from wireless chip labeled XR819. Use some external USB or any other board but beware none is capable of handling many clients.

It's possible that some patches are obsolete/broken. Can you provide a patching log? You can find it in output/debug folder

Not necessarily. Did you check if there is an error before that? Build script end-user support exists if you don't touch the build script - except in user configurable areas. I don't know whether we have a problem or you made one.

Probably headers install script patch is not the correct one. It needs to be investigated closely. We don't provide headers package by default since some time and if they are default enabled, this is by mistake. If you don't need them, remove them and update should go with a normal speed.

Remove or commend hwaddress line in /etc/network/interfaces

Those "nightly" are automated builds, currently, on hold since we know its pointless to make them. Absolutely no idea if those old ones boot at all. They are made for developers and those who wanna try how far things are ...

Nope, unknown to this moment. Can you try to get some logs? I assume you are running kernel 4.4.y?

Thanks. We are using those sources: https://github.com/aircrack-ng/rtl8812au ... check if its already fixed, then we can bring them into the kernel and push an update.

This board at this stage is probably not the best for absolute beginners. You will only find yourself frustrated. Start your explorations with previous versions (preferable H3 Orangepi PC+), which are decently supported with Linux, Openelec, Android, Retrogaming, ... And here we are mainly - if not strictly - focused on (Debian like) Linux experience. Android or proprietary Phoenix tools are mainly out of this interest zone. But anyway, welcome for trying things and not being an absolute beginner anymore

I haven't noticed anything like that but this doesn't mean it is not present. There is only one way - to test closely but I can do that fastest once next week. Odroid kernel doesn't have support for 8814au either IIRC, only 8812au.

Thanks. Added, let's see.