Bug 65446 – driver disk not accessible after first try

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 65446 - driver disk not accessible after first try

Summary:	driver disk not accessible after first try

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	i386 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:	Mike McLean
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	67218 79579
	Show dependency tree / graph

Reported:	2002-05-24 05:01 EDT by borgia
Modified:	2007-03-26 23:53 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-01-22 08:40:15 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description borgia 2002-05-24 05:01:46 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (Windows NT 5.0; U)

Description of problem:
If, for any reason, you try to load the same driver from the driver disk twice, the installer says the disk is already in use and you have to reboot.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.start install with dd option
2.insert disk when required, select ne driver, forget to enter irq/io data
3.driver will not load, so go back, enter data and installer will fail because disk is in use(?)
	

Actual Results:  If you really need that driver, you have to restart the installation and not make any mistake in selecting the driver and its options.

Expected Results:  Correct loading of driver

Additional info:

Comment 1 Jeremy Katz 2002-12-11 17:53:46 EST

This seems to work in our current internal codebase

Comment 2 Michael Fulbright 2002-12-20 12:38:25 EST

Time tracking values updated

Comment 3 Jay Turner 2003-01-22 08:40:15 EST

No longer seeing this with the latest code bases.

Note You need to log in before you can comment on or make changes to this bug.