linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: infernix <infernix@infernix.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: PATA port not detected when using AHCI on Intel 82801GB/GR/GH
Date: Fri, 22 Jan 2010 00:31:45 -0500	[thread overview]
Message-ID: <4B593841.2030900@garzik.org> (raw)
In-Reply-To: <4B591D61.8030003@infernix.net>

On 01/21/2010 10:37 PM, infernix wrote:
> Hi,
>
> I've got an Intel SS4200(-ESW) here which according to lspci has an
> Intel 82801GB/GR/GH controller. It has 4 sata ports + 1 pata port in
> which i have a 4GB IDE flash DOM. It also has a SIL 3132 for 2 external
> eSATA ports. There are no disks connected to any of the SATA ports.
>
> The bios allows for two modes:
>
> - Compatible mode, which makes the kernel use ata_piix. lspci shows that
> the chipset uses pci id 8086:27c0.
>
> - Enhanced mode (with sub options IDE, RAID or AHCI - using AHCI here),
> which of course makes the kernel use ahci. lspci shows the the chipset
> now uses pci id 8086:27c1.
>
> In compatible mode, the bios can be configured to make the pata
> controller the first and the sata controller the second controller under
> ata_piix. This works and I can boot off the IDE in the PATA DOM without
> issues. The DOM works fine under ata_piix as /dev/sda.
>
> The problem is with the Enhanced mode with the sub mode set to AHCI (or
> IDE for that matter, it didn't change anything). In Enhanced AHCI mode,
> the SATA ports are detected just fine, but the PATA port is not
> detected. As I'm using an IDE DOM as root device, I can't boot in AHCI
> mode.
>
> What's weird though is that if I enable the old IDE PIIX driver, the
> PATA port does get detected and the DOM shows up as /dev/hda. But
> performance is abysmal, and since this is now deprecated we should try
> to get the PATA port working while in Enhanced AHCI mode.
>
> Running in compatible mode is not an option because this allows me to
> chose PATA for controller 0 and SATA for controller 1, but as a
> consequence i lose 2 sata ports as can be seen in the dmesg output. Or I
> could set it to full SATA but then the PATA port is rendered useless.

What PCI device is the PATA port?  Does the pata_marvell driver enable it?

Can you provide full lspci?

	Jeff



  parent reply	other threads:[~2010-01-22  5:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22  3:37 PATA port not detected when using AHCI on Intel 82801GB/GR/GH infernix
2010-01-22  5:01 ` Robert Hancock
2010-01-22 12:57   ` infernix
2010-01-23  1:23     ` Robert Hancock
2010-01-23  2:29       ` infernix
2010-01-23  7:18         ` Robert Hancock
2010-01-23 13:14           ` infernix
2010-01-23 10:14         ` Alan Cox
2010-01-23 13:08           ` infernix
2010-01-23 13:38             ` Alan Cox
2010-01-23 14:13               ` infernix
2010-01-23 14:30                 ` infernix
2010-02-12 23:30               ` infernix
2010-02-13  0:04                 ` Alan Cox
2010-02-13  0:21                   ` infernix
2010-01-22  5:31 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-05  2:17 Joe Ceklosky
2010-02-06  1:43 ` Robert Hancock

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=4B593841.2030900@garzik.org \
    --to=jeff@garzik.org \
    --cc=infernix@infernix.net \
    --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).