Igor

Don't worry. It works You only need to run hostapd with multiple configuration files.

Yes. No other way.

Armbian Bionic stock settings are set to Network manager override: https://github.com/armbian/build/blob/development/lib/distributions.sh#L278-L282 /etc/netplan/armbian-default.yaml network: version: 2 renderer: NetworkManager ... which means the default/preferred way of connecting to the wireless (nmtui-connect) works out of the box. On the other hand, Netplan is quite handy.

Those images are a pile of crap and not supported. Hit the download button above or just pick your board here: https://www.armbian.com/download/?tx_maker=xunlong Then proceed with https://docs.armbian.com/User-Guide_Getting-Started/ and if nothing will work out, we might help you. If you would read at least comments below http://www.instructables.com/id/Orange-Pi-PC-Get-Started/ you would already do that.

Yes, you do. Sometimes, rarely we push update only to some critical sections. In this case, only armbian-config was updated, while Armbian internal number or a majority of packages remained the same. A version number is taken from BSP (board support package). This means it won't change until that package gets an update. This usually happens at the major upgrade. Nothing to worry. If you find some specific problem with armbian-config, the best way is to open an issue ticket here: https://github.com/armbian/config/issues

Agree. Technical wise this looks very nice, while the rest. Time will tell. We have spoken Hauk!

There will be more and more vendors using ARMBIAN as a reference because good support is one of the most important selling points. They will use "Armbian (will) support(s) ..." in their sales speeches even it's a complete fiction. Sales are not engineering We can't do anything if they use that. A threshold for legal actions for abusing trademark is pretty high, it is a lot of work and it is not worth the troubles. It's sad that they (and others) will just use this solo for their gain without asking and giving something in return.

Switched. Let's see if it's any better but ... they can disable it.

I think all Odroid's have 1.8V TTL logic https://forum.odroid.com/viewtopic.php?f=53&t=4758

With serial console to see if thingie was booted with a new u-boot. I assume you don't have one?

DEVICE=/dev/mmcblk1 dpkg -i linux-u-boot-next-odroidc2_5.45_arm64.deb

OK and check PCB. I've moved related posts to a separate thread.

They have different bootloader bl1 and adjusted u-boot to support 2G memory. If you don't have 2G of memory or memory has some different configuration, which is extremely unlikely, than this can make troubles. The rest is the same. I know that T3+ image doesn't boot on 1G boards (M3 for example). Your board looks the same, but I did a picture to double check. How do you power the board? I use lab PSU 5V / 5A Running low on ideas. This is serial console log - try to catch something on yours:

That is normal. How long did you wait until declare it doesn't work. It takes 17s from power on until I get a login prompt (Sandisk Ultra Class 10/average SD card). I agree that we should set some verbose output by default but hey, Rome was not built in a day. Bootlog: http://ix.io/1aP5 This image: https://dl.armbian.com/nanopct3plus/Ubuntu_bionic_next.7z

That is strange. I am highly confident that both found here: https://www.armbian.com/nanopc-t3-plus/ has been tested. I can test them again later in the evening. Currently out of office. Can you make a PCB photo and/or get revision number.

With the image for M3? Yes, that is normal. it does not work. Image for T3+ works only on T3+ Please drop URL to the image which you tried?

Fixed but a bit different since it doesn't work the way we have before.

It seems they are not sorted at all - as they were added. We had many troubles with this plugin so my modification: manually order by importance without showing exotics - fell out. All variants have advantages and disadvantages. I'll adjust that asap.

Gone automatically with the last forum upgrade. Haven't figured out why.

There are some issues with K2 u-boot, which is still WIP, but in general S905x boards are decently supported now.

What? Is it broken? Last time I was playing with this feature it was working. At least on recent images made from the development branch.

Hotplugging might not work but when you boot you should get a screen. I don't recall any troubles of this kind. Try another cable.

https://github.com/armbian/upload/commit/761f38516873149506f886eec78abcf65653ffc6 apt update & upgrade on the stable branch. Nightly building still offline.

Mount it on some Linux machine and peek into /boot https://github.com/armbian/build/blob/master/packages/bsp/armbian_first_run.txt.template

I didn't notice. Perhaps enabling it would help? https://github.com/armbian/build/commit/c1cb1d77f0812978160506de9646c352df0c9d48