From: Justin Cormack <justin@street-vision.com>
To: Brian Jackson <brian-kernel-list@mdrx.com>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: promise ide problem: missing disks (RESOLVED)
Date: 06 Nov 2002 15:25:41 +0000 [thread overview]
Message-ID: <1036596349.5076.5.camel@lotte> (raw)
In-Reply-To: <20021106000052.21645.qmail@escalade.vistahp.com>
Ok, the 0.30 Promise driver was ok (in RedHat 7.3 and 2.4.18) if it
supports the card. 0.32 is broken, this is in 2.4.19 and 20-pre. The
0.35 driver in -ac and 2.5 is fine too.
Given that, I think the bbest solution is if the driver updates in -ac
go to Marcello for 2.4.21-pre1... though it seems a pity to ship 2.4.20
with a driver that is broken.
On Wed, 2002-11-06 at 00:00, Brian Jackson wrote:
> I may be able to help you narrow it down a bit. I have used 2.4.19-vanilla
> and it worked fine(all drives showed up). When I tried
> fnk10(www.cipherfunk.org) the drive on the secondary channel doesn't show
> up. I don't know exactly what changes fnk10 has with regards to ide, but I
> know he has put a bunch of stuff from the 20-pre series in fnk10. Hope this
> helps.
>
> --Brian Jackson
>
> Justin Cormack writes:
>
> > On Tue, 2002-11-05 at 19:49, Justin Cormack wrote:
> >> I have a Promise Ultra133 IDE controller, and cannot get any drives to
> >> appear on the second channel under Linux. The controller says it finds
> >> the drive on the second channel on its bios screen, but Linux will not
> >> see it. This is with 2.4.20-pre9 and -rc1.
prev parent reply other threads:[~2002-11-06 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 19:49 promise ide problem: missing disks Justin Cormack
2002-11-05 23:44 ` Justin Cormack
2002-11-06 0:00 ` Brian Jackson
2002-11-06 0:46 ` Justin Cormack
2002-11-06 1:17 ` Justin Cormack
2002-11-06 1:37 ` Justin Cormack
2002-11-06 15:25 ` Justin Cormack [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=1036596349.5076.5.camel@lotte \
--to=justin@street-vision.com \
--cc=brian-kernel-list@mdrx.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.