From: "Brian Jackson" <brian-kernel-list@mdrx.com>
To: Justin Cormack <justin@street-vision.com>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: promise ide problem: missing disks
Date: Tue, 05 Nov 2002 18:00:52 -0600 [thread overview]
Message-ID: <20021106000052.21645.qmail@escalade.vistahp.com> (raw)
In-Reply-To: <1036539902.2291.48.camel@lotte>
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.
>
> As a followup, this does not occur with default Redhat 8.0 kernel, so it
> is a problem with the large changes in the driver since 2.4.18. Will try
> to work out exactly when it broke.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-11-05 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 19:49 Justin Cormack
2002-11-05 23:44 ` Justin Cormack
2002-11-06 0:00 ` Brian Jackson [this message]
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 ` promise ide problem: missing disks (RESOLVED) Justin Cormack
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=20021106000052.21645.qmail@escalade.vistahp.com \
--to=brian-kernel-list@mdrx.com \
--cc=justin@street-vision.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
all inboxes | Powered by JetHome®