Return to BSD News archive
Path: sserve!euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!news.uoregon.edu!news.rediris.es!ordago.uc3m.es!news From: jgb@ordago.uc3m.es (Jesus M. Gonzalez Barahona) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Ether card not working with NetBSD-1.0/i386 Date: 03 Aug 1995 08:34:08 GMT Organization: GSYC, Univ. Carlos III Madrid, Spain. Lines: 33 Distribution: world Message-ID: <JGB.95Aug3093408@hola.uc3m.es> NNTP-Posting-Host: hola.uc3m.es Hi! I've bought a new machine: 486 DX4/100, 16MB, PCI bus with hard disk controller in it, #9 graphics card. NetBSD works there like a charm, except for the Ethernet card. I've tried 2c503 and 3c509, which where both working in other NetBSD systems. But they doesn't in the new one. With 3c503 I get, as soon as I try to send a packet to the card: ed1: device timeout (when using int 2) ed0: host down (when using int 5, obviously when pinging a live and conected host). With 3c509, I get the "host down" message. First message (timeout), seems to be a watchdog that triggers when it's waiting too long for an interrupt. So I suspect there are other device interfering int 2 (thougth I don't know whcih could be, NetBSD says nothing about that when booting). Second message (just host down) is a mistery for me. In this case, "arp -a" gives me no ether number. Ligths on the card seem to be pretty well, anyway. Does anybody know what's the matter? Has anybody seen something like that? Has PCI something to do with all this? O.S. is NetBSD/i386-1.0 Thanks in advance, Jesus.