Date: Sat, 04 Jul 1998 23:11:27 -0700 From: Soren Kristensen <soren@soekris.dk> To: Joe Abley <jabley@clear.co.nz>, hackers@FreeBSD.ORG Subject: Re: ethernet peculiarity Message-ID: <359F190F.5A83@soekris.dk> References: <Pine.BSF.3.96.980705121406.26585A-100000@buddha.clear.net.nz> <359ED491.7F3C@soekris.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, I think I'm getting old, the mouse port is of course irq 12. But I still thinks it looks like a classic interrupt conflict. But it might be because irq 10 is assigned to the PCI slots, that's default for most PCI based computers. Go into the BIOS and make sure that the irq 10 setting is assigned to ISA instead of PCI/PnP. Soren Kristensen wrote: > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?359F190F.5A83>