linux-kernel - Re: Marvell eSATA - 88SE6121 on Asus M3A79-T Deluxe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100512055935.707919p7r441z54n@topdeck.tinsleyviaduct.com>
Date:	Wed, 12 May 2010 05:59:35 +0100
From:	"Phil Reynolds" <phil-linux@...sleyviaduct.com>
To:	"Phil Turmel" <pturmel-kernel@...mel.org>
Cc:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: Marvell eSATA - 88SE6121 on Asus M3A79-T Deluxe - not in AHCI

Quoting "Phil Turmel" <pturmel-kernel@...mel.org>:

> Hmmm.  If you post your dmesg, lspci, and config, I'll be happy to compare
> to my setup.  It might be something as simple as the Marvell driver loading
> first and claiming the device.

They are attached - and I think you are right about the cause.

> The Marvell driver never gets a chance to claim my device, as it is  
> disabled in
> my kernel config.  If you are using modules, you might want to  
> blacklist "sata_mv".

Tried that - no change.

> If you are using modules from an initramfs, you might need to update your
> initramfs, too.

That is possible but I am not very familiar with modifying this.

-- 
Phil Reynolds
email: phil-linux@...sleyviaduct.com
Not subscribed to lkml - please CC replies to me

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


View attachment "dmesg.noesata" of type "text/plain" (60846 bytes)

View attachment "lspci.noesata" of type "text/plain" (26782 bytes)

View attachment "config-2.6.32-bpo.3-amd64" of type "text/plain" (105203 bytes)