Bug 29714 - Wolverine Expert Mode Installation Problem
Summary: Wolverine Expert Mode Installation Problem
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Erik Troan
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-27 05:15 UTC by Need Real Name
Modified: 2007-04-18 16:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-02-27 16:47:19 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2001-02-27 05:15:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (Windows NT 5.0; U)


Failure to identify any scsi cd installation drives (even after booting from them) if expert mode is selected, but scsi subsystem is seen after the 
ide boot drive.  Full graphic auto mode with update finds it properly.  After using the F2 key to add the scsi controller (adaptec 2940UW), it 
continued to allow me to only choose a hard drive as the storage location of the iso images, even though it did now show one of the scsi hard 
drives as well as the original ide drive.  The scsi cdrom was not recognized even though it booted the installation disc, it would only recognize 
the ide hard drives as the source of the installation files.

Reproducible: Always
Steps to Reproduce:
1.Bootable SCSI CDROM drive boot the installation disk.  Select expert mode installation
2. Normal booting device is the ide0 primary drive.  Add a scsi controller with the F2 key
3. Additional (SCSI) drives now show up, but SCSI CDROMs do not (two of them and neither appears)
	

Actual Results:  SCSI CDROM(s) were not offered as the source of the installation disks even though scsi drives appeared after adding the 
scsi 
controller

Expected Results:  Allow selection of SCSI cdrom(s) as the source drive for the installation to continue from

No error....just could not proceed with installation or update

Comment 1 Michael Fulbright 2001-02-27 16:47:15 UTC
I think this issue is fixed, assigning to developer.

Comment 2 Erik Troan 2001-02-27 16:54:38 UTC
This should be fixed internally.


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