From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 7 18:33:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5DBD5BD; Thu, 7 Nov 2013 18:33:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 65E852430; Thu, 7 Nov 2013 18:33:09 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id e16so777027qcx.34 for ; Thu, 07 Nov 2013 10:33:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=vOJuNYOkapFgaQ2jhQf+nGFSJbENG1XrDR65HeOp8Vo=; b=Nd7GzsjHQhGb5GCJHX1sSzIvpe99i54GIu645SFS388dBgFzMxP9ccE3JCp81jd7UC G4/hOdmA61fVYpTO4bosgDE4a7zMpTiK/tdWzn3lwbwseVUQWV2SlanGKpbxi0OtR0Vw l5ETA+gQRtK0TmeSW2e2K/tbkrSXrTkcuZJwz1H/OB72Q2SA7bBjbEUnIopXTyW8xFVX Vvb+cDu3ITAFuK+YUEwPrR1ZFA8V5+x/W1aPjooj00TVT5YEdrBj+KF0Tbsh+ljij4W2 cNJ4FCs+c9JIBYRn+c2C+eum7dpi0akEclI6QWoAKoGFcSISh9+lQT+nmmqlENxa+9yB 48Fg== MIME-Version: 1.0 X-Received: by 10.224.28.130 with SMTP id m2mr16581657qac.98.1383849188572; Thu, 07 Nov 2013 10:33:08 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Thu, 7 Nov 2013 10:33:08 -0800 (PST) In-Reply-To: <1383847701.1866.2.camel@localhost> References: <1383847701.1866.2.camel@localhost> Date: Thu, 7 Nov 2013 10:33:08 -0800 X-Google-Sender-Auth: URamG3tLeas0i2Vq5DPnfNJXH1U Message-ID: Subject: Re: [iwn] my first attempt at porting cedric's hardware update patches over From: Adrian Chadd To: Sean Bruno Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 18:33:09 -0000 I can't stay associated to Y!Guest with wpa_supplicant (11n). Connecting without wpa_supplicant works out very very well. So, maybe wpa_supplicant is bitching. It has 'locally_generated=1' which I believe says "wpa_supplicant made the decision!" Can you check your wpa_supplicant logs and see if the reason(s) it gives is locally generated? Would you also try connecting to Y!Guest without wpa_supplicant? Thanks! -adrian On 7 November 2013 10:08, Sean Bruno wrote: > On Tue, 2013-11-05 at 17:15 -0800, Adrian Chadd wrote: >> Hi, >> >> So: >> >> http://people.freebsd.org/~adrian/iwn/20131105-iwn-update-works-full-5100-5.diff >> >> This is my attempt at merging in all of Cedric's work to date, _minus_ >> the PAN stuff. Ie, it's only the hardware addons. It turns out that >> it's not that big a change - a large part of the diff is just the >> config options. >> >> The biggest annoyance here is the calibration stuff. If the wrong >> calibration commands are sent up (ie, not all of them, in the right >> order!) then the firmware just panics after association. >> >> So, all I've done thus far is test it on my Intel 5100. Next is >> testing it on the 4965. After that, I'll try the 6xxx, 2xxx and 1xxx / >> 100 series stuff. >> >> I'd appreciate some testing of this. It's against -HEAD, so yes, >> you'll have to run -HEAD. >> >> Thanks, >> >> >> >> -adrian >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > > > Initial test looks good. I've enabled bluetooth to make sure that it > doesn't break iwn(4) and I see no issues running on wireless. > > I reverted my hack to disable 11N support and iwn(4) still has serious > issues negotiating with my $DAYJOB wireless APs. So, I'm still running > with 11N disabled for now. > > sean