Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 13190

Summary: Driver Disk not readable
Product: [Retired] Red Hat Linux Reporter: Neil Darlow <neil>
Component: anacondaAssignee: Michael Fulbright <msf>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: hdegoede
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-06-30 21:20:17 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 Neil Darlow 2000-06-28 17:11:12 UTC 
Created Driver Disk from Beta2 images/drivers.img using dd.

At the stage of the install where the Driver disk is requested the
following is output to VC4:

  <4>VFS: Can't find a valid MSDOS filesystem on dev 02:00.

This results in the list of available drivers being displayed empty.
Comment 1 Hans de Goede 2000-06-30 21:20:15 UTC 
This is a normal message, the driver disk can be either dos or ext2. When you
take bootnet.img on a system where the network card is not detected for example,
and then press F2, insert the driverdisk and press enter, the driver disk is
recognised and the list of networkdrivers does become larger.

Trying to use a driver from the disk fails one step later btw, but the disk is
recognised, the failure is an other bug which is already in bugzilla.

I guess your talking about trying todo an install form a propietary interface
cdrom, that is an unrelated bug in the driver disk itself which is also already
in bugzilla.