Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Apr 2009 22:44:49 +0200
From:      "Paul B. Mahol" <onemda@gmail.com>
To:        michael <michael.copeland@gmail.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Unable to associate using NDIS driver to WPA/WPA2 APs post  2009/03/26
Message-ID:  <3a142e750904061344k3c6f5f9aue1efbd16bef0e53a@mail.gmail.com>
In-Reply-To: <49DA23A9.50707@gmail.com>
References:  <20090406092653.W48458@admin16.site.uottawa.ca> <3a142e750904060832r41febee3k1dd6e4f5d7bc0f22@mail.gmail.com> <49DA23A9.50707@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 4/6/09, michael <michael.copeland@gmail.com> wrote:
>
>
> Paul B. Mahol wrote:
>> On 4/6/09, Keith White <kwhite@site.uottawa.ca> wrote:
>>
>>> The platform is an msi wind U100 using an NDIS driver for the onboard
>>> rt2860.
>>>
>>> This has worked well, both at home with WPA2-PSK and at work with
>>> WPA2-EAP, until recently [post 2009/03/26?].  It stopped working
>>> with the recent changes to if_ndis and net80211.
>>>
>>> My current workaround is to use older versions of wlan.ko and
>>> if_ndis.ko, but that's not going to continue forever...
>>>
>>
>> Known issue, I'm slowly working on it ... any help is appreicated
>>
>>
>>
> ndis is causing my machine to panic with rt2870 and rt2860 devices.
> specifically, it was causing a panic the moment rt2870_sys.ko was
> loaded, however, if ndis.ko was loaded first, it would take up to a minute.

amd64 or i386 8.CURRENT, do you have backtrace?


-- 
Paul



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750904061344k3c6f5f9aue1efbd16bef0e53a>