From owner-freebsd-wireless@freebsd.org Wed Mar 9 20:52:31 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 93DF4AC9E31 for ; Wed, 9 Mar 2016 20:52:31 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id 4C08817D for ; Wed, 9 Mar 2016 20:52:31 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [10.209.139.169] (mobile-107-107-60-117.mycingular.net [107.107.60.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 1E65F14DA; Wed, 9 Mar 2016 20:52:30 +0000 (UTC) User-Agent: K-9 Mail for Android In-Reply-To: References: <86B2B57E-A595-490E-9A9A-67F14EA5BB90@metricspace.net> <2466598D-721C-4C05-870A-136A562C581B@metricspace.net> <3FACAF7E-007B-440B-91AC-6AA60C4A6AE1@metricspace.net> <5DC254C0-75A9-4C9B-A197-EBFFB87B4D01@metricspace.net> <1F4E1FE8-5D38-4CB6-ACC2-2F0BC1E11FF0@metricspace.net> <5A6F6CD5-F987-4772-9227-291C321490FA@metricspace.net> MIME-Version: 1.0 Subject: Re: Atheros 9462 detected but nonfunctional From: Eric McCorkle Date: Wed, 09 Mar 2016 15:52:28 -0500 To: Adrian Chadd CC: freebsd-wireless@freebsd.org Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.21 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, 09 Mar 2016 20:52:31 -0000 Thanks for the help. In the mean time, I'll see if I can diagnose the resume issue. On March 9, 2016 1:40:43 PM EST, Adrian Chadd wrote: >Okm I bought a NIC and pigtails. I'll see what happens. >On Mar 9, 2016 9:41 AM, "Eric McCorkle" wrote: > >> Yes. The log message showed up. >> >> On March 9, 2016 11:42:03 AM EST, Adrian Chadd > >> wrote: >>> >>> Ok, it may not be exactly the same as the WB222 module (that's in >the >>> chromebook c720.) I'll have to go poke around in ath9k to see how >>> they've set it up. >>> >>> When you added that hints entry, did it log what I said? >>> >>> >>> -adrian >>> >>> >>> On 9 March 2016 at 04:46, Eric McCorkle >wrote: >>> >>>> I took off the back panel. There are three codes, aside from the >MAC >>>> address: >>>> >>>> S/N WCBN802AAAC434007684 >>>> Atheros model QCNFA222 >>>> BD ID 3010B377E299 >>>> >>>> It's an NGFF (M.2) card. >>>> >>>> On Mar 9, 2016, at 00:16, Adrian Chadd >wrote: >>>> >>>> Ok. I need to know the part number of the device and what >Bluetooth chip it >>>> has I can see what ath9k does for this part. >>>> >>>> If it's mini pcie then let's see if theyll send >>>> me just the NIC. >>>> >>>> Adrian >>>> >>>> On Mar 8, 2016 8:44 PM, "Eric McCorkle" >wrote: >>>> >>>>> >>>>> Sadly, no effect. However, the Bluetooth system does seem to >timeout >>>>> shortly after detection, which lends support to your diagnosis. >>>>> >>>>> On Mar 8, 2016, at 20:56, Adrian Chadd >wrote: >>>>>> >>>>>> Try setting this in /boot/.hints : >>>>>> >>>>>> hint.ath.0.btcoex_profile="wb222" >>>>>> >>>>>> Then reboot. >>>>>> >>>>>> It should output this: >>>>>> >>>>>> ath0: Enabling WB222 BTCOEX >>>>>> >>>>>> .. during boot. Try that and see what happens! >>>>>> >>>>>> >>>>>> >>>>>> -adrian >>>>>> >>>>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-wireless@freebsd.org Wed Mar 9 21:06:42 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 737ACAC840F for ; Wed, 9 Mar 2016 21:06:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::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 391A9C9E for ; Wed, 9 Mar 2016 21:06:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-ig0-x22f.google.com with SMTP id ig19so2360647igb.0 for ; Wed, 09 Mar 2016 13:06:42 -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; bh=SO0IVbOFGot5hxUCGCBTeOc1QtkHqWRJ56QRVX5o2Sk=; b=D6EAWiJi7zhZDKEEkN2BDYAKcgLQAW28ewBIdWS+ZRFiGNaqLo63OPQ50wGXsJ9/5M 3e4ApLx8Z18+YnYCEbRESEQ+hNuYFZ8FzMcQj5geNi6s66lcUnx7KXccaAzOojaqCx0M Pa8mrNXd8562lwmvMp/N3VzOBE3PP1fY8bdyoEBthuKFVXeAL0OX8MpndqMSUwN02dDB atoyxKAN0CUfeUJgSn3ignOJqnu3uUlvuhOnC/N0E1aEY2rz+t0lidhMK1UNPJsl+043 0MDIghAIjDl2T7YmlOH+hCB2RGQjfrl41RsclqJhi9gZIAGUNZvbjDzsCAewlccFlnLv 399A== 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; bh=SO0IVbOFGot5hxUCGCBTeOc1QtkHqWRJ56QRVX5o2Sk=; b=T20g3PhAU287tSLKbQmxl3s2iIYBdDZy2NcgaihP1ZZsIqMH5/jHmYzbo+c4s3lXHv rNbtu1ViCZCudNTAn1xxGrVL3UWURNMZu1k6lgtngPt613ukeLTXp9OQvJIMY66s/7yZ KtRkRLsuXmCO/UymvNfGkzJvzHDQIxOfgnVdCQJwkHUTric7E4mcOYFwt28hWdcUfy7O W677lx2rKVguxI2MguXSCjsRf5+vd5noFHZWz6jssikpaVzUC05OHo+qJRWxO4WLOcar SBTPvWs7aAqvz6jzZomvnMkjVcmxLy1+tg43Kc+DAXXVC8XWi+v5CnUEl1IFok6JDdZV fENQ== X-Gm-Message-State: AD7BkJKL8/CJHtCWVeybnd+7zAHJz33LK9TK8OWmduvtv/S6U7R7S+QRu5LHZRyWjMXcXo2Ynv4xOItaJj19qg== MIME-Version: 1.0 X-Received: by 10.50.78.200 with SMTP id d8mr387898igx.61.1457557601598; Wed, 09 Mar 2016 13:06:41 -0800 (PST) Received: by 10.36.14.19 with HTTP; Wed, 9 Mar 2016 13:06:41 -0800 (PST) In-Reply-To: References: <86B2B57E-A595-490E-9A9A-67F14EA5BB90@metricspace.net> <2466598D-721C-4C05-870A-136A562C581B@metricspace.net> <3FACAF7E-007B-440B-91AC-6AA60C4A6AE1@metricspace.net> <5DC254C0-75A9-4C9B-A197-EBFFB87B4D01@metricspace.net> <1F4E1FE8-5D38-4CB6-ACC2-2F0BC1E11FF0@metricspace.net> <5A6F6CD5-F987-4772-9227-291C321490FA@metricspace.net> Date: Wed, 9 Mar 2016 13:06:41 -0800 Message-ID: Subject: Re: Atheros 9462 detected but nonfunctional From: Adrian Chadd To: Eric McCorkle Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.21 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, 09 Mar 2016 21:06:42 -0000 if it's haswell, then it's likely related to drm. Try updating to the latest -head and try again. -a On 9 March 2016 at 12:52, Eric McCorkle wrote: > Thanks for the help. In the mean time, I'll see if I can diagnose the resume issue. > > On March 9, 2016 1:40:43 PM EST, Adrian Chadd wrote: >>Okm I bought a NIC and pigtails. I'll see what happens. >>On Mar 9, 2016 9:41 AM, "Eric McCorkle" wrote: >> >>> Yes. The log message showed up. >>> >>> On March 9, 2016 11:42:03 AM EST, Adrian Chadd >> >>> wrote: >>>> >>>> Ok, it may not be exactly the same as the WB222 module (that's in >>the >>>> chromebook c720.) I'll have to go poke around in ath9k to see how >>>> they've set it up. >>>> >>>> When you added that hints entry, did it log what I said? >>>> >>>> >>>> -adrian >>>> >>>> >>>> On 9 March 2016 at 04:46, Eric McCorkle >>wrote: >>>> >>>>> I took off the back panel. There are three codes, aside from the >>MAC >>>>> address: >>>>> >>>>> S/N WCBN802AAAC434007684 >>>>> Atheros model QCNFA222 >>>>> BD ID 3010B377E299 >>>>> >>>>> It's an NGFF (M.2) card. >>>>> >>>>> On Mar 9, 2016, at 00:16, Adrian Chadd >>wrote: >>>>> >>>>> Ok. I need to know the part number of the device and what >>Bluetooth chip it >>>>> has I can see what ath9k does for this part. >>>>> >>>>> If it's mini pcie then let's see if theyll send >>>>> me just the NIC. >>>>> >>>>> Adrian >>>>> >>>>> On Mar 8, 2016 8:44 PM, "Eric McCorkle" >>wrote: >>>>> >>>>>> >>>>>> Sadly, no effect. However, the Bluetooth system does seem to >>timeout >>>>>> shortly after detection, which lends support to your diagnosis. >>>>>> >>>>>> On Mar 8, 2016, at 20:56, Adrian Chadd >>wrote: >>>>>>> >>>>>>> Try setting this in /boot/.hints : >>>>>>> >>>>>>> hint.ath.0.btcoex_profile="wb222" >>>>>>> >>>>>>> Then reboot. >>>>>>> >>>>>>> It should output this: >>>>>>> >>>>>>> ath0: Enabling WB222 BTCOEX >>>>>>> >>>>>>> .. during boot. Try that and see what happens! >>>>>>> >>>>>>> >>>>>>> >>>>>>> -adrian >>>>>>> >>>>>> >>> -- >>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>> > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > 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"