Jump to content

dorin

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, thanks for the great work. Did I miss somehow the information about how to backup original android firmware? I booted from sd on a TX6, ran armbian-config but the only option I found was to burn image to flash, which I haven't done yet for obvious reasons (I'm not even sure yet if it's eMMC or NAND).
  2. I was able to get a 2x2 grid working in hw accelerated ffmpeg this way: glrun ffmpeg \ -i $CH1 -i $CH2 -i $CH3 -i $CH4 \ -filter_complex \ "[0:v][1:v]hstack=inputs=2[top]; \ [2:v][3:v]hstack=inputs=2[bottom]; \ [top][bottom]vstack=inputs=2[v]" \ -map "[v]" -f matroska - \ | glrun ffplay - (CH1-4 are the video source URI's) While it's faster than non-accelerated ffmpeg (invoked without glrun), it's still way too slow compared to mpv player. To put it into perspective, based on some rought monitoring with htop: ffplay -i $CH1: uses about 340% of CPU (almost maxes out the capacity) glrun ffplay -i $CH1: uses about 140% of CPU mpv $CH1 uses about 300% of CPU mpv --hwdec=rkmpp -vo=gpu --gpu-api=opengl --gpu-context=drm --opengl-es=yes $CH1: uses only about 15% of CPU So obviously mpv has the potential to be much faster than ffmpeg, therefore I tried: # WARNING: this doesn't work mpv --hwdec=rkmpp -vo=gpu --gpu-api=opengl --gpu-context=drm --opengl-es=yes \ $CH1 --external-file=$CH2 --external-file=$CH3 --external-file=$CH4 \ --lavfi-complex='[vid1] [vid2] hstack [t1] ; [vid3] [vid4] hstack [t2] ; [t1] [t2] vstack [vo]' But this doesn't work because the ffmpeg filter used under the hood apparently cannot be accelerated: [ffmpeg] Impossible to convert between the formats supported by the filter 'mpv_src_vid1' and the filter 'auto_scaler_0' [lavfi] failed to configure the filter graph Again, running mpv without hw accel but with --lavfi-complex works, and works slightly faster than ffmpeg but still not satisfactory. I'll have a look on the mpv forums.
  3. Hmm but it sounds like the rockchip cannot provide a sustainable solution this way. Even if I got a source playing and sized correctly in each plane, I would have a hard limit of 2-3 streams. My goal is to monitor cctv cameras, like the rpi can play 16 streams quite easily (example), which I guess it's possible due to the arbitrary number of hw planes you mentioned.
  4. Thanks, I tried this and it works. Now I am trying to play a couple of video streams simultaneously and display them in a grid. This is possible to achieve with omxplayer (https://github.com/popcornmix/omxplayer) but omxplayer works exclusively on raspberry pi GPU. But I cannot find how to do this with mpv, I had a look on the mpv documentation and the window geometry flags are ignored in gpu mode, and gpu rendering flags are a bit esoteric for me: https://mpv.io/manual/master/#gpu-renderer-options It's actually possible to start multiple mpv processes but since the window is always fullscreen, the image flickers between the sources. Any idea?
  5. I come back with a couple of updates. After about 30 seconds of no HDMI signal, it came back booting. I thought yayyy so good. And I flashed to eMMC. And I managed to brick the box, getting stuck into a reboot loop. It turns out I used the wrong u-boot due to confusing instructions from balbes150 - though I'm still thankful for his great technical work - (for S905W it should be u-boot-s905x-s912) and I also used the wrong eMMC installtion script (should be install-aml.sh). This post luckily clarified it for me: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus Now in order to unbrick the box I had to use this method of shorting resistor pad to GND It was a very tricky procedure of trial and error timing the shorting / release of the pad, had the windows burning tool crash a few times... Better to not brick in the first place. After unbricking with original android I was able to retry the armbian procedure successfully.
  6. I have a very strange problem with my X96 mini with S905W. About 2 years ago I followed the instructions for https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x-ver-544/ and I got it working. But now using the newer unified image (the exact same the author of this topic used) it doesn't boot from USB anymore. I used the same dtb /dtb/amlogic/meson-gxl-s905w-p281.dtb and u-boot-s905 as u-boot.ext and the AV button pressed using a toothpick but there's no signal on HDMI. Using the old USB drive flashed with the 5.1.15 (2019-07 ?) version it still boots fine. Now if this new unified image still can't work for whatever reason I'd like to flash a fresh USB drive using the old version but I see the archive links have been deleted..
  7. Nevermind, I'd probably done something stupid like removing the USB memory before poweroff. I re-flashed USB memory, ran again /root/install.sh and permissions are ok, no more 1023 garbage.
  8. Oh thanks, I didn't know it can be done with armbian-config. I will give it a try, because my ownership change "fix" only messed the system in subtle ways (ping returns "operation not permitted", pip install hangs forever, git clone hangs forever..). So, did you run armbian-config from root or from a normal user with sudo? Also, where is the option to do so? In System settings I can only see Freeze, Nightly, Bootenv, etc. but no Install.
  9. Okay, I rebooted and the mount was not read-only anymore for some reason. Then I tried to fix ownership and so far everything works fine. It's probably still messed up but so far so good: cd / find . -uid 1023 -exec chown root {} + find . -gid 1023 -exec chgrp root {} + There were some symlinks like /var/run -> /run that could not be changed, they are still under 1023, but I hope it doesn't affect operation. EDIT: This made my system functional but it's still messed up in subtle ways -> Don't try this fix. If you see any uid 1023, run away, do a clean reinstall because it's simply not fixable.
  10. Hi guys, and thank you balbes150 for your great efforts! I've been trying to get ubuntu working on x96mini. I flashed USB drive with Armbian_5.91_Aml-s905_Ubuntu_bionic_default_5.1.15_20190710.img.xz and it works just fine from USB boot, however there are some problems installing to eMMC. Before running /root/install.sh I edited uEnv.ini and extlinux.conf to include meson-gxl-s905w-p281.dtb as I considered it's the most suitable dtb for x96 mini because the SoC is s905w. Installation to eMMC completed and I was able to boot from eMMC after removing USB drive, the problem is that the majority of directories and files (including /bin, /etc, /usr and) are owned by uid 1023 and gid 1023 instead of root. They also seem to be read-only. This basically renders the system useless, because root can't edit system files or install system packages, etc. I tried replacing 1023 with root but it's not allowed (read-only). What could be the issue? Is it because of wrong eMMC partition tables? Or is it something from the installation script?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines