Date: Thu, 22 Feb 1996 13:46:18 +0100 From: root <root@spase.nl> To: hackers@freebsd.org Message-ID: <199602221246.NAA11123@mercurius.spase.nl>
next in thread | raw e-mail | index | archive | help
>From freefall.freebsd.org!owner-freebsd-hackers Wed Feb 21 10:27:27 1996 remote from sun4nl
Received: from ra.dkuug.dk by sun4nl.NL.net with SMTP
id AA26072 (5.65b/CWI-3.3); Wed, 21 Feb 1996 10:27:27 +0100
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [192.216.222.4]) by ra.dkuug.dk (8.6.12/8.6.12) with ESMTP id JAA05054; Wed, 21 Feb 1996 09:55:07 +0100
Received: from localhost (daemon@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA07742
Tue, 20 Feb 1996 21:33:30 -0800 (PST)
Received: (from root@localhost)
by freefall.freebsd.org (8.7.3/8.7.3) id VAA07716
for hackers-outgoing; Tue, 20 Feb 1996 21:33:27 -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 VAA07702
for <hackers@freebsd.org>; Tue, 20 Feb 1996 21:33:23 -0800 (PST)
Received: (from news@localhost) by baygull.rtd.com (8.6.9/8.6.9.1) id WAA14935; Tue, 20 Feb 1996 22:33:10 -0700
To: hackers@freebsd.org
Path: freefall.freebsd.org!owner-freebsd-hackers
From: tomppa@fidata.fi (Tomi Vainio)
Newsgroups: rtd.freebsd.hackers
Subject: Re: 3Com Etherlink II/16 device timeouts
Date: Wed, 21 Feb 1996 03:30:12 +0200 (EET)
Lines: 25
Message-Id: <199602210130.DAA05886@zeta.fidata.fi>
Nntp-Posting-Host: seagull.rtd.com
Sender: owner-hackers@freebsd.org
Precedence: bulk
Andreas Schulz writes:
>
> > > 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.
>
> No, he says Etherlink II/16 not Etherlink III. The ep0 driver
> is for the Etherlink III ( 3COM 509 and 579) cards. The Etherlink II
> is the 3COM 3C503 and the ed0 driver is correct for that.
> I suspect that the card jumpers and settings disagree with the values
> given in FreeBSD.
> Also some other ethernet driver may incorrectly hit that card. Boot
> with a -c flag at the boot prompt and disable all other cards that
> also use the 0x300 address and you don't have in the system. I assume
> that the card is default configured to address 0x300 for the I/O port.
>
I think that Etherlink II/16 is known as 3c507 so you should use
ie-driver with it. I have this card and I can check what driver I'm
using with it.
Tomppa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602221246.NAA11123>