Igor

Nope. Few things will work, for other hard to judge. From few weeks to months of work. Go, try, report back, submit fixes ...

@FloKra I download latest image 5.35 and update ... Everything is fine. This could be the problem with the board, not Armbian. http://ix.io/Kl4

Mainline kernel is labeled testing since we are not sure that it runs stable. Therefore you just proceed (downgrade from armbian-config or start with a new build) to legacy kernel ... still 100x better than Raspbian with years old kernel full of bugs and security holes. Edit: I am running TVheadserver / VPN on H5 board with weeks of uptime. It would have been months, but I do an upgrade from time to time.

Change it in /etc/default/nodm

I would say it is pretty irrelevant what OS you run - we provide Debian Jessie and Stretch because some applications (OMV for example) are dependent on what you use. It is also possible to build Ubuntu version if this is what you need. I have no idea how is this with Plex. There is also an option to run Plex containerized and again, both kernels (!) are Docker ready. Hardware wise it is powerful and matured well enough. You need to try all combinations or pick randomly and see.

I assume via upgrade? Now via deboostrap method

First move to this version: https://dl.armbian.com/orangepipc2/Ubuntu_xenial_next.7z which is first stable to be. Then explain exactly what you did - I can not tell whether this is our problem or something else, out of our power to fix. Support for H5 boards is still considered testing.

First stable image for Orange Pi Win with a legacy kernel was released on 10th of January, v5.37 "Mainline coming soon". Not released to this day. We don't care if development versions break. It is expected that they break ... and we fix them ... they break ... and we fix again. And after a while, when this is not happening that often, an image is released.

RAM size is determined in u-boot. I don't have any 4G board so you will have to try with one of the attached. Use NEXT if you have kernel 4.14.y otherwise the one without. Install with: sudo dpkg -i name.deb linux-u-boot-cubox-i_5.41_armhf.deb linux-u-boot-next-cubox-i_5.41_armhf.deb

Yes, but usually this is better in first place and problems usually not related. We are about to change kernel for Rockchip boards to the one used by TinkerOS. It looks like it is generally in a better condition than the one we use now. Will this effect on audio or RT functionality? Probably. Changes are already applied to the build script, while images and update are just about to be released. Since you are able to build on your own, try recompiling the kernel with your own config and with most recent RT patch for 4.4.115 You can recompile the kernel with your own config - just put it into userpatches directory and use the same name as we do (linux-rockchip-default.config)

@TonyMac32 Is it time to push out updated images?

Did you try on the old kernel as well?

Ethernet is currently broken on (some) A64 boards with mainline kernel due to recent changes in the driver. Banana M64, which is a similar design, was happy with such patch https://github.com/armbian/build/commit/6ab13a0122ee80c0ffbd57c0a42a969935787117 while I actually don't have Pine64 (ordered) to check if the same trick works.

This fix is present at least in NEXT (4.14.y) kernel.

USB/SATA installer with boot from SPI also works. https://github.com/armbian/build/commit/69ccc04e88872b75bf6d70cc1e32cce483f3cf25 It's plan to move the board under stable ... but we need some help. With maintaining. Since our board count is huge, it already took days before all boards are tested (at major release), sometimes we skip certain and then Murphy law strikes Roles are not strictly specified and nothing special is planed. We seek someone, who is up2date with development status, has a spare board for testing and is willing to update "known issues" or add specific tips for this board on the (new when ready) download page. Also, do testing when major updates are planned. Any volunteers?

https://docs.armbian.com/User-Guide_Allwinner_overlays/

Reading documentation? https://docs.armbian.com/User-Guide_Allwinner_overlays/

https://tvheadend.org/projects/tvheadend/wiki/AptRepository Nope, it doesn't work on Stretch. Method for Raspbian Stretch also fails with: "doesn't support architecture 'arm64'" You probably need to build from sources then: https://github.com/tvheadend/tvheadend or use Ubuntu Xenial, where it works out of the box.

It is enabled for Ubuntu Only. I guess it (used to?) fail on Debian. https://github.com/armbian/config/blob/dev/softy#L25 Check manual way: https://github.com/armbian/config/blob/dev/softy#L464-L475 I'll add back if it works.

Bus 001 Device 010: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter Bus 001 Device 008: ID 0bda:a811 Realtek Semiconductor Corp. Bus 001 Device 012: ID 0bda:8813 Realtek Semiconductor Corp. Serial # [ 1560.988790] usb 1-1.4.4.2: Product: 802.11ac NIC [ 1560.988802] usb 1-1.4.4.2: Manufacturer: Realtek [ 1560.988813] usb 1-1.4.4.2: SerialNumber: 123456 8814 https://www.gearbest.com/network-cards/pp_625323.html 8811 https://www.gearbest.com/network-cards/pp_613225.html 8812 is no name from eBay. It looks like this one. Try again building from sources, Odroid XU4 NEXT ... I just pushed patches up. Those are tested.

@AlexisTM Odroid XU4 4.9.y Cubox 4.14.18 It looks normal, no glitch. This driver update was already pushed into most kernels. Same results with 8814 or 8812, both test were made on 2.4 band.

I can see my mouse, keyboard or my phone, but it cannot make a connection. The same kernel works on Pinebook and there BT works ... but there we have a different chip in first place. Also one tip: you need to reboot after first boot.

We made this tool with the purpose to make kernel recompilation as easy as possible. In just about every other way you have many potential obstacles to overcome. All those Youtube guides are usually made for Intel world/perfect scenarios where things just work. ARM variety is big. You need some x86 desktop computer where you recompile the kernel in a virtual machine, transfer two .deb packages to your Tinkerboard via a network or via SD, install them with (dpkg -i package.deb) and reboot Tinkerboot into a new kernel. If you use our tools you have small chances to fail for anything else you need some experiences. It is possible to recompile kernel on your board, but ... you are on your own. Sources are accessible this way: apt install linux-source-4.14.14-next-rockchip Since you don't want that upgrades overwrite your own made kernel you need to freeze kernel updates (armbian-config) or send your changes upstream and they might be included in the kernel by default.

Now read the error text. We don't support native compiling ... remember that you need to include all those patches https://github.com/armbian/build/tree/master/patch/kernel/rockchip-next if you want to proceed this way ... or use sources from our repository.

You need to start here/this way: https://docs.armbian.com/Developer-Guide_Build-Preparation/ with enabled at least this config option: KERNEL_CONFIGURE="yes" (actually if you don't change anything you are asked "do you want to change kernel config") https://docs.armbian.com/Developer-Guide_Build-Options/ You only install (dpkg -i kernel.deb) resoulting kernel and dtb package. I am not aware if CAN is working on Tinkerboard.