From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: (was Re: [RFC] IDE 80-core cable detect - chipset-specific code to over-ride eighty_ninty_three())
Date: Thu, 12 Feb 2004 20:41:53 +0000 (UTC) [thread overview]
Message-ID: <c0goeh$hs4$1@news.cistron.nl> (raw)
In-Reply-To: 200402122106.41947.bzolnier@elka.pw.edu.pl
In article <200402122106.41947.bzolnier@elka.pw.edu.pl>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:
>
>Hi,
>
>word93 of drive identify is:
>
>0x603b for IC35L120AVV207-0
>0x3469 for QUANTUM FIREBALLlct20 30
>
>and eighty_ninty_three() checks for bit 0x4000, so...
>
>Willy, it seems you are hitting some other problem.
>Have you already tried booting with "ide0=ata66"?
That reminds me, there is currenly no way to boot with
ide0=ata33, right ?
I have a tyan motherboard with a serverworks chipset, and the
(2.5" system-) disk is connected with a 40 pins cable. However
the serverworks chipset doesn't detect this, and tries to run
it in UDMA<lots> mode. That results in lots of nasty messages
before it falls back to UDMA33 mode.
Could you put a way to force it into UDMA33 (UDMA2) mode on the
wishlist, please ?
Mike.
next prev parent reply other threads:[~2004-02-12 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 20:06 (was Re: [RFC] IDE 80-core cable detect - chipset-specific code to over-ride eighty_ninty_three()) Bartlomiej Zolnierkiewicz
2004-02-12 20:41 ` Miquel van Smoorenburg [this message]
2004-02-13 17:33 ` Bartlomiej Zolnierkiewicz
2004-02-13 8:37 ` Willy Tarreau
2004-02-13 17:23 ` Bartlomiej Zolnierkiewicz
2004-02-13 17:44 ` Erik Mouw
2004-02-13 18:30 ` Bartlomiej Zolnierkiewicz
[not found] <1ovjW-1Ol-7@gated-at.bofh.it>
2004-02-18 7:26 ` Athol Mullen
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='c0goeh$hs4$1@news.cistron.nl' \
--to=miquels@cistron.nl \
--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.