From owner-freebsd-questions Tue Nov 7 21: 6:14 2000 Delivered-To: freebsd-questions@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id EC6D937B4C5 for ; Tue, 7 Nov 2000 21:06:12 -0800 (PST) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA27379; Wed, 8 Nov 2000 00:06:09 -0500 (EST) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA21915; Wed, 8 Nov 2000 00:06:08 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA21911; Wed, 8 Nov 2000 00:06:08 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Wed, 8 Nov 2000 00:06:08 -0500 (EST) From: Kenneth Wayne Culver To: Lee J Carmichael Cc: mac , freebsd-questions@FreeBSD.ORG Subject: Re: KNE100TX - Ethernetcard In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In that case it would not have said "de0" I did look at the code, it would > say "pci0" instead of "de0" so it at least got through the probe portion > of the code, it probably failed in attach, I guess I just used the wrong > word... chances are that if someone goes through the code it is probably > not too hard to make this chip work. > > PS, just in case you didn't see, I have the same card and same chip as this guy, and mine works fine (how do you think I'm accessing the network now?) chances are there is some sort of hardware misconfiguration, as I have run into his problem before and when I fiddled with bios (reset configuration data) it worked fine. Sorry if my previous mail seemed rude... but I KNOW this guy's card works because it works fine on my computer... under 4.2-BETA (4.x-STABLE). Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message