Difference between pages "Pandaboard" and "Install/BootLoader"

(Difference between pages)
m (Removed the Pandaboard category, as there was only one member. This page is now only in ARM.)
 
(Installing GRUB)
 
Line 1: Line 1:
The '''PandaBoard''' is a low-power, low-cost single-board computer development platform based on the Texas Instruments OMAP4430 system on a chip (SoC). The board has been available to the public since 27 October 2010. It is a community supported development platform.
+
<noinclude>
 +
{{InstallPart|boot loader configuration}}
 +
</noinclude>
 +
=== Installing a Bootloader ===
  
The '''PandaBoard ES''' is a newer version based on the OMAP4460 SoC, with the CPU and GPU running at higher clock rates. The board has been available to the public since 16 November 2011. Like its predecessor, it is a community supported development platform.
+
These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school).
  
== Features ==
+
==== Old School (BIOS) ====
The OMAP4430 SoC on the PandaBoard features a dual-core 1&nbsp;GHz ARM Cortex-A9 MPCore CPU, a 304&nbsp;MHz PowerVR SGX540 graphics processing unit (GPU), a Texas Instruments TMS320C6400 digital signal processor (DSP), and 1&nbsp;GiB of DDR2 SDRAM.
+
  
The PandaBoard ES uses a newer SoC, with a dual-core 1.2&nbsp;GHz CPU and 384&nbsp;MHz GPU. Primary persistent storage is via an Secure Digital (SD) Card slot allowing SDHC cards up to 32&nbsp;GB to be used. The board includes wired 10/100 Ethernet as well as wireless Ethernet and bluetooth connectivity. The board can output video signals via Digital Visual Interface (DVI) and HDMI interfaces. It also has 3.5&nbsp;mm audio connectors. It has two Universal Serial Bus (USB) host ports and one USB On-The-Go port, supporting USB 2.0.
+
If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.
 +
 
 +
To use this recommended boot method, first emerge <code>boot-update</code>. This will also cause <code>grub-2</code> to be merged, since it is a dependency of <code>boot-update</code>.
 +
 
 +
<console>
 +
(chroot) # ##i##emerge boot-update
 +
</console>
 +
 
 +
Then, edit <code>/etc/boot.conf</code> and specify "<code>Funtoo Linux genkernel</code>" as the <code>default</code> setting at the top of the file, replacing <code>"Funtoo Linux"</code>.  
 +
 
 +
<code>/etc/boot.conf</code> should now look like this:
  
=== CPUinfo ===
 
* Pandaboard
 
 
<pre>
 
<pre>
Processor      : ARMv7 Processor rev 2 (v7l)
+
boot {
processor      : 0
+
generate grub
BogoMIPS        : 599.22
+
default "Funtoo Linux genkernel"
 +
timeout 3
 +
}
  
processor      : 1
+
"Funtoo Linux" {
BogoMIPS        : 582.68
+
kernel bzImage[-v]
 +
}
  
Features        : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls
+
"Funtoo Linux genkernel" {
CPU implementer : 0x41
+
kernel kernel[-v]
CPU architecture: 7
+
initrd initramfs[-v]
CPU variant    : 0x1
+
params += real_root=auto
CPU part        : 0xc09
+
}
CPU revision    : 2
+
  
Hardware        : OMAP4 Panda board
+
"Funtoo Linux better-initramfs" {
Revision        : 0020
+
kernel vmlinuz[-v]
Serial          : 0000000000000000
+
initrd /initramfs.cpio.gz
 +
}
 
</pre>
 
</pre>
  
== Funtoo Linux Instalation ==
+
Please read <code>man boot.conf</code> for further details.
First of all you have to prepare/format your SD card (ALL DATA WILL BE LOST!).
+
 
 +
===== Running grub-install and boot-update =====
 +
 
 +
Finally, we will need to actually install the GRUB boot loader to your disk, and also run <code>boot-update</code> which will generate your boot loader configuration file:
 +
 
 +
<console>
 +
(chroot) # ##i##grub-install --no-floppy /dev/sda
 +
(chroot) # ##i##boot-update
 +
</console>
 +
 
 +
Now you need to update your boot loader configuration file:
 +
<console>
 +
(chroot) # ##i##boot-update
 +
</console>
 +
You only need to run <code>grub-install</code> when you first install Funtoo Linux, but you need to re-run <code>boot-update</code> every time you modify your <code>/etc/boot.conf</code> file, so your changes are applied on next boot.
 +
 
 +
==== New School (UEFI) ====
 +
 
 +
If you're using UEFI to boot, setting up the boot loader is a bit more complicated for now, but this process will be improving soon. Perform the following steps.
 +
 
 +
===== Emerging GRUB =====
 +
 
 +
You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this,
 +
add the following line to <code>/etc/make.conf</code>:
  
 
<pre>
 
<pre>
sdcardsetup.sh
 
# sdcardsetup.sh script
 
#!/bin/sh
 
  
if [ ! "$1" = "/dev/sda" ] ; then
+
For 64-bit systems:
        DRIVE=$1
+
 
        if [ -b "$DRIVE" ] ; then
+
GRUB_PLATFORMS="efi-64"
                dd if=/dev/zero of=$DRIVE bs=1024 count=1024
+
 
                SIZE=`fdisk -l $DRIVE | grep Disk | awk '{print $5}'`
+
For 32-bit systems, i.e. Intel Atom devices and systems with less than 4GB of RAM:
                echo DISK SIZE - $SIZE bytes
+
 
                CYLINDERS=`echo $SIZE/255/63/512 | bc`
+
GRUB_PLATFORMS="efi-32"
                echo CYLINDERS - $CYLINDERS
+
 
                {
+
                echo ,9,0x0C,*
+
                echo ,,,-
+
                } | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE
+
                mkfs.vfat -F 32 -n "boot" ${DRIVE}1
+
                mke2fs -j -L "rootfs" ${DRIVE}2
+
        fi
+
fi
+
 
</pre>
 
</pre>
  
Follow the general steps from [[Funtoo on ARM#Installing Funtoo]].
+
Then, <code>emerge boot-update</code>. You will notice <code>grub</code> and <code>efibootmgr</code> getting pulled in as dependencies. This is expected and good:
  
These steps include:
+
<console>
* Extract stage3 to the 2nd partition of the SD card
+
(chroot) # ##i##emerge boot-update
* Extract portage snapshot (required to emerge things and ntp(see below))
+
</console>
* 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)
+
* Correct RTC "bug" with swclock
+
  
 +
===== Installing GRUB =====
  
=== Enabling serial console access ===
+
Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to <tt>/boot</tt>. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command (for 32bit simply set it as i386-efi):
These are instructions specific for Pandaboard.
+
nano -w /mnt/SD_root/etc/inittab
+
s0:12345:respawn:/sbin/agetty 115200 ttyO2 vt100
+
  
=== Kernel and bootloader ===
+
<console>
Here you can find kernel and bootloader files for a quick start.
+
(chroot) # ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
Put these on first partition of your SD card. Archive name boot.tar.xz
+
</console>
 +
This command will simply install all the stuff to <tt>/boot/EFI</tt> and <tt>/boot/grub</tt> that your system needs to boot. In particular, the <tt>/boot/EFI/grub/grubx64.efi</tt> file will be created. This is the GRUB boot image that UEFI will load and start.
  
* http://www.mediafire.com/?h5m1mnqqdrnyb
+
A more detailed explanation of the flags used in the above command:
 +
* <code>--target=x86_64-efi</code>: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
 +
* <code>--efi-directory=/boot</code>: All GRUB UEFI files will be installed in ''/boot''
 +
* <code>--bootloader-id="Funtoo Linux [GRUB]"</code>: This flag is not necessary for GRUB to boot. However, it allows you to change the text of the boot option in the UEFI BIOS. The stuff in the quotes can be set to anything that you would like.
 +
* <code>--recheck</code>: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
 +
* <code>/dev/sda</code>:The device that we are installing GRUB on.
  
Of course you can build your own kernel and U-Boot files, but these are provided here so you don't have to go through the cross-compiling pains and can use your Pandaboard to do native compiling once running.
+
===== Configuring GRUB =====
  
=== Modules and firmware ===
+
OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps. Since boot-update doesn't yet support UEFI, we will use boot-update, but then edit our <code>/boot/grub/grub.cfg</code> to support UEFI booting.  
Put these inside /lib folder on second partition. Archive name modules.tar.xz
+
  
* http://www.mediafire.com/?h5m1mnqqdrnyb
+
First, you will need to edit <code>/etc/boot.conf</code>. Format this as you would if you were booting without UEFI. If you are not sure how this should look, below is an example of what it could look like if you are booting from an unencrypted ext4 partition:
 +
 
 +
{{file|name=/etc/boot.conf|desc=|body=
 +
boot {
 +
        generate grub
 +
        default "Funtoo Linux"
 +
        timeout 3
 +
}
 +
 
 +
"Funtoo Linux" {
 +
        kernel vmlinuz[-v]
 +
        params += rootfstype=ext4 root=/dev/sda2
 +
}
 +
}}
 +
 
 +
After you have edited your <code>/etc/boot.conf</code> file, run <code>boot-update</code>. You should now have a <code>/boot/grub/grub.cfg</code> file, which you can edit using the following command:
 +
 
 +
<console>
 +
# ##i##nano /boot/grub/grub.cfg
 +
</console>
 +
 
 +
 
 +
To get your <code>/boot/grub/grub.cfg</code> to support booting with UEFI, make the following changes. Below the existing insmod lines, add the following lines.  Both of these involve adding support for the UEFI framebuffer to GRUB.:
 +
 
 +
<pre>
 +
  insmod efi_gop
 +
  insmod efi_uga
 +
</pre>
 +
 
 +
Then, change the <code>set gfxpayload</code> line to read as follows. UEFI does not support text mode, so we will keep video initialized to the current resolution.:
 +
 
 +
<pre>
 +
  set gfxpayload=keep
 +
</pre>
  
[[Category:ARM]]
+
You can now save your changes by pressing <code>Control-X</code> and answering <code>y</code> when asked if you want to save the modified buffer. When prompted for a filename, hit Enter to use the existing filename.

Revision as of 07:36, January 1, 2015


Note

This is a template that is used as part of the Installation instructions which covers: boot loader configuration. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.


Installing a Bootloader

These install instructions show you how to use GRUB to boot using BIOS (old-school) or UEFI (new-school).

Old School (BIOS)

If you're using the BIOS to boot, setting up GRUB, the bootloader, is pretty easy.

To use this recommended boot method, first emerge boot-update. This will also cause grub-2 to be merged, since it is a dependency of boot-update.

(chroot) # emerge boot-update

Then, edit /etc/boot.conf and specify "Funtoo Linux genkernel" as the default setting at the top of the file, replacing "Funtoo Linux".

/etc/boot.conf should now look like this:

boot {
	generate grub
	default "Funtoo Linux genkernel" 
	timeout 3 
}

"Funtoo Linux" {
	kernel bzImage[-v]
}

"Funtoo Linux genkernel" {
	kernel kernel[-v]
	initrd initramfs[-v]
	params += real_root=auto 
} 

"Funtoo Linux better-initramfs" {
	kernel vmlinuz[-v]
	initrd /initramfs.cpio.gz
}

Please read man boot.conf for further details.

Running grub-install and boot-update

Finally, we will need to actually install the GRUB boot loader to your disk, and also run boot-update which will generate your boot loader configuration file:

(chroot) # grub-install --no-floppy /dev/sda
(chroot) # boot-update

Now you need to update your boot loader configuration file:

(chroot) # boot-update

You only need to run grub-install when you first install Funtoo Linux, but you need to re-run boot-update every time you modify your /etc/boot.conf file, so your changes are applied on next boot.

New School (UEFI)

If you're using UEFI to boot, setting up the boot loader is a bit more complicated for now, but this process will be improving soon. Perform the following steps.

Emerging GRUB

You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this, add the following line to /etc/make.conf:


For 64-bit systems:

GRUB_PLATFORMS="efi-64"

For 32-bit systems, i.e. Intel Atom devices and systems with less than 4GB of RAM:

GRUB_PLATFORMS="efi-32"

Then, emerge boot-update. You will notice grub and efibootmgr getting pulled in as dependencies. This is expected and good:

(chroot) # emerge boot-update
Installing GRUB

Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to /boot. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command (for 32bit simply set it as i386-efi):

(chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda

This command will simply install all the stuff to /boot/EFI and /boot/grub that your system needs to boot. In particular, the /boot/EFI/grub/grubx64.efi file will be created. This is the GRUB boot image that UEFI will load and start.

A more detailed explanation of the flags used in the above command:

  • --target=x86_64-efi: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
  • --efi-directory=/boot: All GRUB UEFI files will be installed in /boot
  • --bootloader-id="Funtoo Linux [GRUB]": This flag is not necessary for GRUB to boot. However, it allows you to change the text of the boot option in the UEFI BIOS. The stuff in the quotes can be set to anything that you would like.
  • --recheck: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
  • /dev/sda:The device that we are installing GRUB on.
Configuring GRUB

OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps. Since boot-update doesn't yet support UEFI, we will use boot-update, but then edit our /boot/grub/grub.cfg to support UEFI booting.

First, you will need to edit /etc/boot.conf. Format this as you would if you were booting without UEFI. If you are not sure how this should look, below is an example of what it could look like if you are booting from an unencrypted ext4 partition:

/etc/boot.conf
boot {
        generate grub
        default "Funtoo Linux"
        timeout 3
}

"Funtoo Linux" {
        kernel vmlinuz[-v]
        params += rootfstype=ext4 root=/dev/sda2
}

After you have edited your /etc/boot.conf file, run boot-update. You should now have a /boot/grub/grub.cfg file, which you can edit using the following command:

# nano /boot/grub/grub.cfg


To get your /boot/grub/grub.cfg to support booting with UEFI, make the following changes. Below the existing insmod lines, add the following lines. Both of these involve adding support for the UEFI framebuffer to GRUB.:

  insmod efi_gop
  insmod efi_uga

Then, change the set gfxpayload line to read as follows. UEFI does not support text mode, so we will keep video initialized to the current resolution.:

  set gfxpayload=keep

You can now save your changes by pressing Control-X and answering y when asked if you want to save the modified buffer. When prompted for a filename, hit Enter to use the existing filename.