mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Evan Montgomery-Recht <evanrecht@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Cardbus conflicts...
Date: Fri, 27 Apr 2001 04:36:57 -0700 (PDT)	[thread overview]
Message-ID: <20010427113657.73542.qmail@web11105.mail.yahoo.com> (raw)

About 2 years ago, I bought a IBM 600E laptop with one
of the IBM branded Xircom CardBUS cards.  It took me
about a month (with the help of a lot of people with
simular machines) to figure out why the card would be
recognized, and even connect to the network, but could
never get a IP address from DHCP.  It turned out that
the sound card which is a one of the CS based chips. 
The fix that I found was that if I added the following
line to the /etc/pcmcia/config.opts The card would be
detected, and recognized, and get a IP address.

exclude ports 0x2f8-0x2ff

The unfortunate side effect is that I cannot seem to
get the sound card to work, even with OSS-commercial
which I had a old license for that expires soon from
when I bought a copy way back in I think 96' (what a
scary thought).

I realize that this this is a older machine, but this
is not unique, I've found over the years that every
machine I've owned has had a custom "profile" to get
all addin-cards to work.  So I leave with two
questions.

1. Does someone have a better fix for this problem
then I've been able to find?

2. It seems like there is a need to have like a
"vendor-profile" support that allows for these special
types of conflicts.  I havn't been able to find much
on this.  Is anyone aware of such a thing.

thanks,

evan

__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/

             reply	other threads:[~2001-04-27 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27 11:36 Evan Montgomery-Recht [this message]
2001-04-27 17:48 ` Jeff Garzik
2001-05-01  2:40 David Hinds

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=20010427113657.73542.qmail@web11105.mail.yahoo.com \
    --to=evanrecht@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=montge@mianetworks.net \
    /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®