From: Mark Valiukas <mark.valiukas@vu.edu.au>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] OT: 3c590C, 3c509B-C repeated carrier loss with e-tech
Date: Fri, 9 Aug 2002 08:57:19 +0000 [thread overview]
Message-ID: <3D535706.8BAD56A2@vu.edu.au> (raw)
In-Reply-To: <200208071320.g77DKJV24081@zamenhof.cs.utwente.nl>
Axel Belinfante wrote:
> Any ideas, anyone? (I suspect some sort of auto-negotation failing?)
>
> 3com card details:
> 3c590C (pci, combo) 03-0046-000 rev A
> 3c509B-C (isa, combo) assy 03-0021-002 rev A
I never leave these on auto-negotiate at home. I always select a
media type. I've had problems with the 509b's detecting coax, and
with them detecting the network when connected to some oddball
gear (a hub of dubious provenance that I can't remember the brand
of right now)
Haven't had a problem since forcing the settings with the appropriate
3Com configuration utilities.
next prev parent reply other threads:[~2002-08-09 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 13:20 [9fans] OT: 3c590C, 3c509B-C repeated carrier loss with e-tech wireless router Axel Belinfante
2002-08-09 8:57 ` Mark Valiukas [this message]
2002-08-09 14:29 ` [9fans] OT: 3c590C, 3c509B-C repeated carrier loss with e-tech Axel Belinfante
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=3D535706.8BAD56A2@vu.edu.au \
--to=mark.valiukas@vu.edu.au \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).