From owner-freebsd-hackers Thu Jul 9 09:30:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06773 for freebsd-hackers-outgoing; Thu, 9 Jul 1998 09:30:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06762 for ; Thu, 9 Jul 1998 09:30:20 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA25435; Thu, 9 Jul 1998 11:30:42 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA04740; Thu, 9 Jul 1998 11:29:59 -0500 (CDT) (envelope-from joelh) Date: Thu, 9 Jul 1998 11:29:59 -0500 (CDT) Message-Id: <199807091629.LAA04740@detlev.UUCP> To: sbabkin@dcn.att.com CC: mike@smith.net.au, hackers@FreeBSD.ORG In-reply-to: (sbabkin@dcn.att.com) Subject: Re: NIC drivers From: Joel Ray Holveck References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Last I heard, the 509 driver was buggy. (According to LINT, it >>> still is.) When I last tried it about eight months ago, it was >>> still buggy. Cursory tests now (I've got one in this box, on the >>> same LAN as an NE2000) indicate that it may still be broken. >> Yes; the driver is not spectacular, and neither is the card. > It worked fine for me in '95-'97 in my machine at work. Yes, it > occasionally loses packets under high load but it's still faster > than NE2000 (although I agree that the card is somewhat > pathological). It can easily handle FTP at full Ethernet speed > (1.1MB/s) in an old 486. Although I don't know about the current > state of the driver. There was a period (early '95) when packet loss > led to the hang of the card and that's the reason why it was marked > as "buggy" in LINT at that time. This was fixed but this comment > just was not cleaned up. There was the same problem somewhere in '96 > when David Greenman had changed the way the watchdog routines are > called for network drivers, but after this driver was changed > according to the new way it worked again. Hmmm... What version of FreeBSD are you using? I'd like to get mine working; you appear to know what's going on. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message