Installing Fedora Core

Overview

This page describes how to install Fedora Core on the One Laptop hardware. As of the writing of this document, the test-A boards have been built and distributed to quite a few people. Fedora Core does run on the hardware, with some minor changes. We'll walk you through how to make those changes.

Requirements

Hardware

You will need a few pieces of hardware to install the software on the Laptop board.

• 1 test-A or pre-test-A OLPC board
• 1 USB hub
• 1 USB flash drive
• 1 USB hard drive
• 1 USB ethernet adapter
• 1 external VGA-compatible monitor for display
• 1 USB keyboard
• 1 USB mouse

Software

Right now, you need to use the Rawhide (unstable) version of Fedora Core to install on the laptop. We will be putting our kernel changes, dependency and software changes into FC Rawhide. So our current requirements for the software include:

• A recent rawhide snapshot (we provide some known good snapshots)
• A place to host that snapshot on the network
• The serenity to accept that sometimes Rawhide is broken
• A strong will to live

Download

• Notes here about which versions to download

Getting Ready to Install

Setting up a bootable image

Insert your USB key into another Fedora machine and run the command dmesg. The output should look something like this:

usb-storage: waiting for device to settle before scanning
  Vendor: Kingston  Model: DataTraveler 2.0  Rev: 6.16
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 2004991 512-byte hdwr sectors (1027 MB)
sda: Write Protect is off
sda: Mode Sense: 45 00 00 08
sda: assuming drive cache: write through
SCSI device sda: 2004991 512-byte hdwr sectors (1027 MB)
sda: Write Protect is off
sda: Mode Sense: 45 00 00 08
sda: assuming drive cache: write through
 sda: sda1
sd 3:0:0:0: Attached scsi removable disk sda
sd 3:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete

Note the fact that this USB key has shown up as sda. You will need this in a moment.

Make sure the device is not mounted. You can do this with a simple mount command. If /dev/sda1 shows up in the output, it's mounted. You can unmonut it by running umount /dev/sda1. Like so:

[blizzard@mobile2 images]$ mount
/dev/hda2 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda1 on /boot type ext3 (rw)
/dev/sda1 on /media/Kingston type vfat (rw,noexec,nosuid,nodev,shortname=winnt,uid=500)
[blizzard@mobile2 images]$ sudo umount /dev/sda1
[blizzard@mobile2 images]$

Locate the Fedora rawhide tree. In that tree find the file

images/diskboot.img

This is the file that contains a bootable image that you can use to boot on the board and run the installer. You will need to copy it in a raw format to the USB key. You use this using the dd command to the raw device. Note that this is /dev/sda not /dev/sda1. This will destroy or replace any filesystems or data on this drive.

[root@mobile2 2006-06-08-0245]# dd if=images/diskboot.img of=/dev/sda
16384+0 records in
16384+0 records out
8388608 bytes (8.4 MB) copied, 1.88433 seconds, 4.5 MB/s
[root@mobile2 2006-06-08-0245]#

Boot on the laptop

Insert the USB flash drive into one of the USB ports that's directly connected to the laptop. Do not connect it through the USB hub.

Power on the laptop board. If the BIOS detects the USB key you will see a message in the upper left hand corner of the screen that says something like:

Press F1 for Setup INITIALIZING BOOT USB DEVICE - DataTraveler 2.0  
USB Storage Class Device [xxxxxxxx/xxxx/xxxx]

or

Press F1 for Setup INITIALIZING BOOT USB DEVICE - WD1600BB-00RDA0
USB BOOTABLE HDD DEVICE [xxxxxxxx/xxxx/xxxx]

You should see the Linux kernel being loaded and then the installer being loaded. If you don't, try the USB key in a different port or disconnecting the hub. The BIOS and USB are very flaky right now because this is a temporary BIOS until LinuxBIOS comes up on the boards.

When you see the installer screen type in linux text to enter the Linux text mode installer.

Installing

• linux text
• point it at an http repo
• install the minimal system?

Fixing post-install

• After the install fix the bootdisk (rescue)
• take apart the initrd
• fix up the usb modules and sleep
• put it all back together
• make sure the initrd is rebuild

Common Errors

• "invalid file system" on boot
• kernel panic on boot