Topics

1

Gemini PDA - Linux / VNC server and xrandr on Gemini

« on: August 30, 2018, 04:28:40 pm »

I had planned on using an Android tablet (more specifically the Android e-Reader Onyx Boox Note) as an extended external screen for the Gemini on Linux, basically along the lines of what is described here: https://www.hitbits.net/2016/02/26/use-an-a...r-for-linux-pc/

Unfortunately, I hadn't thought of the issues that the Gemini's somewhat idiosyncratic graphics implementation raises. In particular, I'm stumbling on the crucial step of getting xrandr to make an additional, virtual output available. The only advice I found online for that so far involved adding lines to xorg.conf (or the modern descendants), but those instructions were specific to intel graphics. On the gemini, xrandr only has a hwcomposer device. I don't know much about these things, but I got the impression that's actually an Android thing?

In any case, does anyone have any advice to either introduce a VIRTUAL output for xrandr to then pipe to a VNC server, or any other method of being able to use a tablet device with a VNC client to display an extended Linux desktop?

As an aside, in case anyone else is interested in such a solution -if it turns out to be feasible - in terms of connectivity I'm aiming to have the Android device connected to the Gemini via a USB network, which should be comparatively unproblematic using the rndis device that automatically shows up (and for the Android-side of things, in case anyone's interested, there are quick instructions and even a simple app on mobilereads by user mdp: https://www.mobileread.com/forums/showthrea...2001&page=5 ).

2

Gemini PDA - Linux / Using newer packages than stretch

« on: July 15, 2018, 10:01:55 am »

I noted before even getting my Gemini that it appears to be impossible for now to use Debian testing proper, as there seem to be some special packages that aren't available there. (Correct me if I'm wrong, of course!)

I can live with having stretch as the basis, but there are some packages that I'd need newer packages of, for example texlive, which has an old 2016 version in stretch. I also have trouble with i3 window manager, which may or may not be solvable with the packages (may ask in the i3-related thread separately).
So I thought, I'd use apt-pinning to make stretch-backports and/or testing packages available without updating the whole system.
Unfortunately, that doesn't seem to be how it works, even with only stretch-backports the system does not boot up properly after apt upgrade. I was still able to get into it via Linux Deploy from Android, but the normal Linux boot just sat on the splash screen for half an hour, until I decided to just shut down the device.

I have for now decided that I cannot use the native Linux productively with this restriction and am trying to get workable Linux Deploy chroot + XSDL x-server setup running in Android. (This has its own issues with getting the keymap to work properly, unfortunately, but I'll try and find the appropriate thread for asking about that when I find some more time).  However, ideally I'd like to be able to use the native Linux without fearing not to get back in. Does anyone know of a way to get newer packages working without breaking the device? Or could anyone pinpoint what is causing the problems when trying to update so as to try and build around the relevant packages that must not be updated?