After working on this for a while, I think it is a problem with LXQt. I
installed the core of LXDE and a few LXDE apps, rebooted and then removed
LXQt. Now I have no problem using TurboVNC. This also saved a large amount
of eMMC space. LXDE works just fine for my purposes.
sudo
no matter which vnc client (tight, turbo, tiger), the keyboard mapping is
wrong when running tighvnc on the bbg wireless.
asdf becomes abfh...
xsetup does have "export XKL_XMODMAP_DISABLE=1"
does anyone have a work-around?
Thanks.
--
For more options, visit http://beagleboard.org/discuss
---
this is a fairly recent install of Jessie, apt-get update/upgrade, and a
few packages like tightvncserver, gksu, ntp, autocutsel, tightvncserver,
leafpad, ... and I didn't ask explicitly for connman or cmst to be
installed.
running from xterm "cmst" puts up a dialog box about installing a new
My experience is that the echo only works if you are logged on as root. it
never worked with sudo for me.
I found uEnv.txt at /boot/uEnv.txt
For fear of opening a can of worms, the numbering of the three I2C buses
is, for lack of a better term, illogical. From the aspect of an engineer,
My experience is that the echo only works if you are logged on as root. it
never worked with sudo for me.
I found uEnv.txt at /boot/uEnv.txt
For fear of opening a can of worms, the numbering of the three I2C buses
is, for lack of a better term, illogical. From the aspect of an engineer,
Does anyone know if there is an update to this figure anywhere, which
accurately shows the locations of TP5-8?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this
