From Fedora Project Wiki

(Clean for F13)
Line 1: Line 1:
{{Admon/warning | Document is Final | The contents of this beat have been sent for translation for the GA version of the Release Notes.  Any additional changes to this beat will not appear until after the release of Fedora 12.  If you have zero-day changes, be sure to post a bug. }}
{{Admon/warning | F13 | Beat owner should begin placing Fedora 13 content in this beat. }}
== Installation Notes ==
{{Admon/tip | To learn how to install Fedora, refer to either the ''Fedora Installation Quick Start Guide'' available from or the ''Fedora Installation Guide'' available from| If you encounter a problem or have a question during installation that is not covered in these release notes, refer to and}} 
'''Anaconda''' is the name of the Fedora installer. This section outlines issues related to '''Anaconda''' and installing Fedora {{Template:DocsDict/BeatsVer}}.
=== Ext4 for boot partitions ===
Although ext4 was the default file system in Fedora 11, the version of the GRUB bootloader included with Fedora 11 could not read ext4 partitions. Fedora 11 therefore required a separate ext3 boot partition. The version of GRUB included in Fedora 12 now supports ext4, so '''anaconda''' now allows you to place '''/boot''' on an ext4 partition.
=== Installation in text mode ===
{{Admon/tip | We recommend that you use the graphical installer to install Fedora on your computer wherever possible. If you are installing Fedora on a system that lacks a graphical display, consider performing the installation over a VNC connection (see "Chapter 12. Installing Through VNC" in the Fedora {{Template:DocsDict/BeatsVer}} Installation Guide).  If your system has a graphical display, but graphical installation fails, try booting with the  xdriver&#61;vesa option (see "Chapter 9. Boot Options" in the Fedora 11 Installation Guide) or with the 'Install system with basic video driver' option when booting from the Fedora {{Template:DocsDict/BeatsVer}} DVD.}}
==== Kickstart installations in text mode ====
Text-mode installations using kickstart are carried out in the same way that they were in previous versions. However, because package selection, advanced partitioning, and bootloader configuration are now automated in text mode, Anaconda cannot prompt users for information that it requires during these steps. Users must ensure that the kickstart file includes the packaging, partitioning, and bootloader configurations. If any of this information is missing, Anaconda will exit with an error message.
=== Upgrade Notes ===
Upgrading from Fedora 9 directly to Fedora {{Template:DocsDict/BeatsVer}} using <code>yum</code> is not possible, you must upgrade to Fedora 10 first, then upgrade to Fedora {{Template:DocsDict/BeatsVer}}.  See for more information.  You can also use <code>preupgrade</code> to upgrade directly to Fedora 11 using Anaconda, minimizing the system downtime by downloading the packages in advance.
Some modified configuration files will be replaced by their original versions during the upgrade.  Your modified versions of these configuration files will be saved as <code>*.rpmsave</code> files in that case.
=== Boot menu ===
The boot menu for the Fedora DVD includes a new option: '''Install system with basic video driver'''. This option boots the system with the generic vesa driver (using the '''xdriver=vesa''' kernel option) and allows you to use Fedora's graphical installation mode even when Anaconda cannot load the correct driver for your video card.
=== boot.iso Now Works on Systems With UEFI ===
The fedora installation CDs and DVD provide you with an image file, ''boot.iso'' that you can burn to a CD and use to boot a system and start the installation process.  Typically, you would do this prior to installing Fedora from a local hard drive or from a location on a network.  You can now use the CD produced from the ''boot.iso'' image to start installation on a system that uses Unified Extensible Firmware Interface (UEFI).  CDs produced from older versions of ''boot.iso'' only worked with systems that used Basic Input Output System (BIOS).
=== Installation media ===
{{Admon/note | Fedora DVD ISO image is a large file | If you intend to download the Fedora DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2 GiB in size.  The programs <code>wget</code> 1.9.1-16 and above, <code>curl</code>, and <code>ncftpget</code> do not have this limitation, and can successfully download files larger than 2 GiB. BitTorrent is another method for downloading large files. For information about obtaining and using the torrent file, refer to}}
'''Anaconda''' asks if it should verify the installation medium when ''Install or upgrade an existing system'' is selected during boot from an installation-only media.
For Fedora Live media, press any key during the initial boot countdown to display a boot option menu.  Select ''Verify and boot'' to perform the media test. Installation media can be used to verify Fedora Live media. '''Anaconda''' asks during the mediacheck if you want to check any other disc than the one '''Anaconda''' is running from.  To test additional media, select <code>eject</code> to eject the inserted medium, then replace it with the medium you want to test.
Perform this test for any new installation or Live medium.
The Fedora Project strongly recommends that you perform this test before reporting any installation-related bugs. Many of the bugs reported are actually due to improperly-burned CD or DVDs.
In rare cases, the testing procedure may report some usable discs as faulty. This result is often caused by disc writing software that does not include padding when creating discs from ISO files.
{{Admon/note | BitTorrent Automatically Verifies File Integrity.|If you use BitTorrent, any files you download are automatically validated. If your file completes downloading you do not need to check it. Once you burn your CD or DVD, however, you should still use <code>mediacheck</code> to test the integrity of the media.}}
Another reason for a failure during installation is faulty memory. To perform memory testing before you install Fedora, press any key to enter the boot menu, then select ''Memory Test''. This option runs the '''Memtest86''' standalone memory testing software in place of '''Anaconda'''. '''Memtest86''' memory testing continues until you press the '''[Esc]''' key.
Fedora {{Template:DocsDict/BeatsVer}} supports graphical FTP and HTTP installations. However, the installer image must either fit in RAM or appear on local storage, such as the installation DVD or Live Media. Therefore, only systems with more than 192MiB of RAM or that boot from the installation DVD or Live Media can use the graphical installer. Systems with 192MiB RAM or less fall back to using the text-based installer automatically. If you prefer to use the text-based installer, type <code>linux text</code> at the <code>boot:</code> prompt.
=== Changes in Anaconda ===
=== Installation Related Issues ===
==== IDE device names ====
Use of <code>/dev/hdX</code> on i386 and x86_64 for IDE drives changed to <code>/dev/sdX</code> in Fedora 7.  If you are upgrading from an earlier version than Fedora 7, you need to research about the importance of labeling devices for upgrades and any partition limitations.
==== IDE RAID ====
Not all IDE RAID controllers are supported. If your RAID controller is not yet supported by <code>dmraid</code>, you may combine drives into RAID arrays by configuring Linux software RAID. For supported controllers, configure the RAID functions in the computer BIOS.
==== Multiple NICs and PXE installation ====
Some servers with multiple network interfaces may not assign eth0 to the first network interface as BIOS knows it, which can cause the installer to try using a different network interface than was used by PXE.  To change this behavior, use the following in <code>pxelinux.cfg/*</code> config files:
APPEND ksdevice=bootif
The configuration options above causes the installer to use the same network interface as BIOS and PXE use. You can also use the following option:
This option causes the installer to use the first network device it finds that is linked to a network switch.
=== Upgrade related issues ===
Refer to for detailed recommended procedures for upgrading Fedora.
==== SCSI driver partition limits ====
Whereas older IDE drivers supported up to 63 partitions per device, SCSI devices are limited to 15 partitions per device. '''Anaconda''' uses the <code>libata</code> driver in the same fashion as the rest of Fedora, so it is unable to detect more than 15 partitions on an IDE disk during the installation or upgrade process.
If you are upgrading a system with more than 15 partitions, you may need to migrate the disk to Logical Volume Management (LVM). This restriction may cause conflicts with other installed systems if they do not support LVM. Most modern Linux distributions support LVM and drivers are available for other operating systems as well.
==== Disk partitions must be labeled ====
A change in the way that the Linux kernel handles storage devices means that device names like <code>/dev/hdX</code> or <code>/dev/sdX</code> may differ from the values used in earlier releases. '''Anaconda''' solves this problem by relying on partition labels or UUIDs for finding devices. If these are not present, then '''Anaconda''' presents a warning indicating that partitions need to be labelled and that the upgrade can not proceed. Systems that use Logical Volume Management (LVM) and the device mapper usually do not require relabeling.
===== To check disk partition labels =====
To view partition labels, boot the existing Fedora installation, and enter the following at a terminal prompt:
Confirm that each volume line in the list has a <code>LABEL=</code> value, as shown below:
<pre>/dev/hdd1: LABEL="/boot" UUID="ec6a9d6c-6f05-487e-a8bd-a2594b854406" SEC_TYPE="ext2" TYPE="ext3"
===== To set disk partition labels =====
For ext2 and ext3 partitions without a label, use the following command:
<pre>su -c 'e2label /dev/example f7-slash'
For a VFAT file system use <code>dosfslabel</code> from the <code>dosfstools</code> package, and for NTFS file system use <code>ntfslabel</code> from the <code>ntfsprogs</code> package.  Before rebooting the machine, also update the file system mount entries, and the GRUB kernel root entry.
===== Update the file system mount entries =====
If any file system labels were added or modified, then the device entries in <code>/etc/fstab</code> must be adjusted to match:
<pre>su -c 'cp /etc/fstab /etc/fstab.orig'
su -c 'gedit /etc/fstab'
An example of a mount by label entry is:
<pre> LABEL=f7-slash  /  ext3  defaults  1 1
===== Update the grub.conf kernel root entry =====
If the label for the / (root) file system was modified, the kernel boot parameter in the grub configuration file must also be modified:
<pre>su -c 'gedit /boot/grub/grub.conf'
A matching example kernel grub line is:
<pre> kernel /vmlinuz-2.6.20-1.2948.fc6 ro root=LABEL=f7-slash rhgb quiet
===== Test changes made to labels =====
If partition labels were adjusted, or the <code>/etc/fstab</code> file modified, then boot the existing Fedora installation to confirm that all partitions still mount normally and login is successful. When complete, reboot with the installation media to start the installer and begin the upgrade.
==== Upgrades versus fresh installations ====
In general, fresh installations are recommended over upgrades. This is particularly true for systems that include software from third-party repositories. Third-party packages remaining from a previous installation may not work as expected on an upgraded Fedora system. If you decide to perform an upgrade anyway, the following information may be helpful:
Before you upgrade, back up the system completely. In particular, preserve <code>/etc</code>, <code>/home</code>, and possibly <code>/opt</code> and <code>/usr/local</code> if customized packages are installed there. You may want to use a multi-boot approach with a "clone" of the old installation on alternate partition(s) as a fallback. In that case, create alternate boot media, such as a GRUB boot floppy.
{{Admon/tip | Configuration backups | Backups of configurations in <code>/etc</code> are also useful in reconstructing system settings after a fresh installation.}}
After you complete the upgrade, run the following command:
<pre>rpm -qa --last > RPMS_by_Install_Time.txt
Inspect the end of the output for packages that pre-date the upgrade. Remove or upgrade those packages from third-party repositories, or otherwise deal with them as necessary. Some previously installed packages may no longer be available in any configured repository. To list all these packages, use the following command:
<pre>su -c 'yum list extras'
=== Kickstart HTTP Issue ===
When using a kickstart configuration file via HTTP, kickstart file retrieval may fail with an error that indicates the file could not be retrieved. Click the ''OK'' button several times without making modifications to override this error successfully. As a workaround, use one of the other supported methods to retrieve kickstart configurations.
  <noinclude>[[Category:Release Notes]]<noinclude>
  <noinclude>[[Category:Release Notes]]<noinclude>

Revision as of 21:08, 16 February 2010

Beat owner should begin placing Fedora 13 content in this beat.