From owner-freebsd-hackers Tue Feb 20 21:38:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA08102 for hackers-outgoing; Tue, 20 Feb 1996 21:38:32 -0800 (PST) Received: from baygull.rtd.com (baygull.rtd.com [198.102.68.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA08097 for ; Tue, 20 Feb 1996 21:38:30 -0800 (PST) Received: (from news@localhost) by baygull.rtd.com (8.6.9/8.6.9.1) id WAA14967; Tue, 20 Feb 1996 22:38:16 -0700 To: hackers@freebsd.org Path: freefall.freebsd.org!owner-freebsd-hackers From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: rtd.freebsd.hackers Subject: Re: 3Com Etherlink II/16 device timeouts Date: Wed, 21 Feb 1996 01:17:15 +0100 (MET) Lines: 22 Message-ID: <199602210017.BAA17712@uriah.heep.sax.de> NNTP-Posting-Host: seagull.rtd.com Sender: owner-hackers@freebsd.org Precedence: bulk As Jordan K. Hubbard wrote: > > > I'm getting the following error with my 3Com card: > > > > ed0: device timeout > > Wrong device.. :-) > > You want to configure the ep0 device for this card. Nope. 3Com has a confusing naming policy, but the ``Etherlink II'' is a 3c503 actually, even though it's one of the later cards with a 16-bit bus in this case. The ``Etherlink III'' is the 3c509. Perhaps the wrong network interface (AUI/BNC)? You can select the AUI interface with the ``-link2'' option to ifconfig if i'm not mistaken. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)