From owner-freebsd-wireless@FreeBSD.ORG Mon May 23 11:07:12 2011 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF60A1065677 for ; Mon, 23 May 2011 11:07:11 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DF2E88FC16 for ; Mon, 23 May 2011 11:07:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4NB7BOw051854 for ; Mon, 23 May 2011 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4NB7Bs3051852 for freebsd-wireless@FreeBSD.org; Mon, 23 May 2011 11:07:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 May 2011 11:07:11 GMT Message-Id: <201105231107.p4NB7Bs3051852@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 23 May 2011 11:07:12 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/154007 wireless [ath] Atheros ar9287 card does not get recognized. o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149539 wireless [ath] atheros ar9287 is not supported by ath_hal o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/149307 wireless [ath] Doesn't work Atheros 9285 o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148112 wireless [ath] Atheros 9285 cannot register with wifi AP (timeo o kern/148078 wireless [ath] wireless networking stops functioning o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o kern/143868 wireless [ath] [patch] [request] allow Atheros watchdog timeout o conf/143079 wireless hostapd(8) startup missing multi wlan functionality o kern/140796 wireless [ath] [panic] Cannot attach (unable to attach hardware p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 49 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue May 24 12:20:14 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C894106567F for ; Tue, 24 May 2011 12:20:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5C8688FC14 for ; Tue, 24 May 2011 12:20:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4OCKEpI074669 for ; Tue, 24 May 2011 12:20:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4OCKEZc074668; Tue, 24 May 2011 12:20:14 GMT (envelope-from gnats) Date: Tue, 24 May 2011 12:20:14 GMT Message-Id: <201105241220.p4OCKEZc074668@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Dalibor Gudzic Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dalibor Gudzic 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: Tue, 24 May 2011 12:20:14 -0000 The following reply was made to PR kern/140796; it has been noted by GNATS. From: Dalibor Gudzic To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x Date: Tue, 24 May 2011 13:47:56 +0200 > From-To: freebsd-net->freebsd-wireless > By: adrian > When: Tue May 10 10:13:04 UTC 2011 > Why: Reassigning to freebsd-wireless > Submitter: is this still a problem for you? Yes, card still does NOT work in FreeBSD 8.2-RELEASE. I don't get panic any more though. I don't know if I should send a new dmesg to this PR, or rather do for PR/116444 which is PR I've submitted before, and it considers this ath card. This PR was concerning a panic that prevented system from booting. Now system boots, so I think this PR could be closed, and I should submit a follow-up dmesg on kern/116444. I have dmesg ready, so please tell me which PR should I follow-up? (Btw, I never got this last message in my inbox, that's way I didn't reply to it. Maybe I unsubscribed from the list, or something, dunno) From owner-freebsd-wireless@FreeBSD.ORG Tue May 24 12:29:53 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D09491065670 for ; Tue, 24 May 2011 12:29:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8A7BC8FC1B for ; Tue, 24 May 2011 12:29:53 +0000 (UTC) Received: by gyg13 with SMTP id 13so3241069gyg.13 for ; Tue, 24 May 2011 05:29:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gyXjBldbgTogj5dsvzh9+kumu6lkwuxkm+7zhD0vXM0=; b=jZO4UGl+V1db0VgKOBwIVq6YH/WKjvPfwGDUepPKxH1NdTGHObJJZw94GIH4YQu+T8 K9a2XUq7aYTIoa/bJEL6pZ83eLk8uU3R7PpX62iP15LKw8VTIEGdAh3OGl+XqAe7GFLY /eIy6+OI3yBLiqBRDlVWOSC4gI8InsWNd56jg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=eWR4hx3QMsdX/TkIY3AZ6nEFr6hD1zH7tAsoXXod2lcemxE+DxnFmEDl6Ff5Tuq2Ik col5r8XUGfTWbFMiten7Cg/fSLFkGFNEKpKBoW19QnymcAIfmyemgg8UC4DbbBGMK0y1 aS47NlAhMcmYOg41evim/gTSNTOyS60zdVQ54= MIME-Version: 1.0 Received: by 10.151.78.16 with SMTP id f16mr397743ybl.133.1306240192720; Tue, 24 May 2011 05:29:52 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.91.12 with HTTP; Tue, 24 May 2011 05:29:52 -0700 (PDT) In-Reply-To: <201105241220.p4OCKEZc074668@freefall.freebsd.org> References: <201105241220.p4OCKEZc074668@freefall.freebsd.org> Date: Tue, 24 May 2011 20:29:52 +0800 X-Google-Sender-Auth: j6PhA8DQWHZJU4SMQPoA-L-4-pk Message-ID: From: Adrian Chadd To: Dalibor Gudzic Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 24 May 2011 12:29:53 -0000 On 24 May 2011 20:20, Dalibor Gudzic wrote: > =A0Yes, card still does NOT work in FreeBSD 8.2-RELEASE. I don't get > =A0panic any more though. I don't know if I should send a new dmesg to > =A0this PR, or rather do for PR/116444 which is PR I've submitted before, > =A0and it considers this ath card. This PR was concerning a panic that > =A0prevented system from booting. Now system boots, so I think this PR > =A0could be closed, and I should submit a follow-up dmesg on kern/116444. > > =A0I have dmesg ready, so please tell me which PR should I follow-up? Have you tried freebsd-current? I've done quite a bit of work with the ath driver in FreeBSD-current. Please make sure you're compiling with: options ATH_DEBUG options ATH_DIAGAPI options AH_DEBUG device ath_hal option AH_SUPPORT_AR5416 and see if that works. If not, reboot with the sysctl hw.ath.hal.debug=3D0xffffffff set in /boot/loader.conf appropriately, so I can hopefully get some debugging as to why the hardware isn't waking up as expected. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Tue May 24 16:36:18 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6059E106566B for ; Tue, 24 May 2011 16:36:18 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc1-s10.snt0.hotmail.com (snt0-omc1-s10.snt0.hotmail.com [65.55.90.21]) by mx1.freebsd.org (Postfix) with ESMTP id 387D78FC18 for ; Tue, 24 May 2011 16:36:17 +0000 (UTC) Received: from SNT128-W29 ([65.55.90.7]) by snt0-omc1-s10.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 24 May 2011 09:24:16 -0700 Message-ID: X-Originating-IP: [207.107.246.139] From: Shant Kassardjian Sender: To: Date: Tue, 24 May 2011 16:24:16 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 24 May 2011 16:24:16.0851 (UTC) FILETIME=[06E75230:01CC1A2F] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: SR71-A Txpower Question X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 24 May 2011 16:36:18 -0000 Hello FreeBSD-Wireless=2C I've been running SR71-A on FreeBSD 8.1 for quite some time now and it's be= en running very well. Many thanks to Adrian Chadd who really helped ironing= out all my questions! My only problem so far that I've noticed is that when I do: ifconfig wlan0= txpower 0=3B this does not turn off power to the wireless as it's suppose = to and rather I have to bring down the interface manually to shut it down h= ence whenever I need to start it up again I have to reconfigure the interfa= ce. >From my observation it looks like changing the txpower rate using ifconfig = has little to no effect controlling this adapter. My question is that=2C could it be because I have compiled the kernel with = the following modifications as suggested by Adrian Chadd to take advantage = of Max 3x antenna transmit power that I am having this problem? Edit sys/dev/ath/ath_hal/ar5416/ar5416.h: #define AR5416_DEFAULT_RXCHAINMASK 7 #define AR5416_DEFAULT_TXCHAINMASK 7 Does anyone else have this symptom with their SR71-A (AR5416)? Many thanks in advance=3B Regards=2C Shant K. = From owner-freebsd-wireless@FreeBSD.ORG Tue May 24 16:43:22 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A179106566B for ; Tue, 24 May 2011 16:43:22 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 14B388FC08 for ; Tue, 24 May 2011 16:43:21 +0000 (UTC) Received: by ywf7 with SMTP id 7so3406827ywf.13 for ; Tue, 24 May 2011 09:43:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=aehYItMcIl3f0xO5QQ+/mhrhMy2xLDBNknUfnI7cUek=; b=EOKLi2U4Dfjb+Bx5vdbkO50LSZPtgBi//E1Cu7CzCzFbV5ZZhdxRKz2LU3b8vSaQnI 5HtYk0GXM19Ysk+N0nL9iSTsrm6Rw3q/J2xfydxLSFakU02oXnweYqP+S0C8z0zE3ANK ySpXxuRNoN2dohlKgmrPjFXKl4ls/yVP/kmPs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=gFahoI4MvSlpF+s9m1lyKLGIxikCt4FgWpiXlE65QNBEWTMuhtRM5uHvqRokJfsZYl SmzdtiQW15bHHPYC/j2+WrAz68jB05WHmzEnio6svNg19GqMkv4eGtDGjjtRCMIR5kG6 JwdNcsRE+q0BjpHnUJ7n2EQYwDUn6ehcmBTm4= MIME-Version: 1.0 Received: by 10.150.14.13 with SMTP id 13mr4476546ybn.438.1306255401261; Tue, 24 May 2011 09:43:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.91.12 with HTTP; Tue, 24 May 2011 09:43:21 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 May 2011 00:43:21 +0800 X-Google-Sender-Auth: 2Y84xxUQKdtS0iHSTQq6_6kSTek Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A Txpower Question X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 24 May 2011 16:43:22 -0000 Hi, ifconfig wlan0 txpower 0 merely sets the txpower to 0dBm, which isn't "off" strictly speaking. It's actually 1mW. The SR-71A also has a TX power offset in hardware. If I remember right, the hardware is actually a couple of dBm higher than what you configure. So when you configure 19 dBm, you're programming the hardware at 19dBm, but the hardware responds by allowing a max of 16dBm per channel, which is * 3 (3 TX chains, as per the patch I gave you) to give ~ 21dBm. I'd have to check the math to get the exact tx power offset but that's roughly what's going on. Now, if it's documented somewhere that 0 dBm should be "killing" the interface, let me know. :) Adrian On 25 May 2011 00:24, Shant Kassardjian wrote: > > Hello FreeBSD-Wireless, > > I've been running SR71-A on FreeBSD 8.1 for quite some time now and it's = been running very well. Many thanks to Adrian Chadd who really helped ironi= ng out all my questions! > > My only problem so far that I've noticed is that when I do: =A0ifconfig w= lan0 txpower 0; this does not turn off power to the wireless as it's suppos= e to and rather I have to bring down the interface manually to shut it down= hence whenever I need to start it up again I have to reconfigure the inter= face. > > >From my observation it looks like changing the txpower rate using ifconf= ig has little to no effect controlling this adapter. > > > My question is that, could it be because I have compiled the kernel with = the following modifications as suggested by Adrian Chadd to take advantage = of Max 3x antenna transmit power that I am having this problem? > > Edit sys/dev/ath/ath_hal/ar5416/ar5416.h: > > #define AR5416_DEFAULT_RXCHAINMASK =A0 =A0 =A07 > #define AR5416_DEFAULT_TXCHAINMASK =A0 =A0 =A07 > > > Does anyone else have this symptom with their SR71-A (AR5416)? > > > Many thanks in advance; > > Regards, > Shant K. > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0_______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" > From owner-freebsd-wireless@FreeBSD.ORG Tue May 24 21:17:04 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F294A106566B; Tue, 24 May 2011 21:17:04 +0000 (UTC) (envelope-from dalibor.gudzic@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id BFF4D8FC15; Tue, 24 May 2011 21:17:03 +0000 (UTC) Received: by pvg11 with SMTP id 11so4063727pvg.13 for ; Tue, 24 May 2011 14:17:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UGXs7kT7XOgcM7hyJNytWhQ23+bzwqiPnQsRZXJCZj4=; b=M93kRYP3VNcOYGb4wLSE+XRHRVkeOPYZuJefFEHvOTvpfJUq2z4NkkuKpTzS6iNOo2 AShCeFnqDe8f8CxXU8l6mgtTj7kIbqrHp2HiFXk3KsHNOzPg+PwD1cG0ariI7luMp/pe tBqv3A8eSGh9F4rmerJ8WIWlLBV855giKub+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=flkWky0n6lac0I2or35yNP4MauW8UtILfCWSkR5pwq+Cwl80WmQlC0o5onm8PE2Glh 7hxDm/ZL5scxhXCUbhz8F4SkSj2lHFEuzOzMV8gzxV83j24c1WCm0iwGxJi3fyK8bzgH INZHL91gxJTiU8DOiwhCcInHowmDJ0OJA/wQE= MIME-Version: 1.0 Received: by 10.142.142.8 with SMTP id p8mr1227205wfd.158.1306270481401; Tue, 24 May 2011 13:54:41 -0700 (PDT) Received: by 10.142.194.6 with HTTP; Tue, 24 May 2011 13:54:41 -0700 (PDT) In-Reply-To: References: <201105241220.p4OCKEZc074668@freefall.freebsd.org> Date: Tue, 24 May 2011 22:54:41 +0200 Message-ID: From: Dalibor Gudzic To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 24 May 2011 21:17:05 -0000 Hi Adrian, On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrote: > On 24 May 2011 20:20, Dalibor Gudzic wrote: > snipped > > Have you tried freebsd-current? I've done quite a bit of work with the > ath driver in FreeBSD-current. > No, but I will start downloading it now and give it a try. > Please make sure you're compiling with: > > options =A0 =A0 =A0 =A0 ATH_DEBUG > options =A0 =A0 =A0 =A0 ATH_DIAGAPI > options =A0 =A0 =A0 =A0 AH_DEBUG > device =A0 =A0 =A0 =A0 =A0ath_hal > option =A0 =A0 =A0 =A0 =A0AH_SUPPORT_AR5416 > > and see if that works. If not, reboot with the sysctl > hw.ath.hal.debug=3D0xffffffff set in /boot/loader.conf appropriately, so > I can hopefully get some debugging as to why the hardware isn't waking > up as expected. > > Thanks, > I will try with these, thanx (I'm not on FreeBSD box now). One more thing, should I post replies here or on kern/116444? Also, would you be interested in verbose dmesg from 8.2-RELEASE? Thanx for taking time for this. All best Dalibor From owner-freebsd-wireless@FreeBSD.ORG Wed May 25 06:34:16 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B7B4106566B for ; Wed, 25 May 2011 06:34:16 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 21C898FC0A for ; Wed, 25 May 2011 06:34:15 +0000 (UTC) Received: by gxk28 with SMTP id 28so3743350gxk.13 for ; Tue, 24 May 2011 23:34:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=BcfavQToup1Y2bgk63XORCtRBLD61MZVyE0JC0eoXAQ=; b=miiwRc26OAM2P2D5f6myVhN2AACiZPgrLZSjs9rPuYDrvudWT5pC3EEbr5/g7XZR49 2TQKvEW/VvW+ZUZRrSnwAfar+ypbz+nodhoDTMG6tjBmq3gPmvBf2PqA+JH0obb2cXG9 nHxCi+vv/6Vz8YBWfO3Ge31Fmo/Fv3/CzvxTs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=aMZrX1wMNnG3MQS19Il6eLF6BprgENAF6+7mNy0r3+4Lld9jf42jBlzNDPeubFriJh 9MiUiIBiS0YTc8dQqWaIGXOKrIQSj63bCRxoBfn8e3WR4qTNdVCNaSIq9dBq+FvsiTfm M8T7MH5aCbX6p6e3FTzuSmmOsq97l3noVE5X8= MIME-Version: 1.0 Received: by 10.151.78.16 with SMTP id f16mr1319357ybl.133.1306305255178; Tue, 24 May 2011 23:34:15 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.91.12 with HTTP; Tue, 24 May 2011 23:34:15 -0700 (PDT) In-Reply-To: References: <201105241220.p4OCKEZc074668@freefall.freebsd.org> Date: Wed, 25 May 2011 14:34:15 +0800 X-Google-Sender-Auth: jXhctAHgO3lfljLbyBrirr8Sk5Q Message-ID: From: Adrian Chadd To: Dalibor Gudzic Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 25 May 2011 06:34:16 -0000 I'd prefer you stick testing results on the PR; then the reply will go to freebsd-wireless@ and there's a log in the PR of it all. Adrian On 25 May 2011 04:54, Dalibor Gudzic wrote: > Hi Adrian, > > On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrote: >> On 24 May 2011 20:20, Dalibor Gudzic wrote: >> > snipped >> >> Have you tried freebsd-current? I've done quite a bit of work with the >> ath driver in FreeBSD-current. >> > > No, but I will start downloading it now and give it a try. > > >> Please make sure you're compiling with: >> >> options =A0 =A0 =A0 =A0 ATH_DEBUG >> options =A0 =A0 =A0 =A0 ATH_DIAGAPI >> options =A0 =A0 =A0 =A0 AH_DEBUG >> device =A0 =A0 =A0 =A0 =A0ath_hal >> option =A0 =A0 =A0 =A0 =A0AH_SUPPORT_AR5416 >> >> and see if that works. If not, reboot with the sysctl >> hw.ath.hal.debug=3D0xffffffff set in /boot/loader.conf appropriately, so >> I can hopefully get some debugging as to why the hardware isn't waking >> up as expected. >> >> Thanks, >> > > I will try with these, thanx (I'm not on FreeBSD box now). One more > thing, should I post replies here or on kern/116444? Also, would you > be interested in verbose dmesg from 8.2-RELEASE? > > Thanx for taking time for this. All best > > Dalibor > From owner-freebsd-wireless@FreeBSD.ORG Wed May 25 21:44:40 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4498D106566B; Wed, 25 May 2011 21:44:40 +0000 (UTC) (envelope-from dalibor.gudzic@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 126948FC12; Wed, 25 May 2011 21:44:39 +0000 (UTC) Received: by pzk27 with SMTP id 27so45067pzk.13 for ; Wed, 25 May 2011 14:44:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7Rk3AHxCTxfcPkHofzcqMO0nz34N2xx6vm4EW6dwKJQ=; b=HX5OGI1H/WEOEno+hp5JOP9wU9MhyxnX83GlQRbHDVB2YH5zXYFE+YABEVyZw9rEHe AraDylNg7iTKhCZej4XO0W0y564pomU2MNfiPVAzF+JOMRWsZmTen8pUXUqUUEU/hNdM DbZYlPBmlBwCLy6DDqdbUJMSvuwCADWbjvrCI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=h2F8UMhs7Q0b5pIHuRigJYMmd79V/4UpSYOS0Oso+hDJtxkTKZqwARj/cX77Ll/6LN ZMX51xG3Nx2q2RFKqQ1zuxsYY7eJGhY8kcRwXRd7UapyfXXnUu+dYcAWr/tSHQW7GuBp L0BlMtDJT4sxi+BMXD627QwCWLvtMur+PwJvw= MIME-Version: 1.0 Received: by 10.142.234.9 with SMTP id g9mr14794wfh.101.1306359879344; Wed, 25 May 2011 14:44:39 -0700 (PDT) Received: by 10.142.194.6 with HTTP; Wed, 25 May 2011 14:44:39 -0700 (PDT) In-Reply-To: References: <201105241220.p4OCKEZc074668@freefall.freebsd.org> Date: Wed, 25 May 2011 23:44:39 +0200 Message-ID: From: Dalibor Gudzic To: bug-followup@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 25 May 2011 21:44:40 -0000 > On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrote: > > Please make sure you're compiling with: > > options ATH_DEBUG > options ATH_DIAGAPI > options AH_DEBUG > device ath_hal > option AH_SUPPORT_AR5416 > > and see if that works. If not, reboot with the sysctl > hw.ath.hal.debug=0xffffffff set in /boot/loader.conf appropriately, so > I can hopefully get some debugging as to why the hardware isn't waking > up as expected. Here's the dmesg from 8.2-R with recompiled kernel including above options: Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RELEASE #0: Tue May 24 23:41:58 CEST 2011 root@fbsd8x.fbsd:/usr/obj/usr/src/sys/GENERIC i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) M CPU 430 @ 1.73GHz (1729.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6e8 Family = 6 Model = e Stepping = 8 Features=0xafe9fbff Features2=0xc109 TSC: P-state invariant real memory = 1610612736 (1536 MB) avail memory = 1430380544 (1364 MB) ACPI APIC Table: MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of f0013000, 1000 (3) failed acpi0: reservation of 0, a0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 agp0: aperture size is 128M pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem 0xa0000000-0xbfffffff,0xc8000000-0xc8ffffff irq 16 at device 0.0 on pci1 pcib2: irq 27 at device 2.0 on pci0 pci2: on pcib2 pcib3: irq 31 at device 3.0 on pci0 pci3: on pcib3 atapci0: port 0x60b8-0x60bf,0x60b0-0x60b3,0x6008-0x600f,0x6004-0x6007,0x6010-0x601f,0x6400-0x64ff irq 21 at device 15.0 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x60a0-0x60af at device 15.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] ata1: on atapci1 ata1: [ITHREAD] uhci0: port 0x6020-0x603f irq 20 at device 16.0 on pci0 uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0x6040-0x605f irq 22 at device 16.1 on pci0 uhci1: [ITHREAD] usbus1: on uhci1 uhci2: port 0x6060-0x607f irq 21 at device 16.2 on pci0 uhci2: [ITHREAD] usbus2: on uhci2 uhci3: port 0x6080-0x609f irq 23 at device 16.3 on pci0 uhci3: [ITHREAD] usbus3: on uhci3 ehci0: mem 0xc9400000-0xc94000ff irq 21 at device 16.4 on pci0 ehci0: [ITHREAD] usbus4: waiting for BIOS to give up control usbus4: timed out waiting for BIOS usbus4: EHCI version 1.0 usbus4: on ehci0 isab0: at device 17.0 on pci0 isa0: on isab0 vr0: port 0x6800-0x68ff mem 0xc9400400-0xc94004ff irq 23 at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x7c miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:14:0b:08:64:5b vr0: [ITHREAD] pcib4: at device 19.0 on pci0 pci4: on pcib4 pci4: at device 1.0 (no driver attached) pcib5: at device 19.1 on pci0 pci5: on pcib5 ath0: mem 0xc9000000-0xc900ffff irq 18 at device 1.0 on pci5 ath0: [ITHREAD] ar5212SetPowerModeAwake: Failed to wakeup in 40ms ar5212SetPowerModeAwake: Failed to wakeup in 40ms ath0: unable to attach hardware; HAL status 3 device_attach: ath0 attach returned 6 acpi_acad0: on acpi0 battery0: on acpi0 acpi_tz0: on acpi0 atrtc0: port 0x70-0x75 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model GlidePoint, device ID 0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 p4tcc0: on cpu0 Timecounter "TSC" frequency 1729015093 Hz quality 800 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 acd0: DVDR at ata1-master UDMA33 ad4: 57231MB at ata2-master UDMA100 SATA 1.5Gb/s uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered GEOM: ad4s3: geometry does not match label (255h,63s != 16h,63s). Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Root mount waiting for: usbus4 ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x0000 Root mount waiting for: usbus4 ugen0.2: at usbus0 ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 umass0:0:0:-1: Attached to scbus0 Trying to mount root from ufs:/dev/ad4s2a da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1910MB (3911680 512 byte sectors: 255H 63S/T 243C) GEOM: da0: partition 1 does not end on a track boundary. cryptosoft0: on motherboard GEOM_ELI: Device ad4s2f.eli created. GEOM_ELI: Encryption: AES-XTS 128 GEOM_ELI: Crypto: software GEOM_ELI: Device ad4s2b.eli created. GEOM_ELI: Encryption: AES-XTS 256 GEOM_ELI: Crypto: software I will now try the -CURRENT snapshot and let you know how it went. Thanks Dalibor From owner-freebsd-wireless@FreeBSD.ORG Wed May 25 21:50:14 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B55DF1065720 for ; Wed, 25 May 2011 21:50:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 786DB8FC1A for ; Wed, 25 May 2011 21:50:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4PLoEF0045592 for ; Wed, 25 May 2011 21:50:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4PLoE21045591; Wed, 25 May 2011 21:50:14 GMT (envelope-from gnats) Date: Wed, 25 May 2011 21:50:14 GMT Message-Id: <201105252150.p4PLoE21045591@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Dalibor Gudzic Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dalibor Gudzic 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, 25 May 2011 21:50:14 -0000 The following reply was made to PR kern/140796; it has been noted by GNATS. From: Dalibor Gudzic To: bug-followup@FreeBSD.org Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x Date: Wed, 25 May 2011 23:44:39 +0200 > On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrote: > > Please make sure you're compiling with: > > options ATH_DEBUG > options ATH_DIAGAPI > options AH_DEBUG > device ath_hal > option AH_SUPPORT_AR5416 > > and see if that works. If not, reboot with the sysctl > hw.ath.hal.debug=0xffffffff set in /boot/loader.conf appropriately, so > I can hopefully get some debugging as to why the hardware isn't waking > up as expected. Here's the dmesg from 8.2-R with recompiled kernel including above options: Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RELEASE #0: Tue May 24 23:41:58 CEST 2011 root@fbsd8x.fbsd:/usr/obj/usr/src/sys/GENERIC i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) M CPU 430 @ 1.73GHz (1729.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6e8 Family = 6 Model = e Stepping = 8 Features=0xafe9fbff Features2=0xc109 TSC: P-state invariant real memory = 1610612736 (1536 MB) avail memory = 1430380544 (1364 MB) ACPI APIC Table: MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of f0013000, 1000 (3) failed acpi0: reservation of 0, a0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 agp0: aperture size is 128M pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem 0xa0000000-0xbfffffff,0xc8000000-0xc8ffffff irq 16 at device 0.0 on pci1 pcib2: irq 27 at device 2.0 on pci0 pci2: on pcib2 pcib3: irq 31 at device 3.0 on pci0 pci3: on pcib3 atapci0: port 0x60b8-0x60bf,0x60b0-0x60b3,0x6008-0x600f,0x6004-0x6007,0x6010-0x601f,0x6400-0x64ff irq 21 at device 15.0 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x60a0-0x60af at device 15.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] ata1: on atapci1 ata1: [ITHREAD] uhci0: port 0x6020-0x603f irq 20 at device 16.0 on pci0 uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0x6040-0x605f irq 22 at device 16.1 on pci0 uhci1: [ITHREAD] usbus1: on uhci1 uhci2: port 0x6060-0x607f irq 21 at device 16.2 on pci0 uhci2: [ITHREAD] usbus2: on uhci2 uhci3: port 0x6080-0x609f irq 23 at device 16.3 on pci0 uhci3: [ITHREAD] usbus3: on uhci3 ehci0: mem 0xc9400000-0xc94000ff irq 21 at device 16.4 on pci0 ehci0: [ITHREAD] usbus4: waiting for BIOS to give up control usbus4: timed out waiting for BIOS usbus4: EHCI version 1.0 usbus4: on ehci0 isab0: at device 17.0 on pci0 isa0: on isab0 vr0: port 0x6800-0x68ff mem 0xc9400400-0xc94004ff irq 23 at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x7c miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:14:0b:08:64:5b vr0: [ITHREAD] pcib4: at device 19.0 on pci0 pci4: on pcib4 pci4: at device 1.0 (no driver attached) pcib5: at device 19.1 on pci0 pci5: on pcib5 ath0: mem 0xc9000000-0xc900ffff irq 18 at device 1.0 on pci5 ath0: [ITHREAD] ar5212SetPowerModeAwake: Failed to wakeup in 40ms ar5212SetPowerModeAwake: Failed to wakeup in 40ms ath0: unable to attach hardware; HAL status 3 device_attach: ath0 attach returned 6 acpi_acad0: on acpi0 battery0: on acpi0 acpi_tz0: on acpi0 atrtc0: port 0x70-0x75 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model GlidePoint, device ID 0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 p4tcc0: on cpu0 Timecounter "TSC" frequency 1729015093 Hz quality 800 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 acd0: DVDR at ata1-master UDMA33 ad4: 57231MB at ata2-master UDMA100 SATA 1.5Gb/s uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered GEOM: ad4s3: geometry does not match label (255h,63s != 16h,63s). Root mount waiting for: usbus4 Root mount waiting for: usbus4 Root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Root mount waiting for: usbus4 ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x0000 Root mount waiting for: usbus4 ugen0.2: at usbus0 ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 umass0:0:0:-1: Attached to scbus0 Trying to mount root from ufs:/dev/ad4s2a da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1910MB (3911680 512 byte sectors: 255H 63S/T 243C) GEOM: da0: partition 1 does not end on a track boundary. cryptosoft0: on motherboard GEOM_ELI: Device ad4s2f.eli created. GEOM_ELI: Encryption: AES-XTS 128 GEOM_ELI: Crypto: software GEOM_ELI: Device ad4s2b.eli created. GEOM_ELI: Encryption: AES-XTS 256 GEOM_ELI: Crypto: software I will now try the -CURRENT snapshot and let you know how it went. Thanks Dalibor From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 03:14:20 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1CE51065673 for ; Thu, 26 May 2011 03:14:20 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s1.snt0.hotmail.com (snt0-omc4-s1.snt0.hotmail.com [65.55.90.204]) by mx1.freebsd.org (Postfix) with ESMTP id B660A8FC13 for ; Thu, 26 May 2011 03:14:20 +0000 (UTC) Received: from SNT128-W25 ([65.55.90.199]) by snt0-omc4-s1.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 25 May 2011 20:14:20 -0700 Message-ID: X-Originating-IP: [70.81.14.47] From: Shant Kassardjian Sender: To: Date: Thu, 26 May 2011 03:14:19 +0000 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 26 May 2011 03:14:20.0009 (UTC) FILETIME=[0102AD90:01CC1B53] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A Txpower Question X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 03:14:21 -0000 Hello Adrian=2C Glad to see you're always there for us!=20 I spent countless hours looking for ubiquiti documentation that proves sett= ing txpower 0 turns off the device...=20 and found nothing so far. Either way=2C I still see this as a useful featur= e to consider :)=20 Thanks for the detailed explanation regarding the txpower formula=2C it mak= es much more sense now whenever I play with the power transmit settings. Thanks again! Shant K > Date: Wed=2C 25 May 2011 00:43:21 +0800 > Subject: Re: SR71-A Txpower Question > From: adrian@freebsd.org > To: shant@skylab.ca > CC: freebsd-wireless@freebsd.org >=20 > Hi=2C >=20 > ifconfig wlan0 txpower 0 merely sets the txpower to 0dBm=2C which isn't > "off" strictly speaking. It's actually 1mW. >=20 > The SR-71A also has a TX power offset in hardware. If I remember > right=2C the hardware is actually a couple of dBm higher than what you > configure. So when you configure 19 dBm=2C you're programming the > hardware at 19dBm=2C but the hardware responds by allowing a max of > 16dBm per channel=2C which is * 3 (3 TX chains=2C as per the patch I gave > you) to give ~ 21dBm. I'd have to check the math to get the exact tx > power offset but that's roughly what's going on. >=20 > Now=2C if it's documented somewhere that 0 dBm should be "killing" the > interface=2C let me know. :) >=20 >=20 >=20 > Adrian >=20 > On 25 May 2011 00:24=2C Shant Kassardjian wrote: > > > > Hello FreeBSD-Wireless=2C > > > > I've been running SR71-A on FreeBSD 8.1 for quite some time now and it'= s been running very well. Many thanks to Adrian Chadd who really helped iro= ning out all my questions! > > > > My only problem so far that I've noticed is that when I do: ifconfig w= lan0 txpower 0=3B this does not turn off power to the wireless as it's supp= ose to and rather I have to bring down the interface manually to shut it do= wn hence whenever I need to start it up again I have to reconfigure the int= erface. > > > > >From my observation it looks like changing the txpower rate using ifco= nfig has little to no effect controlling this adapter. > > > > > > My question is that=2C could it be because I have compiled the kernel w= ith the following modifications as suggested by Adrian Chadd to take advant= age of Max 3x antenna transmit power that I am having this problem? > > > > Edit sys/dev/ath/ath_hal/ar5416/ar5416.h: > > > > #define AR5416_DEFAULT_RXCHAINMASK 7 > > #define AR5416_DEFAULT_TXCHAINMASK 7 > > > > > > Does anyone else have this symptom with their SR71-A (AR5416)? > > > > > > Many thanks in advance=3B > > > > Regards=2C > > Shant K. > > ______________________________= _________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe=2C send any mail to "freebsd-wireless-unsubscribe@freebs= d.org" > > = From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 06:15:44 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D7A7106564A for ; Thu, 26 May 2011 06:15:44 +0000 (UTC) (envelope-from dalibor.gudzic@gmail.com) Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id F167E8FC15 for ; Thu, 26 May 2011 06:15:43 +0000 (UTC) Received: by pxi11 with SMTP id 11so245381pxi.7 for ; Wed, 25 May 2011 23:15:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ss7vXfQu8IP3hc4vspkLrxEJkA69M4EHpESA6TL5Lgk=; b=cJqd2XJViftZufsjhdCwkbRQVktYvNkmpGx2Wm4OK1o+US9IL21lGI76m1nEls682k UqHOskcxVtFfiup+Kw4im2fgMtNsQiK7R0L/0I7M/7tfjI+1pdkPlU5KZx2QI5w5OZWd dEmpo6xH416hLtdfvNiHH0X6DFM3ybh0NXdEs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=FDtObvos1vtoDpwuY9xEofXVdW0DiApNFxZ7fBFA/Um8A1qOWtdLFeV0X6k3fJk6dC 41vnrk3imskU71fCyW9wavM21fwO8ezUdnq4/Bbe0yzrbYDj1QhhS1X2K9ICmCvwfZBs xRsz5Og2MwMl6c4PBmJMTXS2VH8QmI/Z7VRfY= MIME-Version: 1.0 Received: by 10.143.26.42 with SMTP id d42mr69559wfj.215.1306390543392; Wed, 25 May 2011 23:15:43 -0700 (PDT) Received: by 10.142.194.6 with HTTP; Wed, 25 May 2011 23:15:43 -0700 (PDT) In-Reply-To: References: <201105241220.p4OCKEZc074668@freefall.freebsd.org> Date: Thu, 26 May 2011 08:15:43 +0200 Message-ID: From: Dalibor Gudzic To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 06:15:44 -0000 Hi Adrian, On Thu, May 26, 2011 at 3:46 AM, Adrian Chadd wrote: > That's odd: > > ar5212SetPowerModeAwake: Failed to wakeup in 40ms > > That means there's something off with the RTC in the card (that > controls power on/power off.) > > Can you try booting a -HEAD kernel ? It may be related to cardbus related stuff. > > > Adrian > I had some problem burning the media, but will try later for sure. In the mean time, here is the relevant section of dmesg with hw.ath.hal.debug in loader.conf (forgot to include it in previous message): ... pcib5: at device 19.1 on pci0 pci5: on pcib5 ath0: mem 0xc9000000-0xc900ffff irq 18 at device 1.0 on pci5 ath0: [ITHREAD] ar5212Attach: sc 0xc49a6000 st 0x1 sh 0xe4ee7000 ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerModeAwake: bogus SCR 0xffffffff, PCICFG 0xffffffff ar5212SetPowerModeAwake: Failed to wakeup in 40ms ar5212Attach: couldn't wakeup chip ar5212Detach: Detaching Ani ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerModeAwake: bogus SCR 0xffffffff, PCICFG 0xffffffff ar5212SetPowerModeAwake: Failed to wakeup in 40ms ar5212SetPowerMode: AWAKE -> FULL-SLEEP (set chip ) ath0: unable to attach hardware; HAL status 3 device_attach: ath0 attach returned 6 acpi_acad0: on acpi0 ... Card works without problem in Windows XP/Ubuntu 10.10. On NetBSD I get the same messages (unable to attach bla bla). It was the same on OpenBSD before 4.8, now there are no messages in dmesg. It spits something like device timeout when I 'ifconfig up' it though, but I think card is working (haven't thoroughly tested it). I don't know how similar code for ath(4) is between *BSD's. All best Dalibor From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 09:32:19 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E38B106564A for ; Thu, 26 May 2011 09:32:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4C5A88FC0A for ; Thu, 26 May 2011 09:32:19 +0000 (UTC) Received: by gyg13 with SMTP id 13so263588gyg.13 for ; Thu, 26 May 2011 02:32:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=am0q4kxpk5CGsBWyETS0YKRygWsanAZoaZVPcTCIk1s=; b=S0+L03j2bGd7eC67W9rEUhpVmRKTiOLQojWZG5uZffxfQ5u8uND3W9Y0hKGojeFyiM 6AVVhTxCMkky8kSGTBEwoid2VLAv1zKZRvxWfixi21MqaMfQFh45DZz5/deXXQ7Cw9TR rAiRg28hywTb9iUEF1XpD83nZreX6H0Q9UhLA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=ME0JCXAEOHpraK2WTGRqvFci6aCz9kAn2SD6hpR06Cjsl9qQBI6KoGgFeI2QgWr0n/ c3OLwu5HA59q8BGzLdPa69zuqVzUvi0g1EXe6w05WMhzIearmbbjkZVL7/IA4le9U4Iy VMzK5q3830c8GGZFIpE/bTeCo5LWCWcm77m0Q= MIME-Version: 1.0 Received: by 10.151.82.16 with SMTP id j16mr721260ybl.356.1306402338371; Thu, 26 May 2011 02:32:18 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.151.107.15 with HTTP; Thu, 26 May 2011 02:32:18 -0700 (PDT) Date: Thu, 26 May 2011 17:32:18 +0800 X-Google-Sender-Auth: tAt-O5BN820ZDxkDQUDiXv9bgIU Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Initial AR9287 RX support in HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 09:32:19 -0000 Hi, After some quick consultation with Bernhard, I've committed the AR9287 work in progress to -HEAD. Why? Because I had a few people show interest in tinkering with porting support for this NIC, so I figured I'd make it a lot easier by committing what I've done to date. I decided it was worth throwing it into -HEAD minus the TX calibration / TX power setting code. It isn't linked into the build because running the NIC in anything other than monitor mode right now is very likely going to do bad things. On the up side, it's behaving itself in monitor mode. I plan on tidying up the closed-loop TX power control code that's currently shared between AR5416/AR9160, AR9280 and AR9285 before adding the needed TX power setting code to the AR9287. But if someone wants to just beat me to it for their own use by copy/pasting the AR9287 TX power calibration and setting routines from ath9k, be my guest. Just be careful that it's doing it correctly or you could damage your card. :) Enjoy, Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 13:24:58 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8F6B106566C; Thu, 26 May 2011 13:24:58 +0000 (UTC) (envelope-from dalibor.gudzic@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 91BF08FC20; Thu, 26 May 2011 13:24:58 +0000 (UTC) Received: by pzk27 with SMTP id 27so376138pzk.13 for ; Thu, 26 May 2011 06:24:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4FuioTw6VQm5R9UkpNY04xmmlPQbzqZDPEDEenkHquA=; b=jLPvcvOfrYXblRdXjURUbmhU6kWmdb9aU1FSbiX7l92E8B7EAB2Tcd0OS10sSedy3P AhREJQnqlYrbXHakT5C/u56GSJUMAKPWXl3G/GrOuHMF3iMkjoi3iFMk5sU7EBFYFVS4 sTLH/Y/VVVG0h40T7dFyGVktRJEO6aNFN9X4s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=EmGK2N+PHsiIIjFxj1K/Siu7YAZ4TIYwFwgXEKOpkkIx6yTHE+tlKL5gcZPIwYnjR6 z1bPh27dfGcq5h2o7J5/Zp8ZI9pbuPLn68+dfZglti81sc4HKf3WPv/95skGJ7o26y7R bQGLRyK8i09951nNasl5GC+T8+DigEAMGYCTU= MIME-Version: 1.0 Received: by 10.68.14.103 with SMTP id o7mr328460pbc.523.1306416298054; Thu, 26 May 2011 06:24:58 -0700 (PDT) Received: by 10.142.194.6 with HTTP; Thu, 26 May 2011 06:24:58 -0700 (PDT) In-Reply-To: References: <201105241220.p4OCKEZc074668@freefall.freebsd.org> Date: Thu, 26 May 2011 15:24:58 +0200 Message-ID: From: Dalibor Gudzic To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 13:24:58 -0000 Hi Adrian, On Thu, May 26, 2011 at 9:13 AM, Adrian Chadd wrote: > What model card is this? > > > Adrian > You could see the 'pciconf -lv' at kern/116444, in my follow-up in 2009 there. If you need more info of any command let me know. Dalibor From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 15:58:44 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2DFB106566B for ; Thu, 26 May 2011 15:58:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 90A3A8FC17 for ; Thu, 26 May 2011 15:58:44 +0000 (UTC) Received: by gwb15 with SMTP id 15so444820gwb.13 for ; Thu, 26 May 2011 08:58:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=JyGlaNJBj+brpqsi20ylyuKD9jzlLGe1SdCmd5hZSv0=; b=sEXd3AT2oI9x3jjqW6Ajkeln53uO4480Rbj2rvngpc2FCq4D/N77v7RaGIGN6PjamX 5Z+Z/WyY3gAx1Ceb+DhBPGx7SZJXJk/IMh4X2thv6iskrEhMMI/+fZbbLg+oQkNLK7S3 C38GFOG5eV2aVz8XvsWrdWmB+dg2z3eM/QhlE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=eDLfDY/ww+uqdrU1LQtHuD4uCIefWG8z3X6sNWNW86XSvlFDles5+T1roUl+b11X3p WB6ww+fakRuhZ4LpNRuvCu5d8uQ9ibzDGOqg02AwlVG8KNrxHD0wyPTQ/euA0Vmt5BGM R6zR35Qf3JCR+jySAbjk75wqMm4l/ctgJI3Ho= MIME-Version: 1.0 Received: by 10.150.182.1 with SMTP id e1mr1064742ybf.299.1306425523821; Thu, 26 May 2011 08:58:43 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.151.107.15 with HTTP; Thu, 26 May 2011 08:58:43 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 May 2011 23:58:43 +0800 X-Google-Sender-Auth: aovBSRfR1VRNETc4uLK-cwOVZDE Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Initial AR9287 RX support in HEAD X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 15:58:44 -0000 .. I gave in, and I finished porting the TX power/calibration code over. It passes some basic 11g TX throughput testing. Who's game? :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 16:04:35 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AED2C1065670 for ; Thu, 26 May 2011 16:04:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 69A5C8FC12 for ; Thu, 26 May 2011 16:04:35 +0000 (UTC) Received: by gwb15 with SMTP id 15so448162gwb.13 for ; Thu, 26 May 2011 09:04:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=O+IbexI3xpblMysKioVtNmPH3Ne1+QfJD0ZIBRqkVEs=; b=ppy/UeOf7mKg3FqgCWV65Cw2Fq9YLZZo5I6yQNwC74iH/Fd/IZxugscFlk85J4rkuV H45fObTSHyawdc5q4HD3Vszg/EVtfiRj/D9AHqxmNrHsbJrhsN0+T6BKFg6/BbvC7EDD NxUcsrXKrqZEJCWAqhf5Y2/3CcBtt8jqi7DM0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=EnTH8QjAsHyl8Zj3HXZkor9Fru8o1qN8G/t+0g4nC1OKyLIIQvIBHfYJqDAZwwZEwd gWO7AXzegMchNJ+E2EeWOsNvNpl3KpX+wX6mhqHmoZalGo2JM9A//Gd6TaDd5L1Auj/V sUo+wEWAbSx/EGq8KqXiNcq3FXx3lsvi7mrUU= MIME-Version: 1.0 Received: by 10.150.63.19 with SMTP id l19mr1196771yba.71.1306425874683; Thu, 26 May 2011 09:04:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.151.107.15 with HTTP; Thu, 26 May 2011 09:04:34 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 May 2011 00:04:34 +0800 X-Google-Sender-Auth: _SfnVTYatafCwkSLkh62elWgx2g Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A Txpower Question X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 16:04:35 -0000 Hi! No worries. I plan on digging up my previous emails with Ubiquiti and documenting exactly what the SR-71A behaviour should be. Thanks, Adrian On 26 May 2011 11:14, Shant Kassardjian wrote: > > Hello Adrian, > > Glad to see you're always there for us! > > I spent countless hours looking for ubiquiti documentation that proves se= tting txpower 0 turns off the device... > > and found nothing so far. Either way, I still see this as a useful featur= e to consider :) > > Thanks for the detailed explanation regarding the txpower formula, it mak= es much more sense now whenever I play with the power transmit settings. > > Thanks again! > Shant K > >> Date: Wed, 25 May 2011 00:43:21 +0800 >> Subject: Re: SR71-A Txpower Question >> From: adrian@freebsd.org >> To: shant@skylab.ca >> CC: freebsd-wireless@freebsd.org >> >> Hi, >> >> ifconfig wlan0 txpower 0 merely sets the txpower to 0dBm, which isn't >> "off" strictly speaking. It's actually 1mW. >> >> The SR-71A also has a TX power offset in hardware. If I remember >> right, the hardware is actually a couple of dBm higher than what you >> configure. So when you configure 19 dBm, you're programming the >> hardware at 19dBm, but the hardware responds by allowing a max of >> 16dBm per channel, which is * 3 (3 TX chains, as per the patch I gave >> you) to give ~ 21dBm. I'd have to check the math to get the exact tx >> power offset but that's roughly what's going on. >> >> Now, if it's documented somewhere that 0 dBm should be "killing" the >> interface, let me know. :) >> >> >> >> Adrian >> >> On 25 May 2011 00:24, Shant Kassardjian wrote: >> > >> > Hello FreeBSD-Wireless, >> > >> > I've been running SR71-A on FreeBSD 8.1 for quite some time now and it= 's been running very well. Many thanks to Adrian Chadd who really helped ir= oning out all my questions! >> > >> > My only problem so far that I've noticed is that when I do: =A0ifconfi= g wlan0 txpower 0; this does not turn off power to the wireless as it's sup= pose to and rather I have to bring down the interface manually to shut it d= own hence whenever I need to start it up again I have to reconfigure the in= terface. >> > >> > >From my observation it looks like changing the txpower rate using ifc= onfig has little to no effect controlling this adapter. >> > >> > >> > My question is that, could it be because I have compiled the kernel wi= th the following modifications as suggested by Adrian Chadd to take advanta= ge of Max 3x antenna transmit power that I am having this problem? >> > >> > Edit sys/dev/ath/ath_hal/ar5416/ar5416.h: >> > >> > #define AR5416_DEFAULT_RXCHAINMASK =A0 =A0 =A07 >> > #define AR5416_DEFAULT_TXCHAINMASK =A0 =A0 =A07 >> > >> > >> > Does anyone else have this symptom with their SR71-A (AR5416)? >> > >> > >> > Many thanks in advance; >> > >> > Regards, >> > Shant K. >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0_______________________________________________ >> > 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" >> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0_______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" > From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 19:21:54 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F13DE106564A; Thu, 26 May 2011 19:21:54 +0000 (UTC) (envelope-from dalibor.gudzic@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id BDEB68FC0C; Thu, 26 May 2011 19:21:54 +0000 (UTC) Received: by pvg11 with SMTP id 11so566035pvg.13 for ; Thu, 26 May 2011 12:21:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=7UYm2WBRwXJTaHCYSFKyaOvySzao0og3kK+nKk4QZLw=; b=a1Gg+SpBnOcl6H2iIzLD5MziNyUUqlAd9O81xi//fkYp4vLsPxzVePsKVDRj9ZyHUa En7p80GlVNRfzNZp8YPIb/TQnJFDpKaRVh3cGlFGYfedSDGfVt1VSsPj3g/wKKCwA9V3 6kkvme4irOJyNVaaGny2k0rr7qZbEuKfuZd0U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=HJp/4A7QvenQ70b7T2aB3vTAatWjHpqC3LQ50QQz9VyYyJcw9Iw3UuTkyT6rcGyj8M cqzpUT0ggIoT0ZXx92vCWsKnWDuGrsHOmf10xyOS83aAAlqSbd2Nm8sZM2UZDeHVXPBv EVCAolW02NfWIwvMSVubnxGl9ZUyT19wnMIiE= MIME-Version: 1.0 Received: by 10.142.142.8 with SMTP id p8mr193473wfd.158.1306437714070; Thu, 26 May 2011 12:21:54 -0700 (PDT) Received: by 10.142.194.6 with HTTP; Thu, 26 May 2011 12:21:54 -0700 (PDT) Date: Thu, 26 May 2011 21:21:54 +0200 Message-ID: From: Dalibor Gudzic To: bug-followup@freebsd.org, Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 19:21:55 -0000 > On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrote: > > Have you tried freebsd-current? I've done quite a bit of work with the > ath driver in FreeBSD-current. Just did. It appears that card is working in HEAD, at least there are no failed messages. Here is the dmesg: Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #0: Thu May 12 11:28:09 UTC 2011 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Celeron(R) M CPU 430 @ 1.73GHz (1729.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6e8 Family = 6 Model = e Stepping = 8 Features=0xafe9fbff Features2=0xc109 TSC: P-state invariant, performance statistics real memory = 1610612736 (1536 MB) avail memory = 1425682432 (1359 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of f0013000, 1000 (3) failed acpi0: reservation of 0, a0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 agp0: aperture size is 128M pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem 0xa0000000-0xbfffffff,0xc8000000-0xc8ffffff irq 16 at device 0.0 on pci1 pcib2: irq 27 at device 2.0 on pci0 pci2: on pcib2 pcib3: irq 31 at device 3.0 on pci0 pci3: on pcib3 atapci0: port 0x60b8-0x60bf,0x60b0-0x60b3,0x6008-0x600f,0x6004-0x6007,0x6010-0x601f,0x6400-0x64ff irq 21 at device 15.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x60a0-0x60af at device 15.1 on pci0 ata0: on atapci1 ata1: on atapci1 uhci0: port 0x6020-0x603f irq 20 at device 16.0 on pci0 usbus0: on uhci0 uhci1: port 0x6040-0x605f irq 22 at device 16.1 on pci0 usbus1: on uhci1 uhci2: port 0x6060-0x607f irq 21 at device 16.2 on pci0 usbus2: on uhci2 uhci3: port 0x6080-0x609f irq 23 at device 16.3 on pci0 usbus3: on uhci3 ehci0: mem 0xc9400000-0xc94000ff irq 21 at device 16.4 on pci0 usbus4: waiting for BIOS to give up control usbus4: timed out waiting for BIOS usbus4: EHCI version 1.0 usbus4: on ehci0 isab0: at device 17.0 on pci0 isa0: on isab0 vr0: port 0x6800-0x68ff mem 0xc9400400-0xc94004ff irq 23 at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x7c miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:14:0b:08:64:5b pcib4: at device 19.0 on pci0 pci4: on pcib4 pci4: at device 1.0 (no driver attached) pcib5: at device 19.1 on pci0 pcib5: failed to allocate initial memory window: 0xc9000000-0xc90fffff pci5: on pcib5 ath0: irq 18 at device 1.0 on pci5 ath0: AR2413 mac 7.8 RF2413 phy 4.5 acpi_acad0: on acpi0 battery0: on acpi0 acpi_tz0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 attimer0: Can't map interrupt. atrtc0: port 0x70-0x75 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 p4tcc0: on cpu0 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 SATA 1.x device ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes) ada0: 57231MB (117210240 512 byte sectors: 16H 63S/T 16383C)cd0 at ata1 bus 0 scbus3 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: cd present [279069 x 2048 byte records] ada0: Previously was known as ad4 Timecounter "TSC" frequency 1729046124 Hz quality 800 WARNING: WITNESS option enabled, expect reduced performance. uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered (cd0:ata1:0:0:0): READ(10). CDB: 28 0 0 4 42 1c 0 0 1 0 (cd0:ata1:0:0:0): CAM status: SCSI Status Error (cd0:ata1:0:0:0): SCSI status: Check Condition (cd0:ata1:0:0:0): SCSI sense: ILLEGAL REQUEST csi:28,33,21,80 asc:64,0 (Illegal mode for this track) (cd0:ata1:0:0:0): cddone: got error 0x6 back GEOM: ada0s3: geometry does not match label (255h,63s != 16h,63s). GEOM: ada0s3: invalid disklabel. Root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... ugen0.2: at usbus0 ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 ugen4.2: at usbus4 I only had time to boot it and see the dmesg, I haven't tried anything with the card yet. All best Dalibor From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 19:30:14 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB3CF106564A for ; Thu, 26 May 2011 19:30:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C1CCA8FC15 for ; Thu, 26 May 2011 19:30:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4QJUEMI075539 for ; Thu, 26 May 2011 19:30:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4QJUENI075534; Thu, 26 May 2011 19:30:14 GMT (envelope-from gnats) Date: Thu, 26 May 2011 19:30:14 GMT Message-Id: <201105261930.p4QJUENI075534@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Dalibor Gudzic Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dalibor Gudzic 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: Thu, 26 May 2011 19:30:14 -0000 The following reply was made to PR kern/140796; it has been noted by GNATS. From: Dalibor Gudzic To: bug-followup@freebsd.org, Adrian Chadd Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x Date: Thu, 26 May 2011 21:21:54 +0200 > On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrote: > > Have you tried freebsd-current? I've done quite a bit of work with the > ath driver in FreeBSD-current. Just did. It appears that card is working in HEAD, at least there are no failed messages. Here is the dmesg: Copyright (c) 1992-2011 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #0: Thu May 12 11:28:09 UTC 2011 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Celeron(R) M CPU 430 @ 1.73GHz (1729.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6e8 Family = 6 Model = e Stepping = 8 Features=0xafe9fbff Features2=0xc109 TSC: P-state invariant, performance statistics real memory = 1610612736 (1536 MB) avail memory = 1425682432 (1359 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of f0013000, 1000 (3) failed acpi0: reservation of 0, a0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 agp0: aperture size is 128M pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem 0xa0000000-0xbfffffff,0xc8000000-0xc8ffffff irq 16 at device 0.0 on pci1 pcib2: irq 27 at device 2.0 on pci0 pci2: on pcib2 pcib3: irq 31 at device 3.0 on pci0 pci3: on pcib3 atapci0: port 0x60b8-0x60bf,0x60b0-0x60b3,0x6008-0x600f,0x6004-0x6007,0x6010-0x601f,0x6400-0x64ff irq 21 at device 15.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x60a0-0x60af at device 15.1 on pci0 ata0: on atapci1 ata1: on atapci1 uhci0: port 0x6020-0x603f irq 20 at device 16.0 on pci0 usbus0: on uhci0 uhci1: port 0x6040-0x605f irq 22 at device 16.1 on pci0 usbus1: on uhci1 uhci2: port 0x6060-0x607f irq 21 at device 16.2 on pci0 usbus2: on uhci2 uhci3: port 0x6080-0x609f irq 23 at device 16.3 on pci0 usbus3: on uhci3 ehci0: mem 0xc9400000-0xc94000ff irq 21 at device 16.4 on pci0 usbus4: waiting for BIOS to give up control usbus4: timed out waiting for BIOS usbus4: EHCI version 1.0 usbus4: on ehci0 isab0: at device 17.0 on pci0 isa0: on isab0 vr0: port 0x6800-0x68ff mem 0xc9400400-0xc94004ff irq 23 at device 18.0 on pci0 vr0: Quirks: 0x0 vr0: Revision: 0x7c miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:14:0b:08:64:5b pcib4: at device 19.0 on pci0 pci4: on pcib4 pci4: at device 1.0 (no driver attached) pcib5: at device 19.1 on pci0 pcib5: failed to allocate initial memory window: 0xc9000000-0xc90fffff pci5: on pcib5 ath0: irq 18 at device 1.0 on pci5 ath0: AR2413 mac 7.8 RF2413 phy 4.5 acpi_acad0: on acpi0 battery0: on acpi0 acpi_tz0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 attimer0: Can't map interrupt. atrtc0: port 0x70-0x75 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 p4tcc0: on cpu0 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 SATA 1.x device ada0: 150.000MB/s transfers (SATA 1.x, UDMA5, PIO 8192bytes) ada0: 57231MB (117210240 512 byte sectors: 16H 63S/T 16383C)cd0 at ata1 bus 0 scbus3 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: cd present [279069 x 2048 byte records] ada0: Previously was known as ad4 Timecounter "TSC" frequency 1729046124 Hz quality 800 WARNING: WITNESS option enabled, expect reduced performance. uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered (cd0:ata1:0:0:0): READ(10). CDB: 28 0 0 4 42 1c 0 0 1 0 (cd0:ata1:0:0:0): CAM status: SCSI Status Error (cd0:ata1:0:0:0): SCSI status: Check Condition (cd0:ata1:0:0:0): SCSI sense: ILLEGAL REQUEST csi:28,33,21,80 asc:64,0 (Illegal mode for this track) (cd0:ata1:0:0:0): cddone: got error 0x6 back GEOM: ada0s3: geometry does not match label (255h,63s != 16h,63s). GEOM: ada0s3: invalid disklabel. Root mount waiting for: usbus4 uhub4: 8 ports with 8 removable, self powered Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... ugen0.2: at usbus0 ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 ugen4.2: at usbus4 I only had time to boot it and see the dmesg, I haven't tried anything with the card yet. All best Dalibor From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 20:11:17 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A207106564A; Thu, 26 May 2011 20:11:17 +0000 (UTC) (envelope-from dalibor.gudzic@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id D8EC48FC12; Thu, 26 May 2011 20:11:16 +0000 (UTC) Received: by pwj8 with SMTP id 8so633503pwj.13 for ; Thu, 26 May 2011 13:11:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Z//7NJzjIfMt7xt+2shtPuBo+V0GqodWW7sXQnsUiIc=; b=CwtIVkr14LEjtZN5GxlBLafsS0MS1D01QyHE8HU5+ZO5YbVpbeZgut/rNvjiQBA/yF PxVzaG32yuW43GUPvKMHF2XjWP1a8Bk46ooxNa7ZxGFHl1tgPubK0/kxgOBXbiIOaq8v aFv7yIozyyZz8u8EQCXmos2Mr8m4WqhNTfZo8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=EL2mVGo+Tq9/8FR6iOouEMgnMNZw7YAfrvtQpZlxRUEvXEEWvXvNbTJQdlkHjBhwda MKQNb9tn/73VLmpHAKMjpYEbPVV89482jAjbDoJlZZjBKK/5AHpaVV3bG9i2La/5MwBF WcuLhonI7Be7dGhmHTTUXzm1xuM8lzEXtHRR0= MIME-Version: 1.0 Received: by 10.142.234.9 with SMTP id g9mr203287wfh.101.1306440676324; Thu, 26 May 2011 13:11:16 -0700 (PDT) Received: by 10.142.194.6 with HTTP; Thu, 26 May 2011 13:11:16 -0700 (PDT) In-Reply-To: References: Date: Thu, 26 May 2011 22:11:16 +0200 Message-ID: From: Dalibor Gudzic To: bug-followup@freebsd.org, Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 20:11:17 -0000 On Thu, May 26, 2011 at 9:21 PM, Dalibor Gudzic wrote: >> On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrote: >> >> Have you tried freebsd-current? I've done quite a bit of work with the >> ath driver in FreeBSD-current. > > Just did. It appears that card is working in HEAD, at least there are > no failed messages. Here is the dmesg: > ... Unfortunately, I cannot do anything with the card. I can 'up' it, but when I try to assign an address to it I get: ifconfig: ioctl (SIOCAIFADDR): Invalid argument ifconfig arguments were fine, everything is OK with vr0 interace. If I try tcpdump on ath0 I get: tcpdump: ath0: No such device exists (BIOCSETIF failed: Device not configured) I guess I started to celebrate to early... :) Dalibor From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 20:12:13 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78E19106564A; Thu, 26 May 2011 20:12:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 207928FC12; Thu, 26 May 2011 20:12:12 +0000 (UTC) Received: by gwb15 with SMTP id 15so575343gwb.13 for ; Thu, 26 May 2011 13:12:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=wZ2/xTPU483h7KCCuEU8CtR51GUe7hGCUegVpWNuKZ0=; b=JO4+Y8Yh0qKvxtASKaGHxudW1L0kpGuBhPLvEBAvxhTkIDpzB68fPLMVG6QUUYvkzh tC6u/HTglLcrcaniy1x4Ey5NEh5rd8dKUjBlAr0FyzBl3+IIVC3DQDS8c7sr+e8wc1cX 2D/rnnk/6c/qzfb1QA9Lp94FWg7lhTAiEPx/4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=avAWmtEmsnDqO0q24byFvqgnhIRYHqmVsLxHav+y27tVax2ll6+rsk/r+drY9xHJNZ QeV/81vCiCnyeNO7W/oPVHMYq83jWpruYJpDzgNiC9PNGfN8paOAVJv1EHxsyBTNL3aB Q+r5/4a3qobCPZfyTghr0tyoHpRgG+V2dpv0Q= MIME-Version: 1.0 Received: by 10.150.182.1 with SMTP id e1mr1341651ybf.299.1306440732449; Thu, 26 May 2011 13:12:12 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.151.107.15 with HTTP; Thu, 26 May 2011 13:12:12 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 May 2011 04:12:12 +0800 X-Google-Sender-Auth: anbKYDqAT7Wgf3c89grARdvmPKw Message-ID: From: Adrian Chadd To: Dalibor Gudzic Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org, bug-followup@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 20:12:13 -0000 Nope, you need to use cloned devices, not ath0. ifconfig wlan0 create wlandev ath0 country Australia then do your stuff to wlan0, not ath0. :) Adrian On 27 May 2011 04:11, Dalibor Gudzic wrote: > On Thu, May 26, 2011 at 9:21 PM, Dalibor Gudzic > wrote: >>> On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrot= e: >>> >>> Have you tried freebsd-current? I've done quite a bit of work with the >>> ath driver in FreeBSD-current. >> >> Just did. It appears that card is working in HEAD, at least there are >> no failed messages. Here is the dmesg: >> ... > > Unfortunately, I cannot do anything with the card. I can 'up' it, but > when I try to assign an address to it I get: > > =A0 =A0 =A0ifconfig: ioctl (SIOCAIFADDR): Invalid argument > > ifconfig arguments were fine, everything is OK with vr0 interace. If I > try tcpdump on ath0 I get: > > =A0 =A0 =A0tcpdump: ath0: No such device exists > =A0 =A0 =A0(BIOCSETIF failed: Device not configured) > > > I guess I started to celebrate to early... :) > > > Dalibor > From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 20:20:12 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 343DB1065672 for ; Thu, 26 May 2011 20:20:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 246C98FC13 for ; Thu, 26 May 2011 20:20:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4QKKBjf022320 for ; Thu, 26 May 2011 20:20:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4QKKBtb022319; Thu, 26 May 2011 20:20:11 GMT (envelope-from gnats) Date: Thu, 26 May 2011 20:20:11 GMT Message-Id: <201105262020.p4QKKBtb022319@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Dalibor Gudzic Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dalibor Gudzic 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: Thu, 26 May 2011 20:20:12 -0000 The following reply was made to PR kern/140796; it has been noted by GNATS. From: Dalibor Gudzic To: bug-followup@freebsd.org, Adrian Chadd Cc: freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x Date: Thu, 26 May 2011 22:11:16 +0200 On Thu, May 26, 2011 at 9:21 PM, Dalibor Gudzic wrote: >> On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrote: >> >> Have you tried freebsd-current? I've done quite a bit of work with the >> ath driver in FreeBSD-current. > > Just did. It appears that card is working in HEAD, at least there are > no failed messages. Here is the dmesg: > ... Unfortunately, I cannot do anything with the card. I can 'up' it, but when I try to assign an address to it I get: ifconfig: ioctl (SIOCAIFADDR): Invalid argument ifconfig arguments were fine, everything is OK with vr0 interace. If I try tcpdump on ath0 I get: tcpdump: ath0: No such device exists (BIOCSETIF failed: Device not configured) I guess I started to celebrate to early... :) Dalibor From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 20:20:16 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82943106566B for ; Thu, 26 May 2011 20:20:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 731DC8FC15 for ; Thu, 26 May 2011 20:20:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4QKKGLe022345 for ; Thu, 26 May 2011 20:20:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4QKKG8c022344; Thu, 26 May 2011 20:20:16 GMT (envelope-from gnats) Date: Thu, 26 May 2011 20:20:16 GMT Message-Id: <201105262020.p4QKKG8c022344@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Adrian Chadd Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Chadd 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: Thu, 26 May 2011 20:20:16 -0000 The following reply was made to PR kern/140796; it has been noted by GNATS. From: Adrian Chadd To: Dalibor Gudzic Cc: bug-followup@freebsd.org, freebsd-wireless@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x Date: Fri, 27 May 2011 04:12:12 +0800 Nope, you need to use cloned devices, not ath0. ifconfig wlan0 create wlandev ath0 country Australia then do your stuff to wlan0, not ath0. :) Adrian On 27 May 2011 04:11, Dalibor Gudzic wrote: > On Thu, May 26, 2011 at 9:21 PM, Dalibor Gudzic > wrote: >>> On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wrot= e: >>> >>> Have you tried freebsd-current? I've done quite a bit of work with the >>> ath driver in FreeBSD-current. >> >> Just did. It appears that card is working in HEAD, at least there are >> no failed messages. Here is the dmesg: >> ... > > Unfortunately, I cannot do anything with the card. I can 'up' it, but > when I try to assign an address to it I get: > > =A0 =A0 =A0ifconfig: ioctl (SIOCAIFADDR): Invalid argument > > ifconfig arguments were fine, everything is OK with vr0 interace. If I > try tcpdump on ath0 I get: > > =A0 =A0 =A0tcpdump: ath0: No such device exists > =A0 =A0 =A0(BIOCSETIF failed: Device not configured) > > > I guess I started to celebrate to early... :) > > > Dalibor > From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 20:34:46 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 048331065670; Thu, 26 May 2011 20:34:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id A50408FC13; Thu, 26 May 2011 20:34:45 +0000 (UTC) Received: by gxk28 with SMTP id 28so586020gxk.13 for ; Thu, 26 May 2011 13:34:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:cc:content-type; bh=Mc4+upjly+Jqhlnu07htA9YAwaE+pDd8dWDRmT07R2s=; b=Hofq+scLUOPP9beoiAEuCzXuSm4oSV9OtGzHnsSddY3v7wvPQoHSS6G8kcmOc/RH4k gLAjZoYXmCiGnPZrB0qeFNaHmAt67sTn7gwOWAHeYDtzZUJ/4iJSh0q3glxCi36FSqUD 2pVgiD4ULr501VwZ4eDzGMCNUI6QRsgD9XDHw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; b=lsD0KDcRCHxcVx9ZDbHTZvjc4mNlraOTXun2QOtetgjOQ1oEs4t9TWh7dp9kEnAkPu DlaHoq9JiAiX2PGVqcaBsM2yG6o1Tv19B9K6d4H9nobidePUh3qrorVL2j5HhbuX00Zr HbyUX6gbcG4kwnGVoWvNGNlq0mpi8/+pAU024= MIME-Version: 1.0 Received: by 10.150.141.8 with SMTP id o8mr1375636ybd.128.1306442085046; Thu, 26 May 2011 13:34:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.151.107.15 with HTTP; Thu, 26 May 2011 13:34:45 -0700 (PDT) Date: Fri, 27 May 2011 04:34:45 +0800 X-Google-Sender-Auth: VZL4yIdce8JyuvuunqzEbrzsk3g Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-mobile@freebsd.org Subject: AR9287 support is now in HEAD! X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 20:34:46 -0000 Hi all, I've been working on the AR9287 support and I now have it in a "works for me" state. It's in -HEAD, both for standalone and module builds. I'd appreciate some testing and feedback. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri May 27 13:30:13 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FD0C106564A for ; Fri, 27 May 2011 13:30:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6512C8FC0A for ; Fri, 27 May 2011 13:30:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4RDUDDL019983 for ; Fri, 27 May 2011 13:30:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4RDUDrt019980; Fri, 27 May 2011 13:30:13 GMT (envelope-from gnats) Date: Fri, 27 May 2011 13:30:13 GMT Message-Id: <201105271330.p4RDUDrt019980@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Dalibor Gudzic Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dalibor Gudzic 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: Fri, 27 May 2011 13:30:13 -0000 The following reply was made to PR kern/140796; it has been noted by GNATS. From: Dalibor Gudzic To: Adrian Chadd Cc: bug-followup@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x Date: Fri, 27 May 2011 15:25:05 +0200 On Thu, May 26, 2011 at 10:12 PM, Adrian Chadd wrote: > Nope, you need to use cloned devices, not ath0. > > ifconfig wlan0 create wlandev ath0 country Australia > > then do your stuff to wlan0, not ath0. :) > > > Adrian > Ah, I haven't been using FreeBSD for some time now... I see things have changed in 7.x. :) Card is WORKING properly now. I tried setting and address and listening on it. I will test further today and see if there are any problems. Anyway, is there a chance for a patch downstream to STABLE? Or change is already there? Again, thank a lot for your time and effort on this issue. All best Dalibor > On 27 May 2011 04:11, Dalibor Gudzic wrote: >> On Thu, May 26, 2011 at 9:21 PM, Dalibor Gudzic >> wrote: >>>> On Tue, May 24, 2011 at 2:29 PM, Adrian Chadd wro= te: >>>> >>>> Have you tried freebsd-current? I've done quite a bit of work with the >>>> ath driver in FreeBSD-current. >>> >>> Just did. It appears that card is working in HEAD, at least there are >>> no failed messages. Here is the dmesg: >>> ... >> >> Unfortunately, I cannot do anything with the card. I can 'up' it, but >> when I try to assign an address to it I get: >> >> =A0 =A0 =A0ifconfig: ioctl (SIOCAIFADDR): Invalid argument >> >> ifconfig arguments were fine, everything is OK with vr0 interace. If I >> try tcpdump on ath0 I get: >> >> =A0 =A0 =A0tcpdump: ath0: No such device exists >> =A0 =A0 =A0(BIOCSETIF failed: Device not configured) >> >> >> I guess I started to celebrate to early... :) >> >> >> Dalibor >> > From owner-freebsd-wireless@FreeBSD.ORG Fri May 27 13:30:17 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1EE78106566B for ; Fri, 27 May 2011 13:30:17 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0DEF78FC0C for ; Fri, 27 May 2011 13:30:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4RDUG9c020151 for ; Fri, 27 May 2011 13:30:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4RDUG9C020143; Fri, 27 May 2011 13:30:16 GMT (envelope-from gnats) Date: Fri, 27 May 2011 13:30:16 GMT Message-Id: <201105271330.p4RDUG9C020143@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Adrian Chadd Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Chadd 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: Fri, 27 May 2011 13:30:17 -0000 The following reply was made to PR kern/140796; it has been noted by GNATS. From: Adrian Chadd To: Dalibor Gudzic Cc: bug-followup@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x Date: Fri, 27 May 2011 21:29:33 +0800 On 27 May 2011 21:25, Dalibor Gudzic wrote: > Ah, I haven't been using FreeBSD for some time now... I see things > have changed in 7.x. :) Card is WORKING properly now. I tried setting > and address and listening on it. I will test further today and see if > there are any problems. > Anyway, is there a chance for a patch downstream to STABLE? Or change > is already there? > > Again, thank a lot for your time and effort on this issue. Hi! I don't even know what the underlying bus issue in earlier versions. I just know that there's been some bugfixes with the bus resource allocation code. I don't even know what to port over. :) I'm just glad it works. :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri May 27 14:30:18 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EA31106564A for ; Fri, 27 May 2011 14:30:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1CFAD8FC19 for ; Fri, 27 May 2011 14:30:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4REUH8O077572 for ; Fri, 27 May 2011 14:30:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4REUH2o077566; Fri, 27 May 2011 14:30:17 GMT (envelope-from gnats) Date: Fri, 27 May 2011 14:30:17 GMT Message-Id: <201105271430.p4REUH2o077566@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Dalibor Gudzic Cc: Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dalibor Gudzic 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: Fri, 27 May 2011 14:30:18 -0000 The following reply was made to PR kern/140796; it has been noted by GNATS. From: Dalibor Gudzic To: Adrian Chadd Cc: bug-followup@freebsd.org Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x Date: Fri, 27 May 2011 16:24:19 +0200 On Fri, May 27, 2011 at 3:29 PM, Adrian Chadd wrote: > On 27 May 2011 21:25, Dalibor Gudzic wrote: > >> Ah, I haven't been using FreeBSD for some time now... I see things >> have changed in 7.x. :) Card is WORKING properly now. I tried setting >> and address and listening on it. I will test further today and see if >> there are any problems. >> Anyway, is there a chance for a patch downstream to STABLE? Or change >> is already there? >> >> Again, thank a lot for your time and effort on this issue. > > Hi! I don't even know what the underlying bus issue in earlier > versions. I just know that there's been some bugfixes with the bus > resource allocation code. I don't even know what to port over. :) > > I'm just glad it works. :) > Me too. :) Alright. I will surely try STABLE as well, as that would be better solution for me that HEAD, and will post info on freebsd-wireless mailing list. This then solves this PR and also kern/116444. Are they gonna be closed? I'm asking in case there is some good/bad info when I try STABLE. Dalibor