makama80

Yes I did. I duplicated the videostream (using vloopback and ffmpeg) from /dev/video0 to /dev/video1 and /dev/video2. I had defined 2 camera's in Kerberos.io: 1 USB on /dev/video1 and had Motion running at the same time on /dev/video2. Subsequently I took de IP stream from Motion and used it successfully as second camera (however, picture / videdo was the same of course since vloopback duplicated the cam on /dev/video0). So it is pseudo-IP camera, but the concept works.

I think it will run on 512 mb without problems, especially if you install a non-desktop version. My OPI+ runs with desktop version of Armbian and Kerberos.io and Motion together using approx 350 MB of RAM. I still have to test if the .deb file + RPI libraries work. I guess it will, but am not sure. Compiling is quite easy and makes sure it will work. I will have a look if I can post the libraries here: they are only needed for compiling and running, but are actually not used because there is no such thing as a raspicam under Armbian. But please give me some time. I will try to have a look in the weekend.

My orangepi camera is not working anymore: the connector is defective I think. However: to my humble knowledge the orange pi camera is functioning as an ordinary USB camera: therefore if you install the program as described (make sure you define the 'USBCamera' in the config file) and select an existing resolution of the OPI cam I guess that it should work.

UPDATE 11-FEB-2017: Version 2.2.0 is released: now including video recording in stead of only images and also a privacy option to black out areas that may not be filmed. UPDATE 09-FEB-2017: Version 2.2.1 is released: memory leak(s) fixed and in some cases video stopped recording. This should be fixed now. Download via this page. Kerberos.io (link) is a relative new video surveillance program focusing mainly on the Raspberry Pi. In collaboration with the owner of the github project I managed to get it working on my Orange Pi Plus and PCDuino3 nano using Armbian (Debian Jessie) and a Logitech UVC compatible USB webcam. It consists of 2 modules: the Machinery module and Web module. The machinery module was very Raspberry Pi specific, but is now updated and can also run with very little extra effort on Armbian. The Web module runs without any modification. Follow the instructions below and you should be able to install or compile it. Kerberos.io is very fast and has a modern interface. Furthermore it is (IMHO) a very nice alternative for zoneminder and motion.It also provides a videostream on a webpage. Follow the instructions below and share your comments, ideas etc. Method 1 (easy) - Install on Armbian Debian Jessie. Follow the instructions on the dedicated Armbian page (link). Here you will find an Armbian precompiled .deb armhf package. Further installation / configuration options can be found on the Kerberios.io webpages. Method 2 (advanced) - Compiling the machinery and web module on Armbian Debian Jessie. Install the following packages: sudo apt-get install pkg-config libavcodec-dev libavformat-dev libswscale-dev Follow the instructions on this page (link). Further installation / configuration options can be found on the Kerberios.io webpages. In all cases: please note that you must alter the camera configuration: default it comes with the Raspberry Pi camera that you probably won't have!

(Suggestion) Check the forum first before posting suggestions: see this post This method also includes updating when a new version is released via apt-update / upgrade. The method above does not.

Don't know if it's relevant, but I always use Webmin to configure samba on my boards running armbian (debian). For those who don't know Webmin: Webmin provides a web-based management console for linux computers In combination with the authentic theme (needs separate installation) Webmin provides a reasonable modern user interface for all kinds of linux management tasks. It also includes a module for samba. Give it a try; I think it makes life easier especially when you do not have a desktop running. Installing is easy and straight forward; start at 'Using the Webmin APT repository' on this page: Webmin After installing start your browser and go to https://yourarmbiancomputer:10000 and Webmin should give you response. I guess it will also work for ubuntu, but have not tried it yet. There is lots of other information and add-ons on the webmin website so give it a try. -End of the commercial break-

I hope the screenshot helps you out. Please refer to the screenshot. Note that this shows load during a http livestream to one of my computers (not recording, only streaming) and my opi+ is in a closed acrylic case without a fan (which I am going to install after this post). So the temperature is somewhat elevated. CPU load is quite acceptable I guess... Off course during recording it's much higher, but the OPI+ is capable of handling recording also quite wel...

This post is to share my successful webcam installation with Armbian and one of my SBC’s (orange pi plus). I’ve used a Logitech C270 which can be purchased from eBay for roughly 20 Euros. Also el-cheapo shops like lightinthebox sell the C270. Benefit of such a cam is that you now have a cable from your SBC to your cam which makes (physical) cam installation easier IMHO. Also IMHO the C270 is a better camera than the famous GC2035, but it is also more expensive. Price / 'bang for the buck' ratio is more or less the same for both camera’s if you ask me. You get what you pay for. Enough talk now: the installation All I did was a fresh Armbian desktop v5.20 installation. The Armbian desktop version makes file editing easier, but is not mandatory. Nano / vim etc. can do this job via SSH as well. Performed the usual ‘apt update’ and ‘apt upgrade’ + reboot after installation. Then after restart ‘apt install xrdp tightvncserver motion’. xrdp and tightvncserver enable remote desktop. This is not needed for camera operation, but makes life easier… you can now access your Armbian installation with the Microsoft remote desktop protocol. The C270 camera works right out of the box and is auto-detected by Armbian. Also the needed modules are loaded automatically (use the lsusb and lsmod commands to see it). Now edit /etc/motion/motion.conf with your favourite editor. Highest resolution I could get from the C270 camera is 1280x960. (search for ‘width’ and ‘height’) and adapt accordingly. Find ‘stream_localhost’ and turn it off. Otherwise you won’t be able to http-stream to other computers. Change ‘target_dir’ to anything you like, but preferably a folder outside of your armbian board with more storage capacity. Movies are rather large and may fill up your sd card or EMMC quickly. Make sure motion has writing privileges in the folder you choose. Then (very important!) edit /etc/default/motion and set “start_motion_demon†to “yesâ€. Otherwise the daemon won’t start. Now a ‘sudo service motion restart’ should start motion. A ‘sudo service motion status’ might provide more info about issues. Then the magical moment: direct your browser to http://your_armbian_board_address:8081 and it should provide the stream of your camera. When movement is detected, avi files are stored in the folder you’ve entered in motion.conf. Further you can tweak some settings from /etc/motion/motion.conf according you your needs. I have disabled ‘output_pictures’ because I am not interested in a JPG file along with a movie file. The default motion detection threshold of 1500 works fine for me (recording backyard). Every time you change something in /etc/motion/motion.conf you have to issue a ‘sudo service motion restart’ to load the new parameters. Always keep a copy of a working motion.conf file; this is helpful in case of mistakes / typos etc. Good luck!

Accodring to my humble opinion: better is having full documentation of the SOC on the board. (Almost) nevertheless what chip is on the board: (a sort of) reverse engineering is sadly what the community has to deal with at the moment...

Hello, It seems like the 'FORCE_MODULE_UNLOAD' parameter was (set to?) 'N' during the generation of the Armbian kernels. I know it's potentially dangerous to use it, but since the community is doing a lot of experimenting it would be convenient sometimes if this is enabled. Does this mean I have to compile a kernel with this option enabled myself, or is it possible to turn it on in future builds?

Thanks! I was already afraid of what you replied. Well... let's pray that Zador can fix the issue or that a manual workaround for the 1GB boards is possible. If help is needed for documenting that, I am willing to help / participate where possible,

First of all ('Boring' alert!): outstanding job with the new updates. It must be lonely at the top. Kudos! Then (just curious!): is there any particular reason known that the amount of memory is an issue for GLshim? Then secondly: I do have an orange pi + (H3, 1 GB memory, Mali400)... according to the changelog GLShim is not in... For me it does not make sense... Regards, Makama80

Ehh... @ My sources.list: Evidence:

Some people say stupid questions do not exist. That's my justification of asking the following: What's wrong with installing the package 'firmware-realtek'? I see people struggling with compiling drivers, while I have 4 different realtek USB wifi dongles (different chipsets as well) and they all work fine for me in the fabulous armbian (it's lonely at the top) after an 'apt-get install firmware-realtek'. This saves me time, which I can now spend on drinking a cold beer in the sun! Maybe someone with greater knowledge then (the simple) me can enlighten what's wrong with installing the firmware-realtek package?

For what it's worth: I managed to compile VICE (classic commodore computer emulators) on my roseapple pi board running Armbian. I could not find it in the repository, so I started fiddling myself. This to address some nostalgic feelings which come by so now and then! Recipe in the spoiler.... Screenshot: