From owner-freebsd-net@FreeBSD.ORG Fri May 28 20:51:24 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 7399B16A4CE for ; Fri, 28 May 2004 20:51:24 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id DE8F643D48 for ; Fri, 28 May 2004 20:51:23 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 88095 invoked from network); 29 May 2004 03:51:20 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 29 May 2004 03:51:20 -0000 X-pair-Authenticated: 209.68.2.70 Date: Fri, 28 May 2004 22:51:19 -0500 (CDT) From: Mike Silbersack To: Larry Rosenman In-Reply-To: <97871D995743BC53AF74402D@lerlaptop.lerctr.org> Message-ID: <20040528224647.H17807@odysseus.silby.com> References: <90F7EEA9460A4D039C291426@lerlaptop.lerctr.org> <97871D995743BC53AF74402D@lerlaptop.lerctr.org> 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: Sat, 29 May 2004 03:51:24 -0000 On Fri, 28 May 2004, Larry Rosenman wrote: > I E-mailed you (Silby) the driver. You should also be able to use > ports/archivers/cabextract to pull stuff from the cab's. > > LER Neat, I didn't know we had that util in ports. I tried it on the cabs, and it told me to use "unshield", which was also in ports, so I was able to pull them apart in the end. After looking through the cabs from linksys's installer, I agree - there is only one non-9x series driver. Looks like the only way to get the card working properly may be to send Bill one of these cards and hope that he has time to debug the problem. In the meantime, you're probably best off buying another card, perhaps one of the ones supported natively by ath(4) or one known to work with the NDISulator properly. If you can find any linux NDISulator support boards it might be worthwhile poking around there... if the driver is also broken there, maybe there's hope that a new driver will fix the problem. That's the end of my knowledge of the NDISulator, good luck! :) Mike "Silby" Silbersack