From owner-freebsd-current Tue Nov 2 1:58:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8522F14F21 for ; Tue, 2 Nov 1999 01:58:45 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA29930; Tue, 2 Nov 1999 09:58:46 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 2 Nov 1999 09:58:46 +0000 (GMT) From: Doug Rabson To: Mark Hittinger Cc: freebsd-current@freebsd.org Subject: Re: ep0 3com etherlink III still unhappy In-Reply-To: <199911020037.SAA13823@freebsd.netcom.com.> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Nov 1999, Mark Hittinger wrote: > > ep0: <3Com EtherLink III (3c509-TPO)> at port 0x300-0x30f irq 10 on isa0 > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: Ethernet address ff:ff:ff:ff:ff:ff > ep1: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5 on isa0 > ep1: Ethernet address 00:a0:24:a1:9a:1e > > The card is actually 0x300, not 0x210. Disabling pnp isn't a work around > any longer. Does ep1 work (i.e. can you send and receive packets on ep1)? If so, you can probably change your kernel config to have just 'device ep0' which would allow the card to appear as ep0 again. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message