From: Jeff Garzik <jgarzik@pobox.com>
To: Josh Litherland <josh@emperorlinux.com>
Cc: linux-kernel@vger.kernel.org, research@emperorlinux.com
Subject: Re: SATA ICH6M problems on Sharp M4000
Date: Mon, 21 Nov 2005 18:41:19 -0500 [thread overview]
Message-ID: <20051121234119.GD24565@havoc.gtf.org> (raw)
In-Reply-To: <43824A6F.6070407@emperorlinux.com>
On Mon, Nov 21, 2005 at 05:30:07PM -0500, Josh Litherland wrote:
> Trying to get this laptop operational; it has SATA for the hard disc and
> PATA for the optical drive. The hard drive is wired to the secondary
> IDE interface, the optical to the primary. As it stands, driving the
> whole system with the PATA (piix) driver works, but performance for the
> hard disc is (predictably) extremely poor.
Expected behavior for combined mode, which only allows DMA for SATA.
Disabling legacy mode in BIOS should fix the performance problem, by
allowing IDE driver to fully drive PATA (including DMA), and libata to
fully drive SATA.
> With ata_piix driving the
> hard drive, performance is great, but the optical device is never
> enumerated.
Expected behavior, since the default for module option atapi_enabled
is zero (disabled).
> When the piix driver tries to load, the following occurs:
>
> ide0: I/O resource 0x1F0-0x1F7 not free.
> ide0: ports already in use, skipping probe
> ide1: I/O resource 0x170-0x177 not free.
> ide1: ports already in use, skipping probe
>
> We have tried to resolve this through a wide variety of kernel command
> line options. Tried every combination we could think of of ide0=0x1f0,
> ide1=0x170, ide0=noprobe, ide1=noprobe, acpi=off, noapic, lapic,
> pci=routeirq. Tried shaking up module load order and using ide-generic
> instead of piix.
So far everything seems to be expected behavior.
> ahci won't bind to the device; throws error -12.
Expected behavior, since your hardware doesn't seem to support AHCI.
> Some information about this system including dmesg and lspci:
>
> http://downloads.emperorlinux.com/research/lkml/sharp_m4000/
In the future, 'lspci -n' and 'lspci -nvvv' is more useful.
Jeff
next prev parent reply other threads:[~2005-11-21 23:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 22:30 Josh Litherland
2005-11-21 22:39 ` Randy.Dunlap
2005-11-21 23:13 ` Marek W
2005-11-21 23:41 ` Jeff Garzik [this message]
2005-11-22 16:20 ` Josh Litherland
2005-11-22 16:28 ` Jeff Garzik
[not found] <200511221013.04798.marekw1977>
2005-12-02 19:33 ` Sergei Organov
2005-12-05 17:22 ` Sergey Vlasov
2005-12-05 18:15 ` Sergei Organov
2005-12-05 18:20 ` Jeff Garzik
2005-12-05 18:48 ` Sergei Organov
2005-12-06 10:31 ` Sergey Vlasov
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=20051121234119.GD24565@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=josh@emperorlinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=research@emperorlinux.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
all inboxes | Powered by JetHome®