Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 50659 - Dell PowerEdge 500SC IDE cable detect
Dell PowerEdge 500SC IDE cable detect
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2001-08-01 18:05 EDT by Matt Domsch
Modified: 2007-04-18 12:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-01 18:06:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
PowerEdge 500SC IDE cable autodetect (1.51 KB, patch)
2001-08-01 18:06 EDT, Matt Domsch
no flags Details | Diff

  None (edit)
Description Matt Domsch 2001-08-01 18:05:50 EDT
We've finally come to a solution regarding automatic detection of an 80-
pin IDE cable on the PE500SC CSB5 IDE controller.  The patch below 
implements it.  I've tested this with a test BIOS which implements this 
functionality (changes the PCI subsystem device ID as described below), 
with both 80-pin and 40-pin cables, and it works fine.  Based on 
controller type, and max UDMA mode set in BIOS setup, hdparm -i shows the 
maximum speed is properly selected in each case.

Current shipping BIOSs never set those top two bits, so the ide0=ata66 
override is necessary until a new BIOS is available.  The new BIOS is 
projected to be made publicly available in 6-8 weeks.  We're also ensuring 
that any Dell system with a CSB5 follows this same rule.

Patch attached was mailed to Andre Hedrick and Arjan on 8/1/01.
Comment 1 Matt Domsch 2001-08-01 18:06:46 EDT
Created attachment 25911 [details]
PowerEdge 500SC IDE cable autodetect
Comment 2 Arjan van de Ven 2001-08-02 11:54:56 EDT
Added for the next build

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