From owner-freebsd-questions Tue Feb 20 20:17:02 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA02919 for questions-outgoing; Tue, 20 Feb 1996 20:17:02 -0800 (PST) Received: from baygull.rtd.com (baygull.rtd.com [198.102.68.5]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA02911 for ; Tue, 20 Feb 1996 20:16:57 -0800 (PST) Received: (from news@localhost) by baygull.rtd.com (8.6.9/8.6.9.1) id VAA14162; Tue, 20 Feb 1996 21:16:44 -0700 To: questions@freebsd.org Path: freefall.freebsd.org!owner-freebsd-questions From: troyc@merix.com (Troy Curtiss) Newsgroups: rtd.freebsd.questions Subject: Re: 3Com Etherlink II/16 device timeouts Date: Tue, 20 Feb 96 17:16:42 PST Lines: 22 Message-ID: NNTP-Posting-Host: seagull.rtd.com Sender: owner-questions@freebsd.org Precedence: bulk I am using a slew of 3Com Etherlink II/16's with the ed driver. The biggest gotcha involve one of 2 things. 1) Using the 3com supplied program, make sure your interrupts are set up correctly. Also, make sure the card is configured for shared memory operation AND the shared memory area is in line with your device probe information (and irq number too, of course.) 2) If you are using the card on a isa->pci bridge, make sure that you have the interrupt and shared memory marked 'as being used' by the isa card (so the PCI stuff won't use/stomp on your interrupts). THis should be in your BIOS somewhere. I've used these cards with FreeBSD for 2 years without a single problem. Good solid card, although showing its age recently. -- /-----------------------------------------------------------\ | Troy Curtiss, HW/SW Engineer | Email: troyc@merix.com | | Merix Corporation, F8-208 | Phone: (503) 359-9300 x54500 | | Forest Grove, OR 97116 | Fax : (503) 359-1624 | \-----------------------------------------------------------/