From owner-freebsd-questions Tue Feb 20 17:18:41 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA21910 for questions-outgoing; Tue, 20 Feb 1996 17:18:41 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA21905 for ; Tue, 20 Feb 1996 17:18:38 -0800 (PST) Received: from merix.merix.com (merix.com [198.145.172.40]) by pdx1.world.net (8.6.9/8.6.9) with SMTP id RAA28721; Tue, 20 Feb 1996 17:18:09 -0800 Received: from sandy.merix.com by merix.merix.com (4.1/1.1) id AA10352; Tue, 20 Feb 96 17:15:14 PST Received: by sandy.merix.com (4.1/8.0) id AA05516; Tue, 20 Feb 96 17:16:42 PST Date: Tue, 20 Feb 96 17:16:42 PST Subject: Re: 3Com Etherlink II/16 device timeouts To: freebsd-questions@freebsd.org, ajones@ctron.com From: Troy Curtiss Message-Id: In-Reply-To: <1105.824852549@time.cdrom.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 | \-----------------------------------------------------------/