From: Jeff Garzik <jgarzik@pobox.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: libata problems on Promise SX4000 controller
Date: Thu, 01 Apr 2004 13:16:23 -0500 [thread overview]
Message-ID: <406C5C77.6020300@pobox.com> (raw)
In-Reply-To: <406BE23F.3000802@gmx.net>
Carl-Daniel Hailfinger wrote:
> Hi,
>
> I had problems getting my Promise SX4000 controller to run with libata.
> First, I noticed libata refused to drive it (no associated PCI id). After
> patching that (including the handler for the right chipset), a
> "modprobe sata_promise" hung for about 15 minutes while initializing the
> ECC RAM. It then recognized the one attached harddisk, but disk access was
> not really possible (I gave up after waiting for half an hour or so).
> Let me apologize for testing an older version of libata. At the time I had
> the problems, it was the newest available version. I enabled debugging and
> post the logs here in the hope that they might help supporting this
> controller in the future.
>
> A note about the controller itself: It has 4 Parallel ATA ports and no
> Serial ATA ports. The controller sports the usual SoftRAID from Promise
> (0,1,0+1 and 5). The RAID5 seems to be a new feature. I do not care about
> the RAID (well, I do, I'm writing a dm configuration helper for it right
> now), but I would like to access the drive.
Well, the main problem is that you are trying to drive a PATA controller
with a SATA driver :)
If you wanted to list this as a feature request on
http://bugzilla.kernel.org/ that might be reasonable...
I have no idea how different the PATA controllers are from the SATA one
I tested. Although it does detect your device, I don't know what
differences exist...
Jeff
prev parent reply other threads:[~2004-04-01 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 9:34 libata problems on Promise SX4000 controller Carl-Daniel Hailfinger
2004-04-01 18:16 ` Jeff Garzik [this message]
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=406C5C77.6020300@pobox.com \
--to=jgarzik@pobox.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox