From owner-freebsd-current Wed Sep 29 10:20:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com. (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with SMTP id 0A277159A1 for ; Wed, 29 Sep 1999 10:18:52 -0700 (PDT) (envelope-from bugs@freebsd.netcom.com) Received: by freebsd.netcom.com. (SMI-8.6/SMI-SVR4) id MAA13361; Wed, 29 Sep 1999 12:18:48 -0500 From: bugs@freebsd.netcom.com (Mark Hittinger) Message-Id: <199909291718.MAA13361@freebsd.netcom.com.> Subject: Re: ep0 etherlink III breakage To: freebsd-current@freebsd.org Date: Wed, 29 Sep 1999 12:18:47 -0500 (CDT) X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Mark Hittinger wrote: >> Hey per request I'm reporting some ep0 breakage in today's -current. I have >> an etherlink III 3c509B and the probing appears correct. >> Sequence of events boot -s >> # ifconfig ep0 inet 192.168.18.200 >> (PC hangs) >> More later... > From: Russell Cattelan > Was there ever a conclusion as to how to get around this problem? One suggestion was to comment out the pnp0 isa line in your config file, i.e. controller isa0 #controller pnp0 # PnP support for ISA controller eisa0 ** It would really be nice if you could disable pnp0 in the boot -c dialog ** (At least I can't see how to do that :-) ). Then config, make depend, and build the kernel. This does work but it doesn't help debug our PnP code, and I have seen several other messages relating to problems in our PnP code over the past couple of days. When I have time I've been looking in the PnP code trying to find the bug - it doesn't look like an easy find to me. Later Mark Hittinger Mindspring/Netcom/Dallas bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message