From owner-freebsd-wireless@FreeBSD.ORG Sun Nov 11 04:22:47 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B06083CB; Sun, 11 Nov 2012 04:22:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 679558FC0A; Sun, 11 Nov 2012 04:22:47 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id bi1so3794752pad.13 for ; Sat, 10 Nov 2012 20:22:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=XHXYOk1y/BjDQfXAtiOlw49Ik362VXVcumfharbU3/4=; b=0dw+gBHs7IvZaWv4EsvK3wSNuZswPZ226c3CYNZAajJSVcPHe6eB/kybuvURPx+sWs tZqnY/ZkjW4imcJlwGt2Wx6VuNwtcjGgYqr9Rz6oLhhqnJywUyljl99BJPM/NoUMIgij cO9F8evjT4vb5ihnexVR7JWmpWQBiJEJ24Q9lseu68XXbGveE/3uAnQQZ1OYeEzFpAX2 0vnW6RHze75EDCoXumCd9j5CiJsRqGU9kHK0SsoIvlyPEJ6hyQqIh8BHGhnmS3PibObR FgSs+NUWYA5VxiRjuo+8OXkVUcIkdMW1oFQ24L7sDc/v4WUpvTPvVEPQwWk2G6tvHNLK /Tbw== MIME-Version: 1.0 Received: by 10.66.87.132 with SMTP id ay4mr44271403pab.67.1352607766952; Sat, 10 Nov 2012 20:22:46 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Sat, 10 Nov 2012 20:22:46 -0800 (PST) In-Reply-To: <1352369243.2368.4.camel@nsl> References: <1352350980.91751.YahooMailNeo@web122401.mail.ne1.yahoo.com> <1352351370.96695.YahooMailNeo@web122401.mail.ne1.yahoo.com> <509B783D.6010403@FreeBSD.org> <1352369243.2368.4.camel@nsl> Date: Sat, 10 Nov 2012 20:22:46 -0800 X-Google-Sender-Auth: 7oiDr2zN6ydGRjoKN3SiR_JyVus Message-ID: Subject: Re: Re: porting urtwn from openbsd to freebsd for RTL8188CE Driver Support From: Adrian Chadd To: Kevin Lo Content-Type: text/plain; charset=ISO-8859-1 Cc: Christopher Patrick , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 04:22:47 -0000 On 8 November 2012 02:07, Kevin Lo wrote: > Kevin Lo wrote: >> I am by no means a serious wireless expert. After hours of porting/hacking, >> I came up with code what finally compiled and a basic function worked >> for me. >> Wish I had more free time to finish it. Sweet! Does it pass packets? adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Nov 12 09:20:16 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6AAF55C4; Mon, 12 Nov 2012 09:20:16 +0000 (UTC) (envelope-from kevlo@FreeBSD.org) Received: from ns.kevlo.org (kevlo.org [220.128.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id F1EA68FC08; Mon, 12 Nov 2012 09:20:15 +0000 (UTC) Received: from srg.kevlo.org (git.kevlo.org [220.128.136.52]) by ns.kevlo.org (8.14.5/8.14.5) with ESMTP id qAC9K7l3047167; Mon, 12 Nov 2012 17:20:07 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <50A0BF4E.6070803@FreeBSD.org> Date: Mon, 12 Nov 2012 17:20:14 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20121009 Thunderbird/15.0.1 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Re: Re: porting urtwn from openbsd to freebsd for RTL8188CE Driver Support References: <1352350980.91751.YahooMailNeo@web122401.mail.ne1.yahoo.com> <1352351370.96695.YahooMailNeo@web122401.mail.ne1.yahoo.com> <509B783D.6010403@FreeBSD.org> <1352369243.2368.4.camel@nsl> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Christopher Patrick , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 09:20:16 -0000 On 2012/11/11 12:22, Adrian Chadd wrote: > On 8 November 2012 02:07, Kevin Lo wrote: >> Kevin Lo wrote: >>> I am by no means a serious wireless expert. After hours of porting/hacking, >>> I came up with code what finally compiled and a basic function worked >>> for me. >>> Wish I had more free time to finish it. > Sweet! Does it pass packets? It hangs when associating with an access point, but I have an idea where the problem lies. This is just a quick port of OpenBSD urtwn, a lot of work needs to be done. :-) Note that urtwn doesn't support RTL8188CE. RTL8188CE is a mini PCIe device. > > > adrian > Kevin From owner-freebsd-wireless@FreeBSD.ORG Mon Nov 12 11:06:54 2012 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EFABFA76 for ; Mon, 12 Nov 2012 11:06:53 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id CA0E08FC12 for ; Mon, 12 Nov 2012 11:06:53 +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 qACB6r8Y000551 for ; Mon, 12 Nov 2012 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qACB6rij000549 for freebsd-wireless@FreeBSD.org; Mon, 12 Nov 2012 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Nov 2012 11:06:53 GMT Message-Id: <201211121106.qACB6rij000549@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 Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 11:06:54 -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/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171394 wireless [ath] ath0: ath_tx_aggr_comp_aggr: num frames seen=1; o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl 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/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/153594 wireless [wlan] netif/devd race 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/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u 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 kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but 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 135 problems total. From owner-freebsd-wireless@FreeBSD.ORG Tue Nov 13 20:01:06 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16FD6917 for ; Tue, 13 Nov 2012 20:01:06 +0000 (UTC) (envelope-from ed@kikkert-online.nl) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mx1.freebsd.org (Postfix) with ESMTP id D05E18FC15 for ; Tue, 13 Nov 2012 20:01:04 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9A60A2054B for ; Tue, 13 Nov 2012 15:00:58 -0500 (EST) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 13 Nov 2012 15:00:58 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=from:content-type:subject:date:message-id :to:mime-version; s=smtpout; bh=5dNG7dCDcdKQC6J0oCOusaeKGI4=; b= rCoC017sAJCDjfucceEwTHxTD3VFt9Q4rmfmeYfzH701lIkmlLORnUgh6vY2uf6p 5nbWphWs9OzF8U+KjwFkQljkVVzE9lKpL5P2h5pvAzRSgQbceLsjTkIexFI7zBXw jdzORTq46enhJWAEE5va478xQOtCsd15sVeLs2NiiYo= X-Sasl-enc: A4KtY3/kim4XyGfvEoHuKSPKSbCu2SnfawlvHcO5pT8O 1352836858 Received: from [10.20.30.104] (unknown [62.238.204.95]) by mail.messagingengine.com (Postfix) with ESMTPA id 240E84827C3 for ; Tue, 13 Nov 2012 15:00:58 -0500 (EST) From: Ed Kikkert Subject: Network Event Kit serving 750+ devices at ApacheCon2012 Date: Tue, 13 Nov 2012 21:01:02 +0100 Message-Id: To: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Apple Message framework v1278) X-Mailer: Apple Mail (2.1278) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 13 Nov 2012 20:01:06 -0000 During ApacheCon2012 The Network Event Kit has served 750+ devices, assisted in making ApacheCon2012 a big success. Our newly defined small cell approach designed by Marten Vijn delivered a stable wireless network on both the 2.4Ghz and 5Ghz bands. Main focus was to reduce the txpower to manageable levels, avoid overlap and pro-actively design rules for congestion control on the multiple OSI levels. This all is now implemented and has an proactive monitoring visualization designed by Rick van der Zwet. Having this amount of devices connected to the 20 access points is causing a lot of local broadcast and multicast traffic filling up the = network stack. This was during the first day growing that in the end it was = almost=20 impossible for other traffic to find it's way to the internet. To stop = this we=20 setup some OpenBSD PF rules on each of the access points and not on=20 the firewall. =20 During the event we got new insights with regards of manageability of ath(4) devices and their configuration, most worthy noticing are the finding with regards to the diversity setup of the cards with a single connected antenna in correlation with the 'stuck baecon; resetting' errors. Thanks to athstats(8) and other useful debugging tools provided by Sam Leffner in the FreeBSD source tree. In the next few weeks we will validate this results and post our findings to the various open source communities. Our newly logistics and deployment approach by Ed Kikkert has tackled successfully our issues with storage and distribution and greatly increased our visibility. Main focus was better communication by using peer-radio-devices and stricter task assignment causing more efficiently. A picture impression made by Roel Guldemond can be found at our new Network Kit Website (under construction): http://nek.wifisoft.org/site/node/9 Screen dumps from the proactive monitoring visualization made by Rick = van der Zwet. http://bsd.wifisoft.org/svn/projects/nek/images/monitoring/ =20 Source code and NanoBSD configuration is found at: http://bsd.wifisoft.org/svn/projects/nek/events/ApacheCon-2012/ All improvements will allows us to start powering 2000+ devices events Gerard Mourits will be continue his efforts of finding new interesting events for The Network Event Kit to power. The organisation likes to thank NLNet, InfraData and other sponsors for their continued support and the volunteers for their endeavoured enthusiasm and enlightening week. Best regards, Ed Kikkert - Secratary of WifiSoft Foundation= From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 15 02:01:08 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A0DDCDA for ; Thu, 15 Nov 2012 02:01:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id CDADB8FC0C for ; Thu, 15 Nov 2012 02:01:07 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id wz12so860264pbc.13 for ; Wed, 14 Nov 2012 18:01:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=B5lH4oO3d0Vf5Y64vkgmftNNQ2cp0My10fDMWWnKvF4=; b=JWu0vldkN/dkF6NRqJ+zSjimxAX/vpz30toHp2lP8WqVQhJVRzW7DJ0bOY/WzVPG3h lvIkRk1YRXSWWG6kmWWY/IyEIH+O8uo/u6wfNOloU3dkwwgOlRr2AKwNLIsfv/IYuAql zIN8RHMsN407K+vv1j/CJQHtv7B1JRV9hTlSaeyzvX/7JeOb0/O91JMUIXKH0aN0LSP5 p1SK8pm52snOD1yyPepDCdRB2Gd4074TTMRFlGCBaabAk70CKlPat0Fl0YPdCh3eWKzl eK2PYgdyHRuSm1aLnVsKmY+tdHCCWxxaYSyFk1IFS0xQrlFBla5KKsJzbhqvUZP/uI0e W5tw== MIME-Version: 1.0 Received: by 10.68.251.197 with SMTP id zm5mr76483230pbc.30.1352944867107; Wed, 14 Nov 2012 18:01:07 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Wed, 14 Nov 2012 18:01:07 -0800 (PST) In-Reply-To: References: Date: Wed, 14 Nov 2012 18:01:07 -0800 X-Google-Sender-Auth: mJDimjdTLti7vLI95qFMQ7I7z3k Message-ID: Subject: Re: Network Event Kit serving 750+ devices at ApacheCon2012 From: Adrian Chadd To: Ed Kikkert Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 02:01:08 -0000 Hi, That's fantastic news! For those who aren't quite tuned in - they're pushing out FreeBSD-8 on Alix's with Atheros 11abg NICs. No 11n NIC yet unfortunately. Adrian On 13 November 2012 12:01, Ed Kikkert wrote: > During ApacheCon2012 The Network Event Kit has served 750+ devices, > assisted in making ApacheCon2012 a big success. > > Our newly defined small cell approach designed by Marten Vijn > delivered a stable wireless network on both the 2.4Ghz and 5Ghz bands. > Main focus was to reduce the txpower to manageable levels, avoid > overlap and pro-actively design rules for congestion control on the > multiple OSI levels. This all is now implemented and has an proactive > monitoring visualization designed by Rick van der Zwet. > > Having this amount of devices connected to the 20 access points is > causing a lot of local broadcast and multicast traffic filling up the network > stack. This was during the first day growing that in the end it was almost > impossible for other traffic to find it's way to the internet. To stop this we > setup some OpenBSD PF rules on each of the access points and not on > the firewall. > > During the event we got new insights with regards of manageability of > ath(4) devices and their configuration, most worthy noticing are the > finding with regards to the diversity setup of the cards with a single > connected antenna in correlation with the 'stuck baecon; resetting' > errors. Thanks to athstats(8) and other useful debugging tools > provided by Sam Leffner in the FreeBSD source tree. In the next few > weeks we will validate this results and post our findings to the > various open source communities. > > Our newly logistics and deployment approach by Ed Kikkert has tackled > successfully our issues with storage and distribution and greatly > increased our visibility. Main focus was better communication by using > peer-radio-devices and stricter task assignment causing more > efficiently. > > A picture impression made by Roel Guldemond can be found at our new > Network Kit Website (under construction): > http://nek.wifisoft.org/site/node/9 > > Screen dumps from the proactive monitoring visualization made by Rick van der Zwet. > http://bsd.wifisoft.org/svn/projects/nek/images/monitoring/ > > Source code and NanoBSD configuration is found at: > http://bsd.wifisoft.org/svn/projects/nek/events/ApacheCon-2012/ > > All improvements will allows us to start powering 2000+ devices events > Gerard Mourits will be continue his efforts of finding new interesting > events for The Network Event Kit to power. > > The organisation likes to thank NLNet, InfraData and other sponsors > for their continued support and the volunteers for their endeavoured > enthusiasm and enlightening week. > > Best regards, > Ed Kikkert - Secratary of WifiSoft Foundation > _______________________________________________ > 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" From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 15 02:54:30 2012 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6245E4F9; Thu, 15 Nov 2012 02:54:30 +0000 (UTC) (envelope-from rpaulo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 2BF758FC14; Thu, 15 Nov 2012 02:54:30 +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 qAF2sUVu068125; Thu, 15 Nov 2012 02:54:30 GMT (envelope-from rpaulo@freefall.freebsd.org) Received: (from rpaulo@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qAF2sU19068121; Thu, 15 Nov 2012 02:54:30 GMT (envelope-from rpaulo) Date: Thu, 15 Nov 2012 02:54:30 GMT Message-Id: <201211150254.qAF2sU19068121@freefall.freebsd.org> To: rpaulo@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: rpaulo@FreeBSD.org Subject: Re: kern/173636: ath1: bad series0 hwrate 0x0, tries 1 ts_status 0x0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 02:54:30 -0000 Synopsis: ath1: bad series0 hwrate 0x0, tries 1 ts_status 0x0 Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: rpaulo Responsible-Changed-When: Thu Nov 15 02:51:56 UTC 2012 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=173636 From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 15 06:36:03 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A57F9F9E for ; Thu, 15 Nov 2012 06:36:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 655EF8FC0C for ; Thu, 15 Nov 2012 06:36:03 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so1683143oag.13 for ; Wed, 14 Nov 2012 22:36:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=KyeacMcONs3LwiVC3+cByhjbeuW6SWqYeewRdQhEGk4=; b=MNLym9gF1wQRIzOYiA22lRONlZR6RjJVF5uRZ64BppMuNqy0C9pj8ReffGIA2nBNYX GaVJSt+DGwISQHO68Z+YhmpclLKi/LEPMsSLJrioYPx55azBODuuKfZg8HHhI4596jhr DqKuUgsHFCPA7rnTPMdU0IFDN20bj9ARBJ5QP+raJHJ6f9ks+xapBLHFRDLVwBgmc0EG 0Oksrl/f04EsEhh8UUD5hnfMfOyvtwfZACrWUrP37c5UwYXJUh1zO+o0KDaVuc0TsKv3 IxMH5fiaEoq5C8ItN6eNE+0U4eXHJdYfX356+3ay3TvjfF/4bUhmCVsm3jmZpUuBz4W6 iVxQ== MIME-Version: 1.0 Received: by 10.60.7.106 with SMTP id i10mr145680oea.5.1352961362809; Wed, 14 Nov 2012 22:36:02 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.76.27.65 with HTTP; Wed, 14 Nov 2012 22:36:02 -0800 (PST) Date: Wed, 14 Nov 2012 22:36:02 -0800 X-Google-Sender-Auth: i_04kKxApxX1HVjpb28BzI8gtfI Message-ID: Subject: Today's wireless update - TL;DR - please test -HEAD From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 06:36:03 -0000 Hi all, Here's another hacking update. The TL;DR version - please update to -HEAD if you're testing 802.11n on ath(4). * I've finished re-engineering the TX aggregation path in preparation for the AR9380 support. Rui reported a rather subtle bug and after a few days of narrowing it down, we nailed it this evening. I've been using an AR9380, AR9390 and AR9485 in 11n (STA) mode and verified that things are behaving quite nicely. * I've disabled the software queue pause/resume stuff for now, at least until I finish implementing a ps-poll implementation. Garrett Cooper donated a HP Touchpad to me (thanks Garrett!) that includes a dual-band atheros 600x wifi module. This does some pretty aggressive ps-poll behaviour for power saving, so it quickly showed the bugs that I had introduced. * I've added a (somewhat temporary) ALQ logging method to if_ath so I can start logging driver events. Until KTR lets me store arbitrary binary data and index it per driver, I plan on using this to debug TX and RX descriptors as well as some general events such as channel change/scan, reset, calibration and such. I'll also likely make the KTR debugging in ath(4) also log to the ath ALQ code. Why? Because I have a need to verify the device behaviour against both the rest of the scheduler framework (hence KTR) as well as against packet TX/RX (hence ALQ.) Right now the ALQ code logs the EDMA descriptors to ALQ (which I've been using to debug the TX aggregation support for AR9380) and I'll add this soon to the legacy descriptors. What I'm going to do next: * I'd like to extend the net80211 alq code I wrote to be per-device and per-vap. Right now it's global (but with a per-wlan marker.) Then I can remove if_ath_alq.[ch] and have the device log to the net80211 ALQ. That way I can combine driver events, descriptor events _and_ net80211 stack events in one ordered queue. That'll make debugging easier - imagine debugging powersave behvaiour or background scan by having this kind of light weight logging. Woo! No more printf debugging! * I'm going to finish off the ps-poll implementation for ath(4), so it first serves out frames from the driver software TX queue, before it goes to the net80211 power save queue. That requires a little more thought and planning. Once the ps-poll support is in the tree, I'll flip that back on and request people test things out. That should conclude the very basic support needed for saying "our 802.11n AP mode is ready!" * I'll teach ath(4) about the LDPC support in AR9380; * I'll teach the ath(4) rate control code to use LDPC and STBC on single-stream rates, but only where appropriate (ie, if the device supports it, if the device is TXing on two streams and whether the remote end has negotiated it.) It's a little more complicated - the HAL may have decided to only select one TX chain rather than the 2 or 3 that the device knows about. I'll have to fix that up, but STBC/LDPC are nice things to have. I'll also verify that the net80211 and ath driver code support 3 stream TX and RX, at least in STA mode Yes, yes I know, the AR9380 HAL code isn't yet public. I'm still working (slowly!) on that. These things take time! Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 15 06:52:52 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 69A5B3C5 for ; Thu, 15 Nov 2012 06:52:52 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 282418FC0C for ; Thu, 15 Nov 2012 06:52:51 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so2378455iea.13 for ; Wed, 14 Nov 2012 22:52:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=hmzBiiW+TS0LugeBC/mJAgeHNL80ytNNOCuAVIjqnho=; b=wzgKcVKxbVcA4CiZQ2Mr+31mUY1WbMqcABKgsvIv+8hCT8k1jApFrFB22+g2/nCHUl V8RalDqiZ5AWPYfn0mh5VA2/nL3yAWWSTfENSl9xcEDkHVjxJID8Tljcuw/lmAa3qYij ArBTuNoTSccvk8de5ibFlDImyYnAN2RU5Djpum0bfCNvoGqAtht9GUa3Fvh+etWkFIrs Dve4E9YITDJjP1Oj292wWIqB44Y3F9Q9bSGSB8T449NHLx2hosEAWiANk065hWkXCwkY SEDZqzKwzlP+RMRi5fKYtNMz9w9UvSDAlJTidqXm4hOVX/AS4TeZ9NHtmnR8nKlqZ50v 592w== Received: by 10.50.40.201 with SMTP id z9mr110958igk.59.1352962370430; Wed, 14 Nov 2012 22:52:50 -0800 (PST) Received: from [192.168.1.14] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id wh5sm3097473igb.17.2012.11.14.22.52.49 (version=SSLv3 cipher=OTHER); Wed, 14 Nov 2012 22:52:49 -0800 (PST) Message-ID: <50A49138.3080700@gmail.com> Date: Thu, 15 Nov 2012 00:52:40 -0600 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Subject: Re: Today's wireless update - TL;DR - please test -HEAD References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 06:52:52 -0000 I recently purchased a wireless card with an AR9380 chipset. I'm wanting to try the driver, but would I need to update my whole kernel to -HEAD or just the directory to -HEAD and keep the rest as -STABLE? I'm using the system as a home server, low use but 24/7 availability as much as possible. How reliable is it currently? From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 15 06:55:34 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7012C41A for ; Thu, 15 Nov 2012 06:55:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2AD208FC0C for ; Thu, 15 Nov 2012 06:55:33 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so1696774oag.13 for ; Wed, 14 Nov 2012 22:55:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=5qbZUEq6XHPciq2q/9ZeJPTrgEuhaqM0NsOZz6B6qVo=; b=CPwcxYX1aydw8DPGUl9kwPL7I2OScIhtJA6Qvtkr7r+hmQXfcXdJC+FulbG33TaDc2 k6+sWNyshyZB2pbrWvQvcHYQ2l8jEj/Gx2knUgOVAvsyyto7XkIJMptXnjXl4unhmafL ZXlJ1+yY8agwmbcsDjZXUf7CoI7k6Qb75lf6Ir8JQhwjEW2QKPM/+Mdrq8Uhe5+MAAD9 yI8geeisg3eE/7eYJaMf/LR//69m//Hc8D1/gdUJMvlmwleqWBNxYAPVeKnR7Lu0fTwK 3l2bOSMlbY/3PH+UIWrj2VLr41yMSVLqydc7woGZ8WBO1MiIpr2aaKi1GHb8QjK0oSN8 Rc1A== MIME-Version: 1.0 Received: by 10.182.1.72 with SMTP id 8mr123747obk.61.1352962533576; Wed, 14 Nov 2012 22:55:33 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.76.27.65 with HTTP; Wed, 14 Nov 2012 22:55:33 -0800 (PST) In-Reply-To: <50A49138.3080700@gmail.com> References: <50A49138.3080700@gmail.com> Date: Wed, 14 Nov 2012 22:55:33 -0800 X-Google-Sender-Auth: VuqMRQ6hU974LES6h-tYh997Ir0 Message-ID: Subject: Re: Today's wireless update - TL;DR - please test -HEAD From: Adrian Chadd To: Joshua Isom Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 06:55:34 -0000 On 14 November 2012 22:52, Joshua Isom wrote: > I recently purchased a wireless card with an AR9380 chipset. I'm wanting to > try the driver, but would I need to update my whole kernel to -HEAD or just > the directory to -HEAD and keep the rest as -STABLE? I test things out on a combination of HEAD and 9.0-RELEASE / 9-STABLE with -HEAD net80211/ath. The latter is .. tricky, but doable. I suggest that testers just run -HEAD unless they know what they're doing. > I'm using the system as a home server, low use but 24/7 availability as much > as possible. How reliable is it currently? Everything pre-AR9380 is stable. The HAL code for the AR9380 isn't open source - I've been committing the non-HAL code to FreeBSD (ie, reimplementing the driver layer bits) and I'm going though the process at ${WORK} to get an open source version of the AR9380 HAL. So there's no real AR9380 support just yet. I've had people ask if I'll release a binary AR9380 HAL KLD for i386/amd64. The short answer (just for the record) is no - I'm not going down that particular road. :-) Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 15 17:24:38 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A5B1A5B; Thu, 15 Nov 2012 17:24:38 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id AE5CC8FC14; Thu, 15 Nov 2012 17:24:37 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so3190519iea.13 for ; Thu, 15 Nov 2012 09:24:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=XHqi7Sx/vcu5dCsdz+9W6WowUjoahzG9aYLorVbcW3Y=; b=RPU6ijIRrl8emyr+TpK/AZe1Xqs0SY5qd0N7NtLnCH7yEYOGp7wI1GS6Z1lhWAjAZd ubqWiJfRg9ErqIFnv6oBx6d7PW0tyZtw/8aAi1bpeUljrMUjR/+BuF+a/Og3pHZuRtz1 l6LLgjZe+bX1hu7mKhylrVyTbKG+54LN01C4jW9eMNbYj3yaBJHSqJg4N5Gktmu3h5M6 teq4ymEdtjP5zhPKuVD/ga2xF4krJnFvwoSnfgo7cGCWaWZ5Yl3PemQsugRxPg0Fkj1c 9mK/AuCmwC5pcwPycIEp3MqvfHVU7hkehfaEZ+ep+uSePzc32sTk6FdEf+0Z5ZP1l+8W s+hA== Received: by 10.50.94.166 with SMTP id dd6mr686015igb.38.1353000277201; Thu, 15 Nov 2012 09:24:37 -0800 (PST) Received: from [192.168.1.14] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id i10sm4052624igb.12.2012.11.15.09.24.32 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 09:24:33 -0800 (PST) Message-ID: <50A52547.6030402@gmail.com> Date: Thu, 15 Nov 2012 11:24:23 -0600 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Today's wireless update - TL;DR - please test -HEAD References: <50A49138.3080700@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 17:24:38 -0000 On 11/15/2012 12:55 AM, Adrian Chadd wrote: > On 14 November 2012 22:52, Joshua Isom wrote: >> I recently purchased a wireless card with an AR9380 chipset. I'm wanting to >> try the driver, but would I need to update my whole kernel to -HEAD or just >> the directory to -HEAD and keep the rest as -STABLE? > > I test things out on a combination of HEAD and 9.0-RELEASE / 9-STABLE > with -HEAD net80211/ath. The latter is .. tricky, but doable. > I suggest that testers just run -HEAD unless they know what they're doing. > >> I'm using the system as a home server, low use but 24/7 availability as much >> as possible. How reliable is it currently? > > Everything pre-AR9380 is stable. The HAL code for the AR9380 isn't > open source - I've been committing the non-HAL code to FreeBSD (ie, > reimplementing the driver layer bits) and I'm going though the process > at ${WORK} to get an open source version of the AR9380 HAL. So there's > no real AR9380 support just yet. > > I've had people ask if I'll release a binary AR9380 HAL KLD for > i386/amd64. The short answer (just for the record) is no - I'm not > going down that particular road. :-) > > > > Adrian > So I'm taking it that currently it will not work without the glue that's not yet available? I'm trying to get ndis working, but it's failing to find the device. I can run pciconf -lv and it shows that it's connected. From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 15 17:41:06 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B47AFFA5 for ; Thu, 15 Nov 2012 17:41:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 830AF8FC14 for ; Thu, 15 Nov 2012 17:41:06 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id kp6so1325900pab.13 for ; Thu, 15 Nov 2012 09:41:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=sCBLmekKemKvcmvtz7JHCdOmaZHUDzx5qhCh34L/WyQ=; b=lIMgGERgyVy1SLhgI/Ijk2KlTWC8OdVBn/tmHdL0xy5V8Pr2eINWXaepW699NmIC71 EApLQHcCz78tZPDN/xc2qKbo3ZTbgeLyuBVduHCOOIkPCD1Zf1D9qT5rJI2ZinVeorUk GmBn1pJ1xgdI5xU4610X4o83MA0yqUPC7puWYCUQiI0dptOryi26M28sfGHw6ObJuW9O PtvpGPJR9DcRkzf5QnPLHg/UQM0Yhm1DCPQilM32HcDj8snNWEDTMwvb06E2B1YUDE+0 O7M6p3DLIEOf3gOOqaCdsz2vAdlDki78zeYHD3OFwo2dSgFz9NkW47haO6NAJE19I+TJ DFLA== MIME-Version: 1.0 Received: by 10.68.251.197 with SMTP id zm5mr6959785pbc.30.1353001266101; Thu, 15 Nov 2012 09:41:06 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Thu, 15 Nov 2012 09:41:06 -0800 (PST) In-Reply-To: <50A52547.6030402@gmail.com> References: <50A49138.3080700@gmail.com> <50A52547.6030402@gmail.com> Date: Thu, 15 Nov 2012 09:41:06 -0800 X-Google-Sender-Auth: r36OMVpViKz5gNnnhSiOxGNlm48 Message-ID: Subject: Re: Today's wireless update - TL;DR - please test -HEAD From: Adrian Chadd To: Joshua Isom Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 17:41:06 -0000 On 15 November 2012 09:24, Joshua Isom wrote: > So I'm taking it that currently it will not work without the glue that's not > yet available? > > I'm trying to get ndis working, but it's failing to find the device. I can > run pciconf -lv and it shows that it's connected. The glue is available. The HAL isn't available. That's the missing piece. As for NDIS, I haven't ever played with that. Sorry. I'm trying to make the drivers support everything so we don't need NDIS. What's the PCI ID of the chip you're using, and which driver are you trying to use with NDIS? Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 16 18:36:09 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40F98AE8 for ; Fri, 16 Nov 2012 18:36:09 +0000 (UTC) (envelope-from gosha-necr@yandex.ru) Received: from forward17.mail.yandex.net (forward17.mail.yandex.net [IPv6:2a02:6b8:0:1402::2]) by mx1.freebsd.org (Postfix) with ESMTP id 99E898FC0C for ; Fri, 16 Nov 2012 18:36:08 +0000 (UTC) Received: from web7g.yandex.ru (web7g.yandex.ru [95.108.252.107]) by forward17.mail.yandex.net (Yandex) with ESMTP id 52AFC10615C8 for ; Fri, 16 Nov 2012 22:36:05 +0400 (MSK) Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web7g.yandex.ru (Yandex) with ESMTP id 1AA904250059; Fri, 16 Nov 2012 22:36:05 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1353090965; bh=RmbMhWHsQopXWy38Z0wIyGlA5ubKtaIlvzc4ZpO1XSQ=; h=From:To:Subject:Date; b=TL5HBoc0Ggo1ixOYNVqVpLQDvSsVSTyBnAO8tW4q/F3HOAPR2YWOC9++Fxth+Mvuj yCjK1BhpwIcGHlKx9SE5bawpJGW4C2s+3aQwceN8Hd0qvzv7gGVtSacUWktuJrWprQ Y8yetopTnZYhdPMbmeIzsdz4BWhNhHKEgUF5zKUc= Received: from mx0.manul-it.ru (mx0.manul-it.ru [92.54.86.120]) by web7g.yandex.ru with HTTP; Fri, 16 Nov 2012 22:36:04 +0400 From: =?koi8-r?B?59XM0cXXIOfP28E=?= To: freebsd-wireless@freebsd.org Subject: Strange output from ndisgen'ed driver in 10-Current Message-Id: <252851353090964@web7g.yandex.ru> Date: Sat, 17 Nov 2012 00:36:04 +0600 X-Mailer: Yamail [ http://yandex.ru ] 5.0 X-Mailman-Approved-At: Fri, 16 Nov 2012 18:54:18 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 18:36:09 -0000 Good day! I'm tryin to get working wireless card RTL8723AE on my laptop with FreeBSD 10-Current amd64 From my early question in that list i know that FreeBSD has not driver for my Wi-Fi card and there is no developer of Realtek drivers in FreeBSD. So I'm trying hard to use that device with ndisgen produced drivers. I'm tryin drivers from XP32, XP64, Vista32, Vista64, W7_32 and W7_64 and it has no effect. Drivers succesfully compiled with ndisgen, but when I'm kldload driver I have such strange output in /var/log/messages: Nov 17 00:32:12 MYBSD root: Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4 But my Wi-Fi card not on USB bus, it is on PCI-E bus as I understand from pciconv -lv: none2@pci0:4:0:0: class=0x028000 card=0x072610ec chip=0x872310ec rev=0x00 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' class = network none3@pci0:5:0:0: class=0xff0000 card=0x27021558 chip=0x528910ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' Maybe somebody can help with me with that? -------------------------------------------- С уважением, Гуляев Гоша. From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 16 18:55:10 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3D393F84 for ; Fri, 16 Nov 2012 18:55:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0BC578FC0C for ; Fri, 16 Nov 2012 18:55:10 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id wz12so2274172pbc.13 for ; Fri, 16 Nov 2012 10:55:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; 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=Pzv4ppNDGi0PfiTG7p0a3cxrS5HszH3Nea9Efsc31GY=; b=Yg2Sh/FIQgAGNowWzfgHbW5ABNrCg/huG82ijoLjeufKEukm9Kp6HzcRCL6yufGQzC Rk7Cb2w+VvEzy5FY3zSC9Bjl9wGzi3gRCIWhpCACsnGWeA8Z90yD/fGaTYE37wfIYp4b oV4bH8DBi2m7evkF47gVNDOdiJLo4+a4Hi4ZkkjUdu8HKCttXEk+DhQwFxOZZmQWR6d9 pbObzbdJAVGaZgbQwuvRsI9Y1IPjve0D0S3aEs7Unzfclv7uU8XzyzZspwQiU0K5NsMG CUPHI3lnAgUWjUS0AGV+tj0C2tfLGVzraaDuGhCAyADGm7GPUv+6EvlmkVWo6fy/KHup Y78g== MIME-Version: 1.0 Received: by 10.68.247.134 with SMTP id ye6mr11910924pbc.69.1353092109832; Fri, 16 Nov 2012 10:55:09 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Fri, 16 Nov 2012 10:55:09 -0800 (PST) In-Reply-To: <252851353090964@web7g.yandex.ru> References: <252851353090964@web7g.yandex.ru> Date: Fri, 16 Nov 2012 10:55:09 -0800 X-Google-Sender-Auth: 4I3RkTc6lEltswRj4sVsIn4wT2s Message-ID: Subject: Re: Strange output from ndisgen'ed driver in 10-Current From: Adrian Chadd To: =?KOI8-R?B?59XM0cXXIOfP28E=?= Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 18:55:10 -0000 Does it have a USB bluetooth adaptor on board? I know the atheros wifi+bt combo cards use a USB bluetooth chip. Adrian On 16 November 2012 10:36, =E7=D5=CC=D1=C5=D7 =E7=CF=DB=C1 wrote: > Good day! > > I'm tryin to get working wireless card RTL8723AE on my laptop with > FreeBSD 10-Current amd64 > > From my early question in that list i know that FreeBSD has not driver > for my Wi-Fi card and there is no developer of Realtek drivers in > FreeBSD. > > So I'm trying hard to use that device with ndisgen produced drivers. > > I'm tryin drivers from XP32, XP64, Vista32, Vista64, W7_32 and W7_64 > and it has no effect. Drivers succesfully compiled with ndisgen, but > when I'm kldload driver I have such strange output in > /var/log/messages: > > Nov 17 00:32:12 MYBSD root: Unknown USB device: vendor 0x5986 product > 0x0315 bus uhub4 > > But my Wi-Fi card not on USB bus, it is on PCI-E bus as I understand > from pciconv -lv: > > none2@pci0:4:0:0: class=3D0x028000 card=3D0x072610ec chip=3D0x872310ec > rev=3D0x00 hdr=3D0x00 > vendor =3D 'Realtek Semiconductor Co., Ltd.' > class =3D network > none3@pci0:5:0:0: class=3D0xff0000 card=3D0x27021558 chip=3D0x528910ec > rev=3D0x01 hdr=3D0x00 > vendor =3D 'Realtek Semiconductor Co., Ltd.' > > Maybe somebody can help with me with that? > > -------------------------------------------- > =F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD, =E7=D5=CC=D1=C5=D7 =E7=CF=DB=C1. > _______________________________________________ > 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 Nov 16 19:59:41 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3D327596 for ; Fri, 16 Nov 2012 19:59:41 +0000 (UTC) (envelope-from michael@fuckner.net) Received: from mo6-p00-ob.rzone.de (mo6-p00-ob.rzone.de [IPv6:2a01:238:20a:202:5300::1]) by mx1.freebsd.org (Postfix) with ESMTP id 941E88FC12 for ; Fri, 16 Nov 2012 19:59:39 +0000 (UTC) X-RZG-AUTH: :IWUHfUGtd9+6EujMWHx57N4dWae4bmTEGbkn8hussqFDiy/d9YYVPbuPr20j0g== Message-ID: X-RZG-CLASS-ID: mo00 Received: from [10.1.2.5] (e176142124.adsl.alicedsl.de [85.176.142.124]) by smtp.strato.de (jorabe mo2) (RZmta 31.4 DYNA|AUTH) with (RC4-MD5 encrypted) ESMTPA id Z07922oAGJ6Jv0 ; Fri, 16 Nov 2012 20:59:36 +0100 (CET) To: "=?utf-8?B?0JPRg9C70Y/QtdCyINCT0L7RiNCw?=" , freebsd-wireless@freebsd.org From: "=?utf-8?B?bWljaGFlbEBmdWNrbmVyLm5ldA==?=" Subject: =?utf-8?B?QW50dy46IFN0cmFuZ2Ugb3V0cHV0IGZyb20gbmRpc2dlbidlZCBkcml2ZXIgaW4g?= =?utf-8?B?MTAtQ3VycmVudA==?= Date: Fri, 16 Nov 2012 20:59:45 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 19:59:41 -0000 SGkgYWxsLCAKVGhpcyBzZWVtcyB0byBiZSB5b3VyIEFjZXIgVVNCIFdlYmNhbS4KClJlZ2FyZHMs IE1pY2hhZWwhIAoKR2VzZW5kZXQgbWl0IG1laW5lbSBIVEMKCi0tLS0tIFJlcGx5IG1lc3NhZ2Ug LS0tLS0KVm9uOiAi0JPRg9C70Y/QtdCyINCT0L7RiNCwIiA8Z29zaGEtbmVjckB5YW5kZXgucnU+ CkFuOiA8ZnJlZWJzZC13aXJlbGVzc0BmcmVlYnNkLm9yZz4KQmV0cmVmZjogU3RyYW5nZSBvdXRw dXQgZnJvbSBuZGlzZ2VuJmFwb3M7ZWQgZHJpdmVyIGluIDEwLUN1cnJlbnQKRGF0dW06IEZyLiwg Tm92LiAxNiwgMjAxMiA3OjM2IFBNCk5vdiAxNyAwMDozMjoxMiBNWUJTRCByb290OiBVbmtub3du IFVTQiBkZXZpY2U6IHZlbmRvciAweDU5ODYgcHJvZHVjdAoweDAzMTUgYnVzIHVodWI0 From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 16 19:27:14 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 904F65EA for ; Fri, 16 Nov 2012 19:27:14 +0000 (UTC) (envelope-from gosha-necr@yandex.ru) Received: from forward4h.mail.yandex.net (forward4h.mail.yandex.net [IPv6:2a02:6b8:0:f05::4]) by mx1.freebsd.org (Postfix) with ESMTP id DDD458FC08 for ; Fri, 16 Nov 2012 19:27:13 +0000 (UTC) Received: from web17h.yandex.ru (web17h.yandex.ru [84.201.186.46]) by forward4h.mail.yandex.net (Yandex) with ESMTP id 744531B227D7 for ; Fri, 16 Nov 2012 23:26:05 +0400 (MSK) Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web17h.yandex.ru (Yandex) with ESMTP id 2A38B6EC81A8; Fri, 16 Nov 2012 23:26:05 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1353093965; bh=buXyfdXzubjoRefmamdM7ETIGvk1MfRE6HoW0stksNU=; h=From:To:In-Reply-To:References:Subject:Date; b=AfvpyHu4IdkErT8V+YroocHBTqpDshJPx0mRXwqVPtsi+iF0Yi3YIc4Bb1sdL3K2B KHXIRhFGB8jJbwp/WQU7iis7V9nrxgbUWBgCitX5XI7bVydEqPBMFViQi24PNrsg8A UcV2U0rvnGtQdxbFKAb2EXj78hNOSLQxVrx/VrO4= Received: from mx0.manul-it.ru (mx0.manul-it.ru [92.54.86.120]) by web17h.yandex.ru with HTTP; Fri, 16 Nov 2012 23:26:04 +0400 From: =?koi8-r?B?59XM0cXXIOfP28E=?= To: freebsd-wireless@freebsd.org In-Reply-To: References: <252851353090964@web7g.yandex.ru> Subject: Re: Strange output from ndisgen'ed driver in 10-Current Message-Id: <36331353093964@web17h.yandex.ru> Date: Sat, 17 Nov 2012 01:26:04 +0600 X-Mailer: Yamail [ http://yandex.ru ] 5.0 X-Mailman-Approved-At: Fri, 16 Nov 2012 20:18:21 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 19:27:14 -0000 Good day Adrian! Yes as I read from internet, that Realtek chip has WiFi+Bluetooth, But from my output I think WiFi and Bluetooth are on PCI-E bus: Wi-FI: none2@pci0:4:0:0: class=0x028000 card=0x072610ec chip=0x872310ec rev=0x00 hdr=0x00 Bluetooth:none3@pci0:5:0:0: class=0xff0000 card=0x27021558 chip=0x528910ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' Device on USB bus from output is Bison Camera, its VENDORID:PRODUCTID fom lsusb -v: Bus /dev/usb Device /dev/ugen2.3: ID 5986:0315 Acer, Inc Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize0 64 idVendor 0x5986 Acer, Inc idProduct 0x0315 bcdDevice 6.08 iManufacturer 2 BISON Corporation iProduct 3 BisonCam, NB Pro iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 507 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 17.11.2012, 00:55, "Adrian Chadd" : Does it have a USB bluetooth adaptor on board? I know the atheros wifi+bt combo cards use a USB bluetooth chip. Adrian On 16 November 2012 10:36, Гуляев Гоша <[1]gosha-necr@yandex.ru> wrote: Good day! I'm tryin to get working wireless card RTL8723AE on my laptop with FreeBSD 10-Current amd64 From my early question in that list i know that FreeBSD has not driver for my Wi-Fi card and there is no developer of Realtek drivers in FreeBSD. So I'm trying hard to use that device with ndisgen produced drivers. I'm tryin drivers from XP32, XP64, Vista32, Vista64, W7_32 and W7_64 and it has no effect. Drivers succesfully compiled with ndisgen, but when I'm kldload driver I have such strange output in /var/log/messages: Nov 17 00:32:12 MYBSD root: Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4 But my Wi-Fi card not on USB bus, it is on PCI-E bus as I understand from pciconv -lv: none2@pci0:4:0:0: class=0x028000 card=0x072610ec chip=0x872310ec rev=0x00 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' class = network none3@pci0:5:0:0: class=0xff0000 card=0x27021558 chip=0x528910ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' Maybe somebody can help with me with that? -------------------------------------------- С уважением, Гуляев Гоша. _______________________________________________ [2]freebsd-wireless@freebsd.org mailing list [3]http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "[4]freebsd-wireless-unsubscribe@freebsd.org" -------------------------------------------- С уважением, Гуляев Гоша. References 1. mailto:gosha-necr@yandex.ru 2. mailto:freebsd-wireless@freebsd.org 3. http://lists.freebsd.org/mailman/listinfo/freebsd-wireless 4. mailto:freebsd-wireless-unsubscribe@freebsd.org From owner-freebsd-wireless@FreeBSD.ORG Fri Nov 16 20:05:13 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 74979781 for ; Fri, 16 Nov 2012 20:05:13 +0000 (UTC) (envelope-from gosha-necr@yandex.ru) Received: from forward15.mail.yandex.net (forward15.mail.yandex.net [IPv6:2a02:6b8:0:801::5]) by mx1.freebsd.org (Postfix) with ESMTP id E0D308FC12 for ; Fri, 16 Nov 2012 20:05:12 +0000 (UTC) Received: from web2f.yandex.ru (web2f.yandex.ru [95.108.130.99]) by forward15.mail.yandex.net (Yandex) with ESMTP id 7C1249E13A6; Sat, 17 Nov 2012 00:05:05 +0400 (MSK) Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web2f.yandex.ru (Yandex) with ESMTP id 319883006C; Sat, 17 Nov 2012 00:05:04 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1353096305; bh=HBZ17G9P4iLaHPhqxICxkjbjQYYZJ6zfDcjK/f3QBYo=; h=From:To:In-Reply-To:References:Subject:Date; b=qMkqSM4K/XjZY3K0E/eAoZ+iRp7nxyd7AhuaDVb4DR6yBz1JpFk7jCqiCzM/yTk4h YrpXnij45tbM87ZgsFBQkotsem14m9kXCZn877xbe/HaT9e2gMpnhWRbKAfqTkEY9t fVgyBjWGi1QbynJhi7NR6GLDxZBfF7xMbPuaqJUM= Received: from mx0.manul-it.ru (mx0.manul-it.ru [92.54.86.120]) by web2f.yandex.ru with HTTP; Sat, 17 Nov 2012 00:05:04 +0400 From: =?koi8-r?B?59XM0cXXIOfP28E=?= To: "michael@fuckner.net" , "freebsd-wireless@freebsd.org" In-Reply-To: References: Subject: Re: Antw.: Strange output from ndisgen'ed driver in 10-Current Message-Id: <2386771353096304@web2f.yandex.ru> Date: Sat, 17 Nov 2012 02:05:04 +0600 X-Mailer: Yamail [ http://yandex.ru ] 5.0 X-Mailman-Approved-At: Fri, 16 Nov 2012 20:47:18 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 20:05:13 -0000 Yes, I know and write this to maillist, but spamassassin not trust to me and my messages waits before moderator approve it :) And I answer, why when I'm kldload kernel module produced from windows driverfor my WiFi card, not any ndis0 interface appears and in /var/log/messages appears that info about Bison Cam. 17.11.2012, 01:59, "michael@fuckner.net" : Hi all, This seems to be your Acer USB Webcam. Regards, Michael! Gesendet mit meinem HTC ----- Reply message ----- Von: "Гуляев Гоша" <[1]gosha-necr@yandex.ru> An: <[2]freebsd-wireless@freebsd.org> Betreff: Strange output from ndisgen'ed driver in 10-Current Datum: Fr., Nov. 16, 2012 7:36 PM Nov 17 00:32:12 MYBSD root: Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4 -------------------------------------------- С уважением, Гуляев Гоша. References 1. mailto:gosha-necr@yandex.ru 2. mailto:freebsd-wireless@freebsd.org From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 17 03:41:01 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01EE8C4E for ; Sat, 17 Nov 2012 03:41:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C41458FC16 for ; Sat, 17 Nov 2012 03:41:00 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id wz12so2495626pbc.13 for ; Fri, 16 Nov 2012 19:40:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=tKbjVUjc6H6js9lMWz6u06N8TbveS+esEHJvB2zU3Yc=; b=QC6VQ69Wkz8cQhcLH82hj+IajnEJuHdWYBYphUQ2WGagrvBRVZOmLJcd0YR6akn8qh qKxVVxjOcF5Rsz0Z9OPibvlQZ95TPuPAFNWHW8WRusDHRFQ02ez4aMNk8doHzIbV8nGO jxyQH/R2SV+cv/nB3AcDN3e+gjVa6DimT2lvmWg+SH3J+9mqXwyWn1RvCKYF9hrnwle1 C+pXeSAPHiaV6vGHqd5djp9UkSam46C4VYLzn3A4KHFDbSDuARy4u9KeKVAyhnPuWz7w SBWeHjJ7mvEHsNyQD9o6L5mZbzAC2Fybbxttp0DBfV9ddJS3XUQt9Wn+h6PLRwUCv0R3 FrIA== MIME-Version: 1.0 Received: by 10.66.89.9 with SMTP id bk9mr18253668pab.67.1353123654501; Fri, 16 Nov 2012 19:40:54 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Fri, 16 Nov 2012 19:40:54 -0800 (PST) In-Reply-To: <201211170239.qAH2dc42007560@svn.freebsd.org> References: <201211170239.qAH2dc42007560@svn.freebsd.org> Date: Fri, 16 Nov 2012 19:40:54 -0800 X-Google-Sender-Auth: 1j9M-QQnCtRjt5HbEdJzS8Ey0aA Message-ID: Subject: Fwd: svn commit: r243174 - head/sys/dev/ath/ath_hal/ar5210 From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 03:41:01 -0000 For like, the two of you out there who still have an AR5210 of some sort, please try this out. This seems to work correctly and correctly populate the RTS duration field. Adrian ---------- Forwarded message ---------- From: Adrian Chadd Date: 16 November 2012 18:39 Subject: svn commit: r243174 - head/sys/dev/ath/ath_hal/ar5210 To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Author: adrian Date: Sat Nov 17 02:39:37 2012 New Revision: 243174 URL: http://svnweb.freebsd.org/changeset/base/243174 Log: Correctly populate the RTS field. Tested: * AR5210, STA mode, RTS enabled Modified: head/sys/dev/ath/ath_hal/ar5210/ar5210_xmit.c Modified: head/sys/dev/ath/ath_hal/ar5210/ar5210_xmit.c ============================================================================== --- head/sys/dev/ath/ath_hal/ar5210/ar5210_xmit.c Sat Nov 17 02:39:09 2012 (r243173) +++ head/sys/dev/ath/ath_hal/ar5210/ar5210_xmit.c Sat Nov 17 02:39:37 2012 (r243174) @@ -518,7 +518,8 @@ ar5210SetupTxDesc(struct ath_hal *ah, st ads->ds_ctl1 = 0; if (flags & HAL_TXDESC_RTSENA) { ads->ds_ctl0 |= AR_RTSCTSEnable; - ads->ds_ctl1 |= rtsctsDuration & AR_RTSDuration; + ads->ds_ctl1 |= (rtsctsDuration << AR_RTSDuration_S) + & AR_RTSDuration; } return AH_TRUE; } From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 17 17:40:20 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75EF9D82 for ; Sat, 17 Nov 2012 17:40:20 +0000 (UTC) (envelope-from gosha-necr@yandex.ru) Received: from forward7.mail.yandex.net (forward7.mail.yandex.net [IPv6:2a02:6b8:0:202::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7A9FA8FC0C for ; Sat, 17 Nov 2012 17:40:19 +0000 (UTC) Received: from web15e.yandex.ru (web15e.yandex.ru [77.88.60.18]) by forward7.mail.yandex.net (Yandex) with ESMTP id A54121C11EC for ; Sat, 17 Nov 2012 21:40:17 +0400 (MSK) Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web15e.yandex.ru (Yandex) with ESMTP id 6F08219C8070; Sat, 17 Nov 2012 21:40:17 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1353174017; bh=zTstZajnp35/ZPrXSzqlpvDNIqq8mLbDgH4nbOHBYCY=; h=From:To:In-Reply-To:References:Subject:Date; b=AQ4+P/7djMBsr9a45QtDMe9MBPWmj4FT5VvEDYxFIyUAO2SEd2aEVblZ7hBtDY63t coVN+g8fXRlDl1uhAoucFbGPOTajQBstHz9GTRq7BYvU28Ibs1OLbzzdLj6KMnFJ3H /IYiTAvgBYLf277aK8opOgg8oqrmTlYmpb1MfxdA= Received: from mx0.manul-it.ru (mx0.manul-it.ru [92.54.86.120]) by web15e.yandex.ru with HTTP; Sat, 17 Nov 2012 21:40:17 +0400 From: =?koi8-r?B?59XM0cXXIOfP28E=?= To: freebsd-wireless@freebsd.org In-Reply-To: References: <252851353090964@web7g.yandex.ru> Subject: Re: Strange output from ndisgen'ed driver in 10-Current Message-Id: <521431353174017@web15e.yandex.ru> Date: Sat, 17 Nov 2012 23:40:17 +0600 X-Mailer: Yamail [ http://yandex.ru ] 5.0 X-Mailman-Approved-At: Sat, 17 Nov 2012 19:04:39 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 17:40:20 -0000 Friends! Is that really so, that nobody have an idea related my issue? 17.11.2012, 00:55, "Adrian Chadd" : Does it have a USB bluetooth adaptor on board? I know the atheros wifi+bt combo cards use a USB bluetooth chip. Adrian On 16 November 2012 10:36, Гуляев Гоша <[1]gosha-necr@yandex.ru> wrote: Good day! I'm tryin to get working wireless card RTL8723AE on my laptop with FreeBSD 10-Current amd64 From my early question in that list i know that FreeBSD has not driver for my Wi-Fi card and there is no developer of Realtek drivers in FreeBSD. So I'm trying hard to use that device with ndisgen produced drivers. I'm tryin drivers from XP32, XP64, Vista32, Vista64, W7_32 and W7_64 and it has no effect. Drivers succesfully compiled with ndisgen, but when I'm kldload driver I have such strange output in /var/log/messages: Nov 17 00:32:12 MYBSD root: Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4 But my Wi-Fi card not on USB bus, it is on PCI-E bus as I understand from pciconv -lv: none2@pci0:4:0:0: class=0x028000 card=0x072610ec chip=0x872310ec rev=0x00 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' class = network none3@pci0:5:0:0: class=0xff0000 card=0x27021558 chip=0x528910ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' Maybe somebody can help with me with that? -------------------------------------------- С уважением, Гуляев Гоша. _______________________________________________ [2]freebsd-wireless@freebsd.org mailing list [3]http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "[4]freebsd-wireless-unsubscribe@freebsd.org" -------------------------------------------- С уважением, Гуляев Гоша. References 1. mailto:gosha-necr@yandex.ru 2. mailto:freebsd-wireless@freebsd.org 3. http://lists.freebsd.org/mailman/listinfo/freebsd-wireless 4. mailto:freebsd-wireless-unsubscribe@freebsd.org From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 17 19:00:01 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DE7DC9A5 for ; Sat, 17 Nov 2012 19:00:01 +0000 (UTC) (envelope-from gosha-necr@yandex.ru) Received: from forward19.mail.yandex.net (forward19.mail.yandex.net [IPv6:2a02:6b8:0:1402::4]) by mx1.freebsd.org (Postfix) with ESMTP id 058438FC17 for ; Sat, 17 Nov 2012 19:00:00 +0000 (UTC) Received: from web21g.yandex.ru (web21g.yandex.ru [95.108.253.230]) by forward19.mail.yandex.net (Yandex) with ESMTP id 444CD1120935 for ; Sat, 17 Nov 2012 22:59:59 +0400 (MSK) Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web21g.yandex.ru (Yandex) with ESMTP id 0C9B47E0059; Sat, 17 Nov 2012 22:59:58 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1353178799; bh=ayO2RR3TG+dXwdb6MdOpwo1WfkAKDrolRD3z1JMIyTI=; h=From:To:In-Reply-To:References:Subject:Date; b=RfPQQRNof1uq4WpQtJThkTWr/bg0Yl7BC2gf2AAUS97V8goOfrXiPhvxXJXAcoIdD T+m9xq/VlfaLZUv70zJrc5ZRq7cAjO8mGQg1J/7ZlGqpdV/u+Eklna6m0AlTbBNa/t lQGGBId0z6/uG+W9HrcM1fwm6F0iS+jkZvOfJ6rM= Received: from mx0.manul-it.ru (mx0.manul-it.ru [92.54.86.120]) by web21g.yandex.ru with HTTP; Sat, 17 Nov 2012 22:59:58 +0400 From: =?koi8-r?B?59XM0cXXIOfP28E=?= To: freebsd-wireless@freebsd.org In-Reply-To: References: <252851353090964@web7g.yandex.ru> Subject: Re: Strange output from ndisgen'ed driver in 10-Current Message-Id: <602521353178798@web21g.yandex.ru> Date: Sun, 18 Nov 2012 00:59:58 +0600 X-Mailer: Yamail [ http://yandex.ru ] 5.0 X-Mailman-Approved-At: Sat, 17 Nov 2012 19:04:49 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 19:00:01 -0000 New info: When I'm do driver from WinXP64 and kldload it I have such output in /var/log/messages and immediately reboots system: Nov 18 00:51:11 MYBSD kernel: no match for RtlGUIDFromString Nov 18 00:51:11 MYBSD kernel: no match for ExNotifyCallback Nov 18 00:51:11 MYBSD kernel: no match for ExCreateCallback Nov 18 00:51:11 MYBSD kernel: no match for IoWMIQueryAllData Nov 18 00:51:11 MYBSD kernel: no match for IoWMIOpenBlock Nov 18 00:51:11 MYBSD kernel: ndis0: port 0xd000-0xd0ff mem 0xf7900000-0xf7903fff irq 18 at device 0.0 on pci4 Nov 18 00:51:11 MYBSD kernel: ndis0: NDIS API version: 5.1 Nov 18 00:51:11 MYBSD kernel: ntoskrnl dummy called... Maybe that helps... With drivers for others versions of windows (32bit and 64bit) i have such line in /var/log/messages: Nov 18 00:49:24 MYBSD root: Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4 (that info is for webcam on my laptop) On 16 November 2012 10:36, Гуляев Гоша <[1]gosha-necr@yandex.ru> wrote: Good day! I'm tryin to get working wireless card RTL8723AE on my laptop with FreeBSD 10-Current amd64 From my early question in that list i know that FreeBSD has not driver for my Wi-Fi card and there is no developer of Realtek drivers in FreeBSD. So I'm trying hard to use that device with ndisgen produced drivers. I'm tryin drivers from XP32, XP64, Vista32, Vista64, W7_32 and W7_64 and it has no effect. Drivers succesfully compiled with ndisgen, but when I'm kldload driver I have such strange output in /var/log/messages: Nov 17 00:32:12 MYBSD root: Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4 But my Wi-Fi card not on USB bus, it is on PCI-E bus as I understand from pciconv -lv: none2@pci0:4:0:0: class=0x028000 card=0x072610ec chip=0x872310ec rev=0x00 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' class = network none3@pci0:5:0:0: class=0xff0000 card=0x27021558 chip=0x528910ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' Maybe somebody can help with me with that? -------------------------------------------- С уважением, Гуляев Гоша. _______________________________________________ [2]freebsd-wireless@freebsd.org mailing list [3]http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "[4]freebsd-wireless-unsubscribe@freebsd.org" -------------------------------------------- С уважением, Гуляев Гоша. References 1. mailto:gosha-necr@yandex.ru 2. mailto:freebsd-wireless@freebsd.org 3. http://lists.freebsd.org/mailman/listinfo/freebsd-wireless 4. mailto:freebsd-wireless-unsubscribe@freebsd.org From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 17 20:47:29 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 347157AD for ; Sat, 17 Nov 2012 20:47:29 +0000 (UTC) (envelope-from onyx@z-up.ru) Received: from mx.z-up.ru (mx.z-up.ru [92.50.244.44]) by mx1.freebsd.org (Postfix) with ESMTP id DB2258FC08 for ; Sat, 17 Nov 2012 20:47:28 +0000 (UTC) Received: from onyx-5552g (unknown [92.50.244.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.z-up.ru (Postfix) with ESMTPSA id 0E03C11470 for ; Sun, 18 Nov 2012 00:37:51 +0400 (GMT-4) Date: Sun, 18 Nov 2012 00:37:53 +0400 From: Dmitry Kolosov To: freebsd-wireless@freebsd.org Subject: Re: Replacing wireless nic on my router Message-Id: <20121118003753.88d1f64cc97a4bdf246dd5cf@z-up.ru> In-Reply-To: <201211042144.08807.onyx@z-up.ru> References: <201211042144.08807.onyx@z-up.ru> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 20:47:29 -0000 Did not found any reasons. Moved to debian linux. From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 17 21:06:03 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6596812C for ; Sat, 17 Nov 2012 21:06:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 341C08FC08 for ; Sat, 17 Nov 2012 21:06:02 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id kp6so2725190pab.13 for ; Sat, 17 Nov 2012 13:06:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=M0mUkrMLI/jegaSJattr/Rf3YOtV0zMyy0Krbh3Jl78=; b=oKYVYepQlyDRavsKG+1w2TFppUv2bOqs96NPdp5yrPMvaIC3GrYX5F3CaV7ohfeLBi arr+/+rDrEvPvsp+LCcBW9HFU60lC1CPC2NcrrV86slfKENKs+vE40YqO6K/AkSr07SK 7VknaxIfXNkHx+yksfSBgm+tofLgLRzjxk2OWEiw7cpMj8kzwaRh/0Q0uw8es+ZkJ0zh olQXSOQ0Mk0G9TTJXHlEB4fnbE0lFycOznimcm6zh8vp6FfXX+clY1y8phxSWPuvqMZ2 PHH9esbKKgA5JbFySUNu2iQdoSyXzRcx6cMvvvY1co1YYPMCOl/j0eUsvxWe0Uc6SSxM BfTQ== MIME-Version: 1.0 Received: by 10.66.77.74 with SMTP id q10mr23884534paw.81.1353186362786; Sat, 17 Nov 2012 13:06:02 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Sat, 17 Nov 2012 13:06:02 -0800 (PST) In-Reply-To: <20121118003753.88d1f64cc97a4bdf246dd5cf@z-up.ru> References: <201211042144.08807.onyx@z-up.ru> <20121118003753.88d1f64cc97a4bdf246dd5cf@z-up.ru> Date: Sat, 17 Nov 2012 13:06:02 -0800 X-Google-Sender-Auth: yFYDrilqwt29Lpb3EHElDBx7G7U Message-ID: Subject: Re: Replacing wireless nic on my router From: Adrian Chadd To: Dmitry Kolosov Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 21:06:03 -0000 On 17 November 2012 12:37, Dmitry Kolosov wrote: > Did not found any reasons. Moved to debian linux. That's a shame, I'd like to try and trace this particular issue down. I've added debugging to the ath driver in -HEAD that lets us record the actual TX and RX descriptors from the driver, so we could actually see if the driver was receiving anything at all. That would also help here. In any case, if you're interested in helping out debug it further please let me know. And as I'm always constantly busy, don't be afraid to pester me on a daily basis until we figure it out. I have other 11n testers who do that and we eventually solve all the bugs. :) _OH_. Hey, since it may be broadcast traffic, I know I fixed a bug in the multicast group encryption key handling. It made it into -9 and -HEAD. I don't think it was backported to -8. The bug was introduced when someone tweaked something for an older NIC but it broke multicast group key handling for the AR5416 and later NICs. Maybe try -9? A live CD will be enough. adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Nov 17 23:57:35 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 29FA4812 for ; Sat, 17 Nov 2012 23:57:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id F0C968FC12 for ; Sat, 17 Nov 2012 23:57:34 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id kp6so2763559pab.13 for ; Sat, 17 Nov 2012 15:57:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=Tmz4Vck7BQ/ibjMisW3SL7YrWpIzio1vWiZD31R8dsU=; b=eFFyH+ny0byt8FROEqd7CVlAQnKCI50ooz1iCn9hcjhklF4Gqydf6i+8XlqyhdQ9Hi i6Mze3HUpf5PPXT7QlhlwlhKomLal4z8M06u4xpYxahUyU/UZMOWy8YK3TYoYNLYUa22 bF69XBGuA1Ha5kWS/0rvFJOxRs5rxt+yjUvDNrETmEU5PCmjt2IQlaXvETwp0QKyuZjH F7ORKRZNzccC6hz6yuDZKdZiwrKKWYtbj+wmXA9T6YVv1TWJGbqDVMbTMw/kC642Ac2D PCrsPQ9KMcBQwmoMmBE8ZXok4RpY/BTsSHmalxVPWUPRW+7MSF+4vCRs+z7BqB9T6Us/ FptA== MIME-Version: 1.0 Received: by 10.69.0.8 with SMTP id au8mr28019194pbd.58.1353196654445; Sat, 17 Nov 2012 15:57:34 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Sat, 17 Nov 2012 15:57:34 -0800 (PST) Date: Sat, 17 Nov 2012 15:57:34 -0800 X-Google-Sender-Auth: 6eFkdLAAuzRHMEXPzfvS7kFu7Dw Message-ID: Subject: (Re) Verifying TDMA behaviour on -HEAD From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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 Nov 2012 23:57:35 -0000 So for the record, I have a couple of -HEAD devices up and running with TDMA. AP: ath0: irq 16 at device 0.0 on cardbus0 ath0: AR5413 mac 10.4 RF5413 phy 6.1 ifconfig wlan0 create wlandev ath0 wlanmode tdma ifconfig wlan0 ssid ADRIAN_TDMA channel 48:a ifconfig wlan0 tdmaslotcnt 2 tdmaslot 0 tdmaslotlen 2500 ifconfig wlan0 192.168.4.1/24 up STA: [100147] ath1: mem 0xe4310000-0xe431ffff irq 16 at device 0.0 on cardbus0 ath1: AR5413 mac 10.4 RF5413 phy 6.1 ifconfig wlan0 create wlandev ath0 wlanmode tdma ifconfig wlan0 ssid ADRIAN_TDMA ifconfig wlan0 inet 192.168.4.2/24 up I'm running an iperf test right now and it's getting a stable 8.3MBit/sec across it. Now, after the work done last year to make the 11n NICs work, I haven't sat down and tried that. I likely should do that soon. But at least for that very specific MAC version above, it seems to work just fine. Adrian