From: Dave Jones <davej@redhat.com>
To: "Wesley J. Landaker" <wjl@icecavern.net>
Cc: Matthew Wilcox <matthew@wil.cx>, Tejun Heo <htejun@gmail.com>,
linux-scsi@vger.kernel.org,
Carlos Pardo <Carlos.Pardo@siliconimage.com>
Subject: Re: Support for (new?) Silicon Image PCI SATA controller
Date: Sat, 11 Nov 2006 17:47:24 -0500 [thread overview]
Message-ID: <20061111224724.GA13292@redhat.com> (raw)
In-Reply-To: <200611091659.16002.wjl@icecavern.net>
On Thu, Nov 09, 2006 at 04:59:15PM -0700, Wesley J. Landaker wrote:
> > > SIMG says there's no such device and it's probably bad hardware
> > > (probably a 3512) with stuck bits in PCI ID. If you bought it, ask for
> > > replacement.
> > It could also be a problem with his motherboard. I'd try it in a
> > different slot (or in a different machine) before returning the card
> > as bad.
>
> Guys, thank you. Your suggestion about a stuck bit sounds reasonable, since I
> couldn't find any indication of any device IDs from SI that matched... that's
> why I originally assumed it was a new device (since the hardware is
> supposedly fairly recent).
>
> I will try this out in a different motherboard slot and if there's no luck
> there see if I can get this card replaced.
>
> Thank for the help, and hopefully I can get it working. =)
I've seen similar things from cards with dirty connectors.
A pencil eraser over the contacts made a similar problem I saw
with a tulip card disappear.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-11-11 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 1:03 Support for (new?) Silicon Image PCI SATA controller Wesley J. Landaker
2006-11-09 23:37 ` Tejun Heo
2006-11-09 23:40 ` Matthew Wilcox
2006-11-09 23:59 ` Wesley J. Landaker
2006-11-11 22:47 ` Dave Jones [this message]
2006-12-05 22:48 ` [SOLVED] " Wesley J. Landaker
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=20061111224724.GA13292@redhat.com \
--to=davej@redhat.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=htejun@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=wjl@icecavern.net \
/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