• Content Count

  • Joined

  • Last visited

About jock

  • Rank
    Embedded member

Recent Profile Visitors

1704 profile views
  1. Thanks @JMCC for the answer, now the situation is much more clear, but I even tried to edit the .desktop file and turn "Terminal=" entry to true. It opens up a terminal but mpv still is not executed in the terminal itself, which sounds a bit strange. Also I'm running X11 + armsoc + libmali X11/GB and mpv runs fine without the need to link to libmali-gbm, so it is run as an X11 application and I thought it would have its own window to capture input events, but it seems not the case. Need to make more experiments and wait for mainline goodness that will make all this mess obsolete. BTW, I happily compiled Kodi with full acceleration on my platform (rk322x), unfortunately rkmpp/drmprime is available only with the GBM version. Compiling against X11 + OpenGL ES provides a much smoother interface but no hardware acceleration
  2. Wasn't that due to the mmc-pwrseq entry for the eMMC node?
  3. ugoos devices are different than el-cheapo tv-boxes, ugoos is a well-known manufacturer and their hardware specs are advertised on the site and stable. There is a single board, not infinite variants and versions like chineses, thus it could be supported as a regular board and would perfectly fit into Armbian community support flow.
  4. Wouldn't it be better to add Ugoos devices as regularly Armbian CSC supported devices?
  5. rk322x-config should be able to tell at least vendor ID and device ID of the wifi chip. Usually wifi and bluetooth are combined, so if you know the wifi chip you also get the companion bluetooth You can take a look to this freshly thread made by me, but at the moment there is the huge problem that you lose control of the mpv if you double click on a video icon from X11 GUI: Although if used from command line it works pretty well. Maybe this one: you need to unplug the power cord and replug it. Unfortunately boards with NAND with system installed on internal flash have this problem on reboot and we have not found a workaround for this yet. edit: I just read again your post, in case the warm reboot does not work yet, you can also try the rk3228b-box-mxq-pro-4k board from rk322x-config script. The board selection at the moment is sub-optimal since you can get the same PCB board but with different components which makes things really messy, but will probably change in the near future with something that better suits the situation. edit: had the chance to try V88 4k device tree and actually it does shut down my box (which is a mxq pro 4k). I'm sorry about that, some of the device trees comes from libreelec patches and I could not guarantee they are really working because I don't have the real hardware. Definitely try the mxq-pro-4k device tree.
  6. Hello, I'm testing mpv with RKMPP hardware acceleration on legacy 4.4 rockchip kernel. This is what I put in /etc/mpv/mpv.conf: vo=gpu hwdec=rkmpp gpu-api=opengl gpu-context=drm opengl-es=yes If works perfectly fine with low cpu usage BUT only if I launch it from command line either from a virtual terminal or an X11 emulated terminal. In case I launch it double clicking on a video from X11 xfce, mpv starts playing video but then completely forgets of the keyboard. No matter what key I hit, it does not respond, I can't even close and I'm forced to kill the process from a ssh session. Using CTRL + ALT + n combinations, I can see the various virtual terminals flashing in the middle of the running video, and if I hit keys the keystrokes then goes to the background virtual terminals instead of mpv. I tried force-window and input-terminal configuration options, but neither worked. Any ideas?
  7. Bona sera to you too I'm very glad everything went smooth for your setup! You can get 1.4 Ghz selecting running rk322x-config and selecting a board with rk3228b/rk3229 processor. There is a great confusion around the chip names and specifications, mostly due to rockchip not being clear and tv box manufacturers not being totally honest. Long story short: most of the rk322x tv boxes are advertised as 1.5 Ghz, but in reality rk3229/rk3228b chips are safe up to 1.4 Ghz and rk3228a chips are safe up to 1.2 ghz. Board manufacturers are often mixing things and don't update the specs. It is very common to buy a tv box advertised as rk3229 and get a rk3228a inside it. Also running a rk3228a at 1.4 Ghz is a mild overclock that is often well tolerated, but it is outside the technical specs of the chip and at last you may get instabilities. The generic 322x board in rk322x-config is the most compatible but also the least performant profile. Other profiles may enhance performance and features (enable eMMC DDR mode, fix the leds, bring 1.4 Ghz speed, ...) but may also incur in less stability, altough you should be safe if you select a board with the "eMMC" label, since your board has eMMC (lucky you!) Bluetooth is a very fiddly beast, it is annoying because it requires different setups for different manufacturers. Unfortunately here I have no boards with bluetooth on board and I could not develop anything about this. You should find the way to enable it googling around, usually drivers are not required, but a firmware and an userland application are, but can be a very tedious experience. I have a recipe for AP6330 chipsets that carry a broadcom bluetooth I can share, but have no experience with realtek ones.
  8. Woah, for some reason the link didn't paste. Fixed now! Thanks!
  9. Media framework installer v0.1 Hello, I managed to package some goodies for rk322x boxes for OpenGL/OpenGL ES applications support and accelerated video decoding. This work is heavily inspired by @JMCC media script, but simpler and more limited. It should bring enough to squeeze something useful from these boxes. This is only for Ubuntu Focal Legacy 4.4.194 Kernel builds. Mainline kernel still require some work on the video acceleration front, but when done everything will be much smoother for all of us! Currently it contains: Armsoc driver Libmali for Utgard Mali 400 (both X11 and GBM versions) GL4ES OpenGL to OpenGL ES wrapper RKMPP Media framework from Rockchip FFmpeg compiled with RKMPP support Kodi 18.6 Leia It doesn't include (yet) gstreamer, although gstreamer rockchip plugin is easy to compile and package. Instructions: Download the package from here Unpack the package in directory of your choice Open a terminal, move to the directory and run ./ - it will take less than 5 minutes to install everything Reboot the machine Done! OpenGL/OpenGL ES: OpenGL ES applications (like glmark2 benchmark) can run as-is. OpenGL applications can be run via GL4ES wrapper from command line using: glrun app_name Kodi: Due to some limitations of the proprietary Mali driver, to start Kodi you need to be in a virtual terminal and X11 must be closed. To do so: Press CTRL-ALT-F1 to move to virtual terminal 1 Log in with your credentials Execute systemctl stop lightdm to close X11 Run start-kodi Execute systemctl start lightdm to bring back X11 mpv: mpv does not require any particular treatment. Can be used directly from X11 in fullscreen mode or from a virtual terminal without X11. Install it if it is not already installed via usual apt command line. Run it with these switches to enable full video acceleration: mpv --hwdec=rkmpp -vo=gpu --gpu-api=opengl --gpu-context=drm --opengl-es=yes <video_file>
  10. jock

    Mainline VPU

    You're absolutely right. I was misguided by the high cpu usage during decoding, in fact when I run ffmpeg with -hwaccel drm I get 45 fps decoding rate (my BBB video is 1080p) but with 25% cpu usage (a single core is maxed to 100%, others are idling). Without -hwaccel drm I get 70 fps but with cpu usage nearly up to 100% and all cores are busy. Besides, outputting the raw frames to framebuffer (with -pix_fmt bgra -f fbdev /dev/fb0) works in both cases
  11. jock

    Mainline VPU

    Thanks a lot! I never thought that kernel headers could be the problem. Looking more thoughly there was a some mess situation with headers and was able to spot some missing definitions looking into ffbuild/config.log that prevented v4l2_request to be compiled in. I surely was not expecting that the configure script fails silently on a feature you explicitly request.. By the way I'm still not out of the tunnel. Ffmpeg compiles and v4l2_request works, but I get the error v4l2_request_try_format: pixelformat 875967059 not supported for type 10. 875967059 (0x34363253) is the ASCII for 462S, I don't know if this has some meaning...
  12. jock

    Mainline VPU

    Thanks for the answer. The command line does not trigger any error, decoding happens but still in software: I see no references about v4l2_request in the ffmpeg output, cpu usage is close to 100% and decoding rate is around 75fps. I see you say that this works for you with rkvdec module, but I have only hantro driver module at the moment. My kernel is vanilla 5.6.13.
  13. Did you have those problems with i2c bus? It was not working on your box if I remember correctly, maybe that's the reason you don't see anything during u-boot bootstrap and maybe that's the reason for the power down error too. From dmesg log I see that u-boot does not detect the attached display, you should get vidconsole after "Out:" and "Err:".
  14. @pro777 Here is a newer image with kernel 5.6.13. Chrony issue is now fixed and has better stability (panfrost gave me some issues with kernel 5.5). Hantro driver is enabled here too. U-boot 2020.01 and 2020.04 have some issues for me, I don't know if the video console is the cause or the fact I'm booting from USB. Anyway often it freezes in the middle of boot process, but not always at the same point and apparently not due to anything specific. Do you observe that thing too? Armbian Ubuntu Focal 20.05 Desktop - Kernel 5.6.13
  15. Just try other devices with on-board eMMC. Most of the differences relates to eMMC/NAND and on-board leds configuration.