Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!aardvark.ucs.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!news.clark.edu!spool.mu.edu!howland.reston.ans.net!xlink.net!fauern!faulrs!hugis!pizza.nbg.sub.org!mnbokaem Newsgroups: comp.os.386bsd.bugs Subject: Problems with WD8013 Clone under Net/FreeBSD Message-ID: <1993Oct20.033347.1124@pizza.nbg.sub.org> From: mnbokaem@pizza.nbg.sub.org (Martin Bokaemper) Date: Wed, 20 Oct 1993 03:33:47 GMT Keywords: Ethernet, ed, driver Lines: 51 I have problems with a WD8013EBT clone under FreeBSD and NetBSD. It works fine under PCNFS, Linux and also worked under 386bsd0.1. I'm sure that the hardware setup is correct - at least this setup works with the software mentioned above. But when I try to use it with the ed-driver from Net/FreeBSD I get 'failed to clear shared mem at fe0dxxxx - check configuration' most of the time. Sometimes the card is correctly initialized during kernel boot, but then after 'ifconfig' the collision-count in netstat goes up rapidly (without packets sent). When 'ping'ing to another host on the network packets seem to be sent (the LEDs are flashing) but receiving packets does not work - every incoming packet results in a message like: 'ed0: shared memory corrupt - invalid packet length 65348'. This happens both under FreeBSD and NetBSD on a 386/40 System. On a 486DX/40 that card ran with ed0 under FreeBSD (did not test NetBSD) and on my 386SX ed0 always brought that 'failed to clear shared mem...' message, even with the kernel that recognized the card on the 386DX System. On all these systems the hardware was properly configured (correct IRQ, good place for shmem, no shadowing in the shmem area etc.) and they all worked with other software (PCNFS tested on all of them, Linux on the SX, 386bsd on the 386DX and SX). Since the card worked under 386bsd I also tried to use the 'we'-driver. The card is always recognized correctly during bootup but then it is very similar to the ed-symptoms: The collision count goes up and when using ping the LEDs flash - but nothing happens. When ping'ing the NetBSD machine from remote these messages appear: 'we0 reject - bad length 2xxxx' (lengths around 26000) Some more info on the Hardware: 386SX/8MB, AMI BIOS, Hercules Mono Card 386DX/16MB, AMI BIOS, SVGA 486DX/8MB, Don't remember BIOS The ethernet adaptor is a 16Bit WD8013EBT Clone from OPTICOM(ET-2200), where IRQ and IOBASE are configured with jumpers, the shmem address is configured by software (the ed-driver seems to do that). There also is a DOS/OS2 jumper on the card which is not very well documented: 'JP1 is used to select this Ethernet adapter operation in DOS or OS2 operating system' (from the manual :-( Most configurations were tested in both settings of this jumper. If you have any idea how to fix this, please let me know. Thank you very much, Martin. --