JMCC

Members
  • Content Count

    441
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by JMCC

  1. JMCC

    Xorg HDMI kiosk with audio

    No, that was for Rockchips and XU4. You need to run a script after installation to enable 3D acceleration in those boards. But the H3-based boards (like your OPi) have it enabled by default. Well, then, if that's the case, flash an Armbian Desktop image and you are good to go. It depends on how you want to set up your kiosk, but maybe the easiest way is configuring the XFCE menu to auto-hide, and put the icons of the apps you want on the desktop.
  2. JMCC

    Xorg HDMI kiosk with audio

    Do you have any special board in mind? If not, I recommend something Rockchip-based or Odroid XU4. With those, you can have GPU acceleration, which can be very useful for a kiosk if your apps use OpenGL, WebGL, etc.. Once you have chosen the board, setting up the kiosk is straightforward: installing an Armbian Desktop image, and then applying the corresponding media-script if you want 3D acceleration.
  3. Hello, and welcome to the forums. First of all, a little clarification: "Linux 4" doesn't mean anything; if you want to give us the information about the kernel you are using, then give us the output of "uname -r". Or, even better, give us the complete information about your system, by running "sudo armbianmonitor -u", while connected to the Internet, and pasting here the resulting URL. Now, about your question, the video you reference does not use HDMI+VGA, but HDMI+DSI dual displays. With Armbian, you can use any Raspberry-Pi DSI compatible screen, and attach it to the MIPI-DSI connector in your Tinker Board. You will need the "Default" (4.4.y) kernel for this to work. It has been tested with the official RPi touchscreen, but it may also work with other screens claiming to be compatible, like for example this one.
  4. JMCC

    Announcement : Odroid N2

    Just a notice that I edited my last post above, to include a link to a very interesting discussion at CNXSoft, that clarifies the PCIe matter. A kind of a summary, with some additional insights by @tkaiser in this article: https://github.com/ThomasKaiser/Knowledge/blob/master/articles/Quick_Preview_of_ODROID-N2.md
  5. The UN-official, UN-supported, UN-timely, UN-derrated... Exynos 5422 MEDIA TESTING SCRIPT Yes, the script is somewhat untimely, because it comes when including kernel 4.14 in Armbian next images is getting troublesome. And underrated, because this old SoC seems to be losing the focus of attention in favor of some more modern powerful ones. But it is still a great SoC, and it is worth trying to get the best out of it. The script will provide the installation of all the libraries and system configurations necessary for GPU accelerated X desktop, Chromium WebGL,VPU decoding/encoding acceleration through MFC, and GLES 3.1 / OpenCL 1.1 support. It will also install two media players (MPV and Kodi stable) and FFmpeg, all of them using VPU acceleration. Two example programs using the OpenCL functionality: Examples form the Arm Compute Library, and a GPU crypto miner (an old version, but small and simple). Two additional small packages, that have no big interest from the developer prospective, but I find them interesting to play with: Support libraries for commercial web video streaming (tested with Netflix), and a simple Pulseaudio GTK equalizer using LADSPA. Since all the features require the 4.14 kernel to work, the script will also give the option to install an archived 4.14.43 Armbian kernel, in case some other version is detected in the system. Of course, the best option is to use armbian-config to perform a kernel upgrade, but we are providing the archived version just in case the 4.14 packages disappear temporarily from Armbian repos. Also, this script can be tailored for desktop or headless installation, by selecting the appropriate options in the main menu. Here is a more thorough documentation: >>> DOWNLOAD LINK <<< Instructions: Download the file above Untar it: tar xvf media-exynos5422_1.0.tar.xz cd exynos5422 ./media-exynos5422.sh Notes: This script is not officially supported by the Armbian project. It is just a community effort to help the development of the main build, by experimenting with a possible implementation of the media capabilities of this particular SoC. Therefore, questions about the script should not be laid out as support requests, but as commentaries or community peer-to-peer assistance. That being said, all commentaries/suggestions/corrections are very welcome. In the same way, I will do my best to help solve any difficulty that may arise regarding the script. Enjoy!
  6. So after all we want to have good old XU4 added to the Bionic multimedia team? Let's see what we can do about it…
  7. JMCC

    Announcement : Odroid N2

    Regarding the lack of support for NVMe/SATA, I think it is as simple as the fact that the SoC doesn't seem to support them. Amlogic aims to release SoC's that are just enough for a standard TV box, they don't have things such as Chromebooks in mind when they design their SoC's (as, for example, Rockchip does for their higher-end SoC's). And that is the reason why we can buy this board much cheaper than any equivalent RK3399. Here you trade brute horsepower for extra features in the SoC. [UPDATE]: Even though PCIe was never mentioned in the official announcements of S922X (see, for example here and here), recently someone pointed out that they got a "leak" from Amlogic saying otherwise. According to that "leak", the SoC would have a single-lane PCIe interface, but it is pin muxed with USB3. In other words, you would need to disable USB3 in order to use PCIe, and that would still be single-lane. Definitely, disabling USB3 in favor of a possible SATA/NVMe interface would be IMO a very bad choice for a general-purpose board. Maybe if they release in the future something like the HC1, based on S922X, it could make sense. However, given the fact that Amlogic has not officialy announced that PCIe support, and after the "fiasco" with the broken PCIe in Allwinner H6, I won't believe that these are real options for this SoC until I see it actually working. You can find the whole discussion about the matter in this page from CNXSoft
  8. Yes, that's the point where everybody gets stuck. @TonyMac32 suggested some posts above that the driver may not be getting the config you feed it, so maybe that can be the cause for the problem. I may give it some other try, but the truth is that I don't think it is worth spending much time on this, until some steps are taken upstream. The v4l2-m2m driver is still immature, and there are also chances that the Lima driver can be mainlined for the next release (see some posts above). It is probably time to wait, and work in some other projects in the meantime (like Rockchip). However, as I said, I may give a try to the possibility of hardcoding the compile options, as a possible temporary solution, as I mentioned some posts above.
  9. Well, no fancy introduction here, because this doesn't pretend to be a script for the general use, only for testers who want to try the current *very early* status of the media capabilities in the Armbian meson mainline kernel. Warning: It will replace your current kernel with a pre-compiled nightly 4.19.20. Instructions: Download, untar and run. If you need further instructions, then you are not ready for this script (again, it is very unpolished, not for general use). Download link: https://mega.nz/#!YvYUhayC!CI1fl52V4tV0G4oqUib4W-NlMpVSpLDp8kmo74g-V08 Things that you can try with this script, on a X session: Use a 1080p@30fps h264 video, and play it with "mpv -hwdec <filename>". You'll see in the logs that it is decoding through v4l-m2mcopy Install and run glmark2-es2 Use Chromium WebGL Play a 1080p@30fps video in YouTube in full-screen smoothly. I'm pretty sure it is not really using HW decoding as it claims (there is no initialization message in dmesg), but it's smooth for sure. Gstreamer is tested not to work, in some other forum I was told that Bionic version is not enough and I need to compile a newer one. Performance is not in any way good, but it is a starting point. Anyway, the first TO-DO is getting the mali module integrated into the kernel, so there is no need to compile it separately.
  10. It looks like you weren't running the install script from the script's folder, but from some other directory. You must untar the tarball, cd into the created "media-script" directory, and run "./media-s905.sh"
  11. Just change the line in the file /opt/emby-server/bin/emby-server, as instructed in the tutorial.
  12. JMCC

    Announcement : Odroid N2

    Seems like it combines many of the advantages of both XU4 (powerful processor, boot switch, fan connector, USB3) and C2 (standard 3.3v GPIO and UART interfaces, IR receiver, and hopefully low consumption). Apparently you can clock the four A73's up to 2Ghz, which means a lot of horsepower. With regards to the RK3399 boards, seems like we lose the PCIe interface, but the price tag is also lower. Looks like a very interesting board.
  13. Using mpv from the command line console should give you a log, with info about the decoder and display driver it is using. Also with gst-play-1.0 for gstreamer. Also, running glmark2-es2 will tell you whether it is using Mesa SW emulation, or Mali. For last, if you have configured chromium to use acceleration (like my script does), you can check whether it is working by typing in the address bar "chrome://gpu" Edit: And, of course, you can also check /var/log/Xorg.0.log
  14. DX910-SW-99002-r7p0-00rel1_meson_gx
  15. But that would mean losing the module when the board updates the kernel, if I'm not wrong. We would need to do a DKMS package for the module, and that can be time consuming too. Specially if you consider that I tried to compile the module natively on the board and it wouldn't work, so we would need to figure out that problem too. I did: https://github.com/armbian/firmware/commit/8bdf0a6b1896a6ce67eb7d10caefeced3cc5e984
  16. If that's the case, then we can just use the tough solution: change the defaults in the module source to the ones we need. Kind of a dirty fix but, as I said, it is probably just a temporary solution until something is figured out in upstream mainline. [Edit:] However, in any case, that was not my problem. When I made config changes, I could confirm that it was making a difference in the way the module was compiled (either as a module or as part of the kernel), the options it enabled, etc.. But, again, nothing worked. I even got to the point of applying a patch from the Odroid forums to enable UMP, and the "/dev/ump" node would appear, but mali still would not.
  17. Well, actually I tried to build it natively against the kernel headers, and it didn't work. I had to cross-compile it against the original kernel build tree. I must recognize that I didn't try too hard the first option, though. However, what we really need is a way to integrate it into the main kernel build which, for some reason, seems to be harder than with other mali flavors. We are having the discussion about the subject on this other thread.
  18. JMCC

    Advice on new SBC device

    Welcome! Avoid Banana M3 at all costs. Besides that, all three other devices are good, depending on your budget and how good of a deal you can get. Probably Nanopi M4 is still a bit immature on the software side (too new), but if you plan to use it in the long term, it's a good choice. XU4 is rather old, but it is still a great computer, and software support is excellent. Plus, now you can find it very cheap. I recommend buying in Ameridroid and adding a emmc module. Tinkerboard S is a great machine, with very good software support too. Though, you'll need to find a very good microusb cable for powering, which is not always easy, and also this board will probably be the most expensive of the three.
  19. I made a very rough and basic, alpha (or pre-alpha) script, to test the v4l2 decoder and the mali kernel module. I tried to integrate the mali module into the kernel, but I wasn't able to make it work. No matter what I tried, it was always the same: the module was loaded, you could see it in dmesg and in lsmod, but the "/dev/mali" node was never there. I suppose that is why everywhere on the net, people are compiling the mali module separately from the kernel. Any suggestions to sort this problem out are welcome: Wait until lima is mainlined? There seems to be hope that it can happen soon. Make a DKMS package for the module? In any case, this is the thread for the script:
  20. JMCC

    Asus Tinkerboard

    So, since RK started to create tags, I guess we can just use them and forget about the old problem of the default 4.4 kernel being a constant pain, right? It's also very comforting to see that they paid attention to our requests in that matter.
  21. JMCC

    Just a test

    Totally agreed. It is very likely that a user's project depends on features that are only available in a certain kernel and not in others. That is particularly true when it means jumping from a kernel that is actively maintained by the vendor (like Hardkernel's 4.14 for the XU4) to a vanilla mainline. Practical examples: A user that has OMV installed on his Odroid HC1 with disk encryption on 4.14 kernel, would lose HW crypto support if upgrading to 4.19 (I think @tkaiser already pointed this out). Or if they have an Emby server with HW transcoding in that machine, it will stop working with the move to 4.19. Or if he has a media player/gaming station for the kids on a XU4. Etcetera. Well, I think everyone is clear on this point already, I just wanted to show my support for the idea of being very careful when making big kernel moves.
  22. JMCC

    Language Support Setting on Debian

    I think that process is not necessary anymore, armbian-config should be enough to take care of configuring the locales. @köksal please confirm if it worked for you.
  23. JMCC

    Language Support Setting on Debian

    What do you mean, the "Language support" menu entry in the Xfce graphical menu? That is a Ubuntu specific app, you won't find it in any Debian. For changing the language, use "armbian-config" instead.
  24. Sorry for the late reply. Well, I don't have much experience with OMV. I tried to use it in combination with Nextcloud on the same machine and it wasn't possible. But it seems like it can be combined with Tvheadend: https://forum.openmediavault.org/index.php/Thread/6023-Tvheadend-Setup-and-Config/ Since OMV is based on Debian Stretch, I would assume you can use the ffmpeg packages I compiled with Exynos-5422 HW encoding support: But, as you see, my tutorial is for emby, not for using HW transcoding directly with Tvheadend. If I want to transcode to h264, Tvheadend only uses transcoding in order to remux the original stream as mpeg-ts, passes it to Emby (through a specific plugin), and Emby does the transcoding. But I never tested it on a machine running OMV. However, I have experienced that many times it is just enough with remuxing the stream, for the client to be able to connect more easily, without needing to recompress from mpeg2 to h264. [TL;DR]: MY RECOMMENDATION: First of all, just try and install Tvheadend alongside OMV, following the tutorial in the link I posted above. Then create a user, and try setting up for that user different default stream profiles (from the list in Settings > Stream > Stream profiles), to see if any of those work well enough for you: I would recommend starting with "htsp", then trying "pass" (those don't perform any processing on the stream). If you are not satisfied, then try "mpeg-ts-transcode". It will just remux the stream as mpeg-ts, with very little CPU use. If it still doesn't work for you, then you should transcode the video. But beware that, if you do it using the CPU, your HC1 will get extremely hot, and that will damage in the long run your attached storage drive. So you should go for HW transcoding, that keeps the CPU nice and cool In order to do HW transcoding, you can either Connect it to Emby through the Emby Tvheadend plugin, and configure emby as in my tutorial linked above. Notice that you must also set up the correct Stream profile for the user you create in Tvheadend as "emby user" (the user that the Emby Tvheadend plugin will use). I think it is "mpeg-ts-transcode" (not sure, it has been some time), but try the other two if it doesn't work. Or just download the Exynos-MFC enabled ffmpeg from that tutorial, and figure out a way to make it work with Tvheadend. It probably won't be easy
  25. Here are my results so far with the v4l2 decoder: I'm able to decode h.264 at 1080p correctly. MPEG2 at 1080p, and h.264 at 2160p are accepted by the decoder, but I get no output, it just hangs. HEVC is simply not accepted by the decoder, I can only do SW decoding. Does that correspond to the current status of the driver, or we should be getting something better?