From owner-freebsd-questions Wed May 12 7:24: 3 1999 Delivered-To: freebsd-questions@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 76BFA15D06 for ; Wed, 12 May 1999 07:23:51 -0700 (PDT) (envelope-from Networks.Manager@rncm.ac.uk) Received: from fs1.rncm.ac.uk ([193.63.96.100]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 10hZvJ-0001yz-00; Wed, 12 May 1999 15:23:49 +0100 Received: from RNCM-FS1/MAILQUEUE by fs1.rncm.ac.uk (Mercury 1.44); 12 May 99 15:12:27 GMT Received: from MAILQUEUE by RNCM-FS1 (Mercury 1.44); 12 May 99 15:12:26 GMT Received: from rncm.ac.uk (193.63.96.102) by fs1.rncm.ac.uk (Mercury 1.44) with ESMTP; 12 May 99 15:12:24 GMT Received: from RNCM-FS3/SpoolDir by rncm.ac.uk (Mercury 1.44); 12 May 99 15:23:50 GMT Received: from SpoolDir by RNCM-FS3 (Mercury 1.44); 12 May 99 15:23:30 GMT Received: from brick (193.63.96.36) by rncm.ac.uk (Mercury 1.44); 12 May 99 15:23:30 GMT From: "Peter McGarvey" To: Cc: Subject: RE: 3Com EtherLink III 3C509B Date: Wed, 12 May 1999 15:23:51 +0100 Message-ID: <001701be9c83$0eb14520$24603fc1@brick.it-dept.rncm.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a 3Com Etherlink III 3C509B in a 486, the card is an ISA...when I > boot up into 3.1-R I get the following relating to the ep0(3C5x9) driver: > > 1 3C5x9 board(s) on ISA found at 0x300 > ep0 at 0x300-0x30f irq 10 on isa > no connectors!ep0: [*UTP*] address 00:a0:24:b9:24:4f > > Although, if I boot the machine into windows95 the card works perfectly > fine, so its not the cable or card. Anyone have any clue to why > it might be > saying theres no connectors? Hi. I've got a 3c509B running quite happily with 2.2.5-RELEASE However, it wasn't always this way - I had some weird and wonderful problems. What I eventually had to do was disable Plug-n-Pray then lock down the board's config to whatever FreeBSD expected. To do the above you'll need to dig out your a copy of the NICs setup disks and run the configure prog from DOS. TTFN, FNORD -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Peter McGarvey, Networks Manager | email: Networks.Manager@rncm.ac.uk Royal Northern College of Music | tel: +44 (0)161 907 5218 124 Oxford Road, Manchester, | fax: +44 (0)161 273 7611 England M13 9RD | mobile: +44 (0)7887 990564 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message