From: Andreas Dilger <adilger@turbolinux.com>
To: Charles Wilkins <chas@pcscs.com>
Cc: Andrzej Krzysztofowicz <ankry@pg.gda.pl>,
linux-raid@vger.kernel.org,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: max number of ide controllers?
Date: Fri, 22 Dec 2000 11:24:13 -0700 (MST) [thread overview]
Message-ID: <200012221824.eBMIOEN27293@webber.adilger.net> (raw)
In-Reply-To: <01e401c06c12$44aeee60$2b6e60cf@pcscs.com> "from Charles Wilkins at Dec 22, 2000 07:25:28 am"
Charles Wilkins writes:
> I added this to lilo.conf:
> append="ide2=0x168,10" and ran lilo
>
> This is what I got:
> ide_setup: ide2=0x168,10
> .
> .
> ide2: ports already in use, skipping probe
>
> The promise controllers then setup as ide3 and ide4, but the SB32 still does
> not report.
> Any ideas?
Maybe set the new dual controller to be IDE 2,3 and have the SB32 as IDE4.
Also, you can check /proc/ioports and /proc/interrupts to see if there
actually are conflicts with the port ranges or interrupts of your card.
I'm guessing not, because it worked before, but you never know.
IDE cards actually have 2 port ranges, so it may be that with the new card
you are getting conflicts. My system shows:
0170-0177 : ide1
01e8-01ef : ide2
01f0-01f7 : ide0
0376-0376 : ide1
03ee-03ee : ide2
03f6-03f6 : ide0
The second ide2 port is in the same place as ttyS2 (com3)...
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-22 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200012221057.LAA18410@sunrise.pg.gda.pl>
2000-12-22 12:25 ` Charles Wilkins
2000-12-22 18:24 ` Andreas Dilger [this message]
2000-12-22 0:34 Charles Wilkins
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=200012221824.eBMIOEN27293@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=ankry@pg.gda.pl \
--cc=chas@pcscs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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®