From owner-freebsd-wireless@FreeBSD.ORG Sun Sep 7 19:34:30 2014 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 ESMTPS id 10BB44FD; Sun, 7 Sep 2014 19:34:30 +0000 (UTC) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD43711EE; Sun, 7 Sep 2014 19:34:29 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id uy5so10203452obc.32 for ; Sun, 07 Sep 2014 12:34:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Hgut8GQCLF11rwMghkN85WFLcffoqsH2dMrixApVlm4=; b=TUWKADc6nX1YsYO1dfN96+Z68wnVfn+Dxm6jylgYtzdzzDju4i1fSiTTgzmQ9hTB+z AlOyxmtwEIcZ5uNsSjOsBp6N8J+slvLaNZh3a0YSTIoz1LN9tTzKhN4QWe74x/fbwuS5 VeViBD4977Qd79LeAt7b+ATUrEMFil0mfrydiS/LoxkZWH7TMM7jb/94smarO7dWIqHY p8PBbNfCNGdy4s1NhQbbj9sFCsTWVyiJ0ekwCsbVf3R8bwKvQK9kH2/riPs1TorhDa5G ZovSzkqWKnoowK5yGAX0arT9HzfZYzBfixxiVPdsmjBVz9IEnbaeBbFndO0RdrFFaLYJ /bqw== MIME-Version: 1.0 X-Received: by 10.182.60.232 with SMTP id k8mr26539208obr.54.1410118469021; Sun, 07 Sep 2014 12:34:29 -0700 (PDT) Received: by 10.182.28.100 with HTTP; Sun, 7 Sep 2014 12:34:28 -0700 (PDT) In-Reply-To: References: Date: Sun, 7 Sep 2014 21:34:28 +0200 Message-ID: Subject: Re: Intel Centrino Wireless-N 2230 status From: Oliver Pinter To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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: Sun, 07 Sep 2014 19:34:30 -0000 I think no. I'm running with this settings: iwn0: flags=8843 metric 0 mtu 2290 ether 60:6c:66:7b:af:75 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 60:6c:66:7b:af:75 inet 10.0.0.102 netmask 0xffffff00 broadcast 10.0.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g status: associated ssid hellooo channel 3 (2422 MHz 11g) bssid c0:4a:00:ea:5a:ea regdomain ETSI country HU authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme roaming MANUAL And these lines are in rc.conf in working case: wlans_iwn0="wlan0" ifconfig_wlan0="WPA NOSYNCDHCP country HU -powersave -ht" and these in not working case: wlans_iwn0="wlan0" ifconfig_wlan0="WPA NOSYNCDHCP country HU -powersave" On 9/5/14, Adrian Chadd wrote: > Also, do you run this with -bgscan ? > > > -a > > > On 5 September 2014 12:26, Adrian Chadd wrote: >> Hi! >> >> This is just an iwn panic. Did your actual -HEAD kernel panic? >> >> Try doing this with sysctl dev.iwn.0.debug=0xff; let's see what >> happens just before the firmware loses its mind. >> >> Thanks! >> >> >> -a >> >> >> On 5 September 2014 12:22, Oliver Pinter wrote: >>> I got the attached iwn panic, even if running in -ht mode. In between >>> I have a working connection. >>> I set up now a serial console and try to enable the ht mode with >>> debugging. >>> >>> On 9/3/14, Oliver Pinter wrote: >>>> Or not, I forgot the -ht option in rc.conf. >>>> >>>> G STA + G AP = ok >>>> G STA + N AP = ok >>>> N STA + N AP = fail >>>> >>>> On 9/3/14, Oliver Pinter wrote: >>>>> Hi! >>>>> >>>>> Small status update: >>>>> The mode N works too, I mistyped the other AP's passwork. >>>>> So both mode G and mode N working after the backports. >>>>> >>>>> BTW, can you MFC the same changes to 10.1? >>>>> >>>>> On 9/2/14, Adrian Chadd wrote: >>>>>> Hi, >>>>>> >>>>>> Compile it with IWN_DEBUG, then >>>>>> >>>>>> sysctl dev.iwn.0.debug=0x1 >>>>>> >>>>>> >>>>>> -a >>>>>> >>>>>> >>>>>> On 2 September 2014 12:41, Oliver Pinter >>>>>> wrote: >>>>>>> I not tried freebsd-head yet, but I'm able today. In mode N seems >>>>>>> like >>>>>>> the NIC sends only one frame, and no more. >>>>>>> >>>>>>> With tcpdump and/or wlandebug I see only rx packets and no tx. >>>>>>> >>>>>>> If you add some pointer what changes must I create to easier debug, >>>>>>> or >>>>>>> what concrete information required, feel free to ping me or send the >>>>>>> details. >>>>>>> >>>>>>> On 9/2/14, Adrian Chadd wrote: >>>>>>>> Cool! Have you tried freebsd-head? Does it work there? >>>>>>>> >>>>>>>> How's it failing in association state? What's it saying? >>>>>>>> >>>>>>>> >>>>>>>> -a >>>>>>>> >>>>>>>> >>>>>>>> On 2 September 2014 12:30, Oliver Pinter >>>>>>>> wrote: >>>>>>>>> Hi All! >>>>>>>>> >>>>>>>>> After I backported all of the net80211 and iwn changes from >>>>>>>>> 11-CURRENT >>>>>>>>> to 10-STABLE the wireless NIC in subject working on mode G. If I >>>>>>>>> try >>>>>>>>> to use with mode N (ht20, ht40) it failed in association state. >>>>>>>>> >>>>>>>>> All of the backports are in this github repo: >>>>>>>>> >>>>>>>>> https://github.com/opntr/opBSD/commits/op/stable/10-iwn-backport >>>>>>>>> >>>>>>>>> Oliver >>>>>>>> >>>>>> >>>>> >>>> >