From owner-freebsd-questions Sun Oct 19 14:17:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA02463 for questions-outgoing; Sun, 19 Oct 1997 14:17:21 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA02455 for ; Sun, 19 Oct 1997 14:17:17 -0700 (PDT) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.8.7/8.8.6) id RAA26772; Sun, 19 Oct 1997 17:17:10 -0400 (EDT) Date: Sun, 19 Oct 1997 17:17:10 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199710192117.RAA26772@istari.home.net> To: paradox@pegasus.rutgers.edu, freebsd-questions@FreeBSD.ORG Subject: Re: 3c509 ethernet adapter driver??? In-Reply-To: Mail from 'Red Barchetta ' dated: Thu, 16 Oct 1997 14:29:21 -0400 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Red Barchetta > Subject: 3c509 ethernet adapter driver??? > > For the past two days, I have been trying to install various versions of > the 2.2.5-BETAs from 22releng.freebsd.org. I need to do a network-based > install, but my network card is not being detected on bootup. I have a > 3com 3c509 adapter (with all 3 connector types), which a search of the list > archives reveals has been a problem in the past. I have tried everything I > can find in the archives, including checking my card's settings with the > 3c5x9cfg.exe program, powering down completely before booting from the > install disk, disabling all other devices that are probed at I/O address > 0x300, assuring that PnP mode is turned off, manually setting the > parameters shown in the boot utility to match those of my card, etc. > > In all cases, I get the following boot messages: > > 16 3x509 board(s) on ISA found at 0x200 0x200 0x200 ... (16 instances of > 0x200) > ep0 not found at 0x300 The "fix" for this problem appears to be to change ELINK_ID_PORT to 0x110 in /usr/src/sys/i386/isa/elink.h. I've submitted a bug report (kern/4559) about this problem [on 16 Sept 97] but haven't heard anything about it yet. -SR