# Raspberry PI VNC

**URL:** <https://discourse.libcinder.org/t/raspberry-pi-vnc/271>\
**Category:** Developing Cinder\
**Created:** [September 18, 2016, 2:53pm UTC](https://discourse.libcinder.org/t/raspberry-pi-vnc/271 "2016-09-18T14:53:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gabor\_papp](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.libcinder.org/gabor_papp/32/769_2.png) [@gabor\_papp](https://discourse.libcinder.org/u/gabor_papp)\
**Post date:** [September 18, 2016, 2:53pm UTC](https://discourse.libcinder.org/t/raspberry-pi-vnc/271/1 "2016-09-18T14:53:30Z")

</div>

I’m trying to setup vnc access on a Raspberry PI. It is a bit tricky because most of the vnc servers work with the X desktop, but does not show anything from the cinder application.

As I learnt this is because OpenGL ES uses dispmanx on the RPi. Fortunately there is [dispmanx\_vnc](https://github.com/patrikolausson/dispmanx_vnc.git), which works very well, except the keyboard and mouse input.

I looked briefly into this, and I suspect the cause of this is that cinder reads the events from [/dev/input/by-id]  
([https://github.com/cinder/Cinder/blob/android\_linux/src/cinder/app/linux/AppImplLinuxEgl.cpp#L680](https://github.com/cinder/Cinder/blob/android_linux/src/cinder/app/linux/AppImplLinuxEgl.cpp#L680)), while the vnc events are in `/dev/input/eventX`, and `/dev/input/mouseX`.

Does anyone have any experience with this? Maybe @petros?

Thanks,  
-Gabor

---

<div class="post-metadata">

**Author:** ![nselikoff](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.libcinder.org/nselikoff/32/157_2.png) [@nselikoff](https://discourse.libcinder.org/u/nselikoff)\
**Post date:** [September 19, 2016, 12:58pm UTC](https://discourse.libcinder.org/t/raspberry-pi-vnc/271/2 "2016-09-19T12:58:55Z")

</div>

I would be interested in being able to do this as well. I know openFrameworks faced the same issue; from [this thread](https://forum.openframeworks.cc/t/problems-raspberry-pi2-openframeworks-and-vnc/21932/6) it looks like they were able to solve the mouse and keyboard input issues. Looking at the [relevant pull request](https://github.com/openframeworks/openFrameworks/pull/2990) it looks like you are right and they modified the core code to fallback to `/dev/input/eventX` etc.

-Nathan