Date: Mon, 16 Nov 2009 10:53:11 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Paul B Mahol <onemda@gmail.com> Cc: freebsd-current@freebsd.org, Rui Paulo <rpaulo@freebsd.org> Subject: Re: wpa_supplicant + wpi0 won't lock in on today's -current Message-ID: <4B019F97.6040209@FreeBSD.org> In-Reply-To: <3a142e750911160035m520819eqdf261c0c493bf3c3@mail.gmail.com> References: <4B0087C2.9070508@FreeBSD.org> <4B00BA99.5000009@FreeBSD.org> <3a142e750911160035m520819eqdf261c0c493bf3c3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul B Mahol wrote: > On 11/16/09, Doug Barton <dougb@freebsd.org> 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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B019F97.6040209>