Bug 6476

Summary: Where is the driver disk???
Product: [Retired] Red Hat Linux Reporter: banasw01
Component: installerAssignee: Jay Turner <jturner>
Status: CLOSED RAWHIDE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-05-09 16:56:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description banasw01 1999-10-28 19:24:48 UTC
Well, so I decided to install RH 6.1 on an old unused 386.
I had to boot from the floppy image in the /images/
directory. I made a boot disk using rawrite on a dos
machine. It booted up and went into the install, but gave
me an error "The floppy disk you inserted is not a valid
driver disk for this relese of RedHat Linux. Humm... In
the /images/ directory on the cd-rom I only see boot.img,
bootnet.img and pcmcia.img, no "driver disk image" or
anything like it. Maybe it is just somewhere on the disk or
maybe I should know something here, or be a mind reader,
but I don't see it. A readme file in the /images/ directory
would be nice.
Thanks
Wojciech Banas

Comment 1 adrian.lawrence 1999-10-30 11:01:59 UTC
Just hit "Cancel", and no driver disc is required. Yes the prompt is
misleading and confusing, and it ought to be improved. Not speaking
for RH, of course. Just solving (?) your problem.

Comment 2 Jay Turner 2000-02-08 19:22:59 UTC
This has been added to a list of features for future releases.

Comment 3 Jay Turner 2000-02-14 17:08:59 UTC
*** Bug 8118 has been marked as a duplicate of this bug. ***

Comment 4 Jay Turner 2000-02-22 14:54:59 UTC
*** Bug 6579 has been marked as a duplicate of this bug. ***

Comment 5 Michael Fulbright 2000-04-14 16:26:59 UTC
*** Bug 8306 has been marked as a duplicate of this bug. ***

Comment 6 Michael Fulbright 2000-04-24 19:19:59 UTC
*** Bug 7789 has been marked as a duplicate of this bug. ***

Comment 7 Erik Troan 2000-05-09 16:56:59 UTC
Fixed for next release -- sorry it took so long.