From owner-freebsd-wireless@freebsd.org Sun Jan 24 20:22:45 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 566C7A1D9DE for ; Sun, 24 Jan 2016 20:22:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C8B88D7 for ; Sun, 24 Jan 2016 20:22:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x231.google.com with SMTP id 1so133581986ion.1 for ; Sun, 24 Jan 2016 12:22:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=t1K7CKVthHjkBbWjtDXTjd83Rakah4ZBEF2SbQXiolY=; b=rX5ukQ197U2YFZrMmfrp7waT5EurdkUMQh2EoEbqpJlHOjnV8xJDzGpY6rFkSygfdB 2P1j3zYr0j1is5eTnbxRRTxsbqAP1mAonxcMpm9MqQPJFr4hXrvhmb53WOJHL18IClfp 7avsbFOB95IhsbUJrAFYuuiesvU8lo1G7UwTm9ISIhcju0Po7sl5PdyHCzD4oWBPUD5c mG4S1N6X7IgmHFz+HxDdLDZizpNISpJFLAQqucUyFWtVkcJNyxHADya2rTc8wEVCbJO/ /FBMrMQX5nPfXIQeOFq0GCjSMm5MVQN9I76thIr+DhAtkeHcQS+N/ySVIIyijbiwCGZO wlwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:content-type; bh=t1K7CKVthHjkBbWjtDXTjd83Rakah4ZBEF2SbQXiolY=; b=TS8pHrxA6Ds4TjJ/LNz557MXOLwzo0PznEj2Xl77EDas+RVQg9AvGYqmvqxAl30mmg De307+8HL1vNEQi5SQ5F+IaMHDRXo4LNW49dAEHVG73wEB8XRama4VP51LrRS7WWsjZL ljPbHSLbjvzRDRXH6iCiZiSXVQD1kwkP6ol/pL7HSQ0ZuIhvpY9tELmYfsUMtxJIGAED GMOjAoEn1IN0kLeJI+clysUyIffl1stjHXodOKHHPZD0QH9ZfPEliVvM3SgCYv6/eRPQ JZ3csOyjBK5kiZc0rRxSeiSYcrR1T7EFZD7IOXCikjQ571FEE9bsCDga/r9RnltellXZ 7asg== X-Gm-Message-State: AG10YOQBXsHXKvS720ZGsNkqPjKt/iwVi4n5dp8Y5OoT/H9qIGZwBVGQusBE1TSF7jeJu8XsBZl5bOvH0ossOQ== MIME-Version: 1.0 X-Received: by 10.107.11.162 with SMTP id 34mr13180147iol.165.1453666964616; Sun, 24 Jan 2016 12:22:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.121.16 with HTTP; Sun, 24 Jan 2016 12:22:44 -0800 (PST) Date: Sun, 24 Jan 2016 12:22:44 -0800 X-Google-Sender-Auth: G0LspyarM5b-MSDbVZhlvII3RsU Message-ID: Subject: net80211: why we ca'nt use the net80211 taskqueue for everything From: Adrian Chadd To: Andriy Voskoboinyk , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 24 Jan 2016 20:22:45 -0000 hi, andriy has a few reviews out that tidy up some things, which I'd reply to, but .. reviews is offline. So, here's the 30 second version: * the net80211 taskqueue runs the software scan engine, and the software scan engine currently sleeps whilst it's running. This means that if you put newstate, deferred transmit, etc into the net80211 taskqueue, then it just won't run during scan. The net80211 software scan thing should be modified to not sleep whilst it's waiting for scan results and instead just kick off another timer event to finish that part of the loop. Then yes, we can just migrate * to the net80211 task queue and use it for all serialisation of a wifi driver. (And yes, I'd like to see that done ASAP..) Thanks, -adrian From owner-freebsd-wireless@freebsd.org Sun Jan 24 21:01:20 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD94E7C09 for ; Sun, 24 Jan 2016 21:01:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A568C1DA for ; Sun, 24 Jan 2016 21:01:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0OL01jJ036435 for ; Sun, 24 Jan 2016 21:01:20 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201601242101.u0OL01jJ036435@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-wireless@FreeBSD.org Subject: Problem reports for freebsd-wireless@FreeBSD.org that need special attention Date: Sun, 24 Jan 2016 21:01:20 +0000 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 24 Jan 2016 21:01:20 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open | 169433 | [iwn] iwn(4) doesn't support 6235 chip. 6 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Sun Jan 24 21:40:44 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2BEC9D99DE for ; Sun, 24 Jan 2016 21:40:44 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4402D762; Sun, 24 Jan 2016 21:40:44 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-lf0-x22f.google.com with SMTP id h129so74751024lfh.3; Sun, 24 Jan 2016 13:40:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:to:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=rAQ++9ypzbYA2BM89EsZeJ2GGjigXyslkFFRB3j+l1I=; b=Jcud1Cj97NgeBxRcCkGZzFIZbDlhbWedLtWZZaJwnRMHQrTqv2v/hvnina/d6YrGnA ErH+ss10Bvzm5+nfz/8c2rg0/S+addtmLnmBEQMq70/Wn3pkRG1DnJ5aXEpAiz1lNM3h kpCkwtX/lsa3TEBiyi9WCGVjs2oyr/jjMqxZGFdwStCvCQuf9tKeNLeYrT1gGBIXSY6W k1ajoElcOJTQ9kwKJMGzgp5iQODaT7adN2jlKdXkM3skcM7mODKzFdG/4B0pqs92wDgN yo4zWL3bIFRX5i1xz/QKWyPbdEKVsEsPi8Ue9EH/+Qj0OZ/WXKdS5m3ZW+tqanUlU5Vh JpsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:to:subject:references:date :mime-version:content-transfer-encoding:from:message-id:in-reply-to :user-agent; bh=rAQ++9ypzbYA2BM89EsZeJ2GGjigXyslkFFRB3j+l1I=; b=GvOx8xF5fH1cQNNYeQAjDc7Wqtfsycl/YEEsarqpEofAAbY/Oq+uzMHka5IS9YRw7P z/IwhxJXEMdcANBhtb4M0s7VBLHFnzArrZdLe9WIYuen3bCkWD6XkaVIh4Mpz2/vKuME 0pSiCQjJ08IKWV1SGA+wGpy38fU9TOxJ/nwHLYLcbBMWZOUCDwM1kLv5I8OBf2YpQFut EDZ28jkkgwLP49jbXnzHGUX0QqFwmml5UVr3aEGF8mjX0ynY4YJQ3wUViS+d8WhTp6Nd GUKSqw+sqnbvXAxX51sHB+Kch+67qrPltinA7Av7SAcgECadhq2bEIOFPO6qk9wT1t00 HpZg== X-Gm-Message-State: AG10YOQ3YsDNlxgx7w3uxUTWYkUJd+SeN9eNxOEqLu52BcvwD9ur1pvYH/mR0g1YMaBYZw== X-Received: by 10.25.136.139 with SMTP id k133mr5088555lfd.157.1453671642309; Sun, 24 Jan 2016 13:40:42 -0800 (PST) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id th4sm2248500lbb.46.2016.01.24.13.40.41 (version=TLS1 cipher=AES128-SHA bits=128/128); Sun, 24 Jan 2016 13:40:41 -0800 (PST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Adrian Chadd" , "freebsd-wireless@freebsd.org" Subject: Re: net80211: why we ca'nt use the net80211 taskqueue for everything References: Date: Sun, 24 Jan 2016 23:40:40 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 24 Jan 2016 21:40:44 -0000 Sun, 24 Jan 2016 22:22:44 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Adrian Chadd = : Hi, is it actual for wpi(4) / iwn(4) ? > hi, > > andriy has a few reviews out that tidy up some things, which I'd reply= > to, but .. reviews is offline. So, here's the 30 second version: > > * the net80211 taskqueue runs the software scan engine, and the > software scan engine currently sleeps whilst it's running. > > This means that if you put newstate, deferred transmit, etc into the > net80211 taskqueue, then it just won't run during scan. > > The net80211 software scan thing should be modified to not sleep > whilst it's waiting for scan results and instead just kick off another= > timer event to finish that part of the loop. Then yes, we can just > migrate * to the net80211 task queue and use it for all serialisation > of a wifi driver. > > (And yes, I'd like to see that done ASAP..) > > Thanks, > > > -adrian From owner-freebsd-wireless@freebsd.org Sun Jan 24 22:01:07 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E34EB7016 for ; Sun, 24 Jan 2016 22:01:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF53720C for ; Sun, 24 Jan 2016 22:01:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x229.google.com with SMTP id z14so23731207igp.1 for ; Sun, 24 Jan 2016 14:01:06 -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:content-transfer-encoding; bh=aagu4sqyVToks9GgyYt0aHcWDD4xL06KSOzF8WZKB3s=; b=m0steyUEU8uOBliFpyQhfxgGElC8u4vo1x/a1mkfwPj0mc5wERc2bApjGp3O2kmeeS 6mWs4cLdQ8W54CiABUue1V5achd3Eh6Xh/A4Sxgck8Puvs3xxf8p661rqdKZFtJOTJi2 D0k4OZIAyTo1ynG/ITe6bLp7eBAi/j+N3J81Kylmbt5DPactIM9bEK9bVEYL9cCPumeQ 7rbUitSbQUHm1ClHRQ/ygdLq2JU5q3QHltFskdzh8N88xdCI26Isq4Nd9fbWOthB8818 /bW1bO9/RD5N6FgZTk8liX1A1M0xLDDl58QgFoTe05lR2vH6Zi/PvbOUeMgwFK7hbDX9 JXgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=aagu4sqyVToks9GgyYt0aHcWDD4xL06KSOzF8WZKB3s=; b=FSMY2dMPUvNuAH/YW6UQ3esdK1zivpNlQQ3b3H5Kb7rZ0Icburr5Q6YdJGwlGgMKUz 4KKl6E23+BxP2E/NKosITpWRznE/l7f3Tc6CuNiTDlzEdpvc8NI2KfN7a81lTvonBrak Y7lslG2/+CvX+GPfpwbc0K5stxz2knprtOgJhMzzYhwJWvaBvMq1ljko/sNddPKZ0060 j+JrwGiticNwJ2N+NYmGjTddNKH66MIhKuhQM9P4+9Xk5x7eI9FBLgGDwxOCUGeoIYHZ UC+ebuYP7qFIIwXfWp6+2J1IaLJVn02Qtkd5ev8WB9NQWxbnsEskydHmDy9rfch2G3/e 6Y0w== X-Gm-Message-State: AG10YOTpujFUvrH97yWSnlZog4FcfCUTfR3xOL7cxQBF9sNvKIsFDoNs9g0fTeTNRksrttOtoUSVOeuYljWrzg== MIME-Version: 1.0 X-Received: by 10.50.137.41 with SMTP id qf9mr13478059igb.22.1453672865939; Sun, 24 Jan 2016 14:01:05 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.121.16 with HTTP; Sun, 24 Jan 2016 14:01:05 -0800 (PST) In-Reply-To: References: Date: Sun, 24 Jan 2016 14:01:05 -0800 X-Google-Sender-Auth: vBTN1bBXl5YV258Ld_N7uaFDkHU Message-ID: Subject: Re: net80211: why we ca'nt use the net80211 taskqueue for everything From: Adrian Chadd To: Andriy Voskoboinyk Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 24 Jan 2016 22:01:07 -0000 On 24 January 2016 at 13:40, Andriy Voskoboinyk wrote: > Sun, 24 Jan 2016 22:22:44 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Adrian Chadd > : > > Hi, > > is it actual for wpi(4) / iwn(4) ? If you defer things like tx, calibration, etc then yeah - you'll see things like software generated probe request frames and such be deferred. (I tried this with ath(4) about 5 years ago - hit the same issue. So I've put it off until the scan code is "fixed".) -adrian > > >> hi, >> >> andriy has a few reviews out that tidy up some things, which I'd reply >> to, but .. reviews is offline. So, here's the 30 second version: >> >> * the net80211 taskqueue runs the software scan engine, and the >> software scan engine currently sleeps whilst it's running. >> >> This means that if you put newstate, deferred transmit, etc into the >> net80211 taskqueue, then it just won't run during scan. >> >> The net80211 software scan thing should be modified to not sleep >> whilst it's waiting for scan results and instead just kick off another >> timer event to finish that part of the loop. Then yes, we can just >> migrate * to the net80211 task queue and use it for all serialisation >> of a wifi driver. >> >> (And yes, I'd like to see that done ASAP..) >> >> Thanks, >> >> >> -adrian From owner-freebsd-wireless@freebsd.org Mon Jan 25 15:23:11 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF1E2A45D07 for ; Mon, 25 Jan 2016 15:23:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C06F82B1 for ; Mon, 25 Jan 2016 15:23:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0PFNBnQ057206 for ; Mon, 25 Jan 2016 15:23:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 206334] [ath] panic integer divide fault Date: Mon, 25 Jan 2016 15:23:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: krisb@interia.eu X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Mon, 25 Jan 2016 15:23:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206334 --- Comment #2 from Kris --- (In reply to John Baldwin from comment #1) Thanks John for analysis of symptoms. Explanation sounds reasonable. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Mon Jan 25 19:51:57 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 230BFA46CEF for ; Mon, 25 Jan 2016 19:51:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1393785E for ; Mon, 25 Jan 2016 19:51:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0PJpuDQ094668 for ; Mon, 25 Jan 2016 19:51:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 163455] [ath] "bssid" in wlanN create_args does not change wlan MAC address Date: Mon, 25 Jan 2016 19:51:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 9.0-PRERELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: john@jnielsen.net X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Mon, 25 Jan 2016 19:51:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D163455 --- Comment #6 from John Nielsen --- The "bssid" parameter does indeed work on 10-STABLE and 11-CURRENT (and probably earlier?). I do seem to recall that the order of ifconfig paramete= rs makes a difference, though. Since opening this ticket I have changed my rc.= conf to have "bssid" at the beginning of the relevant lines instead of at the end and it has been working fine for some time. Excerpt from working rc.conf: wlans_ath1=3D"wlan1 wlan3" create_args_wlan1=3D"bssid wlanmode hostap mode 11g channel 1:ht/40+" create_args_wlan3=3D"bssid wlanmode hostap mode 11g channel 1:ht/40+" Excerpt from ifconfig output: wlan1: flags=3D8943 metric = 0 mtu 1500 ether 00:1b:b1:5d:XX:YY wlan3: flags=3D8943 metric = 0 mtu 1500 ether 06:1b:b1:5d:XX:YY Note the difference in the first octet of the MAC address: '00' for wlan1 a= nd '06' for wlan3. AFAIK this bug can be closed. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Tue Jan 26 06:33:48 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDC7FA47364 for ; Tue, 26 Jan 2016 06:33:48 +0000 (UTC) (envelope-from sm.1205@yahoo.com) Received: from nm49-vm4.bullet.mail.ne1.yahoo.com (nm49-vm4.bullet.mail.ne1.yahoo.com [98.138.121.132]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A32091144 for ; Tue, 26 Jan 2016 06:33:48 +0000 (UTC) (envelope-from sm.1205@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1453789907; bh=duH5/1OjTiGcJm2oB/un+Y5Pgj+bUZdzn5FxM3kLL68=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=dveuQsoj37JvTXg+CVWZRgR/zAAnCAC6JX7oMDmH61mCCHe6YWQIHhu8wk9YvmZgGG01BoD00hm0dL21kuagLG1ZWe0TCrDTHpkrr+5XKYMeIB0/br27Kk9Yki5NMQAaXZaFk2bbRt+L205BL57eYLS3X7mMVcrgtYjuj/fc6lXQVqafgtt92eeLOQ7ofI1QJlxJXzwKuXKR9z8VbDaycPIqRzjwlYJmay9qplwKRy7VpYLnp4o57QjEhzpwv1aK/L5AEKX83CUQdaKTEHKsr+tDS+P1MgDMvAbhDwYa7x8JrfWOSdI+rPRMy1LNxfpm7DYyjhGfLeylrvdds6y0pQ== Received: from [127.0.0.1] by nm49.bullet.mail.ne1.yahoo.com with NNFMP; 26 Jan 2016 06:31:47 -0000 Received: from [98.138.226.176] by nm49.bullet.mail.ne1.yahoo.com with NNFMP; 26 Jan 2016 06:29:01 -0000 Received: from [98.138.89.245] by tm11.bullet.mail.ne1.yahoo.com with NNFMP; 26 Jan 2016 06:29:01 -0000 Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 26 Jan 2016 06:29:01 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 465589.49642.bm@omp1059.mail.ne1.yahoo.com X-YMail-OSG: Cl6gzEoVM1krSjyFF8MjRr.IVtxDz.7r7yU7K5p9kcWIp4ucI8cbs8vetXdqpym bUdzzbu4jXnQdqObeAXCoSSAs8sdf37f0VXoM5JPrHqxTOeIsV4NWFl3oL.eX9uwBoNdt1jxJRxp 6E5wIoo0vnDCAygOmEn3kM8mCHmsGTSwyEqJcMvh0FdsD72b_pa.NSy1uF0fJm7lcTZ4uRzdWNO3 FA3IwWjl2kSJcf1hLI1YD5WYt9qS.LvQCXE8lZzDxN1fukjgG4UwtRQ2_sIw81toriCWYxI9xNXG gcMRKYyU8s7ZAzxfjPeg1nZ5VZhl9gkk8sGj2S1cWwIkD3HuHf63TQErfKgeVu5QK8_zU8uFsLkr rAjV_RO89EcH7WPkUrcez1gYfgdwZsA.9JT5XIHSFREf9gedTUObLoAmiwSwfolVaNqQ0xm4B8ag AjL7ndFaDJ8jeO0npZCEnQUPT37KbPnWWzVpKsUkuPqwXruzJonjwdOmhyzuZLc4- Received: by 98.138.105.253; Tue, 26 Jan 2016 06:29:01 +0000 Date: Tue, 26 Jan 2016 06:29:00 +0000 (UTC) From: Seinstein Meinstein Reply-To: Seinstein Meinstein To: "freebsd-wireless@freebsd.org" Message-ID: <1323337252.130749.1453789740508.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <1453777642.7839.2.camel@michaeleichorn.com> References: <1453777642.7839.2.camel@michaeleichorn.com> Subject: FreeBSD 11-CURRENT - WLAN (802.11) TDMA Support MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Tue, 26 Jan 2016 06:33:48 -0000 Hello All, I would like to know if the latest FreeBSD version has support for the foll= owing: 1. Fully functional TDMA (Time Division Multiple Access) in the 802.11 wire= less driver code.=20 2. What protocol version does it support? Specifically I am looking for the= latest 802.11ac/802.11n protocol support.=20 3. Can the driver code be fully cross compiled for any platform (ARM, Power= PC, etc.?)4. Where can I get the tar ball (tar.gz?). Please provide pointer= s, I can only find web access to the files. GitHub project will also help.= =C2=A0 Thanks very much in advance,Sridharan. From owner-freebsd-wireless@freebsd.org Tue Jan 26 09:54:11 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A411FA467EA for ; Tue, 26 Jan 2016 09:54:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 957DB879 for ; Tue, 26 Jan 2016 09:54:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0Q9sAaC002598 for ; Tue, 26 Jan 2016 09:54:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 163455] [ath] "bssid" in wlanN create_args does not change wlan MAC address Date: Tue, 26 Jan 2016 09:54:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 9.0-PRERELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: madpilot@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Tue, 26 Jan 2016 09:54:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D163455 --- Comment #7 from Guido Falsi --- (In reply to John Nielsen from comment #6) Thanks for your suggestion. I'll test this soon and report back. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Tue Jan 26 20:30:36 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E465A6E511 for ; Tue, 26 Jan 2016 20:30:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6ED5BD4E for ; Tue, 26 Jan 2016 20:30:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0QKUaN1056179 for ; Tue, 26 Jan 2016 20:30:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 206112] [rtwn] Under heavy load, "can't map mbuf (error 12)" arises Date: Tue, 26 Jan 2016 20:30:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: evil.lombo@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Tue, 26 Jan 2016 20:30:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206112 --- Comment #1 from Simone Mario Lombardo --- A little strange news. The issue seems arises when the laptop is booted after few hours of being s= hut down and it's related to the performance issue I cited; I need to reboot the machine twice (!) to get nice performance and not getting the error. I have put three firmware reset in a row in the if_rtwn.c and doubled the w= ait time before accessing to the registry after the reset and now the card is usable after a fresh boot. I'll test if it is sufficient to keep the wait state longer in the next day= s or it needs a "triple" firmware reset. Simone --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Wed Jan 27 18:01:19 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9203A7050E for ; Wed, 27 Jan 2016 18:01:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA15B1CB5 for ; Wed, 27 Jan 2016 18:01:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0RI1J3B031542 for ; Wed, 27 Jan 2016 18:01:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 163455] [ath] "bssid" in wlanN create_args does not change wlan MAC address Date: Wed, 27 Jan 2016 18:01:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 9.0-PRERELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: madpilot@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Wed, 27 Jan 2016 18:01:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D163455 --- Comment #8 from Guido Falsi --- (In reply to Guido Falsi from comment #7) I performed further tests as you suggested on 10.2 and everything worked out fine this time. So, I agree this bug report can be closed now. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Thu Jan 28 00:09:41 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CA3EA70A91 for ; Thu, 28 Jan 2016 00:09:41 +0000 (UTC) (envelope-from polyfemos@gmail.com) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A149AF8 for ; Thu, 28 Jan 2016 00:09:40 +0000 (UTC) (envelope-from polyfemos@gmail.com) Received: by mail-lb0-x229.google.com with SMTP id dx2so14622278lbd.3 for ; Wed, 27 Jan 2016 16:09:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:subject:mime-version:content-type :content-transfer-encoding:content-disposition; bh=BkRrSXKzZAZgXx5BskRsw565txtxL7PP3KZtF9Nwugw=; b=Eq9GIs+IeY9fycG/TWOE4rAmjkDNXIvgnH1cDxDEpZeJSx4tw4jsP3sG2okSCAgrXo GMettO69N0wXwQAiPrDl4Zzu89aVqp6qftPip1i13icl1umyWifQQwybmgDn71RpzNlV u9Y5bVnoTG+5GU153unohgXcN8RxaoDLtyYjcsmekGn+Pbx4sbuAD9U0qi+0xrZ3PSIQ mGLie3pXZYd6TR2kVkleU8LgfMwsjzJjR1PUudXrY7sBBbC65NPyj99g0KzOy78GS2SD F9ZMyLcwaXxH6BWVtk8A0qIru8o5cNAIUF4q4nrqiuibVjqDZGeqTDgiOP+KqHx7Tko3 pH1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:subject:mime-version :content-type:content-transfer-encoding:content-disposition; bh=BkRrSXKzZAZgXx5BskRsw565txtxL7PP3KZtF9Nwugw=; b=b57s54o3bC5QxTiwP9DUaz9g4dx+amDpaSpy+PQVNexWpmq9AUf9ChLJetPs9w48k0 tyFo3CIAvKoRz4Q0DOMgd/x3Tke26iHhMvW0DcGpJGlUTIpdGlRVEoJPYHGzK4ETGJU0 zjORdsaldF2Qx4QKcaP/iLQKLv2vCj2ICfU6slvfr38CD4M1Tx//OWu4MPHXxLcrUerS VFY9t3+4oso7P/WAx2bzn6GToORjxazpnVIdnYNSMS+DQsDMs//Pi3ZoPVAFqYiGLQtG G2CmzzezGsVkAOOMVkhcICoTGpvbrIVWMckNVIOhO4byhEOjFa/TnJlAnwZIDNVnnX8s IwFg== X-Gm-Message-State: AG10YORduAtFPwDq8cI5cTNpVKIYNh3ltmeigsdRUV98b/a2nFFodmdgxi671A0UH+sCpQ== X-Received: by 10.112.161.201 with SMTP id xu9mr16006lbb.35.1453939777617; Wed, 27 Jan 2016 16:09:37 -0800 (PST) Received: from [192.168.89.30] (90-86.soderhamn.com. [81.94.86.90]) by smtp.gmail.com with ESMTPSA id ke9sm1071154lbc.28.2016.01.27.16.09.36 for (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 27 Jan 2016 16:09:37 -0800 (PST) Date: Thu, 28 Jan 2016 01:09:33 +0100 From: =?utf-8?Q?Bj=C3=B6rn_Jonare?= To: freebsd-wireless@freebsd.org Message-ID: <1BDC9AFE6D7C4F7098C83D0779DAF676@gmail.com> Subject: Atheros AR9287 and 5Ghz 11n X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 28 Jan 2016 00:09:41 -0000 Hello, =20 I recently had need for working wireless on an old iMac I use for running= =46reeBSD. As the computer originally had a unsupported broadcom card I = swapped it out for an AR9287 I had in a drawer. Now, the problem is that = while the card connects fine in the 2.4Ghz it won't connect, or more prec= isely won't see anything in the 5Ghz spectrum. A command like 'ifconfig w= lan0 list regdomain' for example only lists 2.4Ghz channels. Now according to my dmesg (relevant bits below) this card has a 5Ghz radi= o (as it should). So what should I do to actually be able to actually con= nect or see anything over 5Ghz=3F ath0: mem 0xc8100000-0xc810ffff irq 17 at device 0.0 on pc= i3 ath0: =5BHT=5D enabling HT modes ath0: =5BHT=5D enabling short-GI in 20MHz mode ath0: =5BHT=5D 1 stream STBC receive enabled ath0: =5BHT=5D 1 stream STBC transmit enabled ath0: =5BHT=5D 2 RX streams; 2 TX streams ath0: AR9287 mac 384.2 R=465133 phy 15.15 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 The relevant parts of my rc.conf would be: create=5Fargs=5Fwlan0=3D=22country SE=22 ifconfig=5Fwlan0=3D=22WPA SYNCDHCP=22 -- =20 Bj=C3=B6rn Jonare Sent with Sparrow (http://www.sparrowmailapp.com/=3Fsig) From owner-freebsd-wireless@freebsd.org Thu Jan 28 00:21:52 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7A1DA70E9F for ; Thu, 28 Jan 2016 00:21:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8474CEA8 for ; Thu, 28 Jan 2016 00:21:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x232.google.com with SMTP id z14so1748098igp.1 for ; Wed, 27 Jan 2016 16:21:52 -0800 (PST) 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:content-transfer-encoding; bh=0ux9wwgUklNKgqjZ/8CmbyaI1hZ2u4fhYCOFOfNRU98=; b=uEaSL2RJwAcGD9LJZWR6dKapjoYqsl8IOYqWfSTdMAQrwQ6MlPQZzWZET1ZQNfPmUW PwP1kuuhPGDFonzjpWGyZkR3G7IpurRQb3LoLtAZVQQcpMlJjURmdTNYrOLH2bEduEpJ EGx+J05bbQ065Rg7K8x0Bkyph7WhGYsqROQ9TlJyBroPO8jPuXijqBYWMy7slWvMzuKN qV6Br9oqUPncPsZOCb3/iwwSSTUbJwub/M8vHuZhYgWbxt7Xj4TXyu7UM2EyLdicqjid B7dChDvbVyCdTmRkxvU22drrhhixcrySIKhivpl/Ov8xiCWVkRYK0uYI8eJ4RGf2WqeQ Orug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0ux9wwgUklNKgqjZ/8CmbyaI1hZ2u4fhYCOFOfNRU98=; b=eqFtm1P5N2Nz7xCv+gw/vTGKPPyWkrzeDrHg/YyEAvsQeXVS+IvRHVUfLcL/VxcYb+ nOPDhvc+IbJmsW8FJBWZWfsRnTu2CgQCKN4exhgr8kOwbjsfh3QL9c9bEpDPljtRavSX xM0H+vPjAP73vnuCCQXya4fY1buJEejEC+oc3jRxHZu3fDBFa2JgL7vfSPLFFgU3Xlix quwKirfMyZx73aj1AgHVfi9TMspSdcP2i/fobdaP5h97BMcoOZXMeJQ5O88AGXYBRcvK Yrkcdt2l3BrAPCoF5Gim23dyBlWJOwxm5IVSOfAHQeB6fiFQ1O/4wo/uyRympf5gRjKB 9TKg== X-Gm-Message-State: AG10YOTScBe21Q6MthnaIwu/g3eNSgXzQHw73uZBn7AntqnjBk5ZpSoGl2nnCPxi091N6yUdaWbhA+npf3ZXsw== MIME-Version: 1.0 X-Received: by 10.50.178.178 with SMTP id cz18mr4387igc.37.1453940511852; Wed, 27 Jan 2016 16:21:51 -0800 (PST) Received: by 10.36.121.16 with HTTP; Wed, 27 Jan 2016 16:21:51 -0800 (PST) In-Reply-To: <1BDC9AFE6D7C4F7098C83D0779DAF676@gmail.com> References: <1BDC9AFE6D7C4F7098C83D0779DAF676@gmail.com> Date: Wed, 27 Jan 2016 16:21:51 -0800 Message-ID: Subject: Re: Atheros AR9287 and 5Ghz 11n From: Adrian Chadd To: =?UTF-8?Q?Bj=C3=B6rn_Jonare?= Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 28 Jan 2016 00:21:52 -0000 hi, ar9287 is 2ghz only. You'll need an AR9280, AR9380. -a On 27 January 2016 at 16:09, Bj=C3=B6rn Jonare wrote: > Hello, > > I recently had need for working wireless on an old iMac I use for running= FreeBSD. As the computer originally had a unsupported broadcom card I swap= ped it out for an AR9287 I had in a drawer. Now, the problem is that while = the card connects fine in the 2.4Ghz it won't connect, or more precisely wo= n't see anything in the 5Ghz spectrum. A command like 'ifconfig wlan0 list = regdomain' for example only lists 2.4Ghz channels. > > Now according to my dmesg (relevant bits below) this card has a 5Ghz radi= o (as it should). So what should I do to actually be able to actually conne= ct or see anything over 5Ghz? > > ath0: mem 0xc8100000-0xc810ffff irq 17 at device 0.0 on pc= i3 > ath0: [HT] enabling HT modes > ath0: [HT] enabling short-GI in 20MHz mode > ath0: [HT] 1 stream STBC receive enabled > ath0: [HT] 1 stream STBC transmit enabled > ath0: [HT] 2 RX streams; 2 TX streams > ath0: AR9287 mac 384.2 RF5133 phy 15.15 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > > > The relevant parts of my rc.conf would be: > > create_args_wlan0=3D"country SE" > ifconfig_wlan0=3D"WPA SYNCDHCP" > > > > > > -- > Bj=C3=B6rn Jonare > Sent with Sparrow (http://www.sparrowmailapp.com/?sig) > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@freebsd.org Thu Jan 28 09:35:16 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82818A6F4D2 for ; Thu, 28 Jan 2016 09:35:16 +0000 (UTC) (envelope-from bjorn.jonare@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 063051B10 for ; Thu, 28 Jan 2016 09:35:16 +0000 (UTC) (envelope-from bjorn.jonare@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id s81so23100209lfd.0 for ; Thu, 28 Jan 2016 01:35:15 -0800 (PST) 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 :content-type; bh=CEE1ywtQcQlMuq72cjAkK3AcArQI8TF+lXdCbCvt+gg=; b=ZFUGy0dTgOquVIvZetraLQZR6ZkHABvlRZibXGRIshW6sBzZ9g/PqGPsAPbKnFbkDh 8i7PIEHABPPbrU9qgEoxh2ZJu9ympxNsi0/TebTuQbyJxcJf/+lbaqv/Ma7Z109EdEGQ S7Znt6JlsgrJI8lxmKrrM+EDQxy3xBwkOwSdn/g8zjxirMmqhZpM6iOL1BzfMb7UfBC1 ip2V1/cJlRNzorUupyE7VlzsXiN51Dj8aXrwYw6oolMtqX24NlsxSeF/7Qy51wriQB2d /nCK3Md8ImuBLSdE+LUcdQ1Iq2K5aGqzKvNP08KgRf/rDe0UCYVD+8XXAjeS+/iwOC2m 9+nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=CEE1ywtQcQlMuq72cjAkK3AcArQI8TF+lXdCbCvt+gg=; b=UA5OfNemsG+mv/w0MTnoe7Kxzs7sDON9KhvuYJ5kUPYLnEMTjCZqowmsHxPyRR0U4I y8jBeuxU+BsKLx+soG+0yVjR3l5Oa5oT+OvUUur57hwXY08psCImqRPA4irhZy1YU0jr mhIyT3n2euRzw0bLGFYV1+NXOMwzaEzXfZCW7Yk8yrPhzV0x5+t1f1CxEDHmdYM36Qte k2v8SAi2IiUrjRwuYP29L69Zft9Svlm6W6AmvF4ozk8FAvISlwEIWVLU/LCo+iTP7Fnr y35NE8lZr04Gr9pSb0cuqydQANpd91abHxE8ybic3560qNxtni4cXp3yOfsmnGQOPTb7 GR3A== X-Gm-Message-State: AG10YORK40E9fMIUMN4PF7pJu7FIJhNHuKbqUSt4cOND0Ib6V969W+QoeNLawYX0nZwHMEzPg5i6EAn6X9ESmw== MIME-Version: 1.0 X-Received: by 10.25.64.5 with SMTP id n5mr745905lfa.89.1453973714171; Thu, 28 Jan 2016 01:35:14 -0800 (PST) Received: by 10.25.81.193 with HTTP; Thu, 28 Jan 2016 01:35:14 -0800 (PST) In-Reply-To: References: <1BDC9AFE6D7C4F7098C83D0779DAF676@gmail.com> Date: Thu, 28 Jan 2016 10:35:14 +0100 Message-ID: Subject: Re: Atheros AR9287 and 5Ghz 11n From: =?UTF-8?Q?Bj=C3=B6rn_Jonare?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 28 Jan 2016 09:35:16 -0000 2016-01-28 1:21 GMT+01:00 Adrian Chadd : > hi, > > ar9287 is 2ghz only. You'll need an AR9280, AR9380. > > > -a > > Ah, that explains the observed behavior. I sort of assumed (stupid) it supported 5Ghz since it is a 11n-card and according to dmesg, has a 5Ghz radio, oh well. Thanks for saving me from more futile reading and experimenting! From owner-freebsd-wireless@freebsd.org Thu Jan 28 17:17:55 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57494A7058C for ; Thu, 28 Jan 2016 17:17:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47C7B1648 for ; Thu, 28 Jan 2016 17:17:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0SHHsbT005317 for ; Thu, 28 Jan 2016 17:17:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 172706] [wpi] wpi0 fails to load firmware when using country Date: Thu, 28 Jan 2016 17:17:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 1.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: t@tobik.me X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 28 Jan 2016 17:17:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D172706 Tobias Kortkamp changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |t@tobik.me --- Comment #2 from Tobias Kortkamp --- FYI, seems like it is still a problem: https://forums.freebsd.org/threads/no-wi-fi.54866/ --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sat Jan 30 22:35:47 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51FECA731F8 for ; Sat, 30 Jan 2016 22:35:47 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F9F6158C for ; Sat, 30 Jan 2016 22:35:46 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from homobox.opal.com (unknown [71.255.165.9]) by outbound3.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Sat, 30 Jan 2016 22:32:33 +0000 (UTC) Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:3:21e:33ff:fe5f:cb65]) (authenticated bits=0) by homobox.opal.com (8.15.2/8.15.2) with ESMTPSA id u0UMYZIf038901 (version=TLSv1.2 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Sat, 30 Jan 2016 17:34:35 -0500 (EST) (envelope-from fbsd@opal.com) Date: Sat, 30 Jan 2016 17:34:34 -0500 From: "J.R. Oldroyd" To: freebsd-wireless@freebsd.org, freebsd-acpi@freebsd.org Subject: Toshiba L675D wifi rfkill acpi support Message-ID: <20160130173434.58cafbd1@shibato> X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (homobox.opal.com [IPv6:2001:470:8cb8:2::1]); Sat, 30 Jan 2016 17:34:35 -0500 (EST) X-Spam-Status: No, score=-0.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, T_RP_MATCHES_RCVD shortcircuit=no autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on homobox.opal.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 30 Jan 2016 22:35:47 -0000 I have just upgraded the wifi mini-PCIe adapters in some older model Toshiba laptops, specifically L305D and L675D models, to AR9280 adapters. This in order to be able to use the 5 GHz band. On the L305D, everything is working well. But on the L675D, the AR9280 radio remains off. Switching the wifi adapter to an Intel 6200 actually reports: iwn0: radio is disabled by hardware switch They both probe and initialize normally in the dmesg and you can talk to them normally using ifconfig. It is just the radio that remains off. Thing is, the L675D does not have a hardware rfkill switch. It does have Fn+F8, however. I should note that two other wifi adapters, the original RTL8191SE and also an AR9285 do both work fine in the L675D. They do not seem to see a phantom rfkill switch! But, neither of these adapters support the 5 GHz band. Despite the RTL8191SE and AR9285 working, I figured that it would be useful to have Fn+F8 working so that I could check and toggle the radio state of the AT9280. I therefore set about updating acpi_toshiba.c to support the TOS1900 HID [1]. I am still no closer, though. I was not able to enable the hotkey Fn+Fx support, so I've implemented a hw.acpi.toshiba.wireless_wifi sysctl which shows that the wifi is enabled and allows it to be toggled. Testing with one of the working adapters (AR9285) does show the wifi LED going on and off and the interface does pass or not-pass traffic accordingly. But, with the AR9280, the LED and the radio remain steadfastly off. I have studied the acpidump[2] and found that the relevant ACPI method (TOI0==0xFF00 TOI1==0x56) supports four devices: 0x0200 wifi 0x0800 unknown 0x2000 wwan (3G device, according to google) 0xFFFF unknown I have played with all of them, but still cannot get the AR9280 radio or the wifi LED on. I have not found any documentation, other than the Linux driver toshiba_acpi.c which provides no further help. Anyone have any thoughts about what is needed to enable the AR9280 (or Intel 6200) in the Toshiba L675D? Thanks, -jr [1] http://opal.com/jr/toshiba_l675d/acpi_toshiba.c [2] http://opal.com/jr/toshiba_l675d/toshiba_l675d.asl From owner-freebsd-wireless@freebsd.org Sat Jan 30 22:53:10 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FF56A7381E; Sat, 30 Jan 2016 22:53:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F3021E50; Sat, 30 Jan 2016 22:53:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x229.google.com with SMTP id h5so11347222igh.0; Sat, 30 Jan 2016 14:53:10 -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=KADa4oG+FBzgMTXz/jVzzd2SC0M8Dal4fQ4bqolktms=; b=LqwB3rH8UHTPxjlESlFDsl4hH+e+K1dbhJUOscxmFRzE0CN6CIJf6y84GLn4tgP0HS S+CCfpahBoedAY7dvQwX6zQRr4CuFWww749TBr9yOUvMcd28OO9b3gMBU3j2xjOnuXjh 7uhoKACoGkEU7E7l7/H8t9Hat7E2oR4KujPR3sCaNcjLCVBp5b/6GfsIAAsftjcyp8tF hn2PY+pGUXydUd7pdu784Titd6Zpo66sXwx7VHuLRFGR2PypaOeF9lL3+Y5plQXyl4cb PT6Ex5XMPUZ152qS/WkqZiZdfkMEEDq9+gSezHkHaNg8LeGXx9Zc7gjJiMRPTdXSwwCn qYwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=KADa4oG+FBzgMTXz/jVzzd2SC0M8Dal4fQ4bqolktms=; b=UAu2pHAq4p+UNWKRuY0FrbNVRLb0vXq24lqfRQOjwW4F4/JBUjqDY3dcSdKnRW86nf 6SrZ2yIWRscQ6QyAHoUt3GDcrnyWEksOcwXn9do2HxuobhaNsqSmqtntEPb2jq2M60GT ARZtXqMJrzkWQLoBLnAbF+HVWnBWRTGPoYFNi98QFozD0QXN3MHGX9HGM8Umx8xqugqZ HWKD6lwIO3fjAkDNKNe67aYKftlfMEUEGzhEEvMMQMGHfEaIV5Q8XlFVgZny6hqGaCNp DQqjMKg751hor8YiQouMT4vp+EQqpOH3QxvEpbp0Q5shZDGwhiuQKXp3FHAvzDSGbBU1 rYXA== X-Gm-Message-State: AG10YOTIhxRDE+EICwS8gNm1i2blZsJ5yxq5Em87jIF+rLwx1Q0wsYOHYW44qBKrWpk3DxKHJI8B5ziMIgFj1A== MIME-Version: 1.0 X-Received: by 10.50.115.40 with SMTP id jl8mr2339437igb.22.1454194389585; Sat, 30 Jan 2016 14:53:09 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.121.16 with HTTP; Sat, 30 Jan 2016 14:53:09 -0800 (PST) In-Reply-To: <20160130173434.58cafbd1@shibato> References: <20160130173434.58cafbd1@shibato> Date: Sat, 30 Jan 2016 14:53:09 -0800 X-Google-Sender-Auth: SpFXCtvWb3CquczIrEg2M0kMAcA Message-ID: Subject: Re: Toshiba L675D wifi rfkill acpi support From: Adrian Chadd To: "J.R. Oldroyd" Cc: "freebsd-wireless@freebsd.org" , "freebsd-acpi@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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: Sat, 30 Jan 2016 22:53:10 -0000 You'll have to figure out what the deal is, or disable it in the driver. The rfkill switch is either hardware or software. Yours is hardware, so I'm guessing it's one of the GPIO lines on the PCIE bus. I don't know how the intel driver figures out which GPIO line is rfkill and pays attention to it; search for that error string in the if_iwn.c driver. Chances are it's reading a register and disabling it in software. -a On 30 January 2016 at 14:34, J.R. Oldroyd wrote: > I have just upgraded the wifi mini-PCIe adapters in some older model > Toshiba laptops, specifically L305D and L675D models, to AR9280 > adapters. This in order to be able to use the 5 GHz band. > > On the L305D, everything is working well. > > But on the L675D, the AR9280 radio remains off. Switching the wifi > adapter to an Intel 6200 actually reports: > iwn0: radio is disabled by hardware switch > They both probe and initialize normally in the dmesg and you can > talk to them normally using ifconfig. It is just the radio that > remains off. > > Thing is, the L675D does not have a hardware rfkill switch. It does > have Fn+F8, however. > > I should note that two other wifi adapters, the original RTL8191SE > and also an AR9285 do both work fine in the L675D. They do not seem > to see a phantom rfkill switch! But, neither of these adapters > support the 5 GHz band. > > Despite the RTL8191SE and AR9285 working, I figured that it would be > useful to have Fn+F8 working so that I could check and toggle the > radio state of the AT9280. I therefore set about updating > acpi_toshiba.c to support the TOS1900 HID [1]. > > I am still no closer, though. I was not able to enable the hotkey > Fn+Fx support, so I've implemented a hw.acpi.toshiba.wireless_wifi > sysctl which shows that the wifi is enabled and allows it to be > toggled. Testing with one of the working adapters (AR9285) does show > the wifi LED going on and off and the interface does pass or not-pass > traffic accordingly. But, with the AR9280, the LED and the radio > remain steadfastly off. > > I have studied the acpidump[2] and found that the relevant ACPI method > (TOI0==0xFF00 TOI1==0x56) supports four devices: > 0x0200 wifi > 0x0800 unknown > 0x2000 wwan (3G device, according to google) > 0xFFFF unknown > > I have played with all of them, but still cannot get the AR9280 radio > or the wifi LED on. > > I have not found any documentation, other than the Linux driver > toshiba_acpi.c which provides no further help. > > Anyone have any thoughts about what is needed to enable the AR9280 (or > Intel 6200) in the Toshiba L675D? > > Thanks, > -jr > > [1] http://opal.com/jr/toshiba_l675d/acpi_toshiba.c > [2] http://opal.com/jr/toshiba_l675d/toshiba_l675d.asl > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"