Driver Disk: Difference between revisions
From Leo's Notes
This page was last edited on 29 April 2013, at 08:07.
No edit summary |
|||
| Line 2: | Line 2: | ||
== Create Driver Disk == | == Create Driver Disk == | ||
<syntaxhighlight lang="bash" line enclose="div"> | |||
# Create a blank, 20MB image | # Create a blank, 20MB image | ||
dd if=/dev/zero of=driverdisk.img bs=1M count=20 | dd if=/dev/zero of=driverdisk.img bs=1M count=20 | ||
| Line 13: | Line 14: | ||
# copy drivers to /mnt/driverdisk, then run | # copy drivers to /mnt/driverdisk, then run | ||
umount /mnt/tmp | umount /mnt/tmp | ||
</syntaxhighlight> | |||
Once you have the driver disk created, you will need to tell the installer to load it by booting into <code>linux expert</code> or <code>linux dd</code> from the boot loader. | Once you have the driver disk created, you will need to tell the installer to load it by booting into <code>linux expert</code> or <code>linux dd</code> from the boot loader. | ||
[[Category:Linux]] | [[Category:Linux]] | ||
Revision as of 08:07, 29 April 2013
Red Hat allows for 'driver disks' to be loaded during an install in case there is no out-of-the-box driver support for a specific piece of hardware. Basically, a driver disk is an ext2 disk image which can be created in the following steps:
Create Driver Disk
# Create a blank, 20MB image
dd if=/dev/zero of=driverdisk.img bs=1M count=20
# Format the image with ext2
mkfs -t ext2 -q driverdisk.img
# mount it and copy the files over
mount -o loop driverdisk.img /mnt/driverdisk
# copy drivers to /mnt/driverdisk, then run
umount /mnt/tmp
Once you have the driver disk created, you will need to tell the installer to load it by booting into linux expert or linux dd from the boot loader.