From owner-freebsd-current Thu Oct 22 09:09:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15032 for freebsd-current-outgoing; Thu, 22 Oct 1998 09:09:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15024 for ; Thu, 22 Oct 1998 09:09:11 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA18487; Thu, 22 Oct 1998 09:08:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 22 Oct 1998 09:08:39 -0700 (PDT) From: Doug White To: steven cc: current@FreeBSD.ORG Subject: Re: 3.0-Current/3Com 509B ether problem In-Reply-To: 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 Wed, 21 Oct 1998, steven wrote: > but i have a problem that no posts seems to clearly identify or > fix. > > i've got a 3com 509b ISA ethernet card. > It worked fine with 2.2.6 2.2.7 and an early Sept 3.0 install. > I went to the last BETA and the bootup stopped seeing the card. > I went 3.0-current and same thing. > > dmesg shows.. > > fd0: 1.44MB 3.5in > ie0: unknown board_id: f000 > ie0 not found at 0x300 > ep0 not found at 0x300 > npx0 on motherboard > > before 3.0 it never detected anything on ie0 and ep0 was always what > i used for the card. > > I swapped the card into my Windows box and the card does appear to > work. Ideas? Um, disable the ethernet card drivers you're not using? Some ether card probes are destructive. Ican't say I've noticed the same thing on my systems with ie and ep both turned on, it sees no ie0 but the ep0 at IRQ 10 port 0x300 is detected properly. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message