From: Jeff Garzik <jeff@garzik.org>
To: Phil Turmel <pturmel-kernel@turmel.org>
Cc: Phil Reynolds <phil-linux@tinsleyviaduct.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Marvell eSATA - 88SE6121 on Asus M3A79-T Deluxe - not in AHCI
Date: Wed, 12 May 2010 02:01:28 -0400 [thread overview]
Message-ID: <4BEA4438.4030608@garzik.org> (raw)
In-Reply-To: <4BEA0E54.4080208@turmel.org>
On 05/11/2010 10:11 PM, Phil Turmel wrote:
> Hi Jeff,
>
> On 05/11/2010 05:09 PM, Jeff Garzik wrote:
>> On 05/11/2010 02:28 PM, Phil Turmel wrote:
>>> On 05/11/2010 01:21 PM, Phil Reynolds wrote:
>>>> Quoting "Phil Turmel"<pturmel-kernel@turmel.org>:
>>>>
>>>>> 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.)
>>>>
>>>> Neither works for me unfortunately.
>>>>
>
> [snip /]
>
>> sata_mv is not related to this hardware.
>>
>> pata_marvell works with 6101/6121/6141/6145 PATA ports.
>>
>> ahci works with 6101/6121/6141/6145 SATA ports, with marvell_enable=1.
>>
>> Jeff
>
> I think you might have me (Phil T) confused with the original poster, Phil
> Reynolds [1].
No confusion. You suggested blacklisting sata_mv, and I note above that
sata_mv has nothing to do with the hardware in question.
Jeff
next prev parent reply other threads:[~2010-05-12 6:01 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
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 [this message]
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=4BEA4438.4030608@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=phil-linux@tinsleyviaduct.com \
--cc=pturmel-kernel@turmel.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.