Driver Disk - Revision history

Leo at 18:25, 14 February 2022

2022-02-14T18:25:53Z

@@ Line 1: / Line 1: @@
-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.
+Red Hat based Linux distributions using dracut allows for driver disks to be loaded during so that the installer is able to load properly on a system. Typically, you'll need to use a driver disk for a deprecated RAID/SAS controller.
 == Using a driver disk ==
 === Locating an appropriate driver ===
 If you have an older server that requires a driver that's been dropped, you can most likely find it from ElRepo's DUD repo that is appropriate for your distro version. For example, for RHEL8: https://elrepo.org/linux/dud/el8/x86_64/.
 === Using a driver disk with Anaconda ===
@@ Line 20: / Line 43: @@
 === Loading a driver disk after Anaconda has started ===
-Enter a shell and install the rpm manually using <code>rpm -ivh dd-some-driver.rpm</code>. If you get any dependency issues with the kernel, try using the <code>--nodeps</code> argument as well. Once the package is installed, try to load the module with <code>modprobe driver</code>.
+Enter a shell and install the rpm manually using <code>rpm -ivh dd-some-driver.rpm</code>. If you get any dependency issues with the kernel, try using the <code>--nodeps</code> argument as well. Once the package is installed, try to load the module with <code>insmod driver</code>. Don't use <code>modprobe</code> since it might not activate the driver.
 If your driver is needed by Anaconda (such as storage), you'll need to restart Anaconda by running <code>systemctl restart anaconda.service</code>.
 === Debugging issues ===
@@ Line 31: / Line 58: @@
 }}
-== Creating a driver disk ==
+=== Disks don't appear after modprobe ===
+Try to use <code>insmod</code> instead. When I tried loading a module with <code>modprobe</code>, it didn't seem to activate the hardware and the devices didn't show up.
 == See also ==

Leo at 02:16, 1 February 2022

2022-02-01T02:16:57Z

← Older revision		Revision as of 02:16, 1 February 2022
Line 18:		Line 18:
	\| lang = terminal		\| lang = terminal
	}}		}}

			=== Loading a driver disk after Anaconda has started ===
			Enter a shell and install the rpm manually using <code>rpm -ivh dd-some-driver.rpm</code>. If you get any dependency issues with the kernel, try using the <code>--nodeps</code> argument as well. Once the package is installed, try to load the module with <code>modprobe driver</code>.

			If your driver is needed by Anaconda (such as storage), you'll need to restart Anaconda by running <code>systemctl restart anaconda.service</code>.

	=== Debugging issues ===		=== Debugging issues ===

Leo: Leo moved page Creating a Driver Disk to Driver Disk

2022-01-31T19:06:50Z

Leo moved page Creating a Driver Disk to Driver Disk

← Older revision		Revision as of 19:06, 31 January 2022
(No difference)

Leo: Added information on using a driver disk

2022-01-31T19:06:20Z

Added information on using a driver disk

← Older revision		Revision as of 19:06, 31 January 2022
Line 1:		Line 1:
	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.		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.

	~~If you have an older server that requires~~ a driver that's been dropped, you can most likely find it from ElRepo. Their DUD repo (Eg. https://elrepo.org/linux/dud/el8/x86_64/) contains various driver disks in an ISO format which you can load with the installer. ISO disk ~~drivers are loaded by passing in a <code>inst.dd~~=~~<path-or-url-to-iso></code> as part of the boot option when starting the installer.~~		== Using a driver disk ==

	== DKMS ==		=== Locating an appropriate driver ===
			If you have an older server that requires a driver that's been dropped, you can most likely find it from ElRepo's DUD repo that is appropriate for your distro version. For example, for RHEL8: https://elrepo.org/linux/dud/el8/x86_64/.

			=== Using a driver disk with Anaconda ===
			To use a driver disk, append <code>inst.dd=location</code> to the kernel arguments by hitting tab while on the grub menu. <code>inst.dd</code> supports network locations via HTTP, FTP, or NFS, and also a local device. For example: <code>inst.dd=<nowiki>http://url/driver.iso</nowiki></code>, <code>inst.dd=nfs:server/export</code>, <code>inst.dd=/dev/sdb</code>

			If you intend to use a removeable device such as a USB stick, floppy, or an iDRAC virtual device, you will need copy the contents of the ISO file into a vfat formatted partition. Eg:
			{{Highlight
			\| code = # dd if=/dev/zero of=driver.img bs=1M count=1
			# mkfs.vfat driver.img # Note: mkfs.vfat is provided by dosfstools
			# mount -o loop driver.img /mnt
			# cp -r /iso-contents/* /mnt
			# umount /mnt
			\| lang = terminal
			}}

			=== Debugging issues ===
			If for some reason Anaconda doesn't start after specifying a driver disk, you can have systemd log to the console to help troubleshoot the issue by appending the following to the kernel arguments:
			{{Highlight
			\| code = systemd.log_target=console systemd.log_level=debug
			\| lang = text
			}}

			== Creating a driver disk ==

			=== Using DKMS ===
	You can use <code>dkms mkdriverdisk</code> to build a driver disk.		You can use <code>dkms mkdriverdisk</code> to build a driver disk.

	For example: <code>dkms mkdriverdisk -d redhat -m qla2x00</code>		For example: <code>dkms mkdriverdisk -d redhat -m qla2x00</code>

	== Manually ==		=== Manually creating a disk ===
	{{Highlight		{{Highlight
	\| code = ## Create a blank, 20MB image		\| code = ## Create a blank, 20MB image

Leo at 05:03, 6 January 2022

2022-01-06T05:03:17Z

← Older revision		Revision as of 05:03, 6 January 2022
Line 1:		Line 1:
	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.		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.

			If you have an older server that requires a driver that's been dropped, you can most likely find it from ElRepo. Their DUD repo (Eg. https://elrepo.org/linux/dud/el8/x86_64/) contains various driver disks in an ISO format which you can load with the installer. ISO disk drivers are loaded by passing in a <code>inst.dd=<path-or-url-to-iso></code> as part of the boot option when starting the installer.

	== DKMS ==		== DKMS ==
Line 26:		Line 28:

	* http://archive.download.redhat.com/pub/redhat/linux/8.0/it/doc/RH-DOCS/rhl-ig-x86-en-8.0/ch-driverdisk.html		* http://archive.download.redhat.com/pub/redhat/linux/8.0/it/doc/RH-DOCS/rhl-ig-x86-en-8.0/ch-driverdisk.html
	*		* [[How to boot Rocky Linux 8 on a Dell R710]]
	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]

Leo at 04:48, 4 January 2022

2022-01-04T04:48:12Z

← Older revision		Revision as of 04:48, 4 January 2022
Line 1:		Line 1:
	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:~~		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.

	== ~~Create Driver Disk~~ ==		== DKMS ==
	<~~syntaxhighlight lang~~=~~"bash" line enclose~~=~~"div">~~		You can use <code>dkms mkdriverdisk</code> to build a driver disk.
	# Create a blank, 20MB image
	dd if=/dev/zero of=driverdisk.img bs=1M count=20		For example: <code>dkms mkdriverdisk -d redhat -m qla2x00</code>

			== Manually ==
			{{Highlight
			\| code = ## 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

	# ~~Format~~ the ~~image with ext2~~		## mount it and copy the files over
	~~mkfs -t ext2~~ -q driverdisk.img		# mount -o loop driverdisk.img /mnt/driverdisk

	# ~~mount it and copy the files over~~		## copy drivers to /mnt/driverdisk, then run
	~~mount -o loop driverdisk.img /mnt/driverdisk~~		# umount /mnt/tmp
			\| lang = terminal
	# 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 {{code\|linux expert}} or {{code\|linux dd}} from the boot loader.
	~~</syntaxhighlight>~~

	~~Once you have the driver disk created, you will need to tell the installer to load it by booting into {{code\|linux expert}} or {{code\|linux dd}} from the boot loader.~~		== See also ==

			* http://archive.download.redhat.com/pub/redhat/linux/8.0/it/doc/RH-DOCS/rhl-ig-x86-en-8.0/ch-driverdisk.html
			*
	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]

Leo: Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

2019-09-01T06:21:04Z

Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

← Older revision		Revision as of 06:21, 1 September 2019
Line 18:		Line 18:
	Once you have the driver disk created, you will need to tell the installer to load it by booting into {{code\|linux expert}} or {{code\|linux dd}} 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}} or {{code\|linux dd}} from the boot loader.

	[[Category:Linux]]~~{{Navbox Linux}}~~		{{Navbox Linux}}[[Category:Linux]]

Leo: Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

2019-09-01T05:09:33Z

Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

← Older revision		Revision as of 05:09, 1 September 2019
Line 18:		Line 18:
	Once you have the driver disk created, you will need to tell the installer to load it by booting into {{code\|linux expert}} or {{code\|linux dd}} 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}} or {{code\|linux dd}} from the boot loader.

	[[Category:Linux]]		[[Category:Linux]]{{Navbox Linux}}

Leo: Text replacement - "" to "}}"

2017-02-24T19:14:06Z

Text replacement - "</code>" to "}}"

← Older revision		Revision as of 19:14, 24 February 2017
Line 16:		Line 16:
	</syntaxhighlight>		</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}} or {{code\|linux dd}} from the boot loader.

	[[Category:Linux]]		[[Category:Linux]]

Leo: Text replacement - "`" to "{{code|"`


2017-02-24T19:12:31Z
Text replacement - "<code>" to "{{code|"

				
				
				
				
				
				← Older revision
				Revision as of 19:12, 24 February 2017
				
Line 16:
Line 16:
</syntaxhighlight> </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]]

← Older revision		Revision as of 19:12, 24 February 2017
Line 16:		Line 16:
	</syntaxhighlight>		</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]]