From owner-freebsd-questions  Wed Jul  9 07:43:12 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA17671
          for questions-outgoing; Wed, 9 Jul 1997 07:43:12 -0700 (PDT)
Received: from sparrow.sanasys.com (root@sparrow.sanasys.com [206.101.242.50])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17666
          for <freebsd-questions@FreeBSD.ORG>; Wed, 9 Jul 1997 07:43:03 -0700 (PDT)
Received: from nschuler (dialup06.sanasys.com [206.101.242.86])
	by sparrow.sanasys.com (8.8.5/8.8.5) with SMTP id JAA18911;
	Wed, 9 Jul 1997 09:42:45 -0500 (CDT)
Message-Id: <2.2.32.19970709144254.00acd920@sparrow.sanasys.com>
X-Sender: nschuler@sparrow.sanasys.com
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 09 Jul 1997 09:42:54 -0500
To: Swee-Chuan Khoo <sckhoo@asiapac.net>
From: Nathan Schuler <nschuler@sanasys.com>
Subject: Re: 3C509 screwed up? or is it me?
Cc: freebsd-questions@FreeBSD.ORG
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> In my case, Cable Type configuration (BNC, UTP, AUI) is one major problem.
>> To be sure, do not enable autodetecting cable type in EPROM but enable 
>> your own cable type.
>
>PnP is disabled, and the cards are actually 3c509tpo. only utp
>there.

Try to specify link argument 1 instead of 0 on the NIC.  This was required
on my BSDI machine with a 3C509B-TPO.


Nathan Schuler <nschuler@sanasys.com>
UNIX Netwoking Solutions / Systems Administrator
Sana Systems Inc.
Clinton, IA 52732
(319) 242-5770