So you’ve got your Raspberry Pi setup, but what if you don’t have a dedicated monitor to use with it (for example, mine’s connected to my TV). How can you use it without disrupting your setup? VNC (Virtual Network Computing) allows you to see your Pi’s desktop and control it remotely using another computer running Mac OS X, Windows or Linux (and other devices too).
The VNC server software runs on your RPi, access it by running VNC client software on your other device.
The VNC Server
- Install tight VNC: “sudo apt-get install tightvncserver”
- Run the program: “tightvncserver”
- Start a VNC session: “vncserver :1 -geometry 1024x728 -depth 24”
- Configure the session’s resolution after the -geometry argument. In the above 1024x768 is used. The RPi is capable of full HD so you could try 1920x1080.
- Colour depth is specified by the -depth argument. In the above exampe, 24-bit colour depth is used. You could use 16-bit instead to reduce network traffic.
- You can start more than one VNC session by running subsequent vncserver commands, just increment the first digit: e.g “vncserver :2 …” for a second, ”vncserver :3 …” for a third (I don’t know how many the RPi could handle).
- You can set this to run at start up, see the eLinux wiki tutorial, or look for a later post on this blog on automatic login which can start the VNC session with less effort.
The VNC Viewer/Client
There are lots of VNC clients you can use, depending on your platform. I’m using Apple’s Remote Desktop software which is incredibly powerful (especially when administering Macs) but is overkill if you are just using it with your RPi. TightVNC has a free client application, there’s a native Windows version and a surprisingly good (but limited) Java version, which should run on any desktop/laptop system. A Google search should find you a suitable app for your own system.
To connect to your RPi:
- Get your RPi’s IP address by running “ip addr show”. The IP address with be shown as highlighted in the image below.
- Connect your client to the IP address obtained from 1.
- Use port “590x”, where “x” is the session number used in step 3 in the previous section. If this doesn’t work, enter the IP address followed by “:x”, e.g. “192.168.1.50:1”.
- cyberneticgutterslut likes this
- playlistplayhouse likes this
- media-gallery-pro likes this
- media-gallery-pro reblogged this from gettingstartedwithraspberrypi and added:
- goddamnitgoodman likes this
- unadjustd likes this
- jcsundevil reblogged this from gettingstartedwithraspberrypi
- elusios reblogged this from gettingstartedwithraspberrypi
- elusios likes this
- cawfeefodinna likes this
- fueledbyb likes this
- bgwilf reblogged this from gettingstartedwithraspberrypi
- bgwilf likes this
- gianttimber likes this
- atphonehome likes this
- getbiggerbutt likes this
- shamurai likes this
- dreams-beds likes this
- newimprovebrainfunction reblogged this from gettingstartedwithraspberrypi
- newimprovebrainfunction likes this
- digitalamit reblogged this from gettingstartedwithraspberrypi and added:
- angelblue01 likes this
- bhargav-ak likes this
- cpmiv reblogged this from gettingstartedwithraspberrypi
- cpmiv likes this
- actsimply likes this
- yolkyolk likes this
- webpi likes this
- webmensch reblogged this from gettingstartedwithraspberrypi
- andreaskopp likes this
- jamesacampbell likes this
- radeusgd likes this
- raspiboys reblogged this from gettingstartedwithraspberrypi
- richddean likes this
- makridenkov likes this
- acoustassist likes this
- dogcowuk likes this
- gettingstartedwithraspberrypi posted this