From: Ion Badulescu <ionut@cs.columbia.edu>
To: Stig Brautaset <stigbrau@start.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: xircom nic itch (drops ip)
Date: Mon, 13 May 2002 11:24:10 -0400 [thread overview]
Message-ID: <200205131524.g4DFOAc30622@buggy.badula.org> (raw)
In-Reply-To: <20020512214217.GA19727@brautaset.org>
On Sun, 12 May 2002 22:42:18 +0100, Stig Brautaset <stigbrau@start.no> wrote:
> My pcmcia network card drops its ip from time to time. This happens
> frequently enough for it to be rather annoying, but not frequently to be
> really annoying. It seems to happen when there is no traffic through
> the link (based on the fact that I cannot ever remember it happening
> while I was on irc ;).
Are you using dhcp on that interface? If so, what happens to the dhcp
client daemon when the interface 'loses' the ip? Is it logging anything?
Is it dying?
If you're not using dhcp, I'm a little stumped..
> The card is a Xircom Cardbus 10/100 NIC (CBEM56G-100), and it use the
> kernel's xircom_cb module. I used to use the module in the pcmcia_cs
> package before, but I can't remember whether it was any better then (I
> don't think it was though).
You could try to use the xircom_tulip_cb module instead, and see if it
solves the problem. I don't think it will, but who knows.
Despite what Configure.help says, xircom_tulip_cb is actually better
than xircom_cb. The latter should only be used if xircom_tulip_cb
has problems -- I haven't heard of any recently, but I do want to hear
about them if they still exist.
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
next prev parent reply other threads:[~2002-05-13 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 21:42 Stig Brautaset
2002-05-13 15:24 ` Ion Badulescu [this message]
2002-05-15 20:25 ` Stig Brautaset
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=200205131524.g4DFOAc30622@buggy.badula.org \
--to=ionut@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=stigbrau@start.no \
/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®