Date: Wed, 08 Dec 1999 21:33:49 +0000 From: Adam Laurie <adam@algroup.co.uk> To: "Niels Chr. Bank-Pedersen" <ncbp@bank-pedersen.dk> Cc: FreeBSD mobile Mailing List <freebsd-mobile@FreeBSD.ORG> Subject: Re: 3c589d w/ freebsd 3.3 works badly. Message-ID: <384ECEBD.485F478@algroup.co.uk> References: <199912060251.NAA16461@cairo.anu.edu.au> <199912062312.QAA37583@harmony.village.org> <19991206210033.19522@mojave.sitaranetworks.com> <19991207160848.A27105@bank-pedersen.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
"Niels Chr. Bank-Pedersen" wrote: > > On Mon, Dec 06, 1999 at 09:00:33PM -0500, Greg Lehey wrote: > > [Moved to FreeBSD-mobile] > > > > On Monday, 6 December 1999 at 16:12:49 -0700, Warner Losh wrote: > > > In message <199912060251.NAA16461@cairo.anu.edu.au> Darren Reed writes: > > > : How reliable should the ep0 driver be with 3c389d pcmcia cards ? > > > > > > I had no problems using 3.3 and my 3C589D, but I've only done minor > > > stuff with that. I've done most of my work on -current, however. The > > > most likely problem is that you're using the wrong IRQ for the card. > > > You'll want to check /etc/rc.conf to make sure that you are using the > > > /etc/pccard.conf file. Also, you'll want to make sure that the irq > > > line is correct. > > > > I don't know if this is the same issue, but I've seen terrible write > > performance on my 3C589C under -CURRENT, and so has phk. Read > > performance is OK. Looking at the hub, I see a short burst of > > activity and then nothing for the rest of a second. This repeats > > itself in this manner. No errors, but a write throughput of less than > > 50 kB/s. I've seen this before recent changes in -CURRENT, but it > > seems worse now (or maybe I've just paid more attention to it now :-). > > I've seen something similar - turned out to be changes in the pcm > detection that resulted in irq conflicts (as mentioned above). > After I hardwired irg/drq in my kernel, the problem was gone... This can also be caused by mis-matched full/half duplex settings... If one end of the link is set to full duplex and the other to half, (i.e the pc and the hub), you will get exactly this problem. I have found a lot of auto-sensing switches detect the speed ok, but get the duplex wrong. Try forcing both ends to half-duplex (make sure you set *everything* in your test chain) and see if the problem goes away - if it does, you can risk trying full (as there are also some switches that claim to support full duplex, but are actually broken). cheers, Adam -- Adam Laurie Tel: +44 (181) 742 0755 A.L. Digital Ltd. Fax: +44 (181) 742 5995 Voysey House Barley Mow Passage http://www.aldigital.co.uk London W4 4GB mailto:adam@algroup.co.uk UNITED KINGDOM PGP key on keyservers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?384ECEBD.485F478>