From: Phil Turmel <pturmel-kernel@turmel.org>
To: Phil Reynolds <phil-linux@tinsleyviaduct.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Marvell eSATA - 88SE6121 on Asus M3A79-T Deluxe - not in AHCI
Date: Tue, 11 May 2010 10:08:02 -0400 [thread overview]
Message-ID: <4BE964C2.1010702@turmel.org> (raw)
In-Reply-To: <20100509151358.84896yzx8vt059gm@topdeck.tinsleyviaduct.com>
Hi Phil,
It seems no one noticed your question. I've CC'd linux-scsi, in case the
experts have additional/better advice.
On 05/09/2010 10:13 AM, Phil Reynolds wrote:
> I have recently had cause to start using the eSATA port on my
> motherboard, an Asus M3A79-T Deluxe, but have found that it is not in
> AHCI mode and therefore not hotplug capable. There are no settings for
> the Marvell 88SE6121 controller available, other than simply whether it
> is enabled or not.
>
> I gather from reading elsewhere that the kernel can put this controller
> into AHCI - I found a patch but found it was already present in the
> kernel in Debian lenny's backports. It is their version 2.6.32-bpo.3 -
> not entirely sure which exact source version this is built from.
> However, this patch does not work on this motherboard - either that or I
> have to make it active somehow, and the method of doing so is not obvious.
[snip /]
I have a similar chipset in my office server: 88SE6145. If yours can run
in AHCI mode, you just need "ahci.marvell_enable=1" on your kernel command
line, or "options ahci marvell_enable=1" in your modprobe.conf. (I have
ahci built-in, and no initramfs, so I put the option in my grub.conf.)
My Marvell chipset has both SATA and PATA ports... the PATA ports are
non-functional when the ahci driver runs the chipset. Your mileage may
vary.
HTH,
Phil Turmel
next prev parent reply other threads:[~2010-05-11 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 14:13 Marvell eSATA - 88SE6121 on Asus M3A79-T Deluxe - not in AHCI Phil Reynolds
2010-05-11 14:08 ` Phil Turmel [this message]
2010-05-11 16:53 ` Phil Reynolds
2010-05-11 17:21 ` Phil Reynolds
2010-05-11 18:28 ` Phil Turmel
2010-05-11 21:09 ` Jeff Garzik
2010-05-12 2:11 ` Phil Turmel
2010-05-12 6:01 ` Jeff Garzik
2010-05-12 4:59 ` Phil Reynolds
2010-05-11 19:14 ` John Stoffel
2010-05-15 11:18 ` Phil Reynolds
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=4BE964C2.1010702@turmel.org \
--to=pturmel-kernel@turmel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=phil-linux@tinsleyviaduct.com \
/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