adrb

I would check armbian docs, maybe something changed - I must admit that I was busy with other things and hadn't recompile Armbian kernel since then.

If you don't plan to use touchscreen, then no need to recompile kernel.

Ad3. Yes, guide is for mainline kernel, I tested it on 4.11 if I recall correctly. Ad 4. Yes, sorry my bad.

I don't know if it will work similar as fbcp, but It's possible.

Installing custom service isn't sounds like "zero config". Sorry , but in current form it's pretty much useless. That may be somehow useful if it will listen to DHCP requests and pull new devices to list. That list also should have options to remove or hide device. Happy to hear that

No wonder it is terribly slow Remove it or change to at least 25.

I don't know if it helps but that one should be interrupts = <0 19 0>;

Corrupted sk_buf list means that it's either buggy driver or memory corruption. Lower your ddr frequency as tkaiser sugests.

Did you try disabling bnep module?

Try to recreate those mount points, but it's more like systemd bug.

Glad to hear that and thanks for sharing. Often people tend to forget share their final solution

CS is handled by kernel, you shouldn't set it manually.

SAS is serial type interface (newer), SCSI is parallel.

Yes it does.

Yes, this is exactly my point. You need to pay for performance. It's most common use case today imho. I know about smart problems, what else?

Well, people are tend to forget about lot of details in regards to "performance". In case of NAS, usually wifi is your bottleneck limiting you to ~40MB in PERFECT conditions - you man even never get such transfers. So, even if you buy device with so called "crappy usb to sata bridge" which can handle 30MB, it's very likely that it would be "good enough" for small home NAS, where your priority would be low TCO. If you really need fast IO, just don't buy SOC device, simple as that ;]

You clearly misunderstood what I wrote. Change "functionalities" to "functions" in my sentence, better?

Prepare ARM based virtual machine, mount sdcard, chroot in it and finish your upgrade

Check nfs versions.

Connect other device with that cable and check if you will get 1000Mbit. If not, then you should know what to do next.

Just to clarify. RedHat was forced by GNU license to open their sources. So some folks recompile it, and there you have CentOS. What is more important competition like Oracle can use those technologies for free CentOS very existence is salt in the eye of RedHat ;] Agreed, but functionalities that are not quite working as expected, should be disabled by default.

Both kernel have pretty much the same drivers (regarding to SPI and ADS7846), you just need to configure them differently. What I would do for "initial stage" is, disable LCD and make ads7846 run alone on spi bus.

Don't forget to share your results

It's simple guide, presenting how to setup LCD (ili9431) with integrated touchscreen (tsc2046) on mainline kernel (4.11). It may be not fully "armbian way", since I'm pretty new in armbian In case that somebody is interested, I recently bought couple those displays from here Few basic informations: 1. OrangePiZero has two SPI buses. First one is usually occupied by build in memory. So we can only use bus1 2. tsc2046 chip is fully compatible with ads7846, and we have drivers for it since years now 3. Maximum clock frequency for ads7846 is 3.25Mhz, but don't expect that it will work with that. Reasonable value is something beetween 0.5-2Mhz. Lower frequency, if you observing misbehavior. 4. Probably most important information ili9431 and tsc2046 poorly cooperate on shared bus. I don't know exactly why, because I don't have access to logic analyzer, but it's proven fact (at least on my equipment). You have to lower bus frequency to 2MHz (highest common value), and even then it work very unstable. My educated guess is that, missed interrupt from touchscreen (when SPI is busy with sending data to LCD) makes it stop making further attempts to communicate. Or maybe there is some incompatibility on electrical level, I really don't know. 5. My electrical setup (keep in mind it's 3.3V) OPIZ - LCD (ili9431) PA13 - CS PA14 - SCK PA16 - SDO PA15 - SDI PA03 - DC PA00 - RESET PA06 - controls transistor which is driving current to LCD pin. You may also connect LCD pin to VCC, and leave PA06 floating. And here is part for touchscreen. We are going to use emulated spi bus with bitbang. At this point bitbang isn't compiled in armbian kernel - we will take care of this later. OPIZ - LCD (tsc2046) PA10 - T_CS PA18 - T_IRQ PA19 - T_CLK PA11 - T_DIN PA12 - T_DO Configuration for the first spi bus: Configuration for touchscreen driver: Compile and add those DTS with "armbian-add-overlay" command. Next, download armbian sources and cross compile kernel - without any modifications, just to make sure that everything is compiling without issues: # mkdir armbian # cd armbian # git clone https://github.com/armbian/build.git # git clone https://github.com/igorpecovnik/lib # cp lib/compile.sh . # ./compile.sh BRANCH=dev BOARD=orangepizero KERNEL_ONLY=yes PROGRESS_DISPLAY=plain RELEASE=jessie Enable required modules : echo "CONFIG_SPI_BITBANG=m" >> lib/config/kernel/linux-sun8i-dev.config echo "CONFIG_SPI_GPIO=m" >> lib/config/kernel/linux-sun8i-dev.config ... and recompile kernel, then install deb packages from output directory. You may also copy drivers, it may be faster for testing but it's not advised for "serious" deployment. Loading modules at startup: # cat > /etc/modprobe.d/fb_ili9341.conf << _EOF_ options fbtft_device custom name=fb_ili9341 gpios=dc:3,reset:0,led:6 speed=16000000 busnum=1 _EOF_ # echo fbtft_device >> /etc/modules # echo ads7846 >> /etc/modules If you connected LED pin to VCC, then you should omit that ",led:6" in configuration above. I hope that this will help anyone who want to connect LCD display and build simple touchscreen based Orange Pi Zero terminal

Ok, seems reasonable. Look here