Date: Wed, 9 Mar 2016 08:42:03 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: Eric McCorkle <eric@metricspace.net> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Atheros 9462 detected but nonfunctional Message-ID: <CAJ-Vmo=TF0BiZTLNG0XBzwGJ_f%2BL5px_kYdDATvNJZm1bvq8NQ@mail.gmail.com> In-Reply-To: <1F4E1FE8-5D38-4CB6-ACC2-2F0BC1E11FF0@metricspace.net> References: <86B2B57E-A595-490E-9A9A-67F14EA5BB90@metricspace.net> <CAJ-Vmo=zVkywvd%2B0zJjzxw6ZVFEXDuCgwEqe1U2OrdzhpVx7sA@mail.gmail.com> <92F6E55B-B086-4589-B37D-F2F85F8390E7@metricspace.net> <CAJ-Vmo=Qg5-8EbSkbsivf7VBhSwe52y4WTHgfS36%2Bi6ADROaFA@mail.gmail.com> <3FBFFC30-0504-4948-A2D3-3AAC3E0FCC7E@metricspace.net> <CAJ-Vmo=0MoVsaYWf0n7FcGaT72YPevYbvfCX_-1n8JSwuD5Rcw@mail.gmail.com> <2466598D-721C-4C05-870A-136A562C581B@metricspace.net> <CAJ-Vmo=S351qENbp-uBtgsKCRFE7GOorzgrv0c1tN4OzNsUf=Q@mail.gmail.com> <3FACAF7E-007B-440B-91AC-6AA60C4A6AE1@metricspace.net> <CAJ-Vmonea2qN7PC9dbyz=gwnNSRQCzx-K6bRfGPrDRiCJwUUvQ@mail.gmail.com> <5DC254C0-75A9-4C9B-A197-EBFFB87B4D01@metricspace.net> <CAJ-Vmon1x8-f9wCUG8XE-C0i7=aYTBcwamN7G1y73Q8AsDvk-Q@mail.gmail.com> <CAJ-VmomP34JTTEc6_TrA8Pe7VDgGp6HTvO1e8iTv7WwU3DQvtg@mail.gmail.com> <B120816E-98F2-42DA-BB4B-B9365C9A23D2@metricspace.net> <CAJ-VmomUhKHvPSmSwqadC_ttoT%2BCD8Z=dk2y57g0QR9Sgciw1g@mail.gmail.com> <CAJ-Vmon27Lngq2jLoJJtaTgGQSaryzQcTahb6nSVjeDGV_ocCA@mail.gmail.com> <1F4E1FE8-5D38-4CB6-ACC2-2F0BC1E11FF0@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <eric@metricspace.net> 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 <adrian.chadd@gmail.com> 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" <eric@metricspace.net> 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 <adrian.chadd@gmail.com> wrote: >> > >> > Try setting this in /boot/<whatever>.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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=TF0BiZTLNG0XBzwGJ_f%2BL5px_kYdDATvNJZm1bvq8NQ>