This page will be a running log for problems I encounter and their solutions.
LXDE under Ubuntu 13.04
On Ubuntu 13.04 I have not been able to log in and use the LXDE desktop environment in the normal manner. The LXDM (Lightwaight X11 Display Manager) did show the login screen and I was able to log in, but got a blank (or blue) screen after that. Writing “ps aux” showed that the [PreLogin] process was stuck on <defunct>. starting lxde manually with startlxde did work fine. The only solution I have found to this so far is instead installing lightdm. Should be as simple as:
sudo apt-get install lightdm lightdm-greeter-example-gtk
The lightDM display manager might be a bit big. An alternative is the Gnome Display Manager (GDM).
Unable to log in via SSH
I’ve had a lot of trouble with logging in via SSH. One of the reasons is that the dropbear RSA key is corrupted. I think it might be related to having two BBBs.. From this thread on the beagleboard.org google group:
rm /etc/dropbear/dropbear_rsa_host_key dropbearkey -t rsa -f /etc/dropbear/dropbear_rsa_host_key
I’ve also had trouble with avahi-daemon.service active up and stealing all the resources. This can be seen by writing “top” and seeing that systemd takes up all the resources. To mask the avahi-daemon:
systemctl mask avahi-daemon.service
I have no idea what the consequences are, but this fixed the problem for me at least..
Driver "fbdev" Option "Rotate" "CCW"
This goes in the section “Device”. The driver replaces the “modesetting”-driver.
CCW stands for counter clock wise.
This only works for X11, so if you want to rotate the framebuffer, add this to the kernel command line:
Device tree compiler on Ubuntu 13.04
If you are getting the error:
dtc: invalid option — ‘@’
Robert C Nelson has a solution:
wget -c https:
//raw.github.com/RobertCNelson/tools/master/pkgs/dtc.sh chmod +x dtc.sh ./dtc.sh
For some reason ‘which dtc’ did point to /usr/local/bin/dtc, but I still had to specify the whole path. Weird..
Unable to configure bonescript
This is the error message:
Job for bonescript.socket failed. See ‘systemctl status bonescript.socket’ and ‘journalctl -xn’ for details.
I noticed that the job was unable to start since there was already a version running. The solution was to kill the running instance:
ps aux | grep server.js
find the pid and run:
Then try to start:
systemctl start bonescript.socket
This is probably not a permanent solution, but it worked for installing tslib that for some reason wanted to configure bonescript..