Red Hat Bugzilla – Bug 299901
We need SB800 SATA Controller supported in RHEL4.7
Last modified: 2013-07-02 22:34:28 EDT
This is for requirements phase to RHEL4.7
Hardware is due to RH by November 13, 2007 for inclusion in RHEL 4.7.
AMD: Does Red Hat have this hardware in house? What's the status of this request?
We do not have the hardware, but we still can support it just according to
SB800 SATA controller spec. We can verify it once we get the HW.
In fact, We need not provide any more SB800 related SATA/IDE patches
because we find that most of the SATA PCI device IDs are same as those
of SB700, except:
0x4394 SATA in AHCI mode with HyperFlash-OneNand support
0x4395 SATA in AHCI mode with HyperFlash-PCIE support
There is one patch submitted by Henry, please check:
And RHEL5.2 has added this feature from kernel 2.6.18-58.el5,
please check BZ# 252961
Shane, have you tested the in 2.6.18-58.el5 kernel or newer from
http://people.redhat.com/dzickus/el5 from the addition posted in bug 252961?
Our QA are testing 2.6.18-81 on SB700, because SB800 is not available.
We will test on SB800 when we get it.
Created attachment 295343 [details]
SB700/800 SATA controller support
Patch has been QA with brew build and submitted to RHML. Please set the
remaining BZ ACKs.
Committed in 68.23 . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
added to RHEL4.7 Driver Updates:
AMD ATI SB800 SATA controller is now supported.
please advise if any further revisions are required. thanks!
the RHEL4.7 release notes deadline is on June 17, 2008 (Tuesday). they will
undergo a final proofread before being dropped to translation, at which point no
further additions or revisions will be entertained.
a mockup of the RHEL4.7 release notes can be viewed here:
please use the aforementioned link to verify if your bugzilla is already in the
release notes (if it needs to be). each item in the release notes contains a
link to its original bug; as such, you can search through the release notes by
~ Attention: ~ Feedback requested regarding this **High Priority** bug.
A fix for this issue should be included in the latest packages contained in
RHEL4.7-Snapshot1--available now on partners.redhat.com.
After you (Red Hat Partner) have verified that this issue has been addressed,
submit a comment describing the passing results of your test in appropriate
detail, along with which snapshot and package version tested. The bugzilla will
be updated by Red Hat Quality Engineering for you when this information has been
If you believe this issue has not properly fixed or you are unable to verify the
issue for any reason, please add a comment describing the most recent issues you
are experiencing, along with which snapshot and package version tested.
If you believe the bug has not been fixed, change the status of the bug to ASSIGNED.
If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and bugzilla will be updated for you.
If you need assistance accessing ftp://partners.redhat.com, please contact your
Red Hat QE Partner Management
Correction: This bug is **Low Priority**. Sorry.
Verified with RHEL4.7 Beta (kernel 2.6.9-70.EL)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Partners, I would like to thank you all for your participation in assuring the
quality of this RHEL 4.7 Update Release. My hat's off to you all. Thanks.