Bug 264321 - Won't Install on Asus M2R32-MVP
Summary: Won't Install on Asus M2R32-MVP
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 7
Hardware: x86_64
OS: All
medium
urgent
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-29 17:10 UTC by Errol Ehrhardt
Modified: 2008-06-05 13:31 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-06-05 13:31:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Errol Ehrhardt 2007-08-29 17:10:00 UTC
Description of problem:  Anaconda won't see hard drive under RAID configuration 
on an Asus M2R32-MVP with the AMD 580 chipset.


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


How reproducible:  It is extremly reproducable on any motherboard with an AMD 
580x chipset.  Fedora 7 won't recognize the RAID controller for the hard drives.


Steps to Reproduce:
1. Get a motherboard with an AMD 580x chipset
2. Try to install linux on the hard drive
3. 
  
Actual results:  No hard drives will be detected under Anaconda Setup.


Expected results:


Additional info:  Tried commands to get around drive detection, and no matter 
how I did it, no drives were able to be detected on my motherboard.

Comment 1 Bug Zapper 2008-05-14 14:09:27 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Andy Lindeberg 2008-06-03 20:44:15 UTC
Have you encountered this problem with Fedora 9?

Comment 3 Errol Ehrhardt 2008-06-04 19:43:39 UTC
No, I haven't.  I think what happened is that my motherboard (at the time) was 
newer than the OS was, which was causing issues.  Fedora 9 installs just fine.  
Thank you for your help.

Comment 4 Andy Lindeberg 2008-06-05 13:31:57 UTC
Our pleasure. Glad to know everything worked out for you.


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