From owner-freebsd-stable Wed Jun 6 7:29:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id E001737B401 for ; Wed, 6 Jun 2001 07:29:21 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA30653; Wed, 6 Jun 2001 07:29:09 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda30651; Wed Jun 6 07:29:05 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.4/8.9.1) id f56ESxr25977; Wed, 6 Jun 2001 07:28:59 -0700 (PDT) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdg25975; Wed Jun 6 07:28:26 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.4/8.9.1) id f56ESPk05110; Wed, 6 Jun 2001 07:28:25 -0700 (PDT) Message-Id: <200106061428.f56ESPk05110@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdQT5106; Wed Jun 6 07:27:27 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: "Steve Coles" Cc: "FreeBSD-Stable" Subject: Re: Problems with 3COM 3C509 In-reply-to: Your message of "Tue, 05 Jun 2001 09:28:10 BST." <011201c0ed99$745d1390$9e9814ac@wolf.tripos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Jun 2001 07:27:27 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <011201c0ed99$745d1390$9e9814ac@wolf.tripos.com>, "Steve Coles" writ es: > FWIW: > > My experience with these cards under FreeBSD has been considerably more > favourable than under MS operating systems. > > Most problems I have seen seem to result from BIOS:NIC interaction rather > than the FreeBSD driver. I have these NICs working in PnP and wired-down > mode under 4.3 - however, I have had less problems using IRQ10 as on my > cheap PCChips MOBOs there seem to be uncooperative isa sound devices > silently grabbing IRQ 5. > > Steve I've found these cards (driver) hanging under high network transmit load under FreeBSD. The workaround was to ifconfig ep0 down; ifconfig ep0 up. I finally got fed up with 3COM cards and replaced my 3C509's and my 3C905's (for an entirely different reason) with NE2000 cards and NE2000 PCI clones. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC > > > -----Original Message----- > > From: owner-freebsd-stable@FreeBSD.ORG > > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Gerhard Sittig > > Sent: Monday, June 04, 2001 2:25 AM > > To: freebsd-stable@FreeBSD.ORG > > Subject: Re: Problems with 3COM 3C509 > > > > > > On Sun, Jun 03, 2001 at 21:05 +0200, Mats Dufberg wrote: > > > > > > On Sun, 3 Jun 2001, Alson van der Meulen wrote: > > > > > > > > I have problems installing 4.3-* on a machine with a 3COM > > > > > 3C509 card (built in on ISA). After some trials and errors > > > > > I've come to the conclusion that I need to give the port > > > > > address, but the device is not available to setting at boot > > > > > time (of installation). > > > > > > [ ... ] > > > > > > > try boot -c, then you should be able to modify the iobase, > > > > irq and stuff of the ep0 device > > > > > > The GENERIC kernel has support for ep, but it is strangely > > > enough not availble for setting. It is just not there. I do not > > > understand why. > > > > With (modern only? have there been cards not participating in > > this mechanism?) 3com ISA cards usually there's _no_need_ to set > > drivers to anything. AFAIK they have some identification port at > > 0x110 where their configuration can be read from and written to. > > Guess where the 3c5x9cfg gets the data from. :) > > > > >From personal experience I would check these points: > > - Make sure you turn off the card's PnP function (and do remember > > to power down the machine after throwing the switch -- I've > > seen people hunting problems for hours when they thought C-A-D > > warmboots would do ...) > > - Make sure your port 0x110 is available -- i.e. don't put other > > hardware at, say, 0x100 when its window is 0x20 bytes wide. I > > once had the problem that a 3c509 wasn't recognized correctly > > (or didn't work? don't know any longer) when I had a PnP ISDN > > card between 0x100 and 0x11f. Moving it to 0x140 worked fine > > -- I learned to love the isapnp tools (it was a Linux system)! > > > > > When I tried 3.5.1 it was available for adjustment, and then it > > > work fine when I set it to IRQ 10 and port 0x250. 4.3 thought > > > it was 5 and 0x210 respectively > > > > Well, as long as the driver "downloads" its assumed configuration > > into the card, *any* setup should work. Only when the driver > > assumes one configuration, doesn't tell the card about it, but > > still doesn't match the card's idea -- that's when things go > > wrong. So it depends on what the driver tells the card in the > > initialization phase. And whether communication via the > > identification port 0x110 is possible and works. > > > > > > virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 > > Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net > > -- > > If you don't understand or are scared by any of the above > > ask your parents or an adult to help you. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message