Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in2.uu.net!newsfeed.internetmci.com!sgigate.sgi.com!enews.sgi.com!decwrl!pa.dec.com!nntpd.lkg.dec.com!usenet
From: matt@lkg.dec.com (Matt Thomas)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: COMPEX ENET32 (Dec21041) PROBLEMS
Date: 29 Feb 1996 16:40:09 GMT
Organization: Digital Equipment Corporation
Lines: 41
Sender: thomas@netrix.lkg.dec.com (Matt Thomas)
Message-ID: <4h4kt9$q27@nntpd.lkg.dec.com>
References: <4gqmrd$3e4@sandmann.prz.tu-berlin.de>
NNTP-Posting-Host: netrix.lkg.dec.com
X-Newsreader: knews 0.9.3
In article <4gqmrd$3e4@sandmann.prz.tu-berlin.de>,
wolf@prz.tu-berlin.de (Thomas Wolfram) writes:
>Hi,
>
>I've FreeBSD 2.1.0 RELEASE running on a ASUS TP4XE board with
>a P90.
>Recently I installed a Compex ENET32 PCI ethernet card. It's
>the new version of the card which uses the newer Digital 21041
>chip instead of the previous used 20140 chip.
>The problem is that the card is normally detected but I cannot
>ping to anywhere when I boot directly into FreeBSD after power-on.
>When I boot into DOS before so that a NDIS driver gets installed
>and then Ctrl-Alt-Del and boot into FreeBSD it works.
>It seems that the short installation of the NDIS driver initializes
>some more register on the card or whatever which isn't done by the
>FreeBSD driver.
I've stepped through the DOSODI driver (and looked through the
Linux driver) and it does nothing that my driver doesn't except
that the DOSODI driver is using the PCI BIOS while my driver is
using the FreeBSD PCI support.
The Compex board works fine with a ASUS TP4P55XE but fails in
a DECpc XL 466.
>BTW, Linux 1.2.13 with the Digital de4x5 driver doesn't have
>this problem. It's only FreeBSD. (But I prefer FreeBSD...)
Someone will correct if I'm wrong; Linux uses the PCI BIOS while
FreeBSD, NetBSD, BSD/OS, etal don't. This seems to be the
significant difference. Why it is significant is beyond me.
The actual problem is that the Compex board is not generating
an interrupt when it should be. I've been looking at this for
over a week and am getting extremely frustrated.
--
Matt Thomas Internet: matt@3am-software.com
3am Software Foundry WWW URL: <pending>
Westford, MA Disclaimer: Digital disavows all knowledge
of this message