• Content Count

  • Joined

  • Last visited

About JMCC

  • Rank
    Embedded member

Recent Profile Visitors

941 profile views
  1. I stand corrected, it does support 10-bit HEVC with the Main profile. I also know that LibreELEC uses some patches to libdrm to support 10 bit display, which we don't do ATM.
  2. TB dows not support 10-bit HW decoding, so all the work needs to be done via software. It's probably able to decode a 1080p file, but not 4K. It looks like newer versions of Chromium are not compatible with the widevine library that the script installs. I haven't found a more recent library yet. In the meantime, if you don't mind using an outdated version of Chromium, you can try to downgrade it: sudo aptitude install chromium-browser=65.0.3325.181-0ubuntu1 sudo apt-mark hold chromium-browser Let us know if that works You can autostart it as the root user, just by placing this line in /etc/rc.local: kodi-gbm-wrapper Or you can disable the desktop altogether through "armbian-config", and then run just "kodi" in your .bashrc file, if you want to autostart it as your regular user.
  3. Seems like the community is seriously demanding 64 bit versions of the RK media script (3399 and 3328). Give me some days, I'll work on it.
  4. No, I need to make another one for RK3399. I made one already, but for a 32 bit Armbian Xenial, when we were in the first stages of development for that SoC. I can search for the link if you are interested. The 64bit Bionic can be ready in a few weeks
  5. I understand you already tried to add these lines to /etc/systemd/resolved.conf: DNS= 2001:4860:4860::8888 FallbackDNS= 2001:4860:4860::8844 And also try adding this one to /etc/rc.local: grep -q 'nameserver' /etc/resolv.conf || echo 'nameserver' >> /etc/resolv.conf And reboot Or even a more radical solution, in case the above doesn't work, putting in /etc/rc.local: echo 'nameserver' > /etc/resolv.conf and reboot.
  6. I'm not aware of any Tinker Board emulator out there, so I can only test on "real hardware". I'm not aware either that Tony is having those issues when running my script with the official Armbian default image. Make sure everything is in place in your setup (double check you're using default, not mainline).
  7. As a matter of fact, I only guarantee my script to work against the official Ubuntu Bionic Armbian desktop default image. That is the one I use as build environment, and as testing system.
  8. Do you mean it should say "Armbian Bionic" instead of "Ubuntu Bionic Armbian"?
  9. JMCC

    Asus Tinkerboard

    Those problems are not present in the released image, nor if you build with the kernel I froze. I think switching to that kernel would have two important advantages: Less headache. Everything in the board would work unless we break it. A solid base to experiment and introduce new features (e.g. the LibreELEC multimedia patches referenced by @Kwiboo, camera ISP driver, new kernel configs, etc.). Right now, if you try something new and the board fails, you are in doubt whether it was because of the change you made or because it broke upstream.
  10. If that application you mention requires an accelerated OpenGLES canvas to display the videos, then the answer is yes. You can try, it won't harm.
  11. JMCC

    Asus Tinkerboard

    Well, going back to the kernel: Do we want to use the frozen version I referenced above? If so, I'll start working on adding the remaining patches (though, as I said, I'll need a little help with that). @Igor @TonyMac32 what do you think?
  12. When did HDMI break? It is working in the stable released images
  13. JMCC

    enable tightvncserver local input

    Probably if you use x11vnc instead of tightvncserver. Maybe this tutorial still works in Xenial.
  14. JMCC

    offically support Khadas VIM?

    Well, that is in a sense what is done now with "board families". All the boards in the same family share the kernel and most filesystem tweaks, and differ only in the device tree and some adjustments for specific hardware. But it is only possible when all the boards share the same SoC or a very close one. With completely different SoC's, that is not possible, each one needs a different kernel. Notice that all different boxes supported by balbes150's images have some Amlogic Meson SoC, and that is why they can use the same image with minor tweaks.
  15. JMCC

    offically support Khadas VIM?

    I completely agree: the core team is overwhelmed with work, if someone wants to see new boards supported, community contributions is the way to go. However, I've always been curious why @balbes150 is maintaining a separate fork, with different boot method etc., instead of making Vim work on regular Armbian. Is it in order to be able to support more TV boxes with a single image?