From owner-freebsd-questions Sun Jan 19 23:16:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA15976 for questions-outgoing; Sun, 19 Jan 1997 23:16:40 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA15971 for ; Sun, 19 Jan 1997 23:16:35 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id IAA20719; Mon, 20 Jan 1997 08:19:03 +0100 (MET) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.8.3/8.6.9) id IAA15652; Mon, 20 Jan 1997 08:17:38 +0100 (MET) From: Christoph Kukulies Message-Id: <199701200717.IAA15652@gilberto.physik.rwth-aachen.de> Subject: Re: Problem in connecting a machine in network In-Reply-To: <199701200649.AA171312959@fakir.india.hp.com> from A JOSEPH KOSHY at "Jan 20, 97 11:49:18 am" To: koshy@india.hp.com (A JOSEPH KOSHY) Date: Mon, 20 Jan 1997 08:17:38 +0100 (MET) Cc: smraj@hotmail.com, questions@FreeBSD.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 ^^^ i/o (port) address (I'm sure you meant that). > 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 > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de