Re: Atheros 9462 detected but nonfunctional
Did you get a chance to play with it yet? 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-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Ok, then you'll have to wait until we hit broadwell support. :P -a ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Nope, it's broadwell. On March 9, 2016 4:06:41 PM EST, Adrian Chadd wrote: >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-unsubscr...@freebsd.org" -- 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-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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. > ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 > ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
I will contact Purism to get the full details. If you have any additional questions, let me know. I can also ask them for any Linux patches they may have submitted. I know they had some folks working on it. If you're right, though, this will kill two issues at once. On March 8, 2016 8:11:56 PM EST, Adrian Chadd wrote: >Hm, can you take a photo of the wifi NIC? Do you mind opening your >laptop up and taking some photos? :) > > >-a -- 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-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Hm, can you take a photo of the wifi NIC? Do you mind opening your laptop up and taking some photos? :) -a ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Aaahahaha okay. I think we have to bring up the bluetooth coexistence configuration before it'll do any data - the default antenna configuration is likely completely wrong! Uhm, okay. Are there any teardowns on this hardware? like, which NIC it is? (WB-222? AR5B22?) -a ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Yes. On March 8, 2016 7:29:27 PM EST, Adrian Chadd wrote: >Oh wait, does this have atheros bluetooth too? > > >-a -- 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-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Oh wait, does this have atheros bluetooth too? -a ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Full dmesg attached. This is where it gets weird. The scan sees nothing. But you're right; the card sees something. Those registers change over time. On March 8, 2016 6:44:08 PM EST, Adrian Chadd wrote: >Ok, do: > >wlandebug -i wlan0 +scan > >then re-do the scan and see what's listed in dmesg. > >I mean, it's seeing /something/. > > > >-adrian -- Sent from my Android device with K-9 Mail. Please excuse my brevity. dmesg Description: Binary data ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Ok, do: wlandebug -i wlan0 +scan then re-do the scan and see what's listed in dmesg. I mean, it's seeing /something/. -adrian ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
Weird. The scan showed nothing. vmstat shows irq19 ath0998 3 (typing on a phone, so the spacing is different) On March 8, 2016 5:44:53 PM EST, Adrian Chadd wrote: >ok, does 'ifconfig wlan0 list scan' show anything? > >It's showing that the air is busy (TFCNT, RFCNT, RCCNT, CCCNT) so the >radio and PHY is on. > >what's vmstat -ia | grep ath0 show? > > >-adrian > >On 8 March 2016 at 14:40, Eric McCorkle wrote: >> 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 > >> 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 >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 > 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 >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@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >> "freebsd-wireless-unsubscr...@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. -- 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-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
ok, does 'ifconfig wlan0 list scan' show anything? It's showing that the air is busy (TFCNT, RFCNT, RCCNT, CCCNT) so the radio and PHY is on. what's vmstat -ia | grep ath0 show? -adrian On 8 March 2016 at 14:40, Eric McCorkle wrote: > 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 > 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 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 >>> 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 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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to > "freebsd-wireless-unsubscr...@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. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 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 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 > >> 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 >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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@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. athregs Description: Binary data pciconf Description: Binary data ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 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 > 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 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@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to >>> "freebsd-wireless-unsubscr...@freebsd.org" > > > -- > 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-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 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 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@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >"freebsd-wireless-unsubscr...@freebsd.org" -- 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-unsubscr...@freebsd.org"
Re: Atheros 9462 detected but nonfunctional
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 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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Atheros 9462 detected but nonfunctional
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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
