Bug 76882

Summary: (SCSI) Use EDID to make the boot scsi controller the first one
Product: [Retired] Red Hat Linux Reporter: Need Real Name <atems>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-30 15:40:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Need Real Name 2002-10-28 18:07:00 UTC
Description of Problem: On a Dell PowerEdge server with an onboard Adaptec SCSI
adapter and a Symbios add-on SCSI adapter, the Symbios is identified as the
primary and the Adaptec as the secondary, both during installation and
afterward. This causes a disk on the external bus, from which the system cannot
be made to boot, to be assigned as /dev/sda, and the boot loader is installed
there.

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


How Reproducible: On this system, 100%. However I realise that this is highly
dependent on hardware configuration.


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Alan Cox 2003-06-08 19:28:17 UTC
This is dependant on the order the modules are loaded. The boot volume
identification can be done by EDID and that facility is in various development
kernels.

Turning this into an RFE


Comment 2 Bugzilla owner 2004-09-30 15:40:08 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/