How to get A gui on my beagle bone

GoogleGroups
21

Lots of gnome related software seems to hard lock the system. Usually
it's as simple as opening gimp and clicking file -> open..

Regards,

22

indeed Robert. Worked for me. You seriously rock!!

23

hey Robert.

I’m using Ubuntu 13.10 and **/boot/uboot/tools/ubuntu/**small-lxde-desktop.sh
as I mentioned before, some applications freeze the BBB.

For text editing - Editra works totally fine.
Have u checked any image viewers / pdf readers / video players with this?
I’ve tried few image viewers, they froze my BBB.

thanks a lot

24

I have the same problem. some softwares freeze the Ubuntu GUI. Is there any criterian to chose softwares such a way the BBB doest freeze?

25

anything libgtk/gnome..

Like i said in another thread... Someone needs to debug this, get a
trace right before the system goes down. Something is locking up the
core..

Regards,

26

Gerald,

well ok, I guess you meant that libgtk/gnome based apps will freeze the BBB. I’ll try to use non libgtk/gnome apps.

Someone needs to debug this, get a trace right before the system goes down.

If you explain/provide a link on how to do it, I will give it a try & update here

thanks for the info.

27

I doubt anyone would have time to teach you to use gdb, but that is what you need to learn how to use. → gdb.

Quite honestly I am still learning gdb myself, and mostly from the context of programming / debugging, but as I recall it is something like gdb with maybe a command line switch or something to load the offending process / program.

28

Read this http://www.linuxjournal.com/article/1298

But in short and directly from the article . . .

To debug a compiled program with gdb, use the command:

$ gdb program [ core-dump ]
where program is the filename of the executable file you want to debug, and core-dump is the name of a core dump file left from an earlier attempt to run your program. By examining the core dump with gdb, you can discover where the program failed and the reason for its failure.

29

Hi RobertCNelson ,

I was using debain 9.2 and 9.3 Iot image on Begale Bone Black wireless board connected to 7 in Lcd.
On Lcd Command line is working . I want to make it Desktop GUI.
I tried your script but unable to make it Desktop GUI on the board ( https://github.com/RobertCNelson/tools/blob/master/debian/small-lxde-desktop.sh#L18)

Please guide me or suggest .

Here is the log
debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l GNU/Linux
debian@beaglebone:~$ cat /etc/debian_version
9.3
debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2017-10-10
debian@beaglebone:~$

Regards,
Sree

30

Hi ,

I want to install desktop environment on begale bone balck compiled kernel.

I tried the script file provide by you.It is not working here is the error message.
Please check the log and provide the solution.

[sudo] password for debian:
Err:1 http://repos.rcn-ee.com/debian stretch InRelease
Temporary failure resolving ‘repos.rcn-ee.com’
Err:2 http://deb.debian.org/debian stretch InRelease
Temporary failure resolving ‘deb.debian.org’
Err:3 http://deb.debian.org/debian stretch-updates InRelease
Temporary failure resolving ‘deb.debian.org’
Err:4 http://deb.debian.org/debian-security stretch/updates InRelease
Temporary failure resolving 'deb.debian.org

31

In other words, your BeagleBone is unable to reach your nameserver, so
doesn't know who on earth 'repos.rcn-ee.com' is. The solution is to
troubleshoot your Internet connection.

Check:
1. Physical connections, i.e. if using Ethernet, that both ends of the
Ethernet cable indicate a successfully negotiated Ethernet link. I have
no idea looking at this post what you are using whether it be Ethernet,
USB, WiFi or avian carrier, so perhaps in future you might want to
include this information.

2. IP addresses on the BeagleBone. Run `ip addr show` and see what
addresses are assigned. I'm not sure what the BeagleBone's ethernet
connection is called; but assuming it is named `eth0`, try `dhclient
eth0` if you're using DHCP or `ip addr add ${CIDR} dev eth0` for static
IP (${CIDR} is your IP address and prefix length; e.g. 192.168.255.224/24).

3. Routes, if using DHCP, that should be taken care of, but double check
with `ip route show`. If your default route is not there; try `ip route
add default via ${ROUTER_IP}`.

4. Nameserver. `cat /etc/resolv.conf` and have a look. Maybe try
running `echo nameserver 8.8.8.8 > /etc/resolv.conf` and see if you fare
better.

Regards,