From: Marko Kreen <marko@l-t.ee>
To: Earle Nietzel <nietzel@yahoo.com>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>, linux-kernel@vger.kernel.org
Subject: Re: Minor 2.4.3 Adaptec Driver Problems
Date: Sun, 1 Apr 2001 14:31:38 +0200 [thread overview]
Message-ID: <20010401143138.A22774@l-t.ee> (raw)
In-Reply-To: <200103312307.f2VN73s55018@aslan.scsiguy.com> <000901c0bae7$ab340a20$1401a8c0@nietzel>
In-Reply-To: <000901c0bae7$ab340a20$1401a8c0@nietzel>; from nietzel@yahoo.com on Sun, Apr 01, 2001 at 01:09:30PM -0700
On Sun, Apr 01, 2001 at 01:09:30PM -0700, Earle Nietzel wrote:
> > Umm. This isn't an aic7xxx driver problem at all. The SCSI layer
> > determines the order of bus attachment *amongst* the various
> > SCSI HBA (or SCSI HBA like) drivers in the system. In this case,
> > it has decided to probe your IDE devices as SCSI devices first.
> > Why it does this I don't really know (link order perhaps???). One
> > way around this would be to put your IDE driver into an initial
> > ram disk and compile the aic7xxx driver directly into the kernel.
> It really wouldn't make a big deal but I consider my cdroms and zip drives
> to be removable devices and if I ever decided to remove my zip my scsi ids
> will change. Removing a harddrive is not the same as removing a zip!
>
> Are there other people with the same problem?
Yes, I have ide-scsi compiled in for cd-writer, so 2.4.3 did not
boot on my machine (that is, could not mount anything).
Not nice.
--
marko
next prev parent reply other threads:[~2001-04-01 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200103312307.f2VN73s55018@aslan.scsiguy.com>
2001-04-01 20:09 ` Earle Nietzel
2001-04-01 12:31 ` Marko Kreen [this message]
2001-03-31 20:42 Earle Nietzel
2001-03-31 15:08 ` Justin T. Gibbs
2001-04-01 4:21 ` Earle Nietzel
2001-04-02 18:02 ` Giuliano Pochini
2001-04-03 20:59 ` Ben Ford
2001-04-03 21:50 ` Alan Cox
2001-04-03 22:01 ` Justin T. Gibbs
2001-04-05 4:26 ` Earle Nietzel
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=20010401143138.A22774@l-t.ee \
--to=marko@l-t.ee \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nietzel@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
all inboxes | Powered by JetHome®