Bug 231557 - Installaation impossible on NFORCE2 chipsets.
Installaation impossible on NFORCE2 chipsets.
Status: CLOSED DUPLICATE of bug 225026
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity urgent
: ---
: ---
Assigned To: Anaconda Maintenance Team
Depends On:
  Show dependency treegraph
Reported: 2007-03-08 17:50 EST by Jean Francois Martinez
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-23 14:21:54 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 Jean Francois Martinez 2007-03-08 17:50:06 EST
Description of problem:
IDE Hardisks not detected on card with Nforce2 chipset

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

How reproducible:

Steps to Reproduce:
1.  You can't install from CD otherwise Anaconda will simpley not load and you
will see nothing
2.  Install from network or from an USB hard disk
3.  Proceed until partitionning.  Disks are not visible.  Neither are CD readers
Actual results:
Impossible to install

Expected results:

Additional info:
FC7test1 already caused problems with NFORCE2 chipsets but you could tell to use
the AMD driver aand it worked.  In FC7test2 it is much worse, it doesn't work at
all.  Also I have noticed that the sata_nv module is loaded but it doesn't seem
to support nforce2
Comment 1 Jean Francois Martinez 2007-03-09 15:47:49 EST
Of course it doesn't work with sata_nv, this is for sata and my disks are pata.
 The driver to use is pata_amd (nforce and nforce2 chipsets are derived from
achipset made by amd) but anaconda sees nvidia and without thinking it twice
assigns the only driver it knows about.
Comment 2 Jeremy Katz 2007-03-23 14:21:54 EDT

*** This bug has been marked as a duplicate of 225026 ***

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