From: Vojtech Pavlik <vojtech@suse.cz>
To: Manuel Ignacio Monge Garcia <ignaciomonge@navegalia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ATA 100 & VIA and linux-2.4.3ac8
Date: Thu, 19 Apr 2001 08:42:50 +0200 [thread overview]
Message-ID: <20010419084250.A689@suse.cz> (raw)
In-Reply-To: <01041820505300.01783@localhost.localdomain> <3ADDE820.2050103@texoma.net> <01041822215300.01341@localhost.localdomain>
In-Reply-To: <01041822215300.01341@localhost.localdomain>; from ignaciomonge@navegalia.com on Wed, Apr 18, 2001 at 10:21:53PM -0400
On Wed, Apr 18, 2001 at 10:21:53PM -0400, Manuel Ignacio Monge Garcia wrote:
> El Mié 18 Abr 2001 15:16, escribiste:
> > I don't know about other possible problems with the kernel, but you must
> > use an 80 wire IDE cable for UDMA66/100 to work.
> >
> > > -----------------------Primary IDE-------Secondary IDE------
> > > Cable Type: 40w 40w
>
>
> Strange thing. With previous version of kernel (2.4.1 I think), I
> haven't got this problem. May be a bios detection problem?
>
> Extract from /usr/src/linux/drivers/ide/via82cxxx..c:
>
> *
> * PIO 0-5, MWDMA 0-2, SWDMA 0-2 and UDMA 0-5
> *
> * (this includes UDMA33, 66 and 100) modes. UDMA66 and higher modes are
> * autoenabled only in case the BIOS has detected a 80 wire cable. To ignore
> * the BIOS data and assume the cable is present, use 'ide0=ata66' or
> * 'ide1=ata66' on the kernel command line.
> *
>
> I've tried with ide0=ata100, but this options doesn't work.
Try ide0=ata66 instead. The option should have been named ide0=80wire,
but, well, "ata66" was chosen as the name, because that was it at the
time.
--
Vojtech Pavlik
SuSE Labs
prev parent reply other threads:[~2001-04-19 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 0:50 ATA 100 & VIA and linux-2.4.3ac8 Manuel Ignacio Monge Garcia
2001-04-18 19:16 ` Moses Mcknight
2001-04-19 0:46 ` Joseph Carter
2001-04-19 2:21 ` Manuel Ignacio Monge Garcia
2001-04-19 6:42 ` Vojtech Pavlik [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=20010419084250.A689@suse.cz \
--to=vojtech@suse.cz \
--cc=ignaciomonge@navegalia.com \
--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 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.