Igor

For serving and running tvheadend (for example) any SBC with mainline kernel should do the job, while for playing content - those which have good KODI support. Don't operate much in this area so I can only guess that C2 might do the job? If you go into two board setup, than you have more options since Open(Libre)elec works ok also on H3, Imx6, ... Don't know anything regarding 264/265 codec support diff.

AFAIK I2S works in this kernel, but its not enabled by default and we usually can't give more than usable hints - solving problems takes more effort, chunks of time - at least a tests on real hardware should be done, to suppress time wasted on future support.

NAND is only supported with legacy kernel. Doing quick search: https://docs.armbian.com/search.html?q=nand (our) Debian Wheezy is long time not supported anymore, but you have plenty other options: https://dl.armbian.com/cubieboard2/ For NAND support look for those with "default" in the name. ... but rather ditch NAND since it's slow an unreliable compared to most SD cards you can find on the market today and use modern (NEXT) kernel.

Note added to download page - I can do tests but only for next few days, than I am notebook only for some time.

What about to provide a separate pinebook-hdmi dtb file? I already searched to understand how to enable hdmi but not found. OK, will RFC. Loaction of this file https://github.com/armbian/build/blob/master/config/50-pine64-pinebook-touchpad.conf is also not very logical. Where should we collect such things?

Release candidate latest fixes + this regarding audio on resume, touch pad and kernel upgraded with upstream patches. Download: (touch pad fix not included) https://dl.armbian.com/pinebook-a64/Ubuntu_xenial_default_desktop.7z What about HDMI out - how to use it?

I know, php7 is stock on Ubuntu Xenial and Debian Stretch. Use php5

Try simply without a number. Beware that running scripts on more recent php7 could lead into problems. There are some incompatibilities which are hard to solve for somebody without experiences. I would suggest you to stick to Debian Jessie and it's stock php5 ...

SPI is build in - not as module. https://github.com/armbian/build/blob/master/config/kernel/linux-sun8i-default.config#L1935-L1942 script.bin/fex is where you enable and disable it.

My quad boot fine, but since you have double and we don't have auto detection ... focus on this part of the boot script: if load mmc 0 0x00000000 /boot/.next || load mmc 0 0x00000000 .next; then setenv fdt_file "imx6q-udoo.dtb" ext4load mmc 0 ${fdt_addr} /boot/dtb/${fdt_file} || fatload mmc 0 ${fdt_addr} dtb/${fdt_file} else setenv fdt_file "imx6q-udoo-hdmi.dtb" ext4load mmc 0 ${fdt_addr} /boot/dtb/${fdt_file} || fatload mmc 0 ${fdt_addr} dtb/${fdt_file} fi Change imx6q-udoo.dtb with imx6dl-udoo.dtb and imx6q-udoo-hdmi.dtb with imx6dl-udoo-hdmi.dtb Recompile and reboot. Edit: U-boot configuration is the same for Q and DL.

(recent) Normal setup is one ext4 partition, while there is currently a problem with eMMC install which need an manual u-boot update first. I am still working on a u-boot update from Linux script. Currently you only can update it from within u-boot. This doesn't looks like our install. Probably you have SD card and eMMC with stock hardkernel Ubuntu ... attached at once and this can looks weirdo, especially if you did some manual adjustments on your own.

Not 100% sure but it looks so. I'll proceed with this later on ...

I changed metric to zero successfully on Ubuntu but no change in stability. I am now trying to upgrade dependencies to install NM v1.8 ... but I think this is a bit too harsh. I hope Debian Stretch's NM works well? One more findings - when disabling and enabling wifi connection it start to work instantly.

Jessie's network manager can't do this ... and I just started with a test on Ubuntu base. @Daneasch also discover few things. Perhaps we would need to upgrade network-manager manually? Edit: after I manage to ate sandwich, connection was dropped.

Just download latest Debian Jessie server version and you should be just fine. https://dl.armbian.com/cubietruck/Debian_jessie_next.7z It should work on Ubuntu and Debian Stretch too, but there you will need to rename packages since php5 is not supported anymore.

Boot log looks fine ... Did you try the other kernel option? We have 3.14 (default) and 4.4 kernel (next) ... If you have some other Linux on hand, try this: Change this to 9 https://github.com/armbian/build/blob/master/config/bootscripts/boot-udoo.cmd#L11 Remove this line: https://github.com/armbian/build/blob/master/config/bootscripts/boot-udoo.cmd#L23 Recompile: ( you might need to install u-boot-tools on that computer) mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr Reboot and you should see more on your console. I only have Quad model here, which is different enough.

https://docs.armbian.com/User-Guide_Getting-Started/#how-to-login In case your password change is not accepted, you have a problem with ready only / corrupted file system due to bad SD card or power supply.

It's an option, but in this case armbian-config will need some rework, since it's dependent from network-manager ... From "windows users" / newbies perspective, those which doesn't want to learn, network manager is better, since all they (need to) know is what is their wireless SSID and password, which is entered in interactive process. Hard to beat that experience. In desktop mode we had problems with alternative (wicd) too so sticking to one and fixing the problems is probably the way to go. I would not rush and change everything before identifying this particular problem, than think again what kind of networking config is overall the best, and than start moving into one or another direction.

1. Study background: https://askubuntu.com/questions/1786/what-is-the-difference-between-network-manager-and-ifconfig-ifup-etc 2. Google for more details to see if others are having this problem and if it's already solved in recent NM. Our Ubuntu packaged version is not latest, with Jessie is even more old. 3. Make sure that classic way of making a network connection works (with disabled Network Manager) ... this means some extensive testing. 4. Identify a problem and apply a fix or workaround for Network manager (or whatever causes this problem) to built system that we all would benefit from it. Something like that I would do ... Anything that helps understanding roots of the problem is valuable.

That is network manager, issues are most likely related and need to be investigated when possible. No quick fix - only workarounds are possible at this stage.

How did you connect to wireless network in first place? This way? Than you use network manager. Or this way: systemctl status network-manager.service

One thing that was noticed lately is this strange issue related to (presumably) Network Manager. Are you using NM and can you rule this out by using ifup or some USB wired adapter?

I think it's not related to suspend / resume ... there is no sound since start. Well, I'll remake image and do some close look. Edit: Sound works on fresh image from sources.

If you get such configuration working on RPi with very similar chip, than one way is to try with mainline kernel, even still development version - build one or try the ones from download section. This way become more but not exactly comparable ... It can be also firmware related and I would double check small print / documentation / ask Broadcomm, do detail compare of both chips. This is wireless networking, which is yet another big area of expertise and pressing on volunteers to help is a bit out. We already save you a lot of work, but Armbian crew (few people) can not fix all generic Linux problems that emerges. Edit: if you are using old kernel (legacy 3.4.113) this module must be loaded with op_mode=2 to provide AP mode - only this way you will see AP. I have no idea if you still can run in client mode at the same time ...

I haven't try headphones yet ... but speakers are off. I am using previous build with upgrade.