From owner-freebsd-current Tue May 5 00:24:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11662 for freebsd-current-outgoing; Tue, 5 May 1998 00:24:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from yard-sale.village.org (ys2.village.org [204.144.255.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA11657 for ; Tue, 5 May 1998 00:24:56 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony.village.org [10.0.0.6] by yard-sale.village.org with esmtp (Exim 1.82 #1) id 0yWc5x-0001fx-00; Tue, 5 May 1998 01:24:57 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id BAA02027; Tue, 5 May 1998 01:24:23 -0600 (MDT) Message-Id: <199805050724.BAA02027@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: ISA Intel EtherExpress PRO/10+ ISA LAN Adapter Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 04 May 1998 15:09:04 EDT." References: Date: Tue, 05 May 1998 01:24:23 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : It just worked for me. (I've got a Pro/10 which uses the same : drivers/setup disk as the 10+) OK. I managed to get it to probe. I wound up disabling all the other drivers that were at 0x300, and it found it fine. I don't know which one of them caused the probe problem, but strongly suspect it is an ordering problem. Does that sound plausable? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message