From: Stig Brautaset <stig@brautaset.org>
To: linux-kernel@vger.kernel.org
Subject: Re: xircom nic itch (drops ip)
Date: Wed, 15 May 2002 21:25:26 +0100 [thread overview]
Message-ID: <20020515202526.GA16671@brautaset.org> (raw)
In-Reply-To: <20020512214217.GA19727@brautaset.org> <200205131524.g4DFOAc30622@buggy.badula.org>
Hi Ion,
Thanks for the answer :)
* Ion Badulescu <ionut@cs.columbia.edu> spake thus:
> > My pcmcia network card drops its ip from time to time. This happens
[...]
> 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..
I am using dhcp from time to time, but the card drops its ip when it is
allocated statically as well :(
However, it *does* seem to drop its ip more frequently if I am using
dhcp, or between usage of dhcp and a reboot (I normally just use
suspend) so this might be the case. I will monitor this a bit closer...
> > 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.
Can't seem to load that module I'm afraid..
> 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.
Thank you very much for your help anyway.
Stig
--
brautaset.org
prev parent reply other threads:[~2002-05-15 20:25 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
2002-05-15 20:25 ` Stig Brautaset [this message]
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=20020515202526.GA16671@brautaset.org \
--to=stig@brautaset.org \
--cc=linux-kernel@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®