Date: Mon, 6 Sep 2010 14:16:04 -0400 (EDT) From: doug <doug@fledge.watson.org> To: Gautham Ganapathy <gautham@lisphacker.org> Cc: freebsd-questions@freebsd.org Subject: Re: 64-bit Windows XP NDIS drivers giving missing symbols Message-ID: <alpine.BSF.2.00.1009061356270.66381@fledge.watson.org> In-Reply-To: <AANLkTi=OyEhRPiOti=6cAweWRV%2BRLqXg3zVB9U5X8PQT@mail.gmail.com> References: <AANLkTinhc-Qp1jV3TB92BYPf3UxVV7Uf0TJN2X7wwLxt@mail.gmail.com> <AANLkTin%2BL3rxWLUGSpzdh4kmJvx43swOJ8E847qjub5t@mail.gmail.com> <20100724084204.597b9e6f@scorpio> <AANLkTim1p4QOm6pm_ddKXwLuwHBixV=UXQR3V-2YhF_t@mail.gmail.com> <20100724154644.75b1938b@scorpio> <AANLkTi=OyEhRPiOti=6cAweWRV%2BRLqXg3zVB9U5X8PQT@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 25 Jul 2010, Gautham Ganapathy wrote:
> On Sun, Jul 25, 2010 at 1:16 AM, Jerry <freebsd.user@seibercom.net> wrote:
>
>> On Sat, 24 Jul 2010 18:45:24 +0000
>> Paul B Mahol <onemda@gmail.com> articulated:
>>
>>
>>> On 7/24/10, Jerry <freebsd.user@seibercom.net> wrote:
>>>> On Sat, 24 Jul 2010 12:01:24 +0000
>>>> Paul B Mahol <onemda@gmail.com> 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?
>>
>> <quote>
>> bwn -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver
>> </quote>
>>
>> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1009061356270.66381>