Ubuntu on BeagleBoard XM

Hi all,

I am trying to get Ubuntu running on XM, but can't get it to work. I
ran the following commands (on Ubuntu running on x86_32) as per the
instructions for the pre-build demo image at (http://elinux.org/
BeagleBoardUbuntu):

wget http://rcn-ee.net/deb/rootfs/lucid/ubuntu-10.04.1-r1-minimal-armel.tar.7z
7za x ubuntu-10.04.1-r1-minimal-armel.tar.7z
tar xf ubuntu-10.04.1-r1-minimal-armel.tar
cd ubuntu-10.04.1-r1-minimal-armel
./setup_sdcard.sh --mmc /dev/sdi --uboot beagle --swap_file 50

The microSD card has 16 GB capacity, and looks like it is creating all
the required files on it. But when I try to boot the BeagleBoard with
it, the USR0 LED near the microSD keeps flashing and nothing comes up
on the LCD screen (connected via HDMI). Am I missing anything here?
The Angstrom dist. that came with the board is working fine.

Thanks,
Rob.

Hi Rob,

On first boot, it'll take a good 2-3 minutes before the console loads
"oem-config" to help you create the first user.. Which will explain
the USR0 LED flashing..

If that isn't happening... Is there anything on your serial log? Can
you pastebin it anyways so i can take a look at it...

Can i have you rerun the "setup_sdcard.sh" script with:
"--use-default-user" , this will bypass the oem-config, does it load
to a login prompt?

user: ubuntu pass: temppwd

Regards,

Hi Robert,

I tried with --use-default-user option, still no luck. Don't see
anything on the screen even after an hour. I don't have a serial cable
around to check the log... is there anything else I can try?

Thanks,
Rob

An hour is way to much... (anything more then 5mins is usually a
failure of some kind)

With out a serial cable, it's pretty hard to see what's going on in your board..

Do you have any smaller sd cards? 4/8G? I've had some issues with
large/oversize cards..

Regards,

I am having the same issue and I do have a serial port connected.

Here is the output, after this output it just sits there (waited 15
minutes):

Hi Trey,

OK, this will really confuse you Robert.

Since it would not load the kernel, I thought I would try a different
kernel. So I took the kernel from the original angstrom build that
came with the beagleboard-xm and put it on the ubuntu sd (uImage on
boot). The kernel then booted and got me to the prompt.

So is something wrong with the uImage that is supplied?

This would be normal if he used the official pre-installed image for
Maverick (as console is disabled by default).

But it seems he's using a different x-loader/u-boot combination than
the official release.

Cheers,

I am using the http://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-minimal-armel.tar.7z
from the http://elinux.org/BeagleBoardUbuntu site.

I am using the following commands:

wget http://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-minimal-armel.tar.7z
md5sum ubuntu-10.10-minimal-armel.tar.7z
7za x ubuntu-10.10-minimal-armel.tar.7z
tar xf ubuntu-10.10-minimal-armel.tar
cd ubuntu-10.10-minimal-armel

sudo ./setup_sdcard.sh --mmc /dev/sdb --uboot beagle

Here is the pastebin of the boot.scr.

http://pastebin.com/XUYgNVRN

I am using no command line arguments. Should I be?

Trey

Hey Trey,

There shouldn't be...

After your first message, i double checked it and posted this..
http://pastebin.com/fXwm4cJx

Which xM revision do you have?

Regards,

I am using the http://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-minimal-armel.tar.7z
from the BeagleBoardUbuntu - eLinux.org site.

I am using the following commands:

wget http://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-minimal-armel.tar.7z
md5sum ubuntu-10.10-minimal-armel.tar.7z
7za x ubuntu-10.10-minimal-armel.tar.7z
tar xf ubuntu-10.10-minimal-armel.tar
cd ubuntu-10.10-minimal-armel

sudo ./setup_sdcard.sh --mmc /dev/sdb --uboot beagle

I don't think it causes any harm, but you don't actually need 'sudo'
as the parts in the script that need it will call sudo itself.. (sudo
sudo xyz effect)

Here is the pastebin of the boot.scr.

http://pastebin.com/XUYgNVRN

That looks fine..

Regards,

You can also try the pre-installed image released for Maverick at
https://wiki.ubuntu.com/ARM/OMAPMaverickInstall , it should work fine.

Cheers,

I noticed that your setenv is this: Kernel command line:
console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait ro
vram=12MB omapfb.mode=dvi:1280x720MR-16@60 fixrtc buddy=none
mpurate=800

I am not sure my monitor would show that resolution, how do I go about
changing it?

I have a Rev A2 board.

Thanks for your help, what should I try now?

I noticed that your setenv is this: Kernel command line:
console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait ro
vram=12MB omapfb.mode=dvi:1280x720MR-16@60 fixrtc buddy=none
mpurate=800

I am not sure my monitor would show that resolution, how do I go about
changing it?

That one is usually the most compatible, but to change it is pretty easy..

First on the 'boot' partition, there is a boot.scr and boot.cmd

Open the boot.cmd file and change the 2/3 line "setenv dvi
1280x720MR-16@60" to 800x600MR-16@60 or something else.. save and
close..

Then:

mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Some Text" -d
./boot.cmd ./boot.scr

I have a Rev A2 board.

Okay, same as mine..

Weird, it should as setup dump over the serial console..

Thanks for your help, what should I try now?

Give this a test... ( i modified the 'setup_sdcard.sh' script to show
more information..)

first remove the existing setup_sdcard.sh file

download this new one:

wget http://rcn-ee.homeip.net:81/dl/updates/omap-image-builder/tools/setup_sdcard.sh

change permissions:

chmod a+x setup_sdcard.sh

then run it on your sd card again...

./setup_sdcard.sh --mmc /dev/sdb --uboot beagle

Regards,

Could not get to your new setup file. I think it is because it is on
port 81, and our company's it dept tries to get in the way any way it
can.

But why would it work with the old uImage file fromthe Angstrom build.

Changing monitor resolution did not help.

Ricardo,

This did not work either, same problem.

Can you try the following?

Edit boot.scr from the first partition and add proper console arguments:
1. Mount your SD card after flashing the image on it;
2. # cd /media/6B57-ED78/
3. # dd if=boot.scr of=boot.script bs=1 skip=72
4. Edit boot.script and add "console=ttyS2,115200n8" at the setenv line, like:
   setenv bootargs vram=12M omapfb.mode=dvi:1280x720MR-16@60
root=/dev/mmcblk0p2 fixrtc console=ttyS2,115200n8 earlyprintk=ttyS2
loglevel=8
5. # mkimage -A arm -T script -C none -n "Ubuntu boot script" -d
boot.script boot.scr
6. Unmount the sd card and boot it on your board

See if changing the bootargs get you at least something at uart.

Cheers,

I will try that Monday.

Do you know why if I replace the uImage file that you provided with
the one that came with Angstom Linux on my Beagle board that it will
boot?