Date: Tue, 8 Mar 2016 23:44:12 -0500 From: Eric McCorkle <eric@metricspace.net> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Atheros 9462 detected but nonfunctional Message-ID: <39A2E398-BABF-40B0-AE61-813CA1546D89@metricspace.net> In-Reply-To: <CAJ-VmomUhKHvPSmSwqadC_ttoT%2BCD8Z=dk2y57g0QR9Sgciw1g@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Sadly, no effect. However, the Bluetooth system does seem to timeout shortl= y after detection, which lends support to your diagnosis. > On Mar 8, 2016, at 20:56, Adrian Chadd <adrian.chadd@gmail.com> wrote: >=20 > Try setting this in /boot/<whatever>.hints : >=20 > hint.ath.0.btcoex_profile=3D"wb222" >=20 > Then reboot. >=20 > It should output this: >=20 > ath0: Enabling WB222 BTCOEX >=20 > .. during boot. Try that and see what happens! >=20 >=20 >=20 > -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39A2E398-BABF-40B0-AE61-813CA1546D89>