From owner-freebsd-questions Wed Sep 15 19:35:52 1999 Delivered-To: freebsd-questions@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 4343B14F12 for ; Wed, 15 Sep 1999 19:35:51 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id UAA22768 for ; Wed, 15 Sep 1999 20:35:46 -0600 (MDT) Message-Id: <4.2.0.58.19990915202601.048d88f0@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 15 Sep 1999 20:34:30 -0600 To: questions@freebsd.org From: Brett Glass Subject: Intel EtherExpress Pro/10+ not working Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have here a machine with an EtherExpress Pro/100+ (PCI) and an EtherExpress Pro/10+ (ISA). The former probes correctly and works just fine; the latter is not detected by the ex driver (which I *believe* is the correct driver) in today's 3.3-RC. I tried using Intel's configuration utility (under DOS) to turn off Plug 'n Play and to nail down the board's I/O port (300h) and IRQ (5) at locations where there are no conflicts. It detected the card, and the card passes the built-in test suite with flying colors. I then cut all extraneous drivers out of the kernel and put I/O port 300h and IRQ 5 explicitly into the config file. But a kernel thus compiled still doesn't recognize the card. Any ideas regarding what might be wrong? --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message