From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org
Subject: Re: Unknown SATA PIIX PCI device ID 0x29b6
Date: Fri, 29 Feb 2008 00:33:56 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0802290010320.10498@axis700.grange> (raw)
In-Reply-To: <20080228225603.2764bfd1@core>
On Thu, 28 Feb 2008, Alan Cox wrote:
> On Thu, 28 Feb 2008 23:37:36 +0100 (CET)
> Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
>
> > Hi
> >
> > just found out that the eSATA connector on my Intel DQ35JO motherboard
> > doesn't work... because it is connected to the controller with product ID
> > 29b6... And this ID is not yet handled by the driver. Can I have a patch,
> > please?:-) I think the correct entry would be
>
> If the device is in AHCI mode it should match the ahci class entry - is
> the device in AHCI mode or PIIX mode ?
Indeed! It was in "IDE" mode, and 2 out of the 3 chips were handled by the
piix driver (btw, why did Intel put 3 different SATA controllers on one
board?). I switched it to AHCI mode (the third possibility is RAID) and
indeed a kernel with (only) ahci driver managed to bring them up!
Although, the eSATA link was "slow to respond":
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: softreset failed (device not ready)
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: softreset failed (device not ready)
ata4: port is slow to respond, please be patient (Status 0x80)
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-7: WDC WD1600BB-00RDA0, 20.00K20, max UDMA/100
ata4.00: 312581808 sectors, multi 16: LBA48
ata4.00: applying bridge limits
ata4.00: configured for UDMA/100
but then it did manage it. Is such a delay normal?
One more question, what do UDMA numbers mean in SATA context? The internal
SATA disk is "ata1.00: configured for UDMA/133", but should be SATA-2.
Thanks
Guennadi
---
Guennadi Liakhovetski
next prev parent reply other threads:[~2008-02-28 23:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 22:37 Unknown SATA PIIX PCI device ID 0x29b6 Guennadi Liakhovetski
2008-02-28 22:56 ` Alan Cox
2008-02-28 23:33 ` Guennadi Liakhovetski [this message]
2008-03-06 8:39 ` Tejun Heo
2008-03-06 11:57 ` Guennadi Liakhovetski
2008-03-06 18:02 ` Gaston, Jason D
2008-03-06 18:05 ` Jeff Garzik
2008-03-06 18:40 ` Guennadi Liakhovetski
2008-04-02 23:49 ` Gaston, Jason D
2008-04-03 0:44 ` Tejun Heo
2008-04-03 15:16 ` Gaston, Jason D
2008-04-03 16:03 ` Tejun Heo
2008-04-19 1:02 ` Gaston, Jason D
2008-04-23 6:37 ` Tejun Heo
2008-04-03 16:04 ` Jeff Garzik
2008-04-03 18:01 ` Gaston, Jason D
2008-03-07 4:51 ` Tejun Heo
2008-03-08 22:47 ` Guennadi Liakhovetski
2008-03-09 5:14 ` Tejun Heo
2008-03-09 21:24 ` Guennadi Liakhovetski
2008-03-10 0:50 ` Tejun Heo
2008-03-10 7:22 ` Guennadi Liakhovetski
2008-03-10 13:05 ` Tejun Heo
2008-03-11 10:11 ` Guennadi Liakhovetski
2008-03-11 10:35 ` Tejun Heo
2008-03-11 11:13 ` Guennadi Liakhovetski
2008-03-11 11:37 ` Tejun Heo
2008-02-29 0:23 ` Felix Miata
2008-02-29 3:50 ` Gaston, Jason D
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=Pine.LNX.4.64.0802290010320.10498@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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