Igor

I have this one: 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) and it works fine. I only test keyboard and mouse. Check this: https://wiki.ubuntu.com/HardwareSupportComponentsBluetoothUsbAdapters This one: http://www.dx.com/p/bluetooth-v4-0-csr4-0-usb-dongle-adapter-black-207993#.WJY3tFUrLAQ should also work but haven't test it yet.

There is only one boot on mainline kernel since some time. We optimise a little, there is no need for reboot and more detailed output is to serial console. Login and start using it.

nand-sata-install script is present on the system. Just open a terminal and type. You have to boot from SD card and have eMMC present. Unfortunately this scenario is untested by me so I don't know it it 100% works. It should.

If you want to have picture on the screen, monitor must be attached at the boot time since it performs auto detection. There are problems with some HDMI2DVI adaptors, but we have a solution for this (kernel 3.4.113). It's called h3disp (run as root and read what pops out).

Kernel 4.8.4. You are using developing kernel for which we don't provide any end user support. It's meant for developers and testing. On the download page, there is a big red sign: Warning: nightly downloads are automated untested builds and no end user support is provided for them! If you want audio and microphone with this kernel and addon, which is not officially supported yet, you need to write a driver. There is nothing like "install a driver". http://linux-sunxi.org/Linux_mainlining_effort / here you can see how far things are developed You will have more success with old kernel 3.4.113 ... but even there you might need to play with board configuration (/boot/script.bin) switches. Microphone or audio might be disabled on this board, since by default it doesn't have audio connector.

Check this patch: https://github.com/igorpecovnik/lib/commit/ba3548468ed915f0540729526b16512ee48da7aa You need to add &emac section to your device tree. Nothing more.

Perhaps logram size is too small for your scenario ... disable or debug the ram logging service. systemctl disable log2ram.service

Can you perhaps provide serial console boot log? Unfortunately I don't have any eMMC for XU4 around. Are you trying to boot mainline kernel 4.x ?

There are slim chances of mainline kernel for this board although we have it for Odroid XU4 and I saw some bits for other Samsung chips, while not for this particular one. Even if you could boot it, there will be very limited support. IIRC Odroid XU4, which is one of most popular boards with Samsung chip, doesn't have any multimedia features, not even a HDMI driver in mainline kernel ... here you can expect only worse than that.

Update from old (testing) images might broke, while images works. I just download, burn and boot this image: https://dl.armbian.com/nanopineo/Ubuntu_xenial_dev.7z on my FA Neo. Network works out of the box. If you made a download yesterday, you could accidentally download broken image. I was correcting those images manually during the evening since I figured out, that network was disabled.

Thanks, will be fixed asap.

https://github.com/igorpecovnik/lib/commit/a83a6957f523946096b1009d0fb1e0f06b88f614 Added with patches. I only try if compile.

NanoPi is a good choice but AFAIK CSI camera, if you need that, is not yet supported in modern kernel.

Hardware is dirt cheap while "free" software can cost you some money. Luckily, if you start with Armbian, your basic things are covered - you already saved yourself hundreds of hours and dollars. That's our main advantage - you don't need to start from a pile of junk (Allwinner stock SDK) or spaghetti tutorials. Why? You are wasting time. Forum is more or less inactive and their official support, just not worth the trouble creating forum username. Still better than fixing legacy kernel where those things also doesn't work.

Than you don't have much choices except Bluetooth and WiFi direct. In both cases expect troubles and stick to modern kernel, where you have more chances of success. For example: I can use BT keyboard and mouse nicely with Cubietruck running kernel 4.9.7 ... I didn't test sending and receiving files to mobile phone.

Perhaps something like this: http://www.dx.com/p/arduino-apc220-wireless-rf-modules-w-antennas-usb-converter-143011#.WJRDf1UrLAQ But since I don't have any real world experiences I am only guessing.

WiFi. Ofc not directly interchangeable.

It's closed source technology, require firmware to run, it's know to cause problems. This simply means that it's to avoid in first place. There are other and better ways for wireless comm. Hardware maker are just people / engineers which sometimes overestimate and make mistakes. If you add commercial agenda to this, things become only worse. For a board which cost 9 USD shipped, 1 USD is a lot . And they don't invest much into software. This goes from zero up to just a little. Even software is "free", it cost a lot of money to develop it. Armbian makes things closer to ordinary users and saves time, but we can't make a perfectly smooth plug and play operating system. Just remember to have fun in first place

Bulletproof is only something like this: https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-freeze-your-filesystem

Regarding CPU power, Opi0 is a decent board. It is usable on a short distance for transferring small chunks of data since transfer speed over on board WiFi chip is low. If your use scenario meets that, you will be fine, otherwise just use Ethernet or attach some high powered (2000mW) USB wireless card like this one: and wireless range will be extremely long.

It boots (I made a test), just video out is somehow failing and we wrote down this fact in release documentation which is hard to miss. We don't have resources to fix such problems in last minute and also removing the board would raise questions. In last 24h I made only few hours sleep since I am fixing small things on the way while releasing around new 150 images, which were built one after another in an automated way (for a whole day). Unfortunately I could not find a fix for M2. With adding a note we give out important information, which should prevent you in using broken image and raising unnecessary and costly support questions. You understand now? Just remind yourself that this operating system and the tool come as is in first place and if it doesn't work, you report that or try to fix the problem on your own. No one will jump and start fixing.

Without a log, only wizard can help Latest image from download section works - I attached mechanical drive yesterday and it works fine. If you ware upgrading we need to see logs to give you advice what to do next. armbianmonitor -u

True, but they usually don't create software in first place. They just push out what they get from Chip maker, something unfinished, half done and they do this all the time. None of board maker produce stable software, but 3rd party companies, groups, community so it's not much relevant if they put out new version every month. Usual community response is that some boards are ignored and therefore support remain on that half done / initial support. Useless for average Joe. Most of boards (if not all) which we support, can be used in production. You just have to read recommendation and not use kernel / image with labels "preview" "beta" "experimental" "development" and you should be fine. Older boards (A10 / A20) are better in term of stability, since they are longer around and all rough edges were found and fixed. Next are most popular boards, where this happens quicker. People use those boards in production for various services - not everybody is playing with them. I use two A20 boards for various services with uptime measured in months. It would be in years if I hadn't update them from time to time. Until fall 2016 all our services were running on A20 and Odroid XU4. Zero problems. Bluetooth and wireless are mostly covered with closed source drivers (firmware), which means troubles. If they work out of the box fine, if not, we try to fix them if it's in our power, otherwise this remain as is. Especially we don't try to fix 3rd party hardware, things which you attach to the board, since this is out of the project scope. We are few people and there are zillions of devices out there. We provide basic system and that system is stable (if not stated otherwise). When you start to plug things into your board you have to understand what are you doing.

Fixed. Tested Neo and ethernet is working fine. I need to rebuild and upload images ... in few hours, in the morning.

Ethernet not working on latest development - i'll try to fix it right away.