From owner-freebsd-questions Sun Jan 19 22:19:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA13804 for questions-outgoing; Sun, 19 Jan 1997 22:19:57 -0800 (PST) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA13797 for ; Sun, 19 Jan 1997 22:19:55 -0800 (PST) Received: from palrel1.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA297731184; Sun, 19 Jan 1997 22:19:44 -0800 Received: from fakir.india.hp.com (fakir.india.hp.com [15.10.40.3]) by palrel1.hp.com with ESMTP (8.7.5/8.7.3) id WAA27095; Sun, 19 Jan 1997 22:19:24 -0800 (PST) Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.20/15.5+ECS 3.3) id AA171312959; Mon, 20 Jan 1997 11:49:19 +0500 Message-Id: <199701200649.AA171312959@fakir.india.hp.com> To: "malarraj malarraj" Cc: questions@FreeBSD.ORG Subject: Re: Problem in connecting a machine in network In-Reply-To: Your message of "20 Jan 1997 05:05:13 GMT." <19970120050513.17150.qmail@hotmail.com> Date: Mon, 20 Jan 1997 11:49:18 +0500 From: A JOSEPH KOSHY Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>> ""malarraj malarraj"" writes > "ed0 at 0x300-0x31f irq 5 on isa > ed0:address 00:80:29:67:43:ec type NE2000 (16 bit) > ifconfig: ioctl (SIOCGIFFLAGS): no such interface > ifconfig: ioctl (SIOCGIFFLAGS): no such interface Check your /etc/sysconfig to see which interface is trying to be ifconfig'ed? It should be "ed0" judging from your message above. > If we execute > "ifconfig ed0 202.229.220.229 netmask 255.255.255.0" > (because we didn't include it in /etc/rc file) > we get > > "Jan 20 11:16:12 apt /kernal: ed0: device time out" > If we ping to any other machine we are getting same "device timeout" > error thrice and after that "Host is Down" message is coming. Looks like the kernel isn't getting the IRQ. > There is no I/O conflicts or IRQ conflicts.We have checked it > while booting (boot -c "visual" option shows there is no conflicts) (a) Check if the card IRQ matches with what the kernel thinks the IRQ is? If I remember right, the probe just looks for the card at the configured IRQ address by reading and writing device memory. Send or recieving a packet uses the interrupt which isn't checked at probe time. If necessary, run your DOS tools to see the IRQ the card is actually configured for. What is printed at startup time is the kernels idea of the IRQ, not the cards actual configuration. Note that this is different from there being any `conflict' of IRQ's assigned. (b) I've seen problems with older NE2K cards on the newer P5 motherboards. Does your card work in the same machine from under DOS? Sometimes fiddling with the motherboard settings (io wait states) etc may help. Koshy My Personal Opinions Only