Questo contenuto non è disponibile nella lingua selezionata.
6.2. Preparing for a Driver Update During Installation
If a driver update is necessary and available for your hardware, Red Hat, your hardware vendor, or another trusted third party will typically provide it in the form of an image file in ISO format. Once you obtain the ISO image, you must decide on the method you want to use to perform the driver update.
The available methods are:
- Automatic driver update
- When starting the installation, the Anaconda installation program will attempt to detect all attached storage devices. If there is a storage device labeled
OEMDRVpresent when the installation begins, Anaconda will always treat it like a driver update disc and attempt to load drivers present on it. - Assisted driver update
- You can specify the
inst.ddboot option when starting the installation. If you use this option without any parameters, Anaconda will display a list of all storage devices connected to the system, and it will prompt you to select a device which contains a driver update. - Manual driver update
- You can specify the
inst.dd=locationboot option when starting the installation, where location is the path to a driver update disc or ISO image. When you specify this option, Anaconda will attempt to load any driver updates it finds at the specified location. With manual driver updates, you can specify either locally available storage devices, or a network location (anHTTP,HTTPSorFTPserver).
Note
You can also use both
inst.dd=location and inst.dd at the same time. However, what Anaconda does in this case depends on the type of location that you use. If it is a device, Anaconda prompts you to select drivers to update from the specified device and then it offers you additional devices. If location is a network location, Anaconda first prompts you to select a device containing a driver update and then it lets you update drivers from the specified network location.
If you want to use the automatic driver update method, you must create a storage device labeled
OEMDRV, and it must be physically connected to the installation system. To use the assisted method, you can use any local storage device any label other than OEMDRV. To use the manual method, you can use any local storage with a different label, or a network location accessible from the installation system.
Important
Make sure to initialize the network using the
ip= option when loading a driver update from a network location. See Section 23.1, “Configuring the Installation System at the Boot Menu” for details.
6.2.1. Preparing to Use a Driver Update Image File on Local Storage
If you use a local storage device to provide the ISO file, such as a hard drive or USB flash drive, you can make the installation program to recognize it automatically by properly labeling the device. Only if it is not possible, install the update manually as described below.
- In order for the installation program to automatically recognize the driver disk, the volume label of the storage device must be
OEMDRV. Also, you will need to extract the contents of the ISO image file to the root directory of the storage device rather than copy the ISO image itself. See Section 6.3.1, “Automatic Driver Update”. Note that installation of a driver from a device labeledOEMDRVis always recommended and preferable to the manual installation. - For manual installation, simply copy the ISO image, as a single file, onto the storage device. You can rename the file if you find it helpful but you must not change the file name extension, which must remain
.iso, for exampledd.iso. See Section 6.3.3, “Manual Driver Update” to learn how to select the driver update manually during installation.
6.2.2. Preparing a Driver Disc
You can create a driver update disc on a CD or DVD. See Section 3.1, “Making an Installation CD or DVD” to learn more about burning discs from image files.
After you burn a driver update disc CD or DVD, verify that the disc was created successfully by inserting it into your system and browsing to it using the file manager. You should see a single file named
rhdd3, which is a signature file that contains the driver disc's description, and a directory named rpms, which contains the RPM packages with the actual drivers for various architectures.
If you see only a single file ending in
.iso, then you have not created the disc correctly and should try again. Ensure that you choose an option similar to Burn from Image if you use a Linux desktop other than GNOME, or if you use a different operating system.
