I just tried the latest Lucid image (http://elinux.org/
BeagleBoardUbuntu#Demo_Image)
I followed the directions on that page exactly (cut & paste)
It hangs, presumably because the wrong X-Loader was used. This is
all I get:
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2010.03-rc1 (Apr 14 2010 - 12:05:52)
OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
Also, I worked past this (removed MLO+U-Boot from SD). It now
boots, but only to a login prompt.
How do I carry on with a more complete install from this point?
Hi Gary,
I just tried the latest Lucid image (http://elinux.org/
BeagleBoardUbuntu#Demo_Image)
I followed the directions on that page exactly (cut & paste)
It hangs, presumably because the wrong X-Loader was used. This is
all I get:
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2010.03-rc1 (Apr 14 2010 - 12:05:52)
OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
That's correct, by default the script copies X-loader 1.4.4ss and
U-Boot 2010.03 to the SD card for XM support.. For Older beagles, you
can either remove the u-boot and MLO from the first partition or
upgrade it with these U-boot commands over the serial interface..
http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/omap-flasher/annotate/head%3A/reset.cmd
Also, I worked past this (removed MLO+U-Boot from SD). It now
boots, but only to a login prompt.
That's good to hear, with the demo image, you only get a minimal console....
How do I carry on with a more complete install from this point?
apt-get and friends... 
Once Bug 532733 is fixed:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/532733
I'll have an X11 image that will ask your for a new user name and
password on first boot...
Regards,
Hi Gary,
I just tried the latest Lucid image (http://elinux.org/
BeagleBoardUbuntu#Demo_Image)
I followed the directions on that page exactly (cut& paste)
It hangs, presumably because the wrong X-Loader was used. This is
all I get:
Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2010.03-rc1 (Apr 14 2010 - 12:05:52)
OMAP3530-GP ES3.0, CPU-OPP2, L3-165MHz, Max clock-600Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
That's correct, by default the script copies X-loader 1.4.4ss and
U-Boot 2010.03 to the SD card for XM support.. For Older beagles, you
can either remove the u-boot and MLO from the first partition or
upgrade it with these U-boot commands over the serial interface..
http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/omap-flasher/annotate/head%3A/reset.cmd
Maybe you should add an option to the setup script that skips these
for older boards?
Also, I worked past this (removed MLO+U-Boot from SD). It now
boots, but only to a login prompt.
That's good to hear, with the demo image, you only get a minimal console....
How do I carry on with a more complete install from this point?
apt-get and friends...
I'm not a Debian/Ubuntu type, so this is all Greek to me 
I tried looking for "Ubuntu NetInstall" help, but didn't get much.
Is there a walk through somewhere for a novice? (not that I'm novice,
I just haven't used Debian/Ubuntu from the ground up)...
Once Bug 532733 is fixed:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/532733
I'll have an X11 image that will ask your for a new user name and
password on first boot...
Thanks
n.b. sorry for the multiple posts, but the mailing list was a
bit cranky yesterday!
Gary,
If you cannot wait for Robert’s X11 image coming out,
do the following steps;
- Hookup usb-to-ethernet device
- I don’t you if you have this device at hand. Wireless(WIFI) are a bit troublesome yet in my experience. So, I recommend you to use a wire type one. When you attach the device to your beagleboard through a powered usb hub.
- Check if your board recognize the device correctly and load the proper device driver with ‘dmesg’ command.
- Get the ip address for the device
- If your beagleboard is connected to a network with dhcp server available, type ‘sudo dhclient eth0’ at the prompt and you will be asked for the sudo password. Type your login password then.
- If you don’t have dhcp server in your network, you have to assign ip address manually with ‘sudo ifconfig’ command.
- Correct system clock
- Once your board get the network access, type ‘sudo ntpdate’. First time when your beagleboard boots, the system time is set to year 1970. The command will install a tool to synchronize the system time with current time through network. You’d better consider installing a backup battery if your board revision is C3 or C4. Instruciton is described in the board manual pdf file.
- Then type ‘ntpdate pool.ntp.org’. You will see the system date is set properly. If you are not sure, type ‘date’ and confirm the system time.
- Update package information
- Type ‘sudo atp-get update’ to update your repository and package information.
- Install X packages
- It seems that Robert prefers xfce for beagleboard. It’s O.K. but I found that xfce still is a bit heavy. So, I prefer lxde. It’s lighter.
: If you want xfce, type ‘sudo apt-get install xfce gdm’
: if you want lxde, type ‘sudo apt-get install lxde lxdm’
Eitherway, you will be guided that a bunch of packages less than 300MB size shall be installed and it will ask you if you really want to do this. Type ‘y’ to say yes. It does take time. Have a coffee break.
- After the installation is completed, don’t forget to type ‘sync’ at the command prompt to be sure all the data are written to the SD card correctly.
- Reboot
- Once everything is O.K., reboot your system and you would see the X Window screen.
Since you said you are not familiar with debian/ubuntu system, I focused on the usage of sudo command assuming that you are familiar with handling general linux stuffs.
If you have furhter problem, post it.
ILKYOUNG.
2010/4/29 Gary Thomas <gary@mlbassoc.com>
Is it possible to use ether-over-usb with the demo image? There
doesn't seem to be a g_ether module.
it's already builtin... a usb0 will show up when you "sudo ifconfig -a"
Regards,
It wasn't showing up with ifconfig initially, but I've added it to
/etc/network/interfaces using the same configuration as my Freerunner:
ubuntu@beagleboard:~$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto usb0
iface usb0 inet static
address 192.168.0.202
netmask 255.255.255.0
gateway 192.168.0.200
ubuntu@beagleboard:~$ sudo ifconfig -a
[snip lo]
usb0 Link encap:Ethernet HWaddr f6:c1:8c:79:f0:90
inet addr:192.168.0.202 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::f4c1:8cff:fe79:f090/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:88 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11938 (11.9 KB) TX bytes:1656 (1.6 KB)
ubuntu@beagleboard:~$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
0.0.0.0 192.168.0.200 0.0.0.0 UG 0 0 0 usb0
On the host side I have:
andrew@sauron:~$ sudo ifconfig -a
[snip]
usb0 Link encap:Ethernet HWaddr d2:e0:6d:38:14:90
inet addr:192.168.0.200 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::d0e0:6dff:fe38:1490/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1494 Metric:1
RX packets:0 errors:42 dropped:0 overruns:0 frame:0
TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:18574 (18.5 KB)
andrew@sauron:~$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
So at this point I'd expect to be able to ping between the two
systems, but I'm getting "Destination Unreachable" at both ends.
Can anybody see what I'm doing wrong?