Gravelrash

i made my own cable from an old usb cable and a power connector of the correct size. i can confirm that: a. with a good quality 2a psu i get no power or stability issues b. with a crappy 2a psu - its unpredictable c. With a good quality 1a psu its works fine.

thanks for you feedback and comments - i will expand and modify the HOWTo with your feedbacks. the request for feedback is to make it more specific to the way people on here use NFS. whilst tryong to keep it as simple as possitble so anyone coming across this for the first time could also use it.

Reserved : Please test / feedback any observations comments you have

NFS Server and Client configuration now posted here : http://forum.armbian.com/index.php/topic/1482-howto-nfs-server-and-client-configuration/

We will be configuring in a mode that allows both NFSv3 and NFSv4 clients to connect to access to the same share. Q. What are the benefits of an NFS share over a SAMBA share? A. This would take an article in itself! But as a brief reasoning, In a closed network (where you know every device), NFS is a fine choice. With a good network, throughput it disgustingly fast and at the same time less CPU intensive on the server. There are a lot of applications that support NFS "Out of the box" KODI being a common example. It's very simple to set up and you can toggle readonly on shares you don't need to be writeable. It only gets complicated if you want to start layering on security through LDAP/gssd. It's capable of very complex and complete security mechanisms... But you don't need them in this scenario. Q. Why are we doing this and not limiting to NFSv4? A. Flexibility, this will allow almost any device you have that supports reading and mounting NFS shares to connect and will also allow the share to be used to boot your clients from which will allow fast testing of new kernels etc. Q. Why would I want to do this? A. You can boot your dev boards from the NFS share to allow you to test new kernels quickly and simply A. You can map your shared locations in Multimedia clients quickly and easily. A. Your friends like to struggle with SAMBA so you can stay native and up your "geek cred" This HOWTO: will be split into distinct areas, "Section One" Install and Configure the server "Section Two" Configure client access. "Section Three" Boot from NFS share. (a separate document in its own right that will be constructed shortly). "Section One" Install and Configure the server Install NFS Server and Client apt-get update ; apt-get upgrade ; apt-get install autofs nfs-kernel-server nfs-common --install-recommends -f -y ; Now reboot sync ; reboot ; I will be making the following assumptions (just amend to suit your environment) 1. You already have a working system! 2. Your media to be shared is mounted via fstab by its label, in this case Disk1 3. The mounted disk resides in the following folder /media/Disk1 4. this mount has a folder inside called /Data Configure NFS Server (as root) cp -a /etc/exports /etc/exports.backup Then open and edit the /etc/exports file using your favourite editing tool: Edit and comment out ANY and ALL existing lines by adding a “#†in front the line. Setup NFS share for each mounted drive/folder you want to make available to the client devices the following will allow both v3 and v4 clients to access the same files # Export media to allow access for v3 and v4 clients /media/Disk1/Data *(rw,sync,insecure,no_root_squash,no_subtree_check,nohide) Explanation of above chosen parameters rw – allows read/write if you want to be able to delete or rename file async – Increases read/write performance. Only to be used for non-critical files. insecure – This setting allow clients (eg. Mac OS X) to use non-reserved ports to connect to the NFS server. no_subtree_check – Improves speed and reliability by eliminating permission checks on parent directories. nohide - makes it visible no_root_squash - *enables* write access for the connecting device root use on a NFS share Further explanations if you so desire can be found in the man page for NFS or from the following link http://linux.die.net/man/5/exports Starting / Stopping / Restarting NFS Once you have setup NFS server, you can Start / Stop / Restart NFS using the following command as root # Restart NFS server service nfs-kernel-server restart # Stop NFS server service nfs-kernel-server stop # Start NFS server # needed to disconnect already connected clients after changes have been made service nfs-kernel-server start Any time you make changes to /etc/exports in this scenario it is advisable to re export your shares using the following command as root export -ra Ok now we have the shares setup and accessible, we can start to use this for our full fat linux/mac clients and or configure our other "dev boards" to boot from the NFS share(s). "Section Two" Configure client access. We now need to interrogate our NFS server to see what is being exported, use the command showmount and the servers ip address showmount -e "192.168.0.100" Export list for 192.168.0.100: /mnt/Disk1 * In this example it shows that the path we use to mount or share is "/mnt/Disk1" (and any folder below that is accessible to us) NFS Client Configuration v4 - NFSv4 clients must connect with relative address Use the mount command to mount a shared NFS directory from another machine, by typing a command line similar to the following at a terminal prompt as the root user (where 192.168.xxx.xxx is the server I.P. address) mount -t nfs -o vers=4 192.168.xxx.xxx:/ /home/â€your user nameâ€/nfs4 The mount point directory /home/â€your user nameâ€/nfs4 must already exist and there should be no files or subdirectories in the /home/â€your user nameâ€/nfs4 directory. Another way to mount an NFS share from your *server is to add a line to the /etc/fstab file. The basic needed is as below 192.168.xxx.xxx:/ /home/â€your user nameâ€/nfs4 nfs auto 0 0 NFS Client Configuration v3 - NFSv3 clients must use full address Use the mount command to mount a shared NFS directory from another machine, by typing a command line similar to the following at a terminal prompt as the root user (where 192.168.xxx.xxx is the server I.P. address) mount -t nfs -o vers=3 192.168.xxx.xxx:/media/Disk1/Data /home/â€your user nameâ€/nfs3 The mount point directory /home/â€your user nameâ€/nfs3 must already exist and there should be no files or subdirectories in the /home/â€your user nameâ€/nfs3 directory. "Section Three" Boot from NFS share. please refer to this document on creating the image https://github.com/igorpecovnik/lib/blob/master/documentation/main-05-fel-boot.md - there will be an additional HOWTO & amendment to this HOWTO to cover this topic in more detail.

soon as my camera lands i will test - wont be for about 2 weeks though

is anyone keeping a list anywhere thats available of claimed & completed tasks & other tasks needing volunteers? if not may be an idea for one of the senior bods to start and own it.

been pipped to the post on the last item i was packaging..... so I will claim. packaging / debianization for the following xf86-video-fbturbo : correct me if i am wrong, but i believe you build this one : https://github.com/ssvb/xf86-video-fbturbo

ok - on to other packaging needs a recomendation for the gucview that i was going to add Two .desktop shortcuts, one for standard usb and one for the onboard camera both require different launch parameters

Just a note to confirm i received my board yesterday morning.

i dont seem to be even able to extract them... having said that - if you already have the files compiled and debs made, do you need me to continue working on a .deb build script?

From the work i have done with @lex thus far: It is recomended that the changes he has made are compiled on the architecture of the board it is to be used on - in this instance H3 - from my notes of our discussions, it absolutely must NOT be cross-compiled

gucview does have this packaed already - https://packages.debian.org/jessie/guvcview- 2.0.1 that is what i intended to base the package on. HOWEVER - when the debian package is extracted, there are quite a few files that are not there that are installed with the "make install" command.

Question : if you remove Removed autodetection for H3 boards - how will we determine which settings to use?

looking good so far (git clone https://github.com/avafinger/guvcview) - issued a make install the from command line, issued guvcview and the application loaded. minor problem my end, i cant test it till the camera module arrives. Q. would you like me to continue with the packaging? Q. would you like me to wait until i have the camera module to test this works and then package.

@lex this is too long a post to send in a P.M. so steps and results listed below. The following is performed on a fresh rootfs on an OrangePi One - with the latest (at time of writing) Debian Desktop http://mirror.igorpecovnik.com/Armbian_5.13_Orangepione_Debian_jessie_3.4.112_desktop.7z following steps performed software installed apt-get install intltool autotools-dev libsdl1.2-dev libgtk-3-dev portaudio19-dev libpng12-dev libavcodec-dev libavutil-dev libudev-dev libusb-1.0-0-dev libpulse-dev libgsl0-dev libv4l-dev libv4l2rds0 --install-recommends -f -y cloned your repo into the working directory /usr/src/ git clone https://github.com/avafinger/guvcview edited ./bootstrap.sh and replace ./configure line with "./configure --prefix=/usr --enable-yuyv --disable-sdl2" -without quotation marks, as performing standard ./bootstrap.sh errors out with attempting to correct ask for mesa utils installation which will not install as it conflicts with other packages WITH A MODIFIED ./bootstrap.sh the following output is seen when issuing the make command, the following is noted is the above expected behaviour of have i forgotten to do somethin??

teken me a while to work this out but this seems to be the files and folder structure that needs packaging (from the master branch - will be doing your fork next +/usr/local/bin/guvcview +/usr/local/include/guvcview-2/libgviewaudio/gviewaudio.h +/usr/local/include/guvcview-2/libgviewencoder/gviewencoder.h +/usr/local/include/guvcview-2/libgviewrender/gviewrender.h +/usr/local/include/guvcview-2/libgviewv4l2core/gview.h +/usr/local/include/guvcview-2/libgviewv4l2core/gviewv4l2core.h +/usr/local/lib/libgviewaudio-2.0.so.2 +/usr/local/lib/libgviewaudio-2.0.so.2.0.0 +/usr/local/lib/libgviewaudio.a +/usr/local/lib/libgviewaudio.la +/usr/local/lib/libgviewaudio.so +/usr/local/lib/libgviewencoder-2.0.so.2 +/usr/local/lib/libgviewencoder-2.0.so.2.0.0 +/usr/local/lib/libgviewencoder.a +/usr/local/lib/libgviewencoder.la +/usr/local/lib/libgviewencoder.so +/usr/local/lib/libgviewrender-2.0.so.2 +/usr/local/lib/libgviewrender-2.0.so.2.0.0 +/usr/local/lib/libgviewrender.a +/usr/local/lib/libgviewrender.la +/usr/local/lib/libgviewrender.so +/usr/local/lib/libgviewv4l2core-2.0.so.2 +/usr/local/lib/libgviewv4l2core-2.0.so.2.0.0 +/usr/local/lib/libgviewv4l2core.a +/usr/local/lib/libgviewv4l2core.la +/usr/local/lib/libgviewv4l2core.so +/usr/local/lib/pkgconfig/libgviewaudio.pc +/usr/local/lib/pkgconfig/libgviewencoder.pc +/usr/local/lib/pkgconfig/libgviewrender.pc +/usr/local/lib/pkgconfig/libgviewv4l2core.pc +/usr/local/share/appdata/guvcview.appdata.xml +/usr/local/share/applications/guvcview.desktop +/usr/local/share/doc/guvcview/AUTHORS +/usr/local/share/doc/guvcview/ChangeLog +/usr/local/share/doc/guvcview/COPYING +/usr/local/share/doc/guvcview/INSTALL +/usr/local/share/doc/guvcview/README.md +/usr/local/share/locale/bg/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/bg/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/bs/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/bs/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/cs/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/cs/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/da/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/da/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/de/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/de/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/en_AU/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/en_AU/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/es/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/es/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/eu/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/eu/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/fo/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/fo/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/fr/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/fr/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/gl/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/gl/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/he/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/he/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/hr/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/hr/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/it/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/it/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/ja/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/ja/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/lv/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/lv/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/nl/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/nl/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/pl/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/pl/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/pt_BR/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/pt_BR/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/pt/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/pt/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/ru/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/ru/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/si/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/si/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/sr/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/sr/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/tr/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/tr/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/uk/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/uk/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/locale/zh_TW/LC_MESSAGES/guvcview.mo +/usr/local/share/locale/zh_TW/LC_MESSAGES/gview_v4l2core.mo +/usr/local/share/man/man1/guvcview.1 +/usr/local/share/menu/guvcview +/usr/local/share/pixmaps/guvcview/audio_controls.png +/usr/local/share/pixmaps/guvcview/camera.png +/usr/local/share/pixmaps/guvcview/close.png +/usr/local/share/pixmaps/guvcview/guvcview.png +/usr/local/share/pixmaps/guvcview/image_controls.png +/usr/local/share/pixmaps/guvcview/movie.png +/usr/local/share/pixmaps/guvcview/video_controls.png

N.M - post retracted

Thankyou for the above, thats interesting and informative reading, I still favour the A20 boards with there true sata interface

One thing i have come across while looking into packages and packaging is "post install scripts". I would look to use this method something along the lines of convert file from y -> x format, use sed or awk or whatever method you deem fit to find and replace/modify the string you are interested in then convert the file back x -> y format.

@all preamble - i can quite straightforwardly craft a script that clones a repository, compiles the software and creates a .deb package Question : to include this for your builds as a standalone package for downloading at a future time, what is your preferred directory structure? I presume that this wont be at the build image stage of the script or even in the image itself. So where would your preferred locations be so i can mirror them into the build script? have i missed a documentation piece of a link somewhere? e.g. clone into /src/"packagename" -> compile -> deb creation -> build output to /?? i can then contribute successfully

had a quick look at what you are proposing and i think i can help you.

Thankyou for posting this. there are many people who visit this forum that are looking for support and solutions as you have posted above. The devs are looking for help to create more Desktop style images and solutions. You seem like just the sort of person they are looking for to assist. Your contribution could well be rewarded!! please take a look here http://forum.armbian.com/index.php/topic/1325-claim-a-task-set-due-date-and-start-doing-it/

i would use the following syntax in my /etc/fstab file //<server>/<share> <mount point> cifs rw,_netdev,user=<username>,password=<password>,uid=<uid>,gid=<gid> 0 0

@Joachim - have you fixed this or do you still need assistance?