From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 11 19:35:51 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 B461F1065675 for ; Sun, 11 Dec 2011 19:35:51 +0000 (UTC) (envelope-from hapvbk@yahoo.co.uk) Received: from nm6.bullet.mail.ukl.yahoo.com (nm6.bullet.mail.ukl.yahoo.com [217.146.182.227]) by mx1.freebsd.org (Postfix) with SMTP id 146268FC0C for ; Sun, 11 Dec 2011 19:35:50 +0000 (UTC) Received: from [217.146.183.184] by nm6.bullet.mail.ukl.yahoo.com with NNFMP; 11 Dec 2011 19:35:49 -0000 Received: from [77.238.184.76] by tm15.bullet.mail.ukl.yahoo.com with NNFMP; 11 Dec 2011 19:35:49 -0000 Received: from [127.0.0.1] by smtp145.mail.ukl.yahoo.com with NNFMP; 11 Dec 2011 19:35:49 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1323632149; bh=SWJts2PdpOMLoWnskHJxnR8Z6ZlKy1OmVDZCtXAzZsI=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:From:To:Cc:References:In-Reply-To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:Importance:X-Mailer:X-MimeOLE; b=KkLnNojLWjcyg3CWZNlCdRWOuruvvoC/YF27F57XrbzC1C+c/RvTGzQA5COcTO5681y+xFrJYolC2qrgWzEp0DwqQAb0kHKsKEfBk4JdDRlPSe11LYyYDAXU+V0vsKmtyYjzBSbbjNMh8tU5M/9O6+RJiOpdCvZjcUEQex0Zv8A= X-Yahoo-Newman-Id: 326605.83470.bm@smtp145.mail.ukl.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: XvUiSKYVM1nYjA3JnfFyDkxGBv7p2VvLHPRCZDmQjMzwxRt _xGHrcfEmQISrTk4MdC.gIIjukv_ZdG1Yl86Mz0sHOV8FubD0HG3QQRq5vW_ g4JU2DpnFiGAfkQYwZ7DB3sGQZS9cLr.GMmpEfuD1IUAC6vEQxkkdP_zXlti XinR0eTELZi__RIikdky4xYrGk7v.eQwzWoShUWif1AjDK88hLKgewXp8Ro2 GnO0x.kCj0K2JPyWd.oIDcyfCbWlhtjOosyXhsO5MWuzIDIAJKMnU5XbV854 szY7H45tQmzzf4U6lFJJcqmMmSG_5.Ahobk0pciFPQ4ypo9IHCcjdYpGIU40 MgFlNa8r0v9qLyGegV4Y_ipKyKAv6Vi7aMPuHBm8- X-Yahoo-SMTP: xBpCc9iswBApASleyiIs9lcZMA-- Received: from PC (hapvbk@66.11.191.2 with login) by smtp145.mail.ukl.yahoo.com with SMTP; 11 Dec 2011 19:35:48 +0000 GMT Message-ID: From: "Viet-Ha Pham" To: "Adrian Chadd" References: <3d4d2d249836fafc6acd885693c02198@webmail.entel.upc.edu><4ECFCDAB.1080407@entel.upc.edu><4ED3B4D1.3020701@entel.upc.edu><4EDA4BBA.6010203@entel.upc.edu><4EDA609F.2080401@entel.upc.edu> In-Reply-To: Date: Sun, 11 Dec 2011 14:35:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3538.513 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3538.513 Cc: Freebsd Wireless Subject: Re: Rate index for 11 Mbps 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: Sun, 11 Dec 2011 19:35:51 -0000 Hi Adrian, Sorry for this late reply. The message goes to my junk box. I found it today. I checked with the source code, do some test by printing our the rate index at different stages in the kernel and found the issue. In the HAL, the rate order is: cck1 - cck2 - cck5.5 - cck11 - ofdm6 - ofdm9 - ofdm 12 In the 802.11, the rate order is: cck1 - cck2 - cck5.5 - ofdm6 - ofdm9 - cck11 - ofdm 12 So, the rate index for 6, 9 and 11 in the HAL and in 802.11 are actually different. When we select the rate, we need to pay attention to this and select the correct one. Here is my test codes: snprintf(log_str, MAX_LOG_MSG_LEN, "rate index: %u %u %u \n", ni->ni_rates.rs_rates[5], GET_RATE_AND_CLEAR_BASIC_BIT(5), sc->sc_rixmap[GET_RATE_AND_CLEAR_BASIC_BIT(5)]); usr_write_log(log_str); GET_RATE_AND_CLEAR_BASIC_BIT is a macro to clear the basic_rate bit, equally to remove 128 from the rate index. usr_write_log() is a user-defined function to write the input string to a separate user-defined log file. The output is: "rate index: 150 22 3" So the rate index number 5 in 802.11 is equally assigned to the rate index number 3 in the HAL. This is not a big thing but hopefully it helps the newbies like me and also ppl who work closely with the transmission rates. Viet-Ha -----Original Message----- From: Adrian Chadd Sent: Sunday, December 04, 2011 12:56 AM To: Viet-Ha Pham Cc: Freebsd Wireless Subject: Re: Rate index for 11 Mbps On 4 December 2011 13:36, Viet-Ha Pham wrote: > Hi there, > > I am working with the rate adaptation algorithm and at the very beginning > point of testing/programing. I have a concern with the rate index used in > the HAL. > > I wonder if the rate order in the rate table for 802.11g is 1 - 2 - 5.5 - > 6 > - 9 - 11 - 12 .... or 1 - 2 - 5.5 - 11 - 6 -9 - 12 ... ? The order of rate table entries is what you see: [for 11g]: /* short ctrl */ /* valid rateCode Preamble dot11Rate Rate */ /* 1 Mb */ { AH_TRUE, CCK, 1000, 0x1b, 0x00, (0x80| 2), 0 }, /* 2 Mb */ { AH_TRUE, CCK, 2000, 0x1a, 0x04, (0x80| 4), 1 }, /* 5.5 Mb */ { AH_TRUE, CCK, 5500, 0x19, 0x04, (0x80|11), 2 }, /* 11 Mb */ { AH_TRUE, CCK, 11000, 0x18, 0x04, (0x80|22), 3 }, /* remove rates 6, 9 from rate ctrl */ /* 6 Mb */ { AH_FALSE, OFDM, 6000, 0x0b, 0x00, 12, 4 }, /* 9 Mb */ { AH_FALSE, OFDM, 9000, 0x0f, 0x00, 18, 4 }, /* 12 Mb */ { AH_TRUE, OFDM, 12000, 0x0a, 0x00, 24, 6 }, .. so it's cck 1, cck 2, cck 5.5, cck 11, ofdm 6, ofdm 9, ofdm 12, ofdm 18 .. ofdm 54. > I read the source code (ar5212_phy.c) but I am still confused. Also there > is > a comment with the rate table for 802.11g: > > /* Venice TODO: roundUpRate() is broken when the rate table does not > represent rates > * in increasing order e.g. 5.5, 11, 6, 9. > * An average rate of 6 Mbps will currently map to 11 Mbps. > */ I don't know where roundUpRate() is - but yes, if your function tries to map a throughput to a rate table index, it'll have problems if it simply finds the first rate greater than your specified bit rate. HTH, Adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 12 11:07:36 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 81A881065680 for ; Mon, 12 Dec 2011 11:07:36 +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 6F1C38FC18 for ; Mon, 12 Dec 2011 11:07:36 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBCB7aji030201 for ; Mon, 12 Dec 2011 11:07:36 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBCB7ZtE030199 for freebsd-wireless@FreeBSD.org; Mon, 12 Dec 2011 11:07:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Dec 2011 11:07:35 GMT Message-Id: <201112121107.pBCB7ZtE030199@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, 12 Dec 2011 11:07:36 -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/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/162475 wireless [ath] functions with return type HAL_BOOL (might) retu o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under 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/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga 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/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/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/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/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 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 56 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 12 12:20:25 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 5E18C1065670 for ; Mon, 12 Dec 2011 12:20:25 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm4-vm0.bullet.mail.sp2.yahoo.com (nm4-vm0.bullet.mail.sp2.yahoo.com [98.139.91.190]) by mx1.freebsd.org (Postfix) with SMTP id 3081C8FC18 for ; Mon, 12 Dec 2011 12:20:25 +0000 (UTC) Received: from [98.139.91.67] by nm4.bullet.mail.sp2.yahoo.com with NNFMP; 12 Dec 2011 12:07:10 -0000 Received: from [98.136.185.47] by tm7.bullet.mail.sp2.yahoo.com with NNFMP; 12 Dec 2011 12:07:10 -0000 Received: from [127.0.0.1] by smtp108.mail.gq1.yahoo.com with NNFMP; 12 Dec 2011 12:07:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1323691630; bh=HAxDRqvQLNUPLtbxSqEcffzzx+axzZ7Fko2A6x4OuUA=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type:Content-Transfer-Encoding; b=l7XBUTM33NCTJp2KkQk17/7EoM0L2N3ZrjtlD/1lxTogjuT7BGHpn2VrqyUfwhHPifKAzNl2du8kIU0mktTFBJXsh4hyPgN6bA9l0Lu4NkBm9AUz5QNc8HYkboAhR/+Hk7XJI0AllimQ7jfa5W1Kzr9YiPHxCXaDkxfbwTzqizQ= X-Yahoo-Newman-Id: 199256.31594.bm@smtp108.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 7ybiqQEVM1mdE4NM3An4Yi0eP8XiY_vw_Lp5mbJYHQ1_Y7a geB61WALbJRRGXumhbAy1y5UXYLMxHpXspGDSvhABD2aTuYhiZGS1tDZbQ7W nPau_QPsJAm8ItkUet_NRd7WN6UteoEijuaSUwF.s9QKXbDk2Oe_mUlq_Qgn admAaZ_9VBCfFWi7DWrXctbz09wZUpm5S750IS5LN063f3E9kuz697.kkzIF TGlWp.LWFAha2YPBraeAc7IWJj6PSoZOecsvAm7J3MmGLXMM.ax5FkxxA_pK LKt8t9wlJ_6ZA4QvHMjYj5tIc.bGG.etg37kte18Rm0nhgLCWjG9sIG.YkCy qI1AQITF2N7WjmwWWSToCzR8gFICNuqTUp5IoEpeVtFJoXT1ev238R7ZpdoZ 6g2bpP3QkGzWvBKctPuU1ZuZbqUQyarzTlHTPDQk6f3oh1Cp1Q_qTuQcFy76 hNVunMEE.3XvJfhVPzcTAkziZKdyWj89V2q9ueQ89RR5ssxrq7bEBahfVeQh xeZ9xAfFaZmBcVBFiG5lPltHiXMxQdo0- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-qy0-f182.google.com (moonlightakkiy@209.85.216.182 with plain) by smtp108.mail.gq1.yahoo.com with SMTP; 12 Dec 2011 04:07:10 -0800 PST Received: by qcse13 with SMTP id e13so5056360qcs.13 for ; Mon, 12 Dec 2011 04:07:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.169.33 with SMTP id ab1mr15285392igc.0.1323691628713; Mon, 12 Dec 2011 04:07:08 -0800 (PST) Received: by 10.231.60.147 with HTTP; Mon, 12 Dec 2011 04:07:08 -0800 (PST) In-Reply-To: <20111211193600.3B0A01065670@hub.freebsd.org> References: <20111211193600.3B0A01065670@hub.freebsd.org> Date: Mon, 12 Dec 2011 05:07:08 -0700 Message-ID: From: PseudoCylon To: Carlos Corona , Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: freebsd-wireless Digest, Vol 28, Issue 1 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, 12 Dec 2011 12:20:25 -0000 > Message: 11 > Date: Thu, 1 Dec 2011 13:42:43 -0300 > From: Carlos Corona > Subject: Problem in FreeBSD 8.2 with Ralink > To: freebsd-wireless@freebsd.org > Message-ID: > =A0 =A0 =A0 =A0 > Content-Type: text/plain; charset=3DISO-8859-1 > > HI * > > I installed FreeBSD 8.2 amd64: > > FreeBSD Antonita 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41 > /src/sys/GENERIC =A0amd64 > > The ethernet is configured: > > re0: flags=3D8843 metric 0 mtu 15= 00 > =A0 =A0 =A0 =A0ether 68:b5:99:d3:ab:61 > =A0 =A0 =A0 =A0inet 200.104.116.57 netmask 0xffffff00 broadcast 200.104.1= 16.255 > =A0 =A0 =A0 =A0media: Ethernet autoselect (100baseTX ) > =A0 =A0 =A0 =A0status: active > > But not Wireless :( > > re0@pci0:1:0:0: class=3D0x020000 card=3D0x1611103c chip=3D0x816810ec rev= =3D0x06 > hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Realtek Semiconductor' > =A0 =A0device =A0 =A0 =3D 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8= 111c)' > =A0 =A0class =A0 =A0 =A0=3D network > =A0 =A0subclass =A0 =3D ethernet > none1@pci0:2:0:0: =A0 =A0 =A0 class=3D0x028000 card=3D0x1637103c chip=3D0= x539f1814 > rev=3D0x00 hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Ralink Technology, Corp.' > =A0 =A0class =A0 =A0 =A0=3D network > > I have HP Pavilion DM1, any idea? thx* > > > Message: 15 > Date: Sat, 3 Dec 2011 14:08:41 +0800 > From: Adrian Chadd > Subject: Re: Problem in FreeBSD 8.2 with Ralink > To: Carlos Corona > Cc: freebsd-wireless@freebsd.org > Message-ID: > =A0 =A0 =A0 =A0 > Content-Type: text/plain; charset=3DISO-8859-1 > > There's likely no support for that in FreeBSD-HEAD just yet. > > Ralink hackers, how's it going? > > > > Adrian > > By the ID, it is a newer chip, RT539x PCIe. None of us has the h/w (OpenBSD has not supported it either.). No data sheet, no h/w, you are out of luck, unfortunately. Try NIDS. Or, since you have the h/w, you can port ralink's driver http://www.ralinktech.com/en/04_support/support.php?sn=3D501 The benefits of porting the driver will be * lots of people will appreciate your work * you can brag about the work to your friends * your curriculum vitae will shine brilliantly * you might get headhunted by some tech company * you might get lucky with beastie chicks at the trade shows AK From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 12 13:50:51 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 40C17106566B for ; Mon, 12 Dec 2011 13:50:51 +0000 (UTC) (envelope-from francesco.rossi0@alice.it) Received: from smtp206.alice.it (smtp206.alice.it [82.57.200.102]) by mx1.freebsd.org (Postfix) with ESMTP id 029DF8FC0A for ; Mon, 12 Dec 2011 13:50:50 +0000 (UTC) Received: from [192.168.0.3] (79.7.187.209) by smtp206.alice.it (8.6.023.02) (authenticated as francesco.rossi0) id 4ECA6079034A733F for freebsd-wireless@freebsd.org; Mon, 12 Dec 2011 14:39:20 +0100 Message-ID: <4EE60407.8070702@alice.it> Date: Mon, 12 Dec 2011 14:39:19 +0100 From: Francesco Rossi User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:8.0) Gecko/20111123 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org References: <4EE60110.8060309@alice.it> In-Reply-To: <4EE60110.8060309@alice.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: freebsd 9rc2 e Atheros ar5413 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, 12 Dec 2011 13:50:51 -0000 From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 12 14:20:52 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 111C8106564A for ; Mon, 12 Dec 2011 14:20:52 +0000 (UTC) (envelope-from francesco.rossi0@alice.it) Received: from smtp209.alice.it (smtp209.alice.it [82.57.200.105]) by mx1.freebsd.org (Postfix) with ESMTP id 947B98FC0C for ; Mon, 12 Dec 2011 14:20:51 +0000 (UTC) Received: from [192.168.0.3] (79.7.187.209) by smtp209.alice.it (8.6.023.02) (authenticated as francesco.rossi0) id 4ECA624F02A82A34 for freebsd-wireless@freebsd.org; Mon, 12 Dec 2011 15:20:50 +0100 Message-ID: <4EE60DC1.8090806@alice.it> Date: Mon, 12 Dec 2011 15:20:49 +0100 From: Francesco Rossi User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:8.0) Gecko/20111123 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org References: <4EE60B0B.7000106@alice.it> <4EE60D64.50307@alice.it> In-Reply-To: <4EE60D64.50307@alice.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: freebsd 9 rc2 and Atheros ar5413 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, 12 Dec 2011 14:20:52 -0000 On 12.12.2011 15:19, Francesco Rossi wrote: > Hello and thanks in advance for your attention. > I am new to FreeBSD, but I must say that I love it. I am in Florence > and I apologize if my English is not quite correct, but I ask your > help please. I have a problem with my wireless card atheros ar5413. > I'm using FreeBSD 9 RC2, I tried PC-BSD RC2, very convenient to > quickly get a working desktop, but the kernel at boot gives me this > error: > > ath0: mem 0xfdee0000 0xfdeeffff irq 16 at device-4.0 on > pci2 > ath0: unable to attach hardware; HAL status 14 > device_attach: ath0 attach returned 6 > > The result of pciconf-lbcv on the wireless card is as follows: > > ath0 @ pci0: 2:4:0: class = 0x020000 card = 0x500111ad chip rev = 0x01 > hdr = 0x001b168c = 0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5413 802.11abg NIC' > class = network > subclass = ethernet > bar [10] = type Memory, range 32, base 0xfdee0000, size 65536, > enabled > Chapter 01 [44] = D0 D3 current powerspec 2 Supports D0 > > > > I went and checked the file GENERIC kernel configuration parameters: > > device ath > device ath_hal > options AH_SUPPORT_AR5416 > device ath_rate_sample > device wlan > I added > > device wlan > > It was not there and instead I removed this line: > > device ath_pci > > Then I recompiled the kernel and the warning no longer appears at > startup: > > ath0: mem 0xfdee0000 0xfdeeffff irq 16 at device-4.0 on > pci2 > ath0: unable to attach hardware; HAL status 14 > device_attach: ath0 attach returned 6 > But the wireless interface is still not recognized. > > If I add back the following line: > device ath_pci > > and recompile the kernel, then start the message > > ath0 attach returned 6. > > After this attempt, I tried removing and adding the following lines in > loader.conf: > > if_ath_load = "YES" > if_alc_load = "YES" > if_ath_pci_load = "YES" > > > but it does not solve the problem. > Help me please > From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 12 14:52: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 D5EB4106566B for ; Mon, 12 Dec 2011 14:52:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 954BC8FC18 for ; Mon, 12 Dec 2011 14:52:35 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so6510540vbb.13 for ; Mon, 12 Dec 2011 06:52:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=iRl4E76gvvo47i1MlLctDPIGlYQO4y1qw1wUb+X/jNQ=; b=G51DOkP7TxFF+qyoKvnUuqmEcgUUOwdvNcKIcsmgYU6Osf3gfsXHtyfQKo9VrpMpQa etgGZ88XSIl7YgEW8utYxzTAh9u1wGlf7GBf5bKsQSqIYxo6TdXaumyCC96dcFOXD147 5m1jx8IUtyXmYom+dbJYxz7aCEK2pITCMMyVk= MIME-Version: 1.0 Received: by 10.52.67.111 with SMTP id m15mr9823230vdt.96.1323701554787; Mon, 12 Dec 2011 06:52:34 -0800 (PST) Received: by 10.52.26.50 with HTTP; Mon, 12 Dec 2011 06:52:34 -0800 (PST) In-Reply-To: <4EE60DC1.8090806@alice.it> References: <4EE60B0B.7000106@alice.it> <4EE60D64.50307@alice.it> <4EE60DC1.8090806@alice.it> Date: Mon, 12 Dec 2011 06:52:34 -0800 Message-ID: From: Adrian Chadd To: Francesco Rossi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: freebsd 9 rc2 and Atheros ar5413 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, 12 Dec 2011 14:52:36 -0000 CAn you please add in: options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI then add this to /boot/loader.conf: hw.ath.hal.debug=3D0xffffffff and then email me the resultant kernel messages from bootup? Please ensure you compile this into your kernel rather than having it loaded as a module. I think PCBSD 9.0 compiles this as a module, and the kernel options won't appear in the module build. Thanks, Adrian On 12 December 2011 06:20, Francesco Rossi wrot= e: > On 12.12.2011 15:19, Francesco Rossi wrote: >> >> Hello and thanks in advance for your attention. >> I am new to FreeBSD, but I must say that I love it. I am in Florence and= I >> apologize if my English is not quite correct, but I ask your help please= . I >> have a problem with my wireless card atheros ar5413. >> I'm using FreeBSD 9 RC2, I tried PC-BSD RC2, very convenient to quickly >> get a working desktop, but the kernel at boot gives me this error: >> >> ath0: mem 0xfdee0000 0xfdeeffff irq 16 at device-4.0 on >> pci2 >> ath0: unable to attach hardware; HAL status 14 >> device_attach: ath0 attach returned 6 >> >> The result of pciconf-lbcv on the wireless card is as follows: >> >> ath0 @ pci0: 2:4:0: class =3D 0x020000 card =3D 0x500111ad chip rev =3D = 0x01 hdr >> =3D 0x001b168c =3D 0x00 >> =A0 =A0 vendor =3D 'Atheros Communications Inc.' >> =A0 =A0 device =3D 'AR5413 802.11abg NIC' >> =A0 =A0 class =3D network >> =A0 =A0 subclass =3D ethernet >> =A0 =A0 bar [10] =3D type Memory, range 32, base 0xfdee0000, size 65536,= enabled >> =A0 =A0 Chapter 01 [44] =3D D0 D3 current powerspec 2 Supports D0 >> >> >> >> I went and checked the file GENERIC kernel configuration parameters: >> >> =A0 =A0 =A0 =A0 =A0 device ath >> =A0 =A0 =A0 =A0 =A0 device ath_hal >> =A0 =A0 =A0 =A0 =A0 options AH_SUPPORT_AR5416 >> =A0 =A0 =A0 =A0 =A0 device ath_rate_sample >> =A0 =A0 =A0 =A0 =A0 device wlan >> I added >> >> =A0 =A0 =A0 =A0 =A0 device wlan >> >> It was not there and instead I removed this line: >> >> =A0 =A0 =A0 =A0 =A0 device ath_pci >> >> Then I recompiled the kernel and the warning no longer appears at startu= p: >> >> ath0: mem 0xfdee0000 0xfdeeffff irq 16 at device-4.0 on >> pci2 >> ath0: unable to attach hardware; HAL status 14 >> device_attach: ath0 attach returned 6 >> But the wireless interface is still not recognized. >> >> If I add back the following line: >> =A0device ath_pci >> >> and recompile the kernel, then start the message >> >> ath0 attach returned 6. >> >> After this attempt, I tried removing and adding the following lines in >> loader.conf: >> >> if_ath_load =3D "YES" >> if_alc_load =3D "YES" >> if_ath_pci_load =3D "YES" >> >> >> but it does not solve the problem. >> Help me please >> > > _______________________________________________ > 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 Dec 15 00:45: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 7D8F61065672 for ; Thu, 15 Dec 2011 00:45:35 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (secure.freebsdsolutions.net [69.55.234.48]) by mx1.freebsd.org (Postfix) with ESMTP id 4B04D8FC12 for ; Thu, 15 Dec 2011 00:45:34 +0000 (UTC) Received: from [192.168.2.82] (jn@stealth.jnielsen.net [74.218.226.254]) (authenticated bits=0) by ns1.jnielsen.net (8.14.4/8.14.4) with ESMTP id pBF0LSui006808 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Wed, 14 Dec 2011 19:21:29 -0500 (EST) (envelope-from lists@jnielsen.net) From: John Nielsen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 14 Dec 2011 19:21:30 -0500 Message-Id: <40D93FD7-96BC-4A79-B92A-E19831BA9FB5@jnielsen.net> To: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-DCC-x.dcc-servers-Metrics: ns1.jnielsen.net; whitelist Subject: Is "bssid" parameter to ifconfig supported with ath? 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, 15 Dec 2011 00:45:35 -0000 I know at some point I was able to do e.g.: ifconfig wlan0 create wlandev ath0 wlanmode hostap bssid ifconfig wlan1 create wlandev ath0 wlanmode hostap bssid and end up with different MAC addresses on wlan0 and wlan1. Recently = (and possibly for some time) that has not been the case. All wlan = interfaces end up with the MAC address of the parent device, which = (obviously) causes problems if actually using more than one vap. Using = "wlanaddr" and a manual address instead works as expected. From owner-freebsd-wireless@FreeBSD.ORG Thu Dec 15 00:46:57 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 B84FD106566C for ; Thu, 15 Dec 2011 00:46:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 72B6A8FC15 for ; Thu, 15 Dec 2011 00:46:57 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so1787591vbb.13 for ; Wed, 14 Dec 2011 16:46:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=W8BEE281JMzQQ/e8lyfIH5nJcKNMgDz+F7LXLhdP8RM=; b=oLANEEOEAsRY/gohzJt6ZXmz7ioANQBIR3opGygwckAiaex4BCwcIM9Wh9iP9e2zT6 CaywI6tqxdvBODcAM/Z8ZLAC2lqRlHzDvdiieKj8SGFFMv1cYLVpHSVCOGd9OvMeT4uc +AiY3hGCkzmuWn6a3acG6L6IBmtliChpbxqD4= MIME-Version: 1.0 Received: by 10.52.65.129 with SMTP id x1mr1063575vds.11.1323910016904; Wed, 14 Dec 2011 16:46:56 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.26.50 with HTTP; Wed, 14 Dec 2011 16:46:56 -0800 (PST) In-Reply-To: <40D93FD7-96BC-4A79-B92A-E19831BA9FB5@jnielsen.net> References: <40D93FD7-96BC-4A79-B92A-E19831BA9FB5@jnielsen.net> Date: Wed, 14 Dec 2011 16:46:56 -0800 X-Google-Sender-Auth: 0VDhkEcNRMKog6ZKPQMA2UQRw4Q Message-ID: From: Adrian Chadd To: John Nielsen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Is "bssid" parameter to ifconfig supported with ath? 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, 15 Dec 2011 00:46:57 -0000 Hi, Please file another bug and I'll investigate what happened/changed. Adrian On 14 December 2011 16:21, John Nielsen wrote: > I know at some point I was able to do e.g.: > > =A0 =A0 =A0 =A0ifconfig wlan0 create wlandev ath0 wlanmode hostap bssid > =A0 =A0 =A0 =A0ifconfig wlan1 create wlandev ath0 wlanmode hostap bssid > > and end up with different MAC addresses on wlan0 and wlan1. Recently (and= possibly for some time) that has not been the case. All wlan interfaces en= d up with the MAC address of the parent device, which (obviously) causes pr= oblems if actually using more than one vap. Using "wlanaddr" and a manual a= ddress instead works as expected. > > _______________________________________________ > 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 Fri Dec 16 07:58:46 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 B41DD106566C; Fri, 16 Dec 2011 07:58:46 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8A9098FC19; Fri, 16 Dec 2011 07:58:46 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBG7wkNC029010; Fri, 16 Dec 2011 07:58:46 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBG7wkgL029006; Fri, 16 Dec 2011 07:58:46 GMT (envelope-from linimon) Date: Fri, 16 Dec 2011 07:58:46 GMT Message-Id: <201112160758.pBG7wkgL029006@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/163318: [ath] ath(4) stops working 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: Fri, 16 Dec 2011 07:58:46 -0000 Old Synopsis: ath(4) stops working New Synopsis: [ath] ath(4) stops working Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Fri Dec 16 07:58:36 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=163318 From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 16 09:07:37 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 432061065670; Fri, 16 Dec 2011 09:07:37 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 195918FC17; Fri, 16 Dec 2011 09:07:37 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBG97akO096275; Fri, 16 Dec 2011 09:07:36 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBG97aon096271; Fri, 16 Dec 2011 09:07:36 GMT (envelope-from linimon) Date: Fri, 16 Dec 2011 09:07:36 GMT Message-Id: <201112160907.pBG97aon096271@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/163312: [panic] [ath driver] kernel panic: page fault with ath0 taskq 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: Fri, 16 Dec 2011 09:07:37 -0000 Synopsis: [panic] [ath driver] kernel panic: page fault with ath0 taskq Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Fri Dec 16 09:07:29 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=163312 From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 16 23:30:15 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 93A8B106564A for ; Fri, 16 Dec 2011 23:30:15 +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 830C68FC16 for ; Fri, 16 Dec 2011 23:30:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBGNUFTq091774 for ; Fri, 16 Dec 2011 23:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBGNUFV6091773; Fri, 16 Dec 2011 23:30:15 GMT (envelope-from gnats) Date: Fri, 16 Dec 2011 23:30:15 GMT Message-Id: <201112162330.pBGNUFV6091773@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Joel Dahl Cc: Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joel Dahl 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, 16 Dec 2011 23:30:15 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Joel Dahl To: bug-followup@freebsd.org Cc: Subject: Re: kern/163318: [ath] ath(4) stops working Date: Sat, 17 Dec 2011 00:09:02 +0100 I left the machine for a few hours again and when I came back I noticed the following messages on the console (wireless died as usual): Dec 16 17:26:31 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Dec 16 17:26:36 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Dec 16 17:43:54 crashbox kernel: ar5416PerCalibrationN: NF calibration didn't finish; delaying CCA Dec 16 18:26:38 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Dec 16 18:26:42 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Dec 16 18:49:24 crashbox kernel: ar5416PerCalibrationN: NF calibration didn't finish; delaying CCA Dec 16 19:26:42 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Dec 16 19:29:50 crashbox kernel: ath0: device timeout Dec 16 19:29:50 crashbox kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing Dec 16 19:29:50 crashbox kernel: ath0: ath_chan_set: danger! concurrent reset! Dec 16 19:29:50 crashbox kernel: ath0: ath_tx_tid_drain: node 0xffffff80014a2000: tid 0: txq_depth=0, txq_aggr_depth=0, sched=1, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=0, ni_txseqs=15229 Dec 16 19:29:50 crashbox kernel: ath0: ath_start: sc_inreset_cnt > 0; bailing Dec 16 20:26:42 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Dec 16 20:26:46 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] Dec 16 21:26:45 crashbox wpa_supplicant[473]: WPA: Group rekeying completed with f8:1e:df:fc:34:2b [GTK=CCMP] -- Joel From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 17 06:35:02 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 804ED106564A for ; Sat, 17 Dec 2011 06:35:02 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.226.44]) by mx1.freebsd.org (Postfix) with ESMTP id 33AF98FC0C for ; Sat, 17 Dec 2011 06:35:01 +0000 (UTC) Received: from amd620.ovitrap.com ([122.129.201.7]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id pBH5wXGb001006 for ; Fri, 16 Dec 2011 22:58:35 -0700 From: Erich Dollansky To: freebsd-wireless@freebsd.org Date: Sat, 17 Dec 2011 12:58:56 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.5; amd64; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201112171258.56891.erichfreebsdlist@ovitrap.com> Subject: Zyxel NWD210N not accepted at boot time but after plugging it in again 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: Sat, 17 Dec 2011 06:35:02 -0000 Hi, I have a simple problem with this Zyxel wireless adaptor. I am not able to use it directly after a reboot. The interface becomes only available after I unplug it and plug it in again. I believe that this is the crucial message: run0: could not load 8051 microcode As I have said, it all works as expected after I plugged it in again. Here is my dmesg with the messages regarding the device. The first part is from the boot and the remaining is from the replugging. run0: <1.0> on usbus1 run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 runfw: root not mounted yet, no way to load image run0: failed loadfirmware of file runfw run0: could not load 8051 microcode device_attach: run0 attach returned 6 run0: <1.0> on usbus1 run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 run0: firmware RT2870 loaded I think that the explanation is so simple but I do not see it. Thanks! Erich From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 17 13:11:08 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 01B94106566B for ; Sat, 17 Dec 2011 13:11:08 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 917F98FC15 for ; Sat, 17 Dec 2011 13:11:07 +0000 (UTC) Received: by eekc50 with SMTP id c50so4690614eek.13 for ; Sat, 17 Dec 2011 05:11:06 -0800 (PST) Received: by 10.14.123.130 with SMTP id v2mr1203290eeh.56.1324127466220; Sat, 17 Dec 2011 05:11:06 -0800 (PST) Received: from amy.lab.techwires.net (dslb-178-002-168-014.pools.arcor-ip.net. [178.2.168.14]) by mx.google.com with ESMTPS id x12sm14843428eef.9.2011.12.17.05.11.04 (version=SSLv3 cipher=OTHER); Sat, 17 Dec 2011 05:11:05 -0800 (PST) Sender: Bernhard Schmidt From: Bernhard Schmidt To: freebsd-wireless@freebsd.org Date: Sat, 17 Dec 2011 14:11:05 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.0-PRERELEASE; KDE/4.7.3; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> In-Reply-To: <201112171258.56891.erichfreebsdlist@ovitrap.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112171411.05872.bschmidt@freebsd.org> Cc: PseudoCylon Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again 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: Sat, 17 Dec 2011 13:11:08 -0000 On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > Hi, > > I have a simple problem with this Zyxel wireless adaptor. I am not able to use it directly after a reboot. The interface becomes only available after I unplug it and plug it in again. > > I believe that this is the crucial message: > > run0: could not load 8051 microcode > > As I have said, it all works as expected after I plugged it in again. > > Here is my dmesg with the messages regarding the device. The first part is from the boot and the remaining is from the replugging. > > run0: <1.0> on usbus1 > run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 > runfw: root not mounted yet, no way to load image > run0: failed loadfirmware of file runfw > run0: could not load 8051 microcode > device_attach: run0 attach returned 6 > run0: <1.0> on usbus1 > run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 > run0: firmware RT2870 loaded > > I think that the explanation is so simple but I do not see it. run(4) tries to load the firmware on attach at which point the root filesystem isn't yet mounted. Actually I think the prefered behaviour is to load it during init, not sure this is possible for run(4) though. Someone should check this. :) As a workaround you can add runfw_load="YES" to /boot/loader.conf -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 17 23:44:52 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 32ADC106566C for ; Sat, 17 Dec 2011 23:44:52 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.226.44]) by mx1.freebsd.org (Postfix) with ESMTP id 083958FC1C for ; Sat, 17 Dec 2011 23:44:51 +0000 (UTC) Received: from amd620.ovitrap.com ([122.129.201.7]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id pBHNinaC025144; Sat, 17 Dec 2011 16:44:50 -0700 From: Erich Dollansky To: Bernhard Schmidt Date: Sun, 18 Dec 2011 06:45:14 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.5; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112171411.05872.bschmidt@freebsd.org> In-Reply-To: <201112171411.05872.bschmidt@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112180645.14868.erichfreebsdlist@ovitrap.com> Cc: freebsd-wireless@freebsd.org, PseudoCylon Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again 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: Sat, 17 Dec 2011 23:44:52 -0000 Hi, On Saturday 17 December 2011 20:11:05 Bernhard Schmidt wrote: > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > > > > I have a simple problem with this Zyxel wireless adaptor. I am not able to use it directly after a reboot. The interface becomes only available after I unplug it and plug it in again. > > > > I believe that this is the crucial message: > > > > run0: could not load 8051 microcode > > > > As I have said, it all works as expected after I plugged it in again. > > > > Here is my dmesg with the messages regarding the device. The first part is from the boot and the remaining is from the replugging. > > > > run0: <1.0> on usbus1 > > run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 > > runfw: root not mounted yet, no way to load image > > run0: failed loadfirmware of file runfw > > run0: could not load 8051 microcode > > device_attach: run0 attach returned 6 > > run0: <1.0> on usbus1 > > run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 > > run0: firmware RT2870 loaded > > > > I think that the explanation is so simple but I do not see it. > > run(4) tries to load the firmware on attach at which point the root > filesystem isn't yet mounted. Actually I think the prefered behaviour > is to load it during init, not sure this is possible for run(4) > though. Someone should check this. :) > > As a workaround you can add runfw_load="YES" to /boot/loader.conf this made it work. You seem to be German. You know then the line 'den Wald vor lauter Baeumen ...' Thanks for your help. Erich > > -- > Bernhard > > From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 17 23:58: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 D7C4A1065670 for ; Sat, 17 Dec 2011 23:58:20 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm24-vm0.bullet.mail.bf1.yahoo.com (nm24-vm0.bullet.mail.bf1.yahoo.com [98.139.213.161]) by mx1.freebsd.org (Postfix) with SMTP id 756328FC12 for ; Sat, 17 Dec 2011 23:58:20 +0000 (UTC) Received: from [98.139.212.144] by nm24.bullet.mail.bf1.yahoo.com with NNFMP; 17 Dec 2011 23:45:19 -0000 Received: from [98.139.211.205] by tm1.bullet.mail.bf1.yahoo.com with NNFMP; 17 Dec 2011 23:45:19 -0000 Received: from [127.0.0.1] by smtp214.mail.bf1.yahoo.com with NNFMP; 17 Dec 2011 23:45:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1324165519; bh=2kMjneHIiKFqzJ7on+1itq43YLNdH9V28MpuNmX/nBg=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=zPW2AgccKWeNpsfkGpWKaL9CGFZoJp+azJ2B/9yB2KzxcRr+ukwoz2G+DxzzWwQvTbdgHru/q4V1ORmgB2XgxnleLpitvFMrKDFHusTn5Fg797ba2BzPHK0UIwRsGlnM4TENy21/1rHbo6UnfMZpSderjgE2Idw32PAmB5L5/3I= X-Yahoo-Newman-Id: 219821.111.bm@smtp214.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: cOIEpAAVM1lt_GuMGdGPj3TLKQr1GLoDA8MNj5E3fQRnOe7 80N8_fjqGsBddClLKWoMklv6ms7JmL976IgOShBfn3Xpgxf7ZzTJenNR8Dth 24T1hAcdFWmzDGFhGqHmM5vrQRsmQx2YCNWTt0YmA2HwXXc.KYsdz.ofkBik Wyr.iU8yiyqZp9oy2AL1LtRpgywpZp5eqEXR4iX_x9abmMUNQVywdLdT3l5e eE5DdVWtzsAinET.DII2vs.sl1k0x6pd2y8Q1rc2wRt5sKgasZLRTfdsiDHu i2xlEDS_COHfj2EfMYV.jNRmXWNT129On7HxKY2zsVu1ihmo_ozI2AKsjbtQ eT7AByqtSm9EZnoVUFC6pLd.ZR5ulcDslvWTvLbEkk2TbyMZW0JxcQbB.oXX HlL7Zb6I_Q.IiAjKbVxLPPsXZ X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-iy0-f182.google.com (moonlightakkiy@209.85.210.182 with plain) by smtp214.mail.bf1.yahoo.com with SMTP; 17 Dec 2011 15:45:19 -0800 PST Received: by iadj38 with SMTP id j38so3577368iad.13 for ; Sat, 17 Dec 2011 15:45:18 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.181.136 with SMTP id dw8mr17914568igc.71.1324165518735; Sat, 17 Dec 2011 15:45:18 -0800 (PST) Received: by 10.231.190.81 with HTTP; Sat, 17 Dec 2011 15:45:18 -0800 (PST) In-Reply-To: <201112171411.05872.bschmidt@freebsd.org> References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112171411.05872.bschmidt@freebsd.org> Date: Sat, 17 Dec 2011 16:45:18 -0700 Message-ID: From: PseudoCylon To: Bernhard Schmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again 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: Sat, 17 Dec 2011 23:58:20 -0000 On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: >> Hi, >> >> I have a simple problem with this Zyxel wireless adaptor. I am not able to use it directly after a reboot. The interface becomes only available after I unplug it and plug it in again. >> >> I believe that this is the crucial message: >> >> run0: could not load 8051 microcode >> >> As I have said, it all works as expected after I plugged it in again. >> >> Here is my dmesg with the messages regarding the device. The first part is from the boot and the remaining is from the replugging. >> >> run0: <1.0> on usbus1 >> run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 >> runfw: root not mounted yet, no way to load image >> run0: failed loadfirmware of file runfw >> run0: could not load 8051 microcode >> device_attach: run0 attach returned 6 >> run0: <1.0> on usbus1 >> run0: MAC/BBP RT2860 (rev 0x0102), RF RT2820 (MIMO 2T2R), address 00:19:cb:85:aa:76 >> run0: firmware RT2870 loaded >> >> I think that the explanation is so simple but I do not see it. > > run(4) tries to load the firmware on attach at which point the root > filesystem isn't yet mounted. Actually I think the prefered behaviour > is to load it during init, not sure this is possible for run(4) > though. Someone should check this. :) > mmm... It seems "someone" is me. At the quick look, the firmware could be loaded during the init. Give me a few days, I will try to change. > As a workaround you can add runfw_load="YES" to /boot/loader.conf > Yep. This should load the firmware during the boot. AK