From: John Doty <jpd@yami.w-d.org>
To: rshawppc@yahoo.com
Cc: linuxppc-dev@lists.linuxppc.org, rshaw@linuxppc.org
Subject: Re: Blue & White & SCSI & Ultra 2 SCSI & Kernel > 2.2.10 -> No Disks
Date: Sat, 08 Apr 2000 21:37:27 -0400 [thread overview]
Message-ID: <38EFDEA8.3A3F9AD0@w-d.org> (raw)
In-Reply-To: 38EF891E.5D14C524@home.com
Robert Shaw wrote:
> John Doty wrote:
>
> > We have finally gotten partway to the bottom of this. Apparently, if the
> > 2930 controller is present the kernel cannot find the 2940 controller
> > (and the 2940 has the disks on it). With the 2930 pulled (I don't really
> > need it the way I'm currently using the system), SCSI works fine with
> > the newer kernels.
>
> Yes, I've found this issue with the latest kernels with someone else as
> well. Do any of the SCSI driver developers out there know what might be
> causing this? Apparently, when there are more than one Adaptec SCSI
> controllers (doesn't seem to matter which ones, but most notably a narrow
> controller and a wide controller combo), the SCSI driver freaks out and
> does not recognize either properly.
>
Actually, in my case the kernel *did* recognize the (narrow) 2930 when the
2940 was there. I even managed to install a working system on a 1G Jaz
cartridge. I just couldn't use my big fast disks. Your mileage may vary,,,
--
John Doty "You can't confuse me, that's my job."
Home: jpd@w-d.org
Work: jpd@space.mit.edu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-09 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-08 15:32 Blue & White & SCSI & Ultra 2 SCSI & Kernel > 2.2.10 -> No Disks John Doty
2000-04-08 19:31 ` Robert Shaw
2000-04-09 1:37 ` John Doty [this message]
2000-04-09 9:13 ` Blue & White & SCSI & Ultra 2 SCSI & Kernel > 2.2.10 -> No Disk s Michel Lanners
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=38EFDEA8.3A3F9AD0@w-d.org \
--to=jpd@yami.w-d.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rshaw@linuxppc.org \
--cc=rshawppc@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).