From owner-freebsd-wireless@FreeBSD.ORG Wed Apr 9 19:28:08 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A3C24BC; Wed, 9 Apr 2014 19:28:08 +0000 (UTC) Received: from mail-qg0-x22a.google.com (mail-qg0-x22a.google.com [IPv6:2607:f8b0:400d:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D99D514AB; Wed, 9 Apr 2014 19:28:07 +0000 (UTC) Received: by mail-qg0-f42.google.com with SMTP id q107so2890528qgd.29 for ; Wed, 09 Apr 2014 12:28:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=8Ask2//aeADCgdsGjy1i7ceRyncaf9Jrs5WoqJYkdZE=; b=HJ6kVyakbF6Md30cgMh2D7YXdtHiqF+YDXn5KOON0rvgOJdYAeoL55LTCZZ+sJk2jX veFH33BlvsYdtuyZirIekTkAkiKIorwNC1TCo4Jm6MhAjRvtvnQjwPVdkG5M+Ri3juis PHuFYKpT7mxtg9aZXmtQHzJRscuQPWAz6yINQq9I+va8IrNzhQOJvI/EQBeaRLZmahjC oS/fRKhw7/nzmNe6bpm/7W/N1JFpelMvaBVTx/N5hELGh2PYDSgGwmiCnhnO/GDmEXRU weaUuO9BusWgVh79zBW4khTilHUG/OAWmSv0EagVqIG8ed3tEs5y68823TEBc0pK6+z3 NetQ== X-Received: by 10.224.65.67 with SMTP id h3mr15103689qai.43.1397071686958; Wed, 09 Apr 2014 12:28:06 -0700 (PDT) Received: from lpnix002.local (static-68-239-84-57.washdc.east.verizon.net. [68.239.84.57]) by mx.google.com with ESMTPSA id m2sm3317921qac.3.2014.04.09.12.28.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Apr 2014 12:28:06 -0700 (PDT) Message-ID: <53459F44.2010102@gmail.com> Date: Wed, 09 Apr 2014 15:28:04 -0400 From: tzoi516 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Atheros AR9565 References: <53453F74.5000403@gmail.com> <53453FB5.20707@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2014 19:28:08 -0000 Hi, Thanks for all of the help. Where is the driver source code? I'll submit a PR today. Thanks, Mike On 04/09/14 15:02, Adrian Chadd wrote: > 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 wrote: >> I'm using the GENERIC kernel. Want me to create a custom kernel? >> >> pciconf info: >> >> hostb0@pci0:0:0:0: class=0x060000 card=0xfa401179 chip=0x0c048086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell DRAM Controller' >> class = bridge >> subclass = HOST-PCI >> pcib1@pci0:0:1:0: class=0x060400 card=0xfa471179 chip=0x0c018086 >> rev=0x06 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Haswell PCI Express x16 Controller' >> class = bridge >> subclass = PCI-PCI >> vgapci1@pci0:0:2:0: class=0x030000 card=0xfa471179 chip=0x04168086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell Integrated Graphics Controller' >> class = display >> subclass = VGA >> hdac0@pci0:0:3:0: class=0x040300 card=0xfa4d1179 chip=0x0c0c8086 >> rev=0x06 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Haswell HD Audio Controller' >> class = multimedia >> subclass = HDA >> xhci0@pci0:0:20:0: class=0x0c0330 card=0xfa401179 chip=0x8c318086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB xHCI Host Controller' >> class = serial bus >> subclass = USB >> none0@pci0:0:22:0: class=0x078000 card=0xfa401179 chip=0x8c3a8086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point MEI Controller' >> class = simple comms >> ehci0@pci0:0:26:0: class=0x0c0320 card=0xfa401179 chip=0x8c2d8086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB Enhanced Host Controller' >> class = serial bus >> subclass = USB >> hdac1@pci0:0:27:0: class=0x040300 card=0xfa4d1179 chip=0x8c208086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point High Definition Audio Controller' >> class = multimedia >> subclass = HDA >> pcib2@pci0:0:28:0: class=0x060400 card=0xfa401179 chip=0x8c108086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> pcib3@pci0:0:28:2: class=0x060400 card=0xfa401179 chip=0x8c148086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> pcib4@pci0:0:28:3: class=0x060400 card=0xfa401179 chip=0x8c168086 >> rev=0xd4 hdr=0x01 >> vendor = 'Intel Corporation' >> device = 'Lynx Point PCI Express Root Port' >> class = bridge >> subclass = PCI-PCI >> ehci1@pci0:0:29:0: class=0x0c0320 card=0xfa401179 chip=0x8c268086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point USB Enhanced Host Controller' >> class = serial bus >> subclass = USB >> isab0@pci0:0:31:0: class=0x060100 card=0xfa401179 chip=0x8c498086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point LPC Controller' >> class = bridge >> subclass = PCI-ISA >> none1@pci0:0:31:3: class=0x0c0500 card=0xfa401179 chip=0x8c228086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point SMBus Controller' >> class = serial bus >> subclass = SMBus >> atapci0@pci0:0:31:5: class=0x010185 card=0xfa401179 chip=0x8c098086 >> rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Lynx Point 2-port SATA Controller 2 [IDE mode]' >> class = mass storage >> subclass = ATA >> vgapci0@pci0:1:0:0: class=0x030200 card=0xfa471179 chip=0x129210de >> rev=0xa1 hdr=0x00 >> vendor = 'NVIDIA Corporation' >> class = display >> subclass = 3D >> ath0@pci0:3:0:0: class=0x028000 card=0x061211ad chip=0x0036168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR9565 Wireless Network Adapter' >> class = network >> none2@pci0:4:0:0: class=0x020000 card=0xfa401179 chip=0x10a11969 >> rev=0x10 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> class = network >> subclass = 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=1' and then paste the output in dmesg here. >>> >>> >>> >>> -a >>> >>> >>> On 8 April 2014 13:38, tzoi516 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=0, nbufs=128? >>>> >>>> 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 wrote: >>>>>> Sorry for another email, the errors are sporadic. I'm trying to find 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 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 wrote: >>>>>>>>>> I have a Toshiba Satellite S55-A5169 >>>>>>>>>> This specific one: >>>>>>>>>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_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 AR9565. For >>>>>>>>>> it to work I have to change the SATA Controller Mode in the BIOS from >>>>>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, 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-unsubscribe@freebsd.org" >>>>>>>> With SATA controller mode set to Compatibility then it works, but a >>>>>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -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 except 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@freebsd.org"