From owner-freebsd-current@FreeBSD.ORG Mon Nov 16 18:53:14 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85AEA106566B for ; Mon, 16 Nov 2009 18:53:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2B4E48FC08 for ; Mon, 16 Nov 2009 18:53:13 +0000 (UTC) Received: (qmail 25142 invoked by uid 399); 16 Nov 2009 18:53:13 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 16 Nov 2009 18:53:13 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B019F97.6040209@FreeBSD.org> Date: Mon, 16 Nov 2009 10:53:11 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: Paul B Mahol References: <4B0087C2.9070508@FreeBSD.org> <4B00BA99.5000009@FreeBSD.org> <3a142e750911160035m520819eqdf261c0c493bf3c3@mail.gmail.com> In-Reply-To: <3a142e750911160035m520819eqdf261c0c493bf3c3@mail.gmail.com> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Rui Paulo Subject: Re: wpa_supplicant + wpi0 won't lock in on today's -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2009 18:53:14 -0000 Paul B Mahol wrote: > On 11/16/09, Doug Barton wrote: >> Doug Barton wrote: >>> I upgraded my -current laptop from r199019 to r199291 and on the newer >>> kernel wpa_supplicant runs but doesn't ever lock in. >> And the winner is .... r199076! > > What about connection without wpa_supplicant, does it work? Yes. > You did rebuild world and kernel with NO_CLEAN undefined? No, I always build with -DNO_CLEAN, in fact I think most people running -current and upgrading on a regular basis do that. Also, the traditional suggestion for upgrading is to build world and kernel, install kernel, reboot, check to make sure things are working. If a change in the kernel sources requires that something in userland be synced up it's customary to put a note about it in UPDATING. > Perhaps driver_freebsd.c from wpa_supplicant is not synced with this change. The sources were in synch. To give this the best shot at debugging quickly I updated my src tree (including the change in 199076), did 'make kernel' to build a clean one then did a clean build/install in src/usr.sbin/wpa. That didn't work either. Interestingly, the new wpa_supplicant works fine with the old kernel, so I don't think that's the issue, but that's not conclusive. I'm now doing a completely clean buildworld and kernel, I'll post again when I have some results. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/