Date: Thu, 9 Jul 1998 10:23:02 +0100 (BST) From: ruth moulton <ruth@muswell.demon.co.uk> To: freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: connecting NT and FBSD via tcp/ip over ethernet using Message-ID: <199807090923.KAA00360@muswell.demon.co.uk>
next in thread | raw e-mail | index | archive | help
Kingston boards In-Reply-To: <199807031703.KAA02588@ix.netcom.com> References: <199807030831.JAA01803@muswell.demon.co.uk> <199807031703.KAA02588@ix.netcom.com> X-Mailer: VM 6.22 under 19.15 XEmacs Lucid Cc: ruth Thanks to everyone who sent me advise on this problem. I sat down more calmly yesterday with a couple of hours in hand and finally solved the problem, I now have an ethernet (utp via hub) with Solaris, Freebsd 2.1 and NT 4.0 all talking to each other using tcp/ip protocols. - HOORAY - freebsd using a Kinsgton ne2000 compatable board. and what was the problem in the end - hardware addressing/irq conflict I believe: this is what finally happened: At last I noticed that the console was displaying the message ed0: device timeout I checked the manual page for ed0 and this suggested IRQ conflicts. I looked at the boot messages - freebsd saw the kingston ethernet board at IRQ5 and nothing else at this IRQ. I tried to change the card's IRQ to 10, using it's config program, but Freebsd kept seeing it at 5. (If I set it to 5 explicitly freebsd didn't see the card at all) And then, whilst booting DOS to run the config program, I noticed that the sound card, a plug and play card, was coming up at IRq5. After some messing about I discovered I could reserve IRQ5 for ISA use instead of PnP - using the boot time bios config. So I did this, the sound card went to 11 - but still no joy!!!!!! I tried a 3com card, freebsd didn't even see it (3C509). I tried other addresses in the ed0 range, but only 280x was seen by freebsd. Then I thought to try the card at it's other address range, again only 300x was actually seen by freebsd, as ed1. I'd left the irq at 10 and still no joy - I was getting timeout messages. So I tried one last time to configure the kingston at IRQ 5, address 300x (duplex and pnp disabled), and glory of glories, the freebsd came up on the net!!!!!!!! I think this is called reading the manual, looking at and believing the evidence, not jumping to conclusions, and staying calm!!! anyway, I'm totally relieved to have sorted the problem at last, many thanks to those who tried to help ruth -- ================================================ Ruth Moulton ruth@muswell.demon.co.uk Consultant 65 Tetherdown, London N.10 1NH, UK Tel:+44 181 883 5823 -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807090923.KAA00360>