linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Craig Block <chblock3@yahoo.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Problems with nVidia nForce 520 Chipset
Date: Thu, 26 Jul 2007 17:26:56 +0900	[thread overview]
Message-ID: <46A85AD0.2070905@gmail.com> (raw)
In-Reply-To: <815613.39679.qm@web58103.mail.re3.yahoo.com>

Craig Block wrote:
> Hello,
> 
> I'm having a problem getting Linux to handle the SATA drives and controllers on
> a new computer with an ASUS M2N-X motherboard.  This is a socket AM2 board and
> has an nVidia nForce 520 chipset.  It has three controller mode settings in the
> BIOS, SATA, AHCI, and RAID.
> 
> I built and tried a couple kernels, one with SATA_NV plus BLK_DEV_IDECD and the
> other with SATA_AHCI plus PATA_AMD.
> 
> With the controllers in SATA mode, the kernel built with SATA_NV doesn't see
> the SATA controllers at all.  The PATA CD drive links to hda and works
> properly.  I tried the same kernel on an nForce 4 system and everything works
> right.
>  
> With the controllers in AHCI mode, the kernel built with SATA_AHCI, hangs when
> probing the SATA controllers.  It literally takes about a minute to get through
> each one.  It never does link any drives to them.  The PATA CD drive links to
> sr0 and seems to work okay.
> 
> I've had MS Windows working without issue in either mode, using the canned IDE
> driver in SATA mode and the nVidia AHCI driver in AHCI mode.
> 
> Output from "dmesg" and "lspci -n -vvv" commands is attached.

Does 'noapic' kernel parameter help?

-- 
tejun

  reply	other threads:[~2007-07-26  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26  5:25 Problems with nVidia nForce 520 Chipset Craig Block
2007-07-26  8:26 ` Tejun Heo [this message]
2007-07-26 17:07   ` Craig Block
2007-07-27  4:14     ` Tejun Heo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46A85AD0.2070905@gmail.com \
    --to=htejun@gmail.com \
    --cc=chblock3@yahoo.com \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).