Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 103796 - Intel S875WP1-LX SATA 150 TX4 PDC20319 does it work?
Intel S875WP1-LX SATA 150 TX4 PDC20319 does it work?
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-09-04 21:42 EDT by chris piechowicz
Modified: 2007-04-18 12:57 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 11:41:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description chris piechowicz 2003-09-04 21:42:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
Intel has only certified their drivers for the PDC20319 SATA 150 TX4 raid 
controller on the S875WP1-LX motherboard.  Compatibility list for RedHat 9 is 
incomplete.  I need to know (before paying more than $200 for the software) if 
RedHat 9 Professional version supports this built-in controller to install and 

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

How reproducible:
Didn't try

Additional info:
Comment 1 chris piechowicz 2003-09-04 21:50:15 EDT
..sorry...intel certified the hardware for RedHat 8 only.
Comment 2 Bugzilla owner 2004-09-30 11:41:30 EDT
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

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/

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