Installing Fedora Core: Difference between revisions
(how to use the bootdisk.img) |
m (remove categories from this obsolete page) |
||
(86 intermediate revisions by 26 users not shown) | |||
Line 1: | Line 1: | ||
{{Deprecated}} |
|||
'''See [[Fedora on XO]] for how to run the Fedora 10 Linux distribution on your 2008 or 2009 XO laptop.''' |
|||
==Overview== |
==Overview== |
||
This page describes how to install Fedora Core on |
This page describes how to install [[Fedora Core]] on '''ancient, obsolete 2006 prototype''' One Laptop per Child hardware using a USB Hard Disk Drive. As of the writing of this document, the A-Test boards have been built and distributed to several hundred people. |
||
==Requirements== |
==Requirements== |
||
Line 7: | Line 13: | ||
===Hardware=== |
===Hardware=== |
||
You will need a few pieces of hardware to install the software on the |
You will need a few pieces of hardware to install the software on the A-Test board. |
||
* 1 |
* 1 A-Test (or pre-A-Test) OLPC board |
||
* 1 USB hub |
|||
* 1 USB flash drive |
|||
* 1 USB hard drive |
* 1 USB hard drive |
||
* 1 USB ethernet adapter |
* 1 USB ethernet adapter |
||
Line 17: | Line 21: | ||
* 1 USB keyboard |
* 1 USB keyboard |
||
* 1 USB mouse |
* 1 USB mouse |
||
* 1 powered USB hub |
|||
====Why you need the ''powered'' USB hub==== |
|||
* The board only has 3 USB ports, and there are 5 USB peripherals involved. |
|||
* But even if you are only using 3 USB peripherals, you still might need a powered hub, because the board's internal power converters are wimpy on ATest; fixed on later boards. |
|||
===Software=== |
===Software=== |
||
==Download== |
|||
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: |
|||
Get an OS image from [http://olpc.download.redhat.com/olpc/streams/development/latest/devel_ext3/ http://olpc.download.redhat.com/olpc/streams/development/latest/devel_ext3/]. You want the ".img.bz2" file, for example: |
|||
* 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 |
|||
olpc-redhat-stream-development-build-86-20060922_1506-devel_ext3.img.bz2 |
|||
== |
==Installing== |
||
Follow the directions at [[OS images for USB disks]], under the "Dedicated USB disk" section. |
|||
* Notes here about which versions to download |
|||
==Enlarging the Partition== |
|||
==Getting Ready to Install== |
|||
The OLPC OS images are 512MB (to fit the onboard flash), but you are installing them to a larger drive. Therefore we must enlarge the partition. Once you have transferred the image to the USB device (the 'dd' step), and synced all disks (the 'sync' step), get a root shell. Then, start the 'fdisk' command like so: |
|||
Insert your USB key into another Fedora machine and run the command <tt>dmesg</tt>. The output should look something like this: |
|||
[root@localhost ~]# fdisk /dev/sda |
|||
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 |
|||
Be '''sure''' to replace '/dev/sda' with the actual device name of the USB Hard Disk Drive on which you are installing the OLPC OS. |
|||
Note the fact that this USB key has shown up as <tt>sda</tt>. You will need this in a moment. |
|||
Next, type 'p' to show the current partition table: |
|||
'''Make sure the device is not mounted.''' You can do this with a simple <tt>mount</tt> command. If <tt>/dev/sda1</tt> shows up in the output, it's mounted. You can unmonut it by running <tt>umount /dev/sda1</tt>. Like so: |
|||
Command (m for help): p<br> |
|||
[blizzard@mobile2 images]$ mount |
|||
/dev/ |
Disk /dev/sda: 5000 MB, 5000970240 bytes |
||
16 heads, 62 sectors/track, 9846 cylinders |
|||
none on /proc type proc (rw) |
|||
Units = cylinders of 992 * 512 = 507904 bytes<br> |
|||
none on /sys type sysfs (rw) |
|||
Device Boot Start End Blocks Id System |
|||
none on /dev/pts type devpts (rw,gid=5,mode=620) |
|||
/dev/sda1 1 993 492497 83 Linux |
|||
/dev/hda1 on /boot type ext3 (rw) |
|||
Command (m for help): |
|||
'''/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]$ |
|||
Next, you wish to delete the existing partition: |
|||
Command (m for help): d |
|||
Locate the Fedora rawhide tree. In that tree find the file |
|||
Selected partition 1<br> |
|||
If you type 'p' again to print the partition table, you'll notice that the partition has been deleted: |
|||
images/diskboot.img |
|||
Command (m for help): p<br> |
|||
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 <tt>dd</tt> 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. |
|||
Disk /dev/sda: 5000 MB, 5000970240 bytes |
|||
16 heads, 62 sectors/track, 9846 cylinders |
|||
Units = cylinders of 992 * 512 = 507904 bytes<br> |
|||
Device Boot Start End Blocks Id System<br> |
|||
Command (m for help): |
|||
Next, you wish to re-create the partition with a much larger size: |
|||
[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]# |
|||
Command (m for help): n |
|||
* boot on that drive |
|||
Command action |
|||
e extended |
|||
p primary partition (1-4) |
|||
Type the letter 'p' here to create a new primary partition. |
|||
==Installing== |
|||
p |
|||
Type '1' here to create primary partition number 1: |
|||
Partition number (1-4): 1 |
|||
Just hit return here to start the partition at cylinder #1: |
|||
First cylinder (1-9846, default 1): 1 |
|||
Just hit return here to end the partition at the end of the disk: |
|||
Last cylinder or +size or +sizeM or +sizeK (1-9846, default 9846): |
|||
Using default value 9846<br> |
|||
You may type 'p' again to print out the new partition table: |
|||
Command (m for help): p<br> |
|||
Disk /dev/sda: 5000 MB, 5000970240 bytes |
|||
16 heads, 62 sectors/track, 9846 cylinders |
|||
Units = cylinders of 992 * 512 = 507904 bytes<br> |
|||
Device Boot Start End Blocks Id System |
|||
/dev/sda1 1 9846 4883615+ 83 Linux |
|||
Now, type 'w' to write the partition table to the disk and quit fdisk. |
|||
==Enlarging the filesystem== |
|||
Now that the partition is large enough, you must resize the filesystem to take advantage of all the new space. First we have to 'fsck' (file system check) the file system to ensure that it is clean. Be '''sure''' to replace the '/dev/sda1' with the actual device you are using, and make sure that you '''do''' have the '1' on the end, to specify checking of the first partition, not the entire device. |
|||
[root@localhost ~]# fsck.ext3 /dev/sda1 |
|||
e2fsck 1.39 (29-May-2006) |
|||
/dev/sda1 is mounted.<br> |
|||
WARNING!!! Running e2fsck on a mounted filesystem may cause |
|||
SEVERE filesystem damage.<br> |
|||
Do you really want to continue (y/n)? yes<br> |
|||
Type 'y' here to continue checking: |
|||
OLPCRoot: recovering journal |
|||
OLPCRoot: clean, 18986/123464 files, 337653/492496 blocks |
|||
[root@localhost ~]# |
|||
Next, you will resize the actual filesystem. Choose a size that matches or is slightly less than the size of your actual USB hard disk drive. resize2fs will warn you if the size you chose is too big. In that case, just readjust the size and try again. |
|||
[root@localhost ~]# resize2fs /dev/sda1 4500M |
|||
resize2fs 1.39 (29-May-2006) |
|||
Filesystem at /dev/sda1 is mounted on /media/OLPCRoot; on-line resizing required |
|||
Performing an on-line resize of /dev/sda1 to 4608000 (1k) blocks. |
|||
When that step is complete (it could take a while), type 'sync' to ensure data is flushed to disk. '''Wait until the disk activity light has stopped''' before unplugging the disk. |
|||
==Done!== |
|||
You may now connect the drive to an OLPC developer board and boot it. |
|||
==Additional Setup== |
|||
The OLPC OS images are set up to automatically start [[Sugar]]. You may not want this. After booting and arriving at the Sugar login screen, switch to a virtual terminal by pressing Ctrl+Alt+F1 all at the same time. You will then see a login prompt. You may log in as 'root' with no password. Change the password to something secure!!! Next, remove the contents of /etc/sysconfig/desktop and leave the file blank to stop sugar from starting by default. |
|||
==Adding more software to the system== |
|||
Since the OLPC images are quite stripped due to the 512MB requirement, you may wish to install additional software. Before installing either a Gnome or KDE environment, you must resolve a conflict between Sugar's artwork package, and the normal Fedora artwork package. |
|||
First, try to install redhat-artwork: |
|||
yum install redhat-artwork |
|||
This will download redhat-artwork and its dependencies. When 'yum' asks: |
|||
Is this ok [y/N]: |
|||
Type 'y' to proceed. The install will fail with a file conflict for /etc/gtk-2.0/gtkrc. That's fine, we'll proceed to force-install redhat-artwork and it's fedora-logos dependency: |
|||
-bash-3.1# cd /var/cache/yum/development/packages |
|||
-bash-3.1# rpm -Uhv redhat-artwork-5.0.7-1.fc6.i386.rpm fedora-logos-6.0.6-1.fc6.noarch --force |
|||
Note that your package versions might be slightly different; that's fine. Replace the filenames in the command above with the versions in the 'packages' directory. Now you may install your desktop environment of choice. |
|||
===Installing Gnome=== |
|||
To install a Gnome desktop environment, run: |
|||
-bash-3.1# yum install nautilus gedit gdm gnome-panel gnome-session |
|||
This will download and install the major pieces of the GNOME desktop. When 'yum' asks: |
|||
Is this ok [y/N]: |
|||
Type 'y' to proceed. If yum fails due to dependency issues, you may need to wait until the problem gets fixed, or you may file a bug at [http://bugzilla.redhat.com Red Hat Bugzilla]. |
|||
===Installing KDE=== |
|||
If you would like the KDE environment, you could type: |
|||
* linux text |
|||
* point it at an http repo |
|||
* install the minimal system? |
|||
yum install kdebase kdeutils |
|||
This will download and install the major pieces of the KDE desktop. When 'yum' asks: |
|||
* 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 |
|||
Is this ok [y/N]: |
|||
==Common Errors== |
|||
Type 'y' to proceed. If yum fails due to dependency issues, you may need to wait until the problem gets fixed, or you may file a bug at [http://bugzilla.redhat.com Red Hat Bugzilla]. |
|||
* "invalid file system" on boot |
|||
* kernel panic on boot |
Latest revision as of 23:04, 5 November 2008
See Fedora on XO for how to run the Fedora 10 Linux distribution on your 2008 or 2009 XO laptop.
OverviewThis page describes how to install Fedora Core on ancient, obsolete 2006 prototype One Laptop per Child hardware using a USB Hard Disk Drive. As of the writing of this document, the A-Test boards have been built and distributed to several hundred people. RequirementsHardwareYou will need a few pieces of hardware to install the software on the A-Test board.
Why you need the powered USB hub
SoftwareDownloadGet an OS image from http://olpc.download.redhat.com/olpc/streams/development/latest/devel_ext3/. You want the ".img.bz2" file, for example: olpc-redhat-stream-development-build-86-20060922_1506-devel_ext3.img.bz2 InstallingFollow the directions at OS images for USB disks, under the "Dedicated USB disk" section. Enlarging the PartitionThe OLPC OS images are 512MB (to fit the onboard flash), but you are installing them to a larger drive. Therefore we must enlarge the partition. Once you have transferred the image to the USB device (the 'dd' step), and synced all disks (the 'sync' step), get a root shell. Then, start the 'fdisk' command like so: [root@localhost ~]# fdisk /dev/sda Be sure to replace '/dev/sda' with the actual device name of the USB Hard Disk Drive on which you are installing the OLPC OS. Next, type 'p' to show the current partition table: Command (m for help): p Next, you wish to delete the existing partition: Command (m for help): d Selected partition 1 If you type 'p' again to print the partition table, you'll notice that the partition has been deleted: Command (m for help): p Next, you wish to re-create the partition with a much larger size: Command (m for help): n Command action e extended p primary partition (1-4) Type the letter 'p' here to create a new primary partition. p Type '1' here to create primary partition number 1: Partition number (1-4): 1 Just hit return here to start the partition at cylinder #1: First cylinder (1-9846, default 1): 1 Just hit return here to end the partition at the end of the disk: Last cylinder or +size or +sizeM or +sizeK (1-9846, default 9846): Using default value 9846 You may type 'p' again to print out the new partition table: Command (m for help): p Now, type 'w' to write the partition table to the disk and quit fdisk. Enlarging the filesystemNow that the partition is large enough, you must resize the filesystem to take advantage of all the new space. First we have to 'fsck' (file system check) the file system to ensure that it is clean. Be sure to replace the '/dev/sda1' with the actual device you are using, and make sure that you do have the '1' on the end, to specify checking of the first partition, not the entire device. [root@localhost ~]# fsck.ext3 /dev/sda1 e2fsck 1.39 (29-May-2006) /dev/sda1 is mounted. Type 'y' here to continue checking: OLPCRoot: recovering journal OLPCRoot: clean, 18986/123464 files, 337653/492496 blocks [root@localhost ~]# Next, you will resize the actual filesystem. Choose a size that matches or is slightly less than the size of your actual USB hard disk drive. resize2fs will warn you if the size you chose is too big. In that case, just readjust the size and try again. [root@localhost ~]# resize2fs /dev/sda1 4500M resize2fs 1.39 (29-May-2006) Filesystem at /dev/sda1 is mounted on /media/OLPCRoot; on-line resizing required Performing an on-line resize of /dev/sda1 to 4608000 (1k) blocks. When that step is complete (it could take a while), type 'sync' to ensure data is flushed to disk. Wait until the disk activity light has stopped before unplugging the disk. Done!You may now connect the drive to an OLPC developer board and boot it. Additional SetupThe OLPC OS images are set up to automatically start Sugar. You may not want this. After booting and arriving at the Sugar login screen, switch to a virtual terminal by pressing Ctrl+Alt+F1 all at the same time. You will then see a login prompt. You may log in as 'root' with no password. Change the password to something secure!!! Next, remove the contents of /etc/sysconfig/desktop and leave the file blank to stop sugar from starting by default. Adding more software to the systemSince the OLPC images are quite stripped due to the 512MB requirement, you may wish to install additional software. Before installing either a Gnome or KDE environment, you must resolve a conflict between Sugar's artwork package, and the normal Fedora artwork package. First, try to install redhat-artwork: yum install redhat-artwork This will download redhat-artwork and its dependencies. When 'yum' asks: Is this ok [y/N]: Type 'y' to proceed. The install will fail with a file conflict for /etc/gtk-2.0/gtkrc. That's fine, we'll proceed to force-install redhat-artwork and it's fedora-logos dependency: -bash-3.1# cd /var/cache/yum/development/packages -bash-3.1# rpm -Uhv redhat-artwork-5.0.7-1.fc6.i386.rpm fedora-logos-6.0.6-1.fc6.noarch --force Note that your package versions might be slightly different; that's fine. Replace the filenames in the command above with the versions in the 'packages' directory. Now you may install your desktop environment of choice. Installing GnomeTo install a Gnome desktop environment, run: -bash-3.1# yum install nautilus gedit gdm gnome-panel gnome-session This will download and install the major pieces of the GNOME desktop. When 'yum' asks: Is this ok [y/N]: Type 'y' to proceed. If yum fails due to dependency issues, you may need to wait until the problem gets fixed, or you may file a bug at Red Hat Bugzilla. Installing KDEIf you would like the KDE environment, you could type: yum install kdebase kdeutils This will download and install the major pieces of the KDE desktop. When 'yum' asks: Is this ok [y/N]: Type 'y' to proceed. If yum fails due to dependency issues, you may need to wait until the problem gets fixed, or you may file a bug at Red Hat Bugzilla. |