From: Matthias Hentges <mailinglisten@hentges.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Serial ATA (SATA) for Linux status report
Date: 15 Jan 2004 03:39:06 +0100 [thread overview]
Message-ID: <1074134345.6094.11.camel@mhcln02> (raw)
In-Reply-To: <4005D9E7.2070203@bigfoot.com>
Hello all,
Am Don, 2004-01-15 um 01.08 schrieb Erik Steffl:
> Raphael Rigo wrote:
> ...<ICH5problems snipped>...
> > One possible workaround it to enable both PATA and SATA drivers (using
> > libata) and pass "ide2=noprobe ide3=noprobe" to kernel at boot.
> > More detailled answer can be found here :
> > http://www.hentges.net/howtos/p4p800_deluxe.html
>
> I have pretty much the same setup he recommends in UPDATE except of
> the "ide2=noprobe ide3=noprobe" kernel boot options, not sure why would
> that be needed but my system (interl D865PERL, cd burner, ide and sata
> disks) works OK without it.
The "Update" section describes the setup which - after *weeks* of
frustrating trail-and-error - managed to get things going.
Notice the unusual BIOS setting (Enhanced Mode - SATA only) which did
the trick and enabled PATA *and* SATA.
You may want to try that if you haven't already.
The ideN=noprobe my indeed not be necessary . It was recommended by Jeff
Garzik to me at some time IIRC. Kernel 2.6 does *not* need the noprobe
stuff AFAICT.
FWIW my P4P800 Deluxe is working flawlessly with 4 P-ATA devices (2 HDs,
a ZIP100 and a 48x Burner) and one SATA 160Gb HD.
I'm using 2.4.22-bk36 with matching libata patch so i'd think that any
kernel 2.4.23+ will do the trick.
HTH and GL
--
Matthias Hentges
Cologne / Germany
[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4 -> No files, no URL's
My OS: Debian Woody. Geek by Nature, Linux by Choice
next prev parent reply other threads:[~2004-01-15 2:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 20:44 Serial ATA (SATA) for Linux status report Jeff Garzik
2003-12-03 23:27 ` Andre Tomt
2003-12-03 23:36 ` Jeff Garzik
2003-12-04 0:21 ` Miquel van Smoorenburg
2003-12-04 0:59 ` Samuel Flory
2003-12-04 1:02 ` Andre Tomt
2003-12-04 13:38 ` Justin Cormack
2003-12-04 14:54 ` Jeff Garzik
2003-12-04 8:17 ` Arnaud Launay
2003-12-04 15:01 ` Jeff Garzik
2003-12-05 17:42 ` Mickael Marchand
2003-12-05 17:47 ` Jeff Garzik
2003-12-05 18:07 ` [PATCH] Silicon image 3114 SATA link (really basic support) Mickael Marchand
2003-12-09 18:22 ` Aron Rubin
2003-12-09 18:54 ` Mickael Marchand
2003-12-09 20:14 ` Bartlomiej Zolnierkiewicz
2003-12-12 0:07 ` Mickael Marchand
2003-12-05 18:16 ` Serial ATA (SATA) for Linux status report Kevin P. Fleming
2003-12-05 18:29 ` Jeff Garzik
2003-12-09 9:39 ` Petr Sebor
2003-12-09 19:59 ` J. Ryan Earl
2004-01-14 22:18 ` Greg Stark
2004-01-14 22:56 ` Erik Andersen
2004-01-14 23:31 ` James Courtier-Dutton
2004-01-15 0:41 ` Jeff Garzik
2004-01-15 2:38 ` Erik Andersen
2004-01-18 12:34 ` Martin Schlemmer
2004-01-14 23:32 ` Raphael Rigo
2004-01-15 0:08 ` Erik Steffl
2004-01-15 2:39 ` Matthias Hentges [this message]
2004-01-15 21:08 ` Greg Stark
2004-01-14 23:12 ` Erik Steffl
2004-01-18 13:32 ` Witold Krecicki
2004-01-18 18:00 ` Jeff Garzik
2004-01-18 20:33 ` Craig Bradney
2003-12-04 18:03 Jon Burgess
2004-08-24 19:49 Jeff Garzik
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=1074134345.6094.11.camel@mhcln02 \
--to=mailinglisten@hentges.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;
as well as URLs for NNTP newsgroup(s).