From owner-freebsd-stable@FreeBSD.ORG Fri Oct 26 16:30:23 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DCF716A4AC for ; Fri, 26 Oct 2007 16:30:23 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: from coruscant.far-far-away.us (coruscant.far-far-away.us [70.91.196.65]) by mx1.freebsd.org (Postfix) with SMTP id 9F9CD13C4B8 for ; Fri, 26 Oct 2007 16:30:22 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: (qmail 51795 invoked from network); 26 Oct 2007 11:58:24 -0400 Received: from pknat1.passkey.com (HELO ?192.168.16.253?) (68.162.198.134) by coruscant.far-far-away.us with SMTP; 26 Oct 2007 11:58:24 -0400 From: Yousif Hassan To: Luis Neves In-Reply-To: <4721F8A8.3010501@co.sapo.pt> References: <4721F8A8.3010501@co.sapo.pt> Content-Type: text/plain Date: Fri, 26 Oct 2007 12:03:41 -0400 Message-Id: <1193414621.96583.14.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: 7.0 BETA1 and Thinkpad T61p : Wireless misadventure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yousif@alumni.jmu.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2007 16:30:23 -0000 > There are no FreeBSD drivers for the included intel 4965AG card. > I've tried to use the ndiswrapper framework without success. The ndisgen wizard > runs without issues, but kldloading the driver freezes and reboots the machine. This occurs if the Windows driver contains function calls that have not been implemented in the ndiswrapper framework. Often, an older version of the Windows driver solves the issue. For Broadcom cards that use bcmwl5.sys, kernel crash is a frequent problem if the newer drivers are used, but the old drivers solve the issue. I don't know if the card you mention would even work with ndis, but it's a good first step that ndisgen wizard works. Trying an older version of the Windows driver *might* help, but only if this card is compatible with ndis framework in the first place. Good luck.