Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Apr 2014 12:28:45 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        Anthony Jenkins <scoobi_doo@yahoo.com>
Cc:        tzoi516 <tzoi516@gmail.com>, "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
Subject:   Re: Atheros AR9565
Message-ID:  <CAJ-Vmom7vHQzd_W=Z_o=Jco_oBDHZhz98conrpioWjin76Nn6Q@mail.gmail.com>
In-Reply-To: <1397225391.66561.YahooMailNeo@web140701.mail.bf1.yahoo.com>
References:  <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> <CAJ-Vmom3DhiX=a2RziV%2B1YV5WUhO30=83Y%2Brxi6GRJ8Z_7qcJw@mail.gmail.com> <1397075717.20022.YahooMailNeo@web140701.mail.bf1.yahoo.com> <CAJ-Vmon4PBYuYcjak2ovXJh4E1uQuuJ0jo1PHf32oGqdfFgcyw@mail.gmail.com> <534695C8.8000802@yahoo.com> <CAJ-Vmo=URbd_xu0cQfkRX126wru3PUHAjDHhMk6urqsy56Yo4g@mail.gmail.com> <1397225391.66561.YahooMailNeo@web140701.mail.bf1.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
It could be a GPIO rfkill setup thing that requires ACPI hacking.

Honestly - the easiest way to get it going is for someone to spring
the $500 or so and by me one. :-)


-a


On 11 April 2014 07:09, Anthony Jenkins <scoobi_doo@yahoo.com> wrote:
> I'll stick -CURRENT back on it and see if it works...
>
> Nope, my AR9565 won't connect to an access point.  The wireless LED on th=
e HP ENVY Sleekbook wireless key is amber (off) and pressing Fn+wireless ke=
y doesn't do anything.  GPIO or something?  I can get you log output from '=
wpa_supplicant -d -d' or ath(4) debug messages or whatever, or can send the=
 device (I kinda wanna keep the laptop :-) ).
>
> Anthony
>
>
> ----- Original Message -----
> From: Adrian Chadd <adrian@freebsd.org>
> To: Anthony Jenkins <Scoobi_doo@yahoo.com>
> Cc: tzoi516 <tzoi516@gmail.com>; "freebsd-wireless@freebsd.org" <freebsd-=
wireless@freebsd.org>
> Sent: Thursday, April 10, 2014 12:25 PM
> Subject: Re: Atheros AR9565
>
> Hm,
>
> I think someone needs to buy me one of these. The AR9565 that I had
> tried on worked fine.
>
>
> -a
>
>
>
> On 10 April 2014 05:59, Anthony Jenkins <Scoobi_doo@yahoo.com> wrote:
>> HP ENVY 6Z-1100 Sleekbook
>>
>> Sorry, tried replying with a URL to HP's product website, but must've go=
tten blocked.  Also my original (brief) email thread on my AR9565 was in Ju=
ly '13, not August.
>>
>> Anthony
>>
>> On 04/09/2014 05:18 PM, Adrian Chadd wrote:
>>> Which HP laptop?
>>>
>>>
>>> -a
>>>
>>>
>>> On 9 April 2014 13:35, Anthony Jenkins <scoobi_doo@yahoo.com> wrote:
>>>> Hey, I've got one of these babies in my HP laptop; I actually posted s=
ome problems I was having to the list back in Aug. '13.  I could loan you m=
ine and/or assist with debugging if I can have it back (can make do with an=
 external wireless device).
>>>>
>>>>
>>>> Anthony
>>>>
>>>>
>>>> ________________________________
>>>> From: Adrian Chadd <adrian@freebsd.org>
>>>> To: tzoi516 <tzoi516@gmail.com>
>>>> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
>>>> Sent: Wednesday, April 9, 2014 3:02 PM
>>>> Subject: Re: Re: Atheros AR9565
>>>>
>>>>
>>>> Hi,
>>>>
>>>> The AR9565 is a relatively new chip that hasn't really been thoroughly
>>>> tested in FreeBSD. Laptop manufacturers have also gone and done some
>>>> rather silly things to save cost on the wireless NIC itself and I'm
>>>> not sure those patches / work arounds are in -HEAD.
>>>>
>>>> please file a PR with this problem complete with your pciconf -lv
>>>> output as above.
>>>>
>>>> Thanks!
>>>>
>>>>
>>>> -a
>>>>
>>>>
>>>> On 9 April 2014 05:40, tzoi516 <tzoi516@gmail.com> wrote:
>>>>> I'm using the GENERIC kernel. Want me to create a custom kernel?
>>>>>
>>>>> pciconf info:
>>>>>
>>>>> hostb0@pci0:0:0:0:    class=3D0x060000 card=3D0xfa401179 chip=3D0x0c0=
48086
>>>>> rev=3D0x06 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Haswell DRAM Controller'
>>>>>     class      =3D bridge
>>>>>     subclass   =3D HOST-PCI
>>>>> pcib1@pci0:0:1:0:    class=3D0x060400 card=3D0xfa471179 chip=3D0x0c01=
8086
>>>>> rev=3D0x06 hdr=3D0x01
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Haswell PCI Express x16 Controller'
>>>>>     class      =3D bridge
>>>>>     subclass   =3D PCI-PCI
>>>>> vgapci1@pci0:0:2:0:    class=3D0x030000 card=3D0xfa471179 chip=3D0x04=
168086
>>>>> rev=3D0x06 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Haswell Integrated Graphics Controller'
>>>>>     class      =3D display
>>>>>     subclass   =3D VGA
>>>>> hdac0@pci0:0:3:0:    class=3D0x040300 card=3D0xfa4d1179 chip=3D0x0c0c=
8086
>>>>> rev=3D0x06 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Haswell HD Audio Controller'
>>>>>     class      =3D multimedia
>>>>>     subclass   =3D HDA
>>>>> xhci0@pci0:0:20:0:    class=3D0x0c0330 card=3D0xfa401179 chip=3D0x8c3=
18086
>>>>> rev=3D0x04 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point USB xHCI Host Controller'
>>>>>     class      =3D serial bus
>>>>>     subclass   =3D USB
>>>>> none0@pci0:0:22:0:    class=3D0x078000 card=3D0xfa401179 chip=3D0x8c3=
a8086
>>>>> rev=3D0x04 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point MEI Controller'
>>>>>     class      =3D simple comms
>>>>> ehci0@pci0:0:26:0:    class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c2=
d8086
>>>>> rev=3D0x04 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point USB Enhanced Host Controller'
>>>>>     class      =3D serial bus
>>>>>     subclass   =3D USB
>>>>> hdac1@pci0:0:27:0:    class=3D0x040300 card=3D0xfa4d1179 chip=3D0x8c2=
08086
>>>>> rev=3D0x04 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point High Definition Audio Controller'
>>>>>     class      =3D multimedia
>>>>>     subclass   =3D HDA
>>>>> pcib2@pci0:0:28:0:    class=3D0x060400 card=3D0xfa401179 chip=3D0x8c1=
08086
>>>>> rev=3D0xd4 hdr=3D0x01
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point PCI Express Root Port'
>>>>>     class      =3D bridge
>>>>>     subclass   =3D PCI-PCI
>>>>> pcib3@pci0:0:28:2:    class=3D0x060400 card=3D0xfa401179 chip=3D0x8c1=
48086
>>>>> rev=3D0xd4 hdr=3D0x01
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point PCI Express Root Port'
>>>>>     class      =3D bridge
>>>>>     subclass   =3D PCI-PCI
>>>>> pcib4@pci0:0:28:3:    class=3D0x060400 card=3D0xfa401179 chip=3D0x8c1=
68086
>>>>> rev=3D0xd4 hdr=3D0x01
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point PCI Express Root Port'
>>>>>     class      =3D bridge
>>>>>     subclass   =3D PCI-PCI
>>>>> ehci1@pci0:0:29:0:    class=3D0x0c0320 card=3D0xfa401179 chip=3D0x8c2=
68086
>>>>> rev=3D0x04 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point USB Enhanced Host Controller'
>>>>>     class      =3D serial bus
>>>>>     subclass   =3D USB
>>>>> isab0@pci0:0:31:0:    class=3D0x060100 card=3D0xfa401179 chip=3D0x8c4=
98086
>>>>> rev=3D0x04 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point LPC Controller'
>>>>>     class      =3D bridge
>>>>>     subclass   =3D PCI-ISA
>>>>> none1@pci0:0:31:3:    class=3D0x0c0500 card=3D0xfa401179 chip=3D0x8c2=
28086
>>>>> rev=3D0x04 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point SMBus Controller'
>>>>>     class      =3D serial bus
>>>>>     subclass   =3D SMBus
>>>>> atapci0@pci0:0:31:5:    class=3D0x010185 card=3D0xfa401179 chip=3D0x8=
c098086
>>>>> rev=3D0x04 hdr=3D0x00
>>>>>     vendor     =3D 'Intel Corporation'
>>>>>     device     =3D 'Lynx Point 2-port SATA Controller 2 [IDE mode]'
>>>>>     class      =3D mass storage
>>>>>     subclass   =3D ATA
>>>>> vgapci0@pci0:1:0:0:    class=3D0x030200 card=3D0xfa471179 chip=3D0x12=
9210de
>>>>> rev=3D0xa1 hdr=3D0x00
>>>>>     vendor     =3D 'NVIDIA Corporation'
>>>>>     class      =3D display
>>>>>     subclass   =3D 3D
>>>>> ath0@pci0:3:0:0:    class=3D0x028000 card=3D0x061211ad chip=3D0x00361=
68c
>>>>> rev=3D0x01 hdr=3D0x00
>>>>>     vendor     =3D 'Atheros Communications Inc.'
>>>>>     device     =3D 'AR9565 Wireless Network Adapter'
>>>>>     class      =3D network
>>>>> none2@pci0:4:0:0:    class=3D0x020000 card=3D0xfa401179 chip=3D0x10a1=
1969
>>>>> rev=3D0x10 hdr=3D0x00
>>>>>     vendor     =3D 'Atheros Communications Inc.'
>>>>>     class      =3D network
>>>>>     subclass   =3D ethernet
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 04/08/14 18:29, Adrian Chadd wrote:
>>>>>> hi,
>>>>>>
>>>>>> ok. Can you please do a pciconf -lv and attach it here?
>>>>>>
>>>>>> Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in =
your kernel?
>>>>>>
>>>>>> Do a 'sysctl dev.ath.0.txagg=3D1' and then paste the output in dmesg=
 here.
>>>>>>
>>>>>>
>>>>>>
>>>>>> -a
>>>>>>
>>>>>>
>>>>>> On 8 April 2014 13:38, tzoi516 <tzoi516@gmail.com> wrote:
>>>>>>> OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig=
 ath0
>>>>>>> up I received a ton of these:
>>>>>>>
>>>>>>> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?!
>>>>>>> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=3D0, nbufs=3D128?
>>>>>>>
>>>>>>> received those about 20 times then this:
>>>>>>>
>>>>>>> ath0: ath_edma_recv_proc_queue: Q1: NULL bf?
>>>>>>>
>>>>>>> And now the top 2 are slowly scrolling.
>>>>>>>
>>>>>>> Mike
>>>>>>>
>>>>>>>
>>>>>>> On 04/08/14 16:03, Adrian Chadd wrote:
>>>>>>>> Right. It sounds like it's not associated.
>>>>>>>>
>>>>>>>> Try wlandebug +assoc and then run wpa_supplicant
>>>>>>>>
>>>>>>>>
>>>>>>>> -a
>>>>>>>>
>>>>>>>>
>>>>>>>> On 8 April 2014 12:21, tzoi516 <tzoi516@gmail.com> wrote:
>>>>>>>>> Sorry for another email, the errors are sporadic. I'm trying to f=
ind the
>>>>>>>>> ioctl errors that I get on shutdown.
>>>>>>>>> These are after logging in:
>>>>>>>>>
>>>>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
>>>>>>>>> dhclient[1001]: send_packet: Invalid argument
>>>>>>>>> dhclient[1001]: send_packet: No buffer space available
>>>>>>>>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
>>>>>>>>> dhclient[1001]: send_packet: No buffer space available
>>>>>>>>> dhclient[1001]: send_packet: Invalid argument
>>>>>>>>> dhclient[1001]: send_packet: Network is down
>>>>>>>>>
>>>>>>>>> Mike
>>>>>>>>>
>>>>>>>>> On 04/08/14 14:38, Adrian Chadd wrote:
>>>>>>>>>> Ah. Can you post the buffer errors you're seeing?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -a
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 8 April 2014 11:37, tzoi516 <tzoi516@gmail.com> wrote:
>>>>>>>>>>> On 04/08/14 14:23, Adrian Chadd wrote:
>>>>>>>>>>>> It should work fine on -10 and HEAD. Is it not working fine?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> -a
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 8 April 2014 09:12, tzoi516 <tzoi516@gmail.com> wrote:
>>>>>>>>>>>>> I have a Toshiba Satellite S55-A5169
>>>>>>>>>>>>> This specific one:
>>>>>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_psk=
k6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html)
>>>>>>>>>>>>>
>>>>>>>>>>>>> It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR=
9565. For
>>>>>>>>>>>>> it to work I have to change the SATA Controller Mode in the B=
IOS from
>>>>>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information h=
elps, and
>>>>>>>>>>>>> it's the only AHCI setting I can tweak.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Mike
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> freebsd-wireless@freebsd.org mailing list
>>>>>>>>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>>>>>>>>>>>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscrib=
e@freebsd.org"
>>>>>>>>>>> With SATA controller mode set to Compatibility then it works, b=
ut a
>>>>>>>>>>> little wonky at startup - sometimes I'll have to run wpa_suppli=
cant -i
>>>>>>>>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error =
appears.
>>>>>>>>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0=
 list
>>>>>>>>>>> scan and see available networks but I can't connect to any exce=
pt for
>>>>>>>>>>> unprotected networks.
>>>>>>>>>>>
>>>>>>>>>>> I'm currently running FreeBSD 10.0-STABLE
>>>>>>>>>>> Mike
>>>>>
>>>>> _______________________________________________
>>>>> freebsd-wireless@freebsd.org mailing list
>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>>>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebs=
d.org"
>>>> _______________________________________________
>>>> freebsd-wireless@freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>>>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd=
.org"
>>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom7vHQzd_W=Z_o=Jco_oBDHZhz98conrpioWjin76Nn6Q>