Atheros 9462 detected but nonfunctional

[Eric McCorkle]

Attached.  Both pciconf and athregs

The price of the laptop varies based on what options you pick.  However, its supply chain is pretty backlogged at the moment, so expect delays if you order one. 

On March 8, 2016 8:45:05 AM EST, Adrian Chadd <adrian.chadd at gmail.com> wrote:
>compile and use 'athregs'. For now, you need to manually use it on
>wlan0 after it's created (it no longer works on ath0):
>
>athregs -i wlan0
>
>And report back what it says.
>
>I bet it's just rfkill and we need to configure it up properly. How
>much is the laptop?
>
>
>
>
>-adrian
>
>
>On 8 March 2016 at 05:42, Eric McCorkle <eric at metricspace.net> wrote:
>> There are, but I've tried flipping it on and off to no avail. Also,
>the
>> current setting is confirmed to be on in Linux.
>>
>>
>> Just to make absolute certain I'm not screwing something up, what is
>the
>> best way to see what the card is doing at the low level?
>>
>> On March 8, 2016 8:38:42 AM EST, Adrian Chadd
><adrian.chadd at gmail.com>
>> wrote:
>>>
>>> i wonder if its an rfkill switch setting. Is there an rfkill switch
>or
>>> button?
>>>
>>>
>>> -a
>>>
>>>
>>> On 8 March 2016 at 05:29, Eric McCorkle <eric at metricspace.net>
>wrote:
>>>>
>>>>  Hello,
>>>>
>>>>  I am trying to diagnose an issue with an Atheros 9462 card.  The
>card is
>>>> being detected, and seemingly works (reports no errors with
>wpa_supplicant
>>>> and friends), however, the radios seem completely nonfunctional, as
>the card
>>>> doesn't actually transmit or receive anything (I checked by turning
>on
>>>> packet logging and running scans/wpa_supplicant).
>>>>
>>>>  There are errors reported in pciconf (it claims they are
>correctable
>>>> errors): receiver error, bad tlp, bad dllp.  The Bluetooth
>subsystem also
>>>> suffered timeouts (very likely related).
>>>>
>>>>  I have confirmed this is not a hardware problem by booting into
>Linux
>>>> with a live
>>>> memstick and running a scan.
>>>>
>>>>  I'm looking for advise on likely root causes and how to go about
>>>> diagnosing the problem (I've never diagnosed a problem on a
>*supported* card
>>>> in FreeBSD before, so I'm relatively unfamiliar with the process).
>>>>
>>>>  Best,
>>>>  Eric
>>>> ________________________________
>>>>
>>>>  freebsd-wireless at freebsd.org mailing list
>>>>  https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>>>>  To unsubscribe, send any mail to
>>>> "freebsd-wireless-unsubscribe at freebsd.org"
>>
>>
>> --
>> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: athregs
Type: application/octet-stream
Size: 2772 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-wireless/attachments/20160308/24125553/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pciconf
Type: application/octet-stream
Size: 8131 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-wireless/attachments/20160308/24125553/attachment-0001.obj>