public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Promise PDC20276 broken in 2.5 and 2.4.21-preX, but not 2.4.20
Date: Mon, 27 Jan 2003 16:43:20 -0800	[thread overview]
Message-ID: <3E35D228.10905@tupshin.com> (raw)

There have been two prior reports of a problem with the promise PDC20276 
chipset (on-board piece-o-crap pseudo raid on some KT333 [and others?] 
motherboards). Both of them reported the same problem, i.e. load the 
pdc202xx_new driver and get "neither IDE port enabled (BIOS)" message, 
and therefore an inability to use drives on that controller using either 
the direct ide interface or the pdcraid module. This problem was 
reported on both kernels 2.4.21-pre1 and 2.5.46, and was reported to 
work correctly with 2.4.20 and 2.5.34.

Neither person got a response (at least on the list), so I can't tell if 
anybody is aware of this.

I'm guessing that the 2.5 problem was introduced here 
http://linux.bkbits.net:8080/linux-2.5/diffs/drivers/ide/pci/pdc202xx_new.c@1.4

and the corresponding 2.4 backport
http://linux.bkbits.net:8080/linux-2.4/cset@1.757.33.36?nav=index.html|tags|ChangeSet@..1.811

I've run into the same problem with 2.4.21-pre3-ac4, and can also verify 
that it works fine with 2.4.20.

Any takers on why  the 20276 isn't getting initialized correctly 
anymore? Presumably this is not a problem with most of the other promise 
chipsets or it would be much more heavily noticed by now.

-Tupshin




                 reply	other threads:[~2003-01-28  0:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3E35D228.10905@tupshin.com \
    --to=tupshin@tupshin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox