From owner-freebsd-questions@FreeBSD.ORG Mon Sep 6 18:16:06 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E58810656CC for ; Mon, 6 Sep 2010 18:16:06 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by mx1.freebsd.org (Postfix) with ESMTP id EA5568FC20 for ; Mon, 6 Sep 2010 18:16:05 +0000 (UTC) Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.4/8.14.4) with ESMTP id o86IG45Y081675; Mon, 6 Sep 2010 14:16:04 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.14.4/8.14.4/Submit) with ESMTP id o86IG4qZ081672; Mon, 6 Sep 2010 14:16:04 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Mon, 6 Sep 2010 14:16:04 -0400 (EDT) From: doug To: Gautham Ganapathy In-Reply-To: Message-ID: References: <20100724084204.597b9e6f@scorpio> <20100724154644.75b1938b@scorpio> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Mon, 06 Sep 2010 14:16:05 -0400 (EDT) Cc: freebsd-questions@freebsd.org Subject: Re: 64-bit Windows XP NDIS drivers giving missing symbols X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: doug@safeport.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2010 18:16:06 -0000 On Sun, 25 Jul 2010, Gautham Ganapathy wrote: > On Sun, Jul 25, 2010 at 1:16 AM, Jerry wrote: > >> On Sat, 24 Jul 2010 18:45:24 +0000 >> Paul B Mahol articulated: >> >> >>> On 7/24/10, Jerry wrote: >>>> On Sat, 24 Jul 2010 12:01:24 +0000 >>>> Paul B Mahol articulated: >>>> >>>>> Such symbols are completly irrelevant for normal operation, because >>>>> NDISulator crash on amd64 during driver initialization. >>>>> I fixed this in my own git repo, but "fpudna in kernel mode" (my >>>>> understanding is that it is source of panic when trying to use ndis0 >>>>> device on amd64), present only on amd64 is still not yet fixed - this >>>>> should be addressed with fpu_kern KPI available on CURRENT - not done >>>>> yet... >>>>> Feel free to send patches. >>>> >>>> I feel his pain. I need 64 bit drivers for cards that FBSD does not >>>> support, mostly 'N' protocol wireless cards. The inability to secure >>>> and use perfectly good drivers that are available for Windows users in >>>> FreeBSD is a real PIA. Of course, it does give my Window user friends >>>> something to laugh about. >>> >>> And bwn(4) doesn't work at all? >> >> >> bwn -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver >> >> >> You will notice that there is no 'n' in the description. In any case, >> it is limited to 'broadcom' chips. >> >> -- >> Jerry ? >> FreeBSD.user@seibercom.net >> > > Nope, bwn did not work. The man page mentioned a port that also had to be > installed. It had two modules, which I put in loader.conf one at a time > along with if_bwn.ko, but still no luck. > > The card I have has a Broadcom 4353 chipset. I think it is b/g/n. > I have a laptop with the same card. In a December 23, 2009 (in current I think) the driver maintainer said: I see that your device has LP-PHY instead of A/B/G/N PHYs so currently it's not supported by bwn(4). AFAIK linux has a weak but working implementation so we could refer to other Open Sources. At least on 8.1 bwn does not recognize the device. I can not find XP drivers. Broadcom's site does not (as far as I could find) mention the card. It does not sound like the XP driver work much better. Using the win7 drivers produces a hard loop upon doing an ifconfig. There are no PRs on either ndis or bwn so I assume this will be the state of things for a while at least. If anyone got the XP drivers to work with this card, please share the solution and how to get the drivers.