Jump to content

Moklev

Members
  • Posts

    65
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Everything posted by Moklev

  1. Maybe libmali-utgard-450-r7p0-fbdev.so is the Linux Framebuffer driver and libmali-utgard-450-r7p0.so the DRM x11 driver? However, a closed source for an obsolete and ridicolous GPU like a Mali 4x0 is pathetic. What is the current status of open source drivers like Lima or Panfrost?
  2. To replace it with a higher efficiency one, without "toothpaste". See the latest intel cpus (without welding).
  3. Ya, this code is too old and unpolished. Just have to wait Bootlin development for the end/2018.
  4. Yes, for CSI camera you must stay on legacy (Jessie dafault). CSI on mainline is on WIP stage. Main difference is Motion 3.2.12 (instead of 4.01). Next kernel 4.14.18 is more stable than 3.x (uptime: weeks vs few days). On Jessie may need "deb multimedia" packages for a recent ffmpeg version. I recommend you a good USB camera H264/MJPEG capable.
  5. With Motioneye use ONLY Debian server/headless, best with cabled ethernet. With wifi the performance is reduced. My setup is: Orange Pi Zero (512MB) with Armbian 5.41/Debian Stretch 4.14.18 (next), MotionEye 0.38.1 and Motion 4.01. Use H264 for maximum performance and MJPEG for maximum quality.
  6. Very bad performance. I got ca. 15/20 fps in 1280x720 and 30+ fps in 640x480 (limited...). With a Orange Pi Zero (slower than your PC Plus) and a system load of 1.30 ca. Motion trigger, light trigger and smart area mask.
  7. Motion has a complex workflow and an accelerated ffmpeg can help only partly. See the Raspberry/OpenMax version... which performs similarly despite is fully gpu accelerated (he's only more rapid to generate mp4 by events). Motion's analysis is frame-by-frame: you need to demux input stream, convert to raw single frames, processing and remux final stream.
  8. With an ELP 2mpx usb camera you can stream at 30+ fps, with streaming only and motion process disabled. Motion's slow dog process is a problem, you require an i5 cpu for a reasonable performance. With a little OPZ @1GHz Motioneye (Motion 4.01) runs at 15fps/720p but drop below 6-7fps if an event starts saving an image sequence (ca. 10 jpeg images).
  9. Simply... a old and patchy kernel (3.x) vs a stable and modern one (4.14.xx). My OPZ mainline runs for weeks too with pihole and motioneye.
  10. Uhmm... a full system backup with rsync? i.e. # rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / /path_to_backup_dir/ (as root) If you wish to restore, use the same command that was executed but with the source and destination reversed. Make you own --exclude list.
  11. 72.000 request (in 24h?) from a single domain is an abnormal situation. My log2ram (var/log) is always between 5 and 10%. This after 6 day pihole filtering (standard list + nocoin, standard logs, no blacklisting, 6 devices):
  12. Standard values (Armbian 5.41 Stretch, kernel xx.18, governor: ondemand). 1008MHz under load, now (after 6 days of uptime) rised up to 1200 Mhz. Without load, disabling motioneye and pihole, system stuck to 1,2GHz and won't get down to 240MHz as reported by @guidol. But... mainline image is in a testing stage and -good news- it's stable, not perfect but stable. :-)
  13. https://wiki.debian.org/Multiarch/HOWTO It's a x86 software... you can run it via qemu (multiarch/platform emulator) or: https://eltechs.com/product/exagear-desktop/ (only 32bit x86, closed source)
  14. No, he can't. For the MXQ Pro 4k (SOC: Amlogic S905X) try first the file "gxl_p212_2g.dtb" (if 2GB... or xxx_1g.dtb if 1GB). In general: p212: for Amlogic S905X p200/p201: for Amlogic S905 q200/q201: for Amlogic S912 ... and other version for specific hardware (S912 100mbps or 1gpps, Weitek Play, Khadas VIM/VIM2, Realtek wifi, etc...).
  15. RE-EDIT: This issue partially solved with new Armbian 5.41 with kernel xx.18. Now OPIZ run stable @1008MHz.
  16. Default pihole installation don't presents this issue. This situation after 24h use (standard log verbose): On OPIZ v1.4, Armbian Stretch 5.41, pihole 3.21
  17. Same feedback. OPIZ v1.4 512MB (Debian Stretch 5.38) Linux orangepizero 4.14.15-sunxi #28 SMP Mon Jan 29 07:24:48 CET 2018 armv7l GNU/Linux Governor: ondemand Stuck at 1,2GHz without load (but load value is normal in my 5.38) Turning to powersave cpu go down correctly to 240 Mhz I have not the file /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate in my installation: System logs: http://ix.io/FvU EDIT: @BRSS this value, in Debian Stretch, is saved to "cpuinfo_transition_latency" (7044144). But (if untouched) "ondemand" governor performs like "performance" one.
  18. ... and a good news about Allwinner VE (H3, H5, A64, h264, h265): https://www.cnx-software.com/2018/02/02/bootlin-wants-to-bring-allwinner-vpu-support-to-mainline-linux-crowdfunding/
  19. Uhm... No camera interface? :/ Inviato dal mio LG-D855 utilizzando Tapatalk
  20. Moklev

    Etcher.io bug

    Have you tried with fdisk + mkfs?
  21. Moklev

    Etcher.io bug

    Try to remove all partitions with gparted (or gnome disk utility). Make a new one and format it.
  22. Moklev

    Etcher.io bug

    1.3.1 https://forums.resin.io/t/etcher-v1-3-1-release/2446
  23. You don't need a new guide. Motion 4.1.1 isn't available on Armbian, Mr Dave's build is only for Raspbian. On Armbian (i.e. Orange Pi Zero) download new Stretch build 5.38 next, mainline 4.14.14. Do not use Ubuntu. Follow original installation guideline: https://github.com/ccrisan/motioneye/wiki/Install-On-Debian (For Debian Stretch) BEFORE point 4 install pip dependencies: sudo pip install wheel sudo pip install setuptools sudo apt-get install zlibc zlib-gst zlib1g-dev Continue to point 4... ... at the end of installation point to [yourip]:8765 and configure it. et voilà! :-) Now Motioneye 0.38 run on motion 4.01. New motion version is usefull for new cam h264/rtsp based. With little OPZ performance is quite respectable: 15fps (streaming) / 10 fps (analisys and capture) with a HD stream 1280x720px, H264 900 kbit/s 12fps (streaming) / 7 fps (analisys and capture) with a HD stream 1280x720px, mjpeg 2,5 mbit/s Load: 1.94 1.24 0.53 Temp: 70 °C (without hardware acceleration...) Mk
  24. Main problem now is related to Motion... mjpeg is not multithreaded, only one core (per camera) work into flow mjpeg->RAW->motion analisys->display output. H264/X264 is multithreaded (but still a low quality approach). Final output (movie) can be accelerated by (a future) version of FFmpeg. A good hw for a cctv project is an A17/A57/A72 ARM (out of order, fast single core performance compared to a A7/A53) or a low power Intel N3350 (Gigabyte Brix with Debian 9).
×
×
  • Create New...