From: Jeff Garzik <jeff@garzik.org>
To: Alan <alan@clueserver.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question on siig sata 3 controller
Date: Thu, 10 Jun 2010 04:53:51 -0400 [thread overview]
Message-ID: <4C10A81F.50801@garzik.org> (raw)
In-Reply-To: <34979.10.6.6.23.1276144792.squirrel@10.6.6.2>
On 06/10/2010 12:39 AM, Alan wrote:
> Does anyone know the status of the SIIG DP SATA 6Gb/s 2S1P PCIe (Part
> number: SC-SA0E12-S1)?
>
> I am encountering problems writing a large quantity through this
> controller and I want to see if there is a way to fix this. The pci ids
> do not appear to be referenced in the kernel.
>
> Are any of the siig sata controllers supported? Is there some issue with
> them supporting Linux that I am not aware of?
>
> Here is the lspci data:
>
> 05:00.0 SATA controller: Device 1b4b:9123 (rev 11) (prog-if 01 [AHCI 1.0])
> Subsystem: Device 1b4b:9123
> Flags: bus master, fast devsel, latency 0, IRQ 30
> I/O ports at dc00 [size=8]
> I/O ports at d880 [size=4]
> I/O ports at d800 [size=8]
> I/O ports at d480 [size=4]
> I/O ports at d400 [size=16]
> Memory at f9fff800 (32-bit, non-prefetchable) [size=2K]
> Expansion ROM at f9fe0000 [disabled] [size=64K]
> Capabilities:<access denied>
> Kernel driver in use: ahci
What issues are you seeing?
The 'ahci' driver is aware of this controller...
Jeff
next prev parent reply other threads:[~2010-06-10 8:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 4:39 Question on siig sata 3 controller Alan
2010-06-10 8:53 ` Jeff Garzik [this message]
2010-06-10 16:28 ` alan
2010-06-11 2:08 ` Alan
2010-06-15 6:57 ` Rogier Wolff
2010-06-15 10:07 ` Alan Cox
2010-06-15 14:53 ` Rogier Wolff
2010-06-15 15:01 ` Alan Cox
2010-06-15 17:25 ` Alan
2010-08-10 13:48 ` Rogier Wolff
2010-08-12 0:27 ` alan
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=4C10A81F.50801@garzik.org \
--to=jeff@garzik.org \
--cc=alan@clueserver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.