Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!spool.mu.edu!sol.ctr.columbia.edu!ira.uka.de!smurf.sub.org!flatlin!bad From: bad@flatlin.ka.sub.org (Christoph Badura) Subject: Re: anyone using the etherlink II driver (i386/isa/if_ec.c) ? Organization: Guru Systems/Funware Department Date: Sun, 7 Mar 1993 20:44:45 GMT Message-ID: <C3JDMM.DDB@flatlin.ka.sub.org> References: <C3E945.4BI.1@cs.cmu.edu> <1993Mar6.000818.3216@news.unomaha.edu> <C3Gu9A.HH7.1@cs.cmu.edu> Lines: 19 In <C3Gu9A.HH7.1@cs.cmu.edu> cmaeda+@cs.cmu.edu (Christopher Maeda) writes: >The driver probes and attaches fine. >ifconfig works ok; another machine running tcpdump reports that the >card is sending the initial arp broadcast during ifconfig >when I run ping, the machine send arps no problem but doesn't see the >incoming arp replies >the card is getting receive interrupts but when I look at the piece of >memory that the driver thinks contains a packet, there is nothing >there that looks like a packet. Maybe you haven't configured that card's memory, interrupt and DMA channel to the values that 386BSD expects. I had similar problems a couple of months ago. -- Christoph Badura --- bad@flatlin.ka.sub.org Personally, I don't care whether someone is cool enough to quote Doug Gwyn--I only care whether Doug Gwyn is cool enough to quote. -- Larry Wall