linux+bb from scratch ??

Hello group, hobbyist / linux noobie here, I just got my bb revb5 it
looks like it's working properly as I was able to boot even with mmc
using angstrom demo 20080730 although I didn't actually see the
desktop since I don't have dvi capable monitor, and no usb devices
plugged in. I now want to try learning more by building linux for bb
from scratch. Is there a guide somewhere for bb+linux? something like
this http://cross-lfs.org/view/clfs-embedded/arm/ . I actually
followed it, I started from section IV busybox, iana, zlib, using the
recommended code sourcery toolchain. All seems well, but got kernel
panic, during boot up, and since the guide din't have a
troubleshooting section I'm kinda lost.

btw, I also tried baking the oe+angstrom 3 times, but compilation
never finish, I always get errors with opkg-native thing, and a couple
of undefines error.

I'm doing this bb stuff on Zenwalk 5.2 distro btw, (if this info is
of any use.)

Hello group, hobbyist / linux noobie here, I just got my bb revb5 it
looks like it's working properly as I was able to boot even with mmc
using angstrom demo 20080730 although I didn't actually see the
desktop since I don't have dvi capable monitor, and no usb devices
plugged in. I now want to try learning more by building linux for bb
from scratch. Is there a guide somewhere for bb+linux? something like
this Las Vegas Media . I actually
followed it, I started from section IV busybox, iana, zlib, using the
recommended code sourcery toolchain. All seems well, but got kernel
panic, during boot up, and since the guide din't have a
troubleshooting section I'm kinda lost.

I was a LFS user years ago and I would like a similar experience on
the Beagle :slight_smile:

btw, I also tried baking the oe+angstrom 3 times, but compilation
never finish, I always get errors with opkg-native thing, and a couple
of undefines error.

Me too. I had to manually patch some packages and even then the
generated images didn't boot.

I'm doing this bb stuff on Zenwalk 5.2 distro btw, (if this info is
of any use.)

I started to compile my own system from scratch with glibc 2.7 and it
seemed to compile fine but I would like compatibility with
CodeSourcery's toolchain which uses glibc 2.5, which apparently needs
some patches.

In the meantime I found the experience with this build system much
more pleasant than OE:
http://linux.onarm.com/index.php/From_scratch

I'm all for a Beagle from scratch guide :slight_smile:

Hello group, hobbyist / linux noobie here, I just got my bb revb5 it
looks like it's working properly as I was able to boot even with mmc
using angstrom demo 20080730 although I didn't actually see the
desktop since I don't have dvi capable monitor, and no usb devices
plugged in. I now want to try learning more by building linux for bb
from scratch. Is there a guide somewhere for bb+linux? something like
this Las Vegas Media . I actually
followed it, I started from section IV busybox, iana, zlib, using the
recommended code sourcery toolchain. All seems well, but got kernel
panic, during boot up, and since the guide din't have a
troubleshooting section I'm kinda lost.

btw, I also tried baking the oe+angstrom 3 times, but compilation
never finish, I always get errors with opkg-native thing, and a couple
of undefines error.

Does restarting the buyild get you past the opkg-native failure?

Philip

nope, restarting the build didn't ignore the error I was getting.

I will continue with my trial and error on my scratch build, it looks
like it's going to work, the uImage I built seems ok, I may have made
mistakes on my startup.

Felipe, if you ever make a guide don't forget to post.

thanks.

Hi,

  Building a Beagle version of LFS is not rocket science. I hacked an
existing script I had created (a cheap and dirty demo for a 'soon to
be released' product) and was able to boot a BB in the terminal mode.
The build was a SYSROOT style and uses svn releases of Busybox and
uClibc. There are still problems accessing the OTG port and flipping
over to the DVI-D monitor but "IT'S ALIVE".

  The real issue in homebrew work is validating the end result and
package management. If you are not in the mood to chase every revision
release and have a small selection of packages it is reasonable to
manually control an install (once you have chased down needed
patches). In the end you will be lord and master of a one serf
kingdom and it is lonely at the bottom. If you enjoy pain and
toolchain design then nothing beats rolling your own. If you want to
write code and make the Beagleboard sing and dance then learning/using
OE or CodeSourcery is a better choice.

    regards,
         George

I think doing it exactly as LFS says is maybe a bit too much. There's
already decent toolchains provided by codesourcery, that's the most
difficult part. The rest should not be that complicated.

Also, the linuxonarm stuff allows you to pick the compiler and kernel
that you want.

I am using codesourcery toolchain as recommended on elinux.org wiki,
that's why I skipped to section IV, compilations works out ok, but
probably
my rootfs setup is not correct.

I'm re-starting again to get more familiar with the process,
and I'm borrowing some configuration from oe/angstrom build this time.
btw, I'm only hoping to make something like the geexbox.org and not
a full blown desktop.