• Content Count

  • Joined

  • Last visited

About JMCC

  • Rank
    Embedded member

Recent Profile Visitors

1216 profile views
  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:
  5. 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…
  6. 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
  7. 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.
  8. 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 "./"
  9. Just change the line in the file /opt/emby-server/bin/emby-server, as instructed in the tutorial.
  10. 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.
  11. 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
  12. DX910-SW-99002-r7p0-00rel1_meson_gx
  13. 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:
  14. 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.
  15. 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.