Date: Tue, 15 Jun 2010 09:00:51 -0700 From: Rui Paulo <rpaulo@FreeBSD.org> To: Lars Engels <lars.engels@0x20.net> Cc: bf1783@gmail.com, Doug Barton <dougb@freebsd.org>, freebsd-current@freebsd.org Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) Message-ID: <FD0B951E-7853-41E7-B1FF-6E94E738C9CF@FreeBSD.org> In-Reply-To: <20100615150305.GA43178@e.0x20.net> References: <AANLkTilCmEAdZXpO_hhQXOkY576POiNqf71fZ4nmu7hO@mail.gmail.com> <4C00832A.4030102@FreeBSD.org> <AANLkTikk34mBzYG_YRyjl9IJXdksdPQCa6JRaYvp-TZ6@mail.gmail.com> <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> <20100530174838.GC41305@e.0x20.net> <20100615150305.GA43178@e.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 Jun 2010, at 08:03, Lars Engels wrote: > On Sun, May 30, 2010 at 07:48:38PM +0200, Lars Engels wrote: >> On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote: >>>=20 >>> On 29 May 2010, at 05:39, b. f. wrote: >>>=20 >>>> On 5/28/10, Doug Barton <dougb@freebsd.org> wrote: >>>>> On 5/28/2010 4:50 PM, b. f. wrote: >>>>>>=20 >>>>>> I can't see any problems when using WPA2 with AES on r208606 i386 = with >>>>>> uath(4). I'm updating this machine to r208630 tonight, and if I >>>>>> encounter problems with the later revision, I'll let you know. >>>>>=20 >>>>> Ok, thanks. >>>>>=20 >>>>>> Are >>>>>> you saying that you experienced problems when trying to use a = r207134 >>>>>> base with a r208626 kernel? If that's the case, I would = recommend >>>>>> updating the base to the same revision as the kernel, and then >>>>>> retesting. >>>>>=20 >>>>> Yes, that's what I'm doing I actually tried running the newly = built >>>>> wpa_supplicant but that didn't work. I'm kind of hesitant to do = the full >>>>> upgrade since I'm having kernel problems with the nvidia driver, = but if >>>>> I'm sure wpa_supplicant will work then I suppose I can bite the = bullet. >>>>>=20 >>>>=20 >>>> It appears that something is wrong. My wireless stick no longer >>>> associates with the network with r208630. I'll do some tinkering. >>>=20 >>> That's odd. The only way for that to happen would be caused bug in = the >>> taskqueue stuff that zml committed, I think, but that's a long shot. >>=20 >> Correction: Wireless actually works if you set the channel manually = and >> start wpa_supplicant afterwards. So wpa_supplicant no longer seems to = be >> able to change the channel itself. >=20 >=20 > The issue is still present in r209168. Which driver? I works fine with my ath. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FD0B951E-7853-41E7-B1FF-6E94E738C9CF>