Bug 76911 - Installer fails to load modules when prameters passed
Installer fails to load modules when prameters passed
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-10-29 05:29 EST by Bryn Jones
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-24 14:16:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bryn Jones 2002-10-29 05:29:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913

Description of problem:
when trying to pass io= parameters to the ne module, the installer trys to mount
the already mounted driver disk, and fails with mountpoint in use. RH8.0 release
bootnet and drvnet.

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

How reproducible:

Steps to Reproduce:
1.boot from bootnet floppy
2.NFS install
3.F2 - load additional drivers
4.insert drvnet floppy
5.select NE1000/NE2000 (ne.o) driver, check additional parameters box
6.specifiy a value for io= and irq=
7.the installer will ask you to insert the driver floppy, hit return

Actual Results:  Installer fails to mount the already mounted drvnet floppy with
the message:

Failed to mount driver disk: Device or resource busy.

Expected Results:  load and fail to insert module due to incorrect io= setting
;), after a couple of goes, get the right io= parameter setting and continue

Additional info:
Comment 1 Jeremy Katz 2002-12-16 12:18:00 EST
This works in our current codebase
Comment 2 Michael Fulbright 2002-12-20 12:38:25 EST
Time tracking values updated
Comment 3 Jeremy Katz 2006-04-24 14:16:32 EDT
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed).  If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.

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