Gentoo on the Beaglebone
1.
Overview
Installing Gentoo in the Beaglebone is pretty simple if you're already a Gentoo user.
You need to use an SD card, at least of 2 GB of size. If you
are familar with the Gentoo Linux installation process, there is not much
different here.
2.
Requirements
To be able to install Gentoo, you'll need the following:
- An x86/amd64 based PC with Gentoo and an SD card reader on it
- A Beaglebone
- One SD card (2 GB is enough)
- A network connection
3.
Preparing to install your Beaglebone
Overview
Before we start the installation process, we need to get/build a kernel, bootloader and X-Loader
for the Beaglebone.
The Beaglebone doesn't have a NAND/flash device, so the bootloader (U-Boot) needs to be located
on the SD card, along with X-Loader and the kernel.
Emerging needed tools
For building the stuff needed to boot our Beaglebone, we need the following tools emerged
on the host system where we're going to build them.
-
dev-vcs/git - to download U-Boot, X-Loader and the kernel
-
sys-devel/crossdev - to create a crosscompiler
-
dev-embedded/u-boot-tools - to create a kernel image U-Boot can understand
-
sys-fs/dosfstools - to create FAT32 filesystems
Code Listing 3.1: Emerge needed tools |
# emerge dev-vcs/git sys-devel/crossdev dev-embedded/u-boot-tools sys-fs/dosfstools
|
Build a crosscompiler
Code Listing 3.2: Building a crosscompiler |
# crossdev -S armv7a-hardfloat-linux-gnueabi
|
Obtaining/Building U-Boot
Code Listing 3.3: Obtaining U-Boot |
# wget ftp://ftp.denx.de/pub/u-boot/u-boot-2012.10-rc3.tar.bz2
# tar xjpf u-boot-2012.10-rc3.tar.bz2 && cd u-boot-*
|
Code Listing 3.4: Compiling U-Boot |
# make ARCH=arm CROSS_COMPILE=armv7a-hardfloat-linux-gnueabi- am335x_evm_config
# make ARCH=arm CROSS_COMPILE=armv7a-hardfloat-linux-gnueabi-
|
Obtaining/Building a kernel
For booting the Beaglebone we need a kernel. The vanilla kernel.org doesn't support the
Beaglebone as of October 2012, for this reason we'll use a kernel provided by TI.
Code Listing 3.5: Obtaining the kernel |
# git clone git://arago-project.org/git/projects/linux-am33x.git
# cd linux-am33x
# git checkout -f v3.2-staging
|
Code Listing 3.6: Obtaining needed firmware |
# wget "http://arago-project.org/git/projects/?p=am33x-cm3.git;a=blob_plain;f=bin/am335x-pm-firmware.bin;hb=HEAD" -O firmware/am335x-pm-firmware.bin
|
Code Listing 3.7: Configuring the kernel |
# make ARCH=arm CROSS_COMPILE=armv7a-hardfloat-linux-gnueabi- am335x_evm_defconfig
# make ARCH=arm CROSS_COMPILE=armv7a-hardfloat-linux-gnueabi- menuconfig
File systems --->
<*>The Extended 4 (ext4) filesystem
|
The kernel includes CPU frequency scaling support, but by default is configured to use the userspace
governor, that means that unless you have any CPU frequency scaling manager in the rootfs, the cpu will be
stuck at 600MHz.
You can change the governor anytime you want, but if you are like me and prefer the ondemand governor
set by default, which makes a CPU frequency scaling manager redundant, or if you prefer the performance
governor which is like disabling CPU frequency scaling, you can choose the default governor in the following kernel
config menu.
Code Listing 3.8: Configuring the default governor in menuconfig |
CPU Power Management --->
CPU Frequency Scaling --->
Default CPUFreq governor (userspace) --->
|
Code Listing 3.9: Cross-compiling the kernel |
# make -j9 ARCH=arm CROSS_COMPILE=armv7a-hardfloat-linux-gnueabi- uImage
|
Once it gets built we'll have a kernel image on arch/arm/boot/uImage.
4.
SD card setup
Overview
OMAP-based systems need a special setup of the SD card to boot from it. For more information please
check this link.
Formatting the SD card
The following script will format your SD card accordingly, creating two partitions.
The first partition size is based on the size of the SD card itself, and it's formatted in vfat.
The second partition is the free space left on the card after the first partition, and it's formatted in ext4.
Code Listing 4.1: Formatting the SD card |
# wget http://dev.gentoo.org/~armin76/arm/beaglebone/mkcard.sh
# bash mkcard.sh /dev/mmcblk0
|
Configuring U-Boot
Important: This part is important |
The default configuration of U-Boot differs a bit from our setup, we fix that by creating a file
called uEnv.txt with the following contents:
Code Listing 4.2: Contents of uEnv.txt |
bootfile=uImage
loaduimage=run loaduimagefat; run mmcboot
|
Copying U-Boot, MLO and the kernel to the SD card
Now we'll mount the first partition on the card and copy the needed files
(the ones that we built before) to boot our Beaglebone.
Code Listing 4.3: Copying U-Boot, MLO and the kernel to the SD card |
# mkdir /mnt/p1 ; mount /dev/mmcblk0p1 /mnt/p1
# cp uEnv.txt /mnt/p1
# cp u-boot-2012.10-rc3/{MLO,u-boot.img} /mnt/p1
# cp linux-am33x/arch/arm/boot/uImage /mnt/p1
|
5.
Installing Gentoo
Overview
The installation on this device is a bit different, and therefore easy, as we can't install Gentoo on it
by booting an installation environment. For installing Gentoo (and any other distro, really)
you need to put the SD card on your PC and prepare there the
minimal installation.
What we'll have to do to setup our installation is:
- Extract stage3 to the 2nd partition of the SD card
- Extract portage snapshot (required to emerge things and ntp(see below))
- Setup fstab
- Setup root password
- Configure hostname and networking (optional, but recommended)
- Enable SSH access (optional, but recommended)
- Enable serial console access (optional, but recommended)
Stages information
Here's some information about the stages.
- Architecture: arm
- Subarchitecture: armv7a_hardf
- CHOST: armv7a-hardfloat-linux-gnueabi
- Profile: default/linux/arm/10.0
We'll be using the new EABI, also called gnueabi. That is armel on Debian.
Therefore, we need an armv7a-hardfloat-linux-gnueabi stage3 for best performance, available under the
releases/arm/autobuilds directory in your favorite mirror
Optionally you can also grab a portage snapshot
Extracting a stage3
Mount the second partition of the SD card and extract the stage3 you downloaded.
Code Listing 5.1: Mounting the partition and extracting the stage3 |
# mkdir /mnt/p2
# mount /dev/mmcblk0p2 /mnt/p2
# tar xjpf stage3-armv7a_hardfp-20121006.tar.bz2 -C /mnt/p2
|
Extracting a portage snapshot (optional)
Code Listing 5.2: Extracting the snapshot |
# tar xjpf portage-latest.tar.bz2 -C /mnt/p2/usr
|
Setup fstab
Edit the /mnt/p2/etc/fstab file to look like this:
Code Listing 5.3: /mnt/p2/etc/fstab |
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/mmcblk0p1 /boot vfat noauto,noatime 1 2
/dev/mmcblk0p2 / ext4 noatime 0 1
/dev/SWAP none swap sw 0 0
/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0
|
Setting the default root password
This is the most important part of the installation. As without the root
password we won't be able to login!
For setting the password, we need to be able to run passwd. However that's
not possible since our PC can't run ARM binaries. Therefore we need to modify
the file that contains the passwords (/etc/shadow) inside the chroot,
so we can set a default root password.
Code Listing 5.4: Change the default root password |
# openssl passwd -1
# nano -w /mnt/p2/etc/shadow
root:s3cr3t:14698:0:::::
root:$6$I9Q9AyTL$Z76H7wD8mT9JAyrp/vaYyFwyA5wRVN0tze8pvM.MqScC7BBm2PU7pLL0h5nSxueqUpYAlZTox4Ag2Dp5vchjJ0:14698:0:::::
|
Setup hostname and networking
Please read
the network configuration chapter of the ARM handbook to configure the network.
Enabling SSH access (optional)
We can add sshd to the startup of our system so we can access our Beaglebone
using ssh.
Code Listing 5.5: Adding sshd to the startup |
# ln -sf /etc/init.d/sshd /mnt/p2/etc/runlevels/default
|
Enabling serial console access (optional)
By default the ttyS0 port is configured at 9600 bps. However, almost all of the
ARM devices run the serial port at 115200 bps. Also, in the case of the Beaglebone,
the port is ttyO0(that is a t-t-y-capitalO-zero) instead of the normal ttyS0.
So this should be added to the /etc/inittab file:
Code Listing 5.6: Configuring serial console |
# nano -w /mnt/p2/etc/inittab
s0:12345:respawn:/sbin/agetty 115200 ttyO0 vt100
|
Finishing the installation
Let's unmount the SD card
Code Listing 5.7: Unmounting the SD card |
# umount /mnt/p1 /mnt/p2
|
This is pretty much all of the installation.
I'd highly recommend that you read all the recommendations of the handbook.
6.
Booting up our new system
Accessing the console (optional)
If you want to see the beaglebone boot, connect an USB cable to the mini USB port
(you should have it if you aren't powering it using an external PSU...) and load the
ftdi_sio kernel module with the following command:
Code Listing 6.1: Loading the ftdi_sio module |
# modprobe ftdi_sio vendor=0x0403 product=0xa6d0
|
New devices called ttyUSB0 and ttyUSB1 should show up on /dev. You should use ttyUSB1
with a terminal emulator like picocom or minicom configuring it with
115200bps 8N1
Once you have the card ready, put it into the Beaglebone... and you should be able to boot it.
7.
After booting
Keeping the clock up to date
One of the problems of the Beaglebone is that it doesn't save the date because it doesn't have
a battery for the clock.
After logging into our new Gentoo on Beaglebone installation, I'd recommend setting a date and
emerging net-misc/ntp to keep the clock up-to-date. Also it's recommended to put both
ntp-client and ntpd to boot on startup, so you get a proper date setup.
However, keep in mind that NTP requires a network connection and a NTP server being reachable,
either on the local network or on the Internet.
Code Listing 7.1: Emerging net-misc/ntp |
# emerge net-misc/ntp
# rc-update add ntpd default
# rc-update add ntp-client default
# /etc/init.d/ntp-client start
# /etc/init.d/ntpd start
|
8.
References
You may find more documentation about the device itself and Linux-related at
the following links:
9.
Thanks
-
http://beagleboard.org/bone for providing me a Beaglebone to document and
support Gentoo on it
- Siarhei Siamashka (ssvb) for giving helpful hints
The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-2.5 license. The Gentoo Name and Logo Usage Guidelines apply.
|