From owner-freebsd-hackers  Sat Jul  4 18:19:24 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA04195
          for freebsd-hackers-outgoing; Sat, 4 Jul 1998 18:19:24 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from Gatekeeper.Alameda.net (root@gatekeeper.Alameda.net [207.90.181.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04178
          for <hackers@FreeBSD.ORG>; Sat, 4 Jul 1998 18:19:21 -0700 (PDT)
          (envelope-from soren@soekris.dk)
Received:  by Gatekeeper.Alameda.net (8.9.0/8.8.6) with SMTP id SAA25469;
	Sat, 4 Jul 1998 18:19:16 -0700 (PDT)
X-SMTP: helo soren.soekris from soren@soekris.dk server @207.90.187.212 ip 207.90.187.212
Message-ID: <359ED491.7F3C@soekris.dk>
Date: Sat, 04 Jul 1998 18:19:13 -0700
From: Soren Kristensen <soren@soekris.dk>
Reply-To: soren@soekris.dk
Organization: Soekris Engineering
X-Mailer: Mozilla 3.04 (Win95; I)
MIME-Version: 1.0
To: Joe Abley <jabley@clear.co.nz>
CC: hackers@FreeBSD.ORG
Subject: Re: ethernet peculiarity
References: <Pine.BSF.3.96.980705121406.26585A-100000@buddha.clear.net.nz>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi Joe,

It looks like a classic interrupt conflict, have you tried using another
irq number, irq 10 is usually used by the PS2 mouse port, even if no
mouse is connected ?


Joe Abley wrote:
> 
> Hi all,
> 
> I just put FreeBSD 2.2.6-RELEASE on a Pentium 133 box, 8M RAM, Intel 82439
> PCI chipset, Intel 82371SB PCI-ISA bridge.
> 
> Everything looks normal, and yet I have had a complete inability to get
> either 3c509 or NE2000-clone ethernet cards to function. The following
> example is from the NE2000 clone, but the 3c509 symptoms were identical
> (but with the ep driver). I tried three different 3c509 cards with the
> same results.
> 
> Basically, the machine appears to boot and identify the card, but I get
> repeated kernel messages of "ed0: device timeout".
> 
> dmesg reveals:
> 
>   ed0 at 0x300-0x31f irq 10 flags 0x4 on isa
>   ed0: address 00:c0:58:20:bg:16, type NE2000 (16 bit)
> 
> This results from a kernel configuration of:
> 
>   device ed0 at isa? port 0x300 net irq 10 flags 0x04 iomem 0xd8000 vector edintr
> 
> I have tried this without the flags parameter, and with a flags parameter
> of 0x02. Same result. This card is an ExpertLan INET2000, which works on
> win95 as an NE2000. The manufacturer's setup utility confirms the card is
> working, and is set for port 0x300, irq 10 (with no memory-mapped I/O).
> 
> This may well be a completely inappropriate list for this (in which case
> "sorry"); however, I _was_ interested in what could cause a generic
> kernel-wide ethernet (or ISA?)  failure in a machine.
> 
> What is going on?
> 
> Joe
> 
> --
> Joe Abley <jabley@clear.co.nz>      Tel +64 9 912-4065, Fax +64 9 912-5008
> Network Architect, CLEAR Net                      http://www.clear.net.nz/
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message