Quote:
Originally Posted by elementarythree
Almost forgot to mention, with the vncserver method having bvnc running in it's own server, the disadvantage is that while we have the stylus and the touchscreen, potentially connected bluetooth keyboard, virtual keyboard etc. usable on the second server, we can't use the keyboard and mouse used on the first X server. (our Desktop)
This can be resolved by the program x2x which can be found in most distributions. Using it is pretty straightforward. Let's assume you have the eReader right of your main screen in front of you, then you'd just type:
x2x -from <number of your primary server the keyboard/mouse is connected to> -to <number of the vncserver> -east <for right of>
then you can move the mouse cursor over the right corner of your screen and into the vnc session of the other device, or type into windows, as if it was a second screen. You will not be able to drag windows into the other screen though.
in my example this would be: (primary xserver is :0)
vncserver :1 (to start the vncserver)
then
x2x -from :0 -to :1 -east
as we are running a full fledged xserver, everything will work in that vnc session that works on our primary server, including game controllers and such. We don't need to care about any security for the created traffic as both severs run on the same PC, and there will logically also be no latency as the tablet has nothing to do with that traffic at all and basically only displays the results. Just a heads-up: this also works over a network. Also yes, you will see two mouse cursors on the vnc session as you'll have two mouse cursors. You can even make them look differently if you want.
EDIT: corrected left to right. Heh.
|
Hi, as the discussion turned more on the (X) server side, I was winding of one of you might have a hint for a problem I can across when trying to use an Onyx Note (probably Likebook Mars would have same issue) in a dual screen setup with a slightly exotic little handheld device running Linux, the Gemini PDA. This runs Linux (sort of) natively, but the display drivers seem to be somehow android based, as xrandr just shows "hwcomposer".
My problem is that I haven't been able to get a Virtual1 head/output accessible via xrandr in order to get a secondary display output of the same virtual screen, which I could then pump into the VNC server.
I fiddled around in the xorg.conf a but, but that usually ended up breaking the internal screen display when nothing was connected, as it was pulling out the whole virtual screen even at the login screen.
There's a sketch of what I'm after here:
https://www.oesf.org/forum/index.php?showtopic=35503
A potential limitation of the Gemini PDA is that it's got no mouse-like device, hence my hope to run i3 and control most things via keyboard.
This is not something I actively look for any more, as I've found another, more powerful little device that might suit my requirements better, but it would still be nice to get something running in the Gemini.
So the short question is, can anyone think of a way that I could get a VIRTUAL1 (or other dummy) head show up in xrandr -without it being used by default (so as to avoid the display issues I had when hard coding stuff into xorg.conf), but making it available when I choose to?