P.P.A.

  • Content Count

    18
  • Joined

  • Last visited

Everything posted by P.P.A.

  1. The patch was very recently added in 5.11.6. I'm not sure how you install the kernel after the fact—I simply built a new bootable image with armbian-build (choosing sunxi-dev as the kernel with ./compile.sh EXPERT="yes") and flashed that to µSD.
  2. It must be 5.11, so you need to build from source. Something I forgot to mention (going to edit the post now): the kernel must be built with this patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7072db89572135f28cad65f15877bf7e67cf2ff8 It's been accepted for upstreaming and will be included in 5.11 later, but up until 5.11.3 at least, you need to include it as a userpatch.
  3. Thanks to the very patient support from jernej and ndufresne on the linux-sunxi IRC channel, I could confirm that GStreamer 1.19+ works out of the box on the 5.11 kernel (sunxi-dev), tested with Hirsute and Bullseye, at least on the H3/Orange Pi PC. (I haven't been able to build or run a 5.11 image on a H6 device, so I couldn't test it there yet.) Kernel: Build 5.11.y with this patch, must be included as a userpatch. 5.11.6 includes it from the getgo, but below that you need to add it yourself: <jernej> PPA: kernel 5.11.6 is released with Cedrus patch Requi
  4. It seems to be system-specific. Pine H64 B + Hirsute: doesn't build. Pine H64 B + Bullseye: doesn't build. Pine H64 B + Focal: builds, doesn't install OPiPC + Hirsute: builds. OPiPC+ + Bullseye: builds. (All sunxi-dev) EDIT: Rock64 + Bullseye: doesn't build. (dev as well)
  5. I'm having the same problem, trying to build sunxi-dev/5.11 images or Pine H64 B: Displaying message: ERROR in function install_deb_chroot image-helpers.sh:148 err Displaying message: Installation of /root/armbian-zsh_21.05.0-trunk_all.deb failed pineh64-b hirsute no sunxi64 err Displaying message: Process terminated info zsh (5.8-6) wird eingerichtet ... tmux (3.1c-1) wird eingerichtet ... armbian-zsh (21.05.0-trunk) wird eingerichtet ... Trigger für man-db (2.9.4-2) werden verarbeitet ... Trigger für libc-bin (2.33-0ubuntu2) werden verarbeitet ... qemu: uncaught target s
  6. Thanks for your reply. That's the idea. I've edited the post, corrected erroneous statements and added your information. (And added some of the information on GStreamer from IRC.)
  7. I've taken peeks at threads related to hardware decoding (of H.264 and HEVC, mainly) on Allwinner and Rockchip platforms on and off, sometimes dabbled in trying and failing to implement solutions recommended there. Being a complete amateur, I find the topic very opaque and confusing, with various different components that need to interface with each other, be patched in sync, and sometimes change drastically between kernel versions, etc. Today I sat down and read up on these subjects, scouring wikis, documentation, this forum, and assorted other sources to try and understand how this works. In
  8. Is there an overview of additional features included in these builds, or are they equivalent to the latest Armbian releases for H6 SBCs, just for TV boxes?
  9. I asked about this in the #linux-sunxi channel some time last year. I believe it was @Icenowy who was actually sitting on a mainline patch to enable TV out, but there was presently no way to detect whether there is a cable inserted in the AV socket, or whether it's hooked up to a TV, and there is too little demand for the feature for anyone to bother.
  10. P.P.A.

    Mainline VPU

    After my last post here, I successfully applied @xmixahlx's linux-5.8-rc4-hwaccel_20200709.diff to balbes150's Armbian Build fork (as a userpatch). For various reasons I was unable to test it properly though. 5.8 having been officially released, I would like to start over and re-trace your steps and patch the kernel the same way you did with 5.7 and 5.8-rc, mainly in order to enable 10-bit HEVC decoding. I read the entirety of this thread and the two at the Pine64; please tell me if I got all of this right: The first patches you applied were the ones from LibreELEC's kernel at
  11. I see; thanks for your detailed response. VAAPI is of interest to me since IIRC it's what jellyfin interfaces with to provide transcoding to clients, but it's more of an abstract interest since I just watch everything on my desktop anyway. In this context I'm pleased to hear that getting mpv to work may not be so difficult after all. When I have time, I'm going to try and look into into how mpv interfaces with ffmpeg.
  12. Am I understanding it correctly that it works as follows? LibreElec patches the kernel to make use of the SoC's VPU. (Some of these patches make their way upstream eventually, but that's a slow process.) It also forks ffmpeg, which is patched to recognise these new kernel features & to make use of them. Kodi then refers to ffmpeg to access them. What would be necessary for players other than Kodi—mpv or VLC for example—to benefit from this as well? And what is the role of libva, VAAPI, and these other things in this process?
  13. If you only want to use Kodi, take a look at LibreElec: https://forum.libreelec.tv/thread/17565-nightly-images-for-a20-a64-h3-h5-and-h6-boards/ It's got more hardware decoding features than mainline or Armbian thanks to various custom patches for both the kernel and Kodi, but it doesn't do anything other than run Kodi.
  14. Xunlong is putting out another batch of H5 devices at the end of the month. Is there any particular reason to go with a H5 board these days? As I understand it, the advantage it has over the H3 are the gigabit ethernet and the 64-bit architecture, while being a bit more mature on mainline and Armbian than the H6 or similar Rockchips?
  15. I tried out my Rock Pi 4B with a custom-built 5.8.0-rc6 kernel based on @balbes150 armbian-build fork, and despite my monitor supporting a resolution of 1920x1200, the maximum I could select was 1920x1080. http://ix.io/2siM Once I've tried the official Armbian images and balbes150's own build, I'm going to edit this post/reply again with whether any of them fix this problem.
  16. P.P.A.

    Mainline VPU

    @xmixahlx How much of what your pbp-tools scripts are doing is specifically tailored to the Pinebook Pro (and would cause incompatibilities elsewhere)? Can most of them be run on any RK3399 platform?
  17. I went into armbian-config and changed from nigthly to stable without knowing what I was doing. After rebooting, I got an error, and now my X96 Air won't boot again with that SD card (never installed to eMMC). Is there a way to fix this, or do I have to re-install everything? I didn't make backups (lesson learned), is it possible to restore my settings and everything by just copying all the files from my old SD to my PC, re-flashing the SD card, and then moving certain folders back to it after setting up a new install?
  18. I bought a X96 Air the other day, and installed Armbian on it using meson-sm1-sei610-ethfix.dtb. Ethernet works, and it runs fine (I haven't tested HDMI audio because I'm using it as a headless server), however WiFi/BT does not. From browsing this and other threads, I gathered that these boxes may have different WiFi chips, and to get it working requires identifying the chip used, and then finding the proper drivers for it (forgive my layman's vocabulary here)… and that this involves the dtb files. How do I find out what chip my box uses? Do I need to open it up and simply look for t