From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 12 12:21:38 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7BDA1065673; Mon, 12 Sep 2011 12:21:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 63D938FC1E; Mon, 12 Sep 2011 12:21:38 +0000 (UTC) Received: by vxi39 with SMTP id 39so3807332vxi.13 for ; Mon, 12 Sep 2011 05:21:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=ai9fpkBiwP8aAVrtQYiGaIt9sdbK8uIinWvZynl1gmQ=; b=tcv/ePS/j8TtJN0/VithHNzUVLgOX+5pXYG5DXZw2Gih4dHIaT9BQdIHdHQu075s91 Fx7PFvZ/5sfqPty/JcXHGgu2DTc+XP5tMtzROu1vSirGjR+KQr+RIYnGQIFSnWHuwoCU ecBdX6tMl8c1OIIp/0Nm7Ouh81cHDaO2Xr6FE= MIME-Version: 1.0 Received: by 10.52.93.143 with SMTP id cu15mr2975472vdb.60.1315830097712; Mon, 12 Sep 2011 05:21:37 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.161.138 with HTTP; Mon, 12 Sep 2011 05:21:37 -0700 (PDT) Date: Mon, 12 Sep 2011 20:21:37 +0800 X-Google-Sender-Auth: wi-kXPKEQyNw_20HrrlEgAB7D9w Message-ID: From: Adrian Chadd To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mobile@freebsd.org Subject: Has ath(4) ever worked one release and not worked another, please poke me.. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 12:21:38 -0000 Hi all, I've had reports here and there from users who have said ath(4) worked for them in a previous release, and then suddenly stopped working. Either it stopped probing at all during boot, or it would probe but then spit out errors when trying to get allocated resources. There's been some recent commits to -HEAD which hopefully have resolved a class of problems that cardbus users have seen. But I'd like to know if this has popped up for anyone else. So, if you're "anyone else", and you've got an example piece of equipment and an ath(4) NIC which used to work and now doesn't, please step forward. Please only do so if you're willing to help diagnose the problem by downloading/compiling/running older kernel images and wrangling verbose boot messages from it all. It's likely going to be time consuming and quite tedious. I'd like to try and nail whatever lingering issues can be tracked down before 9.0-RELEASE if possible. Yes, this even means for older NICs (ie, the non-11n ones.) Thanks, Adrian From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 12 13:15:21 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2281106566B for ; Mon, 12 Sep 2011 13:15:21 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id B3BEB8FC1B for ; Mon, 12 Sep 2011 13:15:21 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.4/8.14.4/NETPLEX) with ESMTP id p8CD1sal015392; Mon, 12 Sep 2011 09:01:54 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.6 (mail.netplex.net [204.213.176.10]); Mon, 12 Sep 2011 09:01:54 -0400 (EDT) Date: Mon, 12 Sep 2011 09:01:54 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Adrian Chadd In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: Has ath(4) ever worked one release and not worked another, please poke me.. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 13:15:22 -0000 On Mon, 12 Sep 2011, Adrian Chadd wrote: > Hi all, > > I've had reports here and there from users who have said ath(4) worked > for them in a previous release, and then suddenly stopped working. > Either it stopped probing at all during boot, or it would probe but > then spit out errors when trying to get allocated resources. > > There's been some recent commits to -HEAD which hopefully have > resolved a class of problems that cardbus users have seen. But I'd > like to know if this has popped up for anyone else. > > So, if you're "anyone else", and you've got an example piece of > equipment and an ath(4) NIC which used to work and now doesn't, please > step forward. Please only do so if you're willing to help diagnose the > problem by downloading/compiling/running older kernel images and > wrangling verbose boot messages from it all. It's likely going to be > time consuming and quite tedious. > > I'd like to try and nail whatever lingering issues can be tracked down > before 9.0-RELEASE if possible. Yes, this even means for older NICs > (ie, the non-11n ones.) As described in previous email to -current, part of r222753 needs to be backed out in order for my cardbus ath to work. -- DE From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 12 15:21:33 2011 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E93C1065670; Mon, 12 Sep 2011 15:21:33 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id DF27E8FC12; Mon, 12 Sep 2011 15:21:32 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p8CFFGq6029356; Mon, 12 Sep 2011 09:15:16 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Mon, 12 Sep 2011 10:15:04 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <802BD398-6F6B-4584-B1AD-36FDFB23D0D2@bsdimp.com> References: To: Daniel Eischen X-Mailer: Apple Mail (2.1084) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [127.0.0.1]); Mon, 12 Sep 2011 09:15:17 -0600 (MDT) Cc: Adrian Chadd , freebsd-current@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: Has ath(4) ever worked one release and not worked another, please poke me.. X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 15:21:33 -0000 On Sep 12, 2011, at 8:01 AM, Daniel Eischen wrote: > On Mon, 12 Sep 2011, Adrian Chadd wrote: >=20 >> Hi all, >>=20 >> I've had reports here and there from users who have said ath(4) = worked >> for them in a previous release, and then suddenly stopped working. >> Either it stopped probing at all during boot, or it would probe but >> then spit out errors when trying to get allocated resources. >>=20 >> There's been some recent commits to -HEAD which hopefully have >> resolved a class of problems that cardbus users have seen. But I'd >> like to know if this has popped up for anyone else. >>=20 >> So, if you're "anyone else", and you've got an example piece of >> equipment and an ath(4) NIC which used to work and now doesn't, = please >> step forward. Please only do so if you're willing to help diagnose = the >> problem by downloading/compiling/running older kernel images and >> wrangling verbose boot messages from it all. It's likely going to be >> time consuming and quite tedious. >>=20 >> I'd like to try and nail whatever lingering issues can be tracked = down >> before 9.0-RELEASE if possible. Yes, this even means for older NICs >> (ie, the non-11n ones.) >=20 > As described in previous email to -current, part of r222753 > needs to be backed out in order for my cardbus ath to work. That's not an ath(4) issue, but a cardbus(4) issue. I'll take care of = it after the funeral when I return home, likely next week. Of course, = John can take care of it sooner if he wants. Warner From owner-freebsd-mobile@FreeBSD.ORG Fri Sep 16 17:58:45 2011 Return-Path: Delivered-To: freebsd-mobile@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2295B1065674; Fri, 16 Sep 2011 17:58:45 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id D145D8FC17; Fri, 16 Sep 2011 17:58:44 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 327E41E000E4; Fri, 16 Sep 2011 19:40:04 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.4/8.14.3) with ESMTP id p8GHbjwW042912; Fri, 16 Sep 2011 19:37:45 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.4/8.14.3/Submit) id p8GHbjD8042911; Fri, 16 Sep 2011 19:37:45 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Fri, 16 Sep 2011 19:37:45 +0200 To: freebsd-current@FreeBSD.org Message-ID: <20110916173745.GA42502@triton8.kn-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-mobile@FreeBSD.org Subject: [PATCH: iwn(4)] Fix channel switching in monitor mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2011 17:58:45 -0000 Hi! I just got a "Centrino Advanced-N 6230" half-size mini-pcie card (using iwn6000g2bfw.ko firmware, my Dell Precision M4500 laptop came with an unsupported Broadcom BCM4313: https://laptop.bsdgroup.de/freebsd/index.html?action=show_laptop_detail&laptop=13061 ), and found channel switching didn't work in monitor mode, the patch below seems to fix it - also at: http://people.freebsd.org/~nox/tmp/patch-iwn-channel-monitor.txt (I also applied the two patches from the `"Intel Centrino Advanced-N + WiMAX 6250" doesn't work' thread tho I'm not 100% sure they are needed for this nic: http://markmail.org/message/exik7phjs2j7pnsi and http://docs.freebsd.org/cgi/mid.cgi?CAAgh0_bL7K3PZVAZxPV8JwdhnopOvdRp0Z+xHU-CfGba5bz1Kw ) And here is the channel switching patch: --- src/sys/dev/iwn/if_iwn.c.orig +++ src/sys/dev/iwn/if_iwn.c @@ -6984,12 +6984,24 @@ iwn_set_channel(struct ieee80211com *ic) const struct ieee80211_channel *c = ic->ic_curchan; struct ifnet *ifp = ic->ic_ifp; struct iwn_softc *sc = ifp->if_softc; + int error; IWN_LOCK(sc); sc->sc_rxtap.wr_chan_freq = htole16(c->ic_freq); sc->sc_rxtap.wr_chan_flags = htole16(c->ic_flags); sc->sc_txtap.wt_chan_freq = htole16(c->ic_freq); sc->sc_txtap.wt_chan_flags = htole16(c->ic_flags); + + /* + * Only need to set the channel in Monitor mode. AP scanning and auth + * are already taken care of by their respective firmware commands. + */ + if (ic->ic_opmode == IEEE80211_M_MONITOR) { + error = iwn_config(sc); + if (error != 0) + device_printf(sc->sc_dev, + "error %d settting channel\n", error); + } IWN_UNLOCK(sc); }