I'm trying to install Ubuntu on a BeagleBoard-xM following the
NetInstall method instructions here - http://elinux.org/BeagleBoardUbuntu.
Everything worked fine (as long as I selected usb1 as the ethernet
port when asking about networking hardware) but it failed repeatedly
during the base system install (at around 76%?) with "Unable to
install busybox-initramfs".
One slightly odd thing - it came up with United Kingdom as the default
mirror. Could this be the problem?
Thanks!
Richard.
Hi Richard,
Don't use the "NetInstall" method for the XM board. Ubuntu dev's made
some assumptions with lucid (released in may of 2010) so it'll never
be compatible with the XM...
The Demo Image should work fine, however note I've only tested them on
an early XM prototype with bad memory.. Just waiting for ups to
deliver my new XM..
Yes.. the only mirror is in the Uk...
Regards,
Robert,
Thanks for the quick response. I'll try the demo image as you suggest.
Just wanted to be sure I wasn't doing something silly!
Regards,
Richard.
The Demo Image install worked perfectly - thanks again.
Hope your BB-xM turns up soon!
Richard.
You could also try the pre-installed image for Beagle-xM (this will be the
default method that Ubuntu is using for Beagle and Pandaboard for Maverick).
Tomorrow we'll get the Maverick beta release, and the omap image should work
fine at Beagleboard xM (image was tested, but not with A2 board).
You'll be able to get the image at
http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/maverick/ . See
http://testcases.qa.ubuntu.com/Install/ARM/PreinstalledImage if you need
instructions on how to set up your sd card (quite simple, just a dd, put the
card and boot).
Let us know if you face any bugs at your testing.
Cheers,
I'm trying to install Ubuntu on a BeagleBoard-xM following the
NetInstall method instructions here - BeagleBoardUbuntu - eLinux.org.
Everything worked fine (as long as I selected usb1 as the ethernet
port when asking about networking hardware) but it failed repeatedly
during the base system install (at around 76%?) with "Unable to
install busybox-initramfs".You could also try the pre-installed image for Beagle-xM (this will be the
default method that Ubuntu is using for Beagle and Pandaboard for Maverick).Tomorrow we'll get the Maverick beta release, and the omap image should work
fine at Beagleboard xM (image was tested, but not with A2 board).
Did you pull in the x-load patch to support both the Numonyx memory
and the Micron memory? The Rev A2 board will ship with both, so you
need to be sure that you've got that patch applied. Sorry for that,
but memory delivery times became the bottleneck to shipping the xMs
and we therefore got stuck with taking memories from both suppliers.
I was also trying my first net install on Beagleboard B4 and had the
same issue. So this particular problem doesn't appear to be related
to xM. But from what I've read the net install while not work for
other reasons on xM right now.
Does anyone know how to get around the busybox-initramfs install error
in the netinstall?
Yeah i think the Canonical guys are safe, they were using sakoman's tree...
https://code.launchpad.net/ubuntu/+source/u-boot-omap3
Otherwise the ones listed on http://elinux.org/BeagleBoardUbuntu are
directly from angstrom..
Regards,
Well the xM definitely won't work, the lucid install assumes NAND
flash. (Maverick doesn't care and there's even a builtin overide i
can use to stop it from trying)..
But well darn... Anything weird in "ctrl alt f4"? other then all the
hid/input noise from 2.6.35?
I had just re-qualified that "NetInstall" on "2010-08-24" on my Bx
with the newer 2.6.35 kernel.. I'll retest it quickly...
Regards,
I'm trying to install Ubuntu on a BeagleBoard-xM following the
NetInstall method instructions here - BeagleBoardUbuntu - eLinux.org.
Everything worked fine (as long as I selected usb1 as the ethernet
port when asking about networking hardware) but it failed repeatedly
during the base system install (at around 76%?) with "Unable to
install busybox-initramfs".You could also try the pre-installed image for Beagle-xM (this will be the
default method that Ubuntu is using for Beagle and Pandaboard for Maverick).Tomorrow we'll get the Maverick beta release, and the omap image should work
fine at Beagleboard xM (image was tested, but not with A2 board).Did you pull in the x-load patch to support both the Numonyx memory
and the Micron memory? The Rev A2 board will ship with both, so you
need to be sure that you've got that patch applied. Sorry for that,
but memory delivery times became the bottleneck to shipping the xMs
and we therefore got stuck with taking memories from both suppliers.Yeah i think the Canonical guys are safe, they were using sakoman's tree...
https://code.launchpad.net/ubuntu/+source/u-boot-omap3
Otherwise the ones listed on BeagleBoardUbuntu - eLinux.org are
directly from angstrom..
OK. Just to be perfectly clear, the patch I'm talking about is
http://gitorious.org/beagleboard-validation/x-load/commit/ead751e4a361ce19552ac94bbeba232f12849244
Crap, yeah that was u-boot, looking at x-load they don't have support
for the future Micron Xm's:
cc'ing Ogra and Loïc
Regards,
Weird, it works fine for me (B5 Board).. 83% just passed
"busybox-initramfs" was watching ctrl-alt-f4... besides the evbug.c
errors from keyboard input and tar time stamps way off. (i should have
it run ntpdate early to get rid of that issue)..
Regards,
Ouch, didn't know we needed an extra patch for x-load 
Too bad the release target for tomorrow, and we'll probably apply the patch just
after Beta.
Thanks for point it out, will update our package so we can at least have working
xM images for our daily builds, after beta.
Cheers,
I've tried three times in the last two days to do the netinstall on a
Rev B4, with the same issue. I also can confirm that the suggested
mirror was for the UK ( I'm in the states), when I tried to manually
specify a mirror I complained about not finding a Release. I may have
not had the path specified correctly. What mirror were you using for
the netinstall?
I was able to parse the error message from console 4; this is not
verbatim but what I used as a google search this morning.
command not executed: 'sh -c debconf-apt-progress install busybox-
initramfs ....
I will try again and take better notes if the error occurs again.
I've tried three times in the last two days to do the netinstall on a
Rev B4, with the same issue. I also can confirm that the suggested
mirror was for the UK ( I'm in the states), when I tried to manually
specify a mirror I complained about not finding a Release. I may have
not had the path specified correctly. What mirror were you using for
the netinstall?
I'm using the same UK mirror and based in the states.. (Actually the
UK mirror is the only ports.ubuntu server..)
The only tweak i do when running mine, is to specify a local
apt-cacher-ng mirror with: "http://192.168.0.10:3142/" during the
install when prompted... (mostly to speed up the slow network
download..)
I was able to parse the error message from console 4; this is not
verbatim but what I used as a google search this morning.command not executed: 'sh -c debconf-apt-progress install busybox-
initramfs ....I will try again and take better notes if the error occurs again.
Yeah, it's pretty hard with the input errors spaming the log too...
Regards,
Bug https://bugs.launchpad.net/ubuntu/+source/x-loader/+bug/628243
I just added the pointed patch, so it should now work with both xM versions.
As I still don't have a board with Numonyx, can anyone help me testing the
binary with it?
All you need to do is to download
http://people.canonical.com/~rsalveti/maverick/boot/xM/MLO , put at your SD card
an boot it with your current working image (no need for Ubuntu). When testing,
please post the result at the bug or at this thread so we can push it to our
archives.
Thanks a lot!
Cheers,
Looks good, tested on my Numonyx powered xM A2 will add to the bug notes..
Regards,
After the busybox-initramfs error I checked the logs for errors and
found
base-installer: cp: write error: No space left on device
df indicates that the tmp space is full
/dev/mmcblk0p1 72102 72102 0 100% /tmp/mmc
I used the mk_mmc.sh script to create the card. I couldn't find and
version information in the script, but the first few lines are:
#!/bin/bash -e
#Notes: need to check for: parted, fdisk, wget, mkfs.*, mkimage,
md5sum
MIRROR="http://rcn-ee.net/deb/"
DIST=squeeze
KERNEL_REL=2.6.35.3
KERNEL_PATCH=1
Did you use a different script to create your card?
Robert
After the busybox-initramfs error I checked the logs for errors and
foundbase\-installer: cp: write error: No space left on devicedf indicates that the tmp space is full
/dev/mmcblk0p1 72102 72102 0 100% /tmp/mmc
weird, can you do a "ls -lh" on this card.. Btw is this with the
'--firmware' option? I haven't run that in awhile..
On a fresh build (before running the ubuntu install), the cards look like this:
./mk_mmc.sh --mmc /dev/mmcblk0 --distro lucid
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p1 72102 33354 38748 47% /media/boot
./mk_mmc.sh --mmc /dev/mmcblk0 --distro lucid --firmware
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p1 72102 50692 21410 71% /media/boot
voodoo@voodoo-e6400:~/bzr_repo/debian-di$ ls -lh /media/boot/
total 50M
-rwxr-xr-x 1 voodoo voodoo 451 2010-09-01 16:08 boot.cmd
-rwxr-xr-x 1 voodoo voodoo 488 2010-09-01 16:08 boot.scr
-rwxr-xr-x 1 voodoo voodoo 24K 2010-09-01 16:08 MLO
-rwxr-xr-x 1 voodoo voodoo 523 2010-09-01 16:08 normal.scr
drwx------ 2 voodoo voodoo 2.0K 2010-09-01 16:08 tools
-rwxr-xr-x 1 voodoo voodoo 205K 2010-09-01 16:08 u-boot.bin
-rwxr-xr-x 1 voodoo voodoo 4.0M 2010-09-01 16:08 uImage
-rwxr-xr-x 1 voodoo voodoo 42M 2010-09-01 16:08 uInitrd
-rwxr-xr-x 1 voodoo voodoo 4.1M 2010-09-01 16:08 uInitrd.final
-rwxr-xr-x 1 voodoo voodoo 911 2010-09-01 16:08 user.cmd
-rwxr-xr-x 1 voodoo voodoo 983 2010-09-01 16:08 user.scr
I used the mk_mmc.sh script to create the card. I couldn't find and
version information in the script, but the first few lines are:KERNEL_REL=2.6.35.3
KERNEL_PATCH=1
^
Yeap this is about the only 'version info' other then bzr revision..
I always use bzr trunk from the same repo..
Did you use a different script to create your card?
Regards,
Okay i see the problem.. First the default boot mmc partition is
64Mb.. When selecting the '--firmware' option, the uInird with the
debian installer is just way to big now (40Mb's). During the install
and before switching to the final uIntird that'll be used on a normal
boot, i back up the install uInitrd to "uInitrd.net" with a copy so
(40 + 40 >= 64Mb ) before blowing the orignal away.. I'll need to
spend some time to cut out the crude which isn't needed.. But I'll
bump the partition size and use a 'mv' instead..
Regards,