From owner-freebsd-net@FreeBSD.ORG Fri May 28 16:19:44 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E93316A4CE for ; Fri, 28 May 2004 16:19:44 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D878043D58 for ; Fri, 28 May 2004 16:19:43 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 3227 invoked from network); 28 May 2004 23:19:37 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 28 May 2004 23:19:37 -0000 X-pair-Authenticated: 209.68.2.70 Date: Fri, 28 May 2004 18:19:36 -0500 (CDT) From: Mike Silbersack To: Larry Rosenman In-Reply-To: Message-ID: <20040528181643.K9659@odysseus.silby.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: NDIS: How can I help with these (2nd request). X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2004 23:19:44 -0000 On Fri, 28 May 2004, Larry Rosenman wrote: > I have a LinkSys WPC54GS PCCARD Wireless card, and am using the NDISulator > to use the windows driver. > > I get the following when transferring large files: > > lerlaptop# tail /var/log/messages > May 28 08:37:47 lerlaptop kernel: NDIS: buggy driver deleting active packet > pool! > > What can I do to help here? > > Is this the right place? > > I've sent the driver to wpaul@freebsd.org as well as wpaul@windriver.com > in the past, with NO replies. > > Thanks! > > Larry Rosenman Well, Bill can be grumpy at times, you might consider being happy that he didn't reply. :) First off, is this 5.2.1, or 5.2-current? If it's older, perhaps bugs in the NDISulator have been fixed since. Second, have you tried various versions of the windows drivers for the card? Maybe different versions of the driver have different bugs. :) Mike "Silby" Silbersack