Date: Thu, 2 May 2002 10:08:04 +0200 From: Guido Kollerie <gkoller@chello.nl> To: Sten <sten@blinkenlights.nl> Cc: Danny Braniss <danny@cs.huji.ac.il>, current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: 3Com 3c905C-TX Message-ID: <20020502080804.GA275@node14e65.a2000.nl> In-Reply-To: <Pine.LNX.4.44-Blink.0205012340220.2142-100000@deepthought.blinkenlights.nl> References: <20020501202806.GA256@node14e65.a2000.nl> <Pine.LNX.4.44-Blink.0205012340220.2142-100000@deepthought.blinkenlights.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Wed, May 01, 2002 at 11:49:02PM +0200, Sten wrote: > The only way to use them reliably is to force > both the card and the switch. We came to the > conclusion that fxp's are a nicer option. I have exchanged the 3Com NIC for an Intel one. I'm using an Intel NIC at work and haven't had any problems with it under FreeBSD. What remains strange though is that the 3Com NIC used to work just fine. As said before the strange behaviour (full-duplex -> half-duplex) occurred about a month ago. Around the same time I performed a 'make world'. Was the xl driver changed somehow in the period before that? -- Guido [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE80PPkC7vo05+GQSwRAqD7AJ4n9ObpLcUOtCH9iEElDUaHn/E0cACdEHrh NzB4AegSgI1NULYAIfJ6Gms= =eK8a -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020502080804.GA275>