From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 29 09:16:14 2012 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 B32B51065679 for ; Sun, 29 Jan 2012 09:16:14 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [91.216.196.25]) by mx1.freebsd.org (Postfix) with ESMTP id F2D178FC08 for ; Sun, 29 Jan 2012 09:16:13 +0000 (UTC) Received: from ibs.dn.ua (localhost [127.0.0.1]) by relay.ibs.dn.ua with ESMTP id q0T95wKE031634 for ; Sun, 29 Jan 2012 11:05:58 +0200 (EET) Message-ID: <20120129110558.31632@relay.ibs.dn.ua> Date: Sun, 29 Jan 2012 11:05:58 +0200 From: Zeus Panchenko To: cc: Organization: IBS LLC X-Mailer: MH-E 8.2; GNU Mailutils 2.99.94; GNU Emacs 23.3.1 X-Face: &sReWXo3Iwtqql1[My(t1Gkx; y?KF@KF`4X+'9Cs@PtK^y%}^.>Mtbpyz6U=,Op:KPOT.uG )Nvx`=er!l?WASh7KeaGhga"1[&yz$_7ir'cVp7o%CGbJ/V)j/=]vzvvcqcZkf; JDurQG6wTg+?/xA go`}1.Ze//K; Fk&/&OoHd'[b7iGt2UO>o(YskCT[_D)kh4!yY'<&:yt+zM=A`@`~9U+P[qS:f; #9z~ Or/Bo#N-'S'!'[3Wog'ADkyMqmGDvga?WW)qd=?)`Y&k=o}>!ST\ Fcc: +sent-messages/201201 Subject: BCM4313 + 9.0R amd64 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Zeus Panchenko 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, 29 Jan 2012 09:16:14 -0000 Hi all, please, may somebody answer: is there way to get working ndis driver for BCM4313 on FreeBSD09.0-RELEASE amd64? here is data: # dmidecode ... System Information Manufacturer: Hewlett-Packard Product Name: HP Pavilion dm1 Notebook PC ... # uname -a FreeBSD 9.0-RELEASE amd64 I was much surprised when found at PCBSD wiki page http://wiki.pcbsd.org/index.php/Wireless_Testing information concerning my notebook WiFi card support the very card is: # pciconf -lvcb none1@pci0:3:0:0: class=0x028000 card=0x1795103c chip=0x472714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4313 802.11b/g/n Wireless LAN Controller' class = network bar [10] = type Memory, range 64, base 0xf0200000, size 16384, enabled cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 09[58] = vendor (length 120) cap 05[48] = MSI supports 1 message, 64 bit cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0002[13c] = VC 1 max VC0 ecap 0003[160] = Serial 1 000019ffff6660d8 ecap 0004[16c] = unknown 1 so, while trying to get NDISulator working on 9.0-RELEASE i receive errors: ... In file included from /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:51: @/compat/ndis/hal_var.h:46:1: warning: "X86_BUS_SPACE_MEM" redefined In file included from ./machine/bus.h:6, from /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:46: ./x86/bus.h:120:1: warning: this is the location of the previous definition /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c: In function 'WRITE_PORT_ULONG': /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:101: error: 'AMD64_BUS_SPACE_IO' undeclared (first use in this function) /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:101: error: (Each undeclared identifier is reported only once /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:101: error: for each function it appears in.) /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c: In function 'WRITE_PORT_USHORT': /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:108: error: 'AMD64_BUS_SPACE_IO' undeclared (first use in this function) /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c: In function 'WRITE_PORT_UCHAR': ... /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:175: error: 'AMD64_BUS_SPACE_IO' undeclared (first use in this function) /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c: In function 'READ_PORT_BUFFER_UCHAR': /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:183: error: 'AMD64_BUS_SPACE_IO' undeclared (first use in this function) *** Error code 1 so, is it because of RELEASE code? after that I risked to convert win drivers with original ndisgen despite warning on PCBSD wiki page and have got wlan0 visible by ifconfig and wpa_supplicant but wpa_supplicant was flapping and got no authorisation ... in log i see this: ... Jan 29 01:40:46 hp wpa_supplicant[293]: Associated with 00:90:4c:91:00:01 Jan 29 01:40:56 hp wpa_supplicant[293]: Authentication with 00:90:4c:91:00:01 timed out. Jan 29 01:40:56 hp wpa_supplicant[293]: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0 Jan 29 01:41:03 hp wpa_supplicant[293]: Trying to associate with 00:90:4c:91:00:01 (SSID='AP' freq=2437 MHz) Jan 29 01:41:04 hp wpa_supplicant[293]: Associated with 00:90:4c:91:00:01 Jan 29 01:41:14 hp wpa_supplicant[293]: Authentication with 00:90:4c:91:00:01 timed out. Jan 29 01:41:14 hp wpa_supplicant[293]: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0 Jan 29 01:41:21 hp wpa_supplicant[293]: Trying to associate with 00:90:4c:91:00:01 (SSID='AP' freq=2437 MHz) Jan 29 01:41:22 hp wpa_supplicant[293]: Associated with 00:90:4c:91:00:01 ... when ifconfig was showing wlan0 associated with AP, dhclient was unable to get IP address ... so, the question: is there *any* way to get BCM4313 working on FreeBSD 9.0-R? 9-STABLE? please, share the experience -- Zeus V. Panchenko IT Dpt., I.B.S. LLC GMT+2 (EET) From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 29 13:20:19 2012 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 7AAEE106566C for ; Sun, 29 Jan 2012 13:20:19 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [91.216.196.25]) by mx1.freebsd.org (Postfix) with ESMTP id BF4498FC14 for ; Sun, 29 Jan 2012 13:20:18 +0000 (UTC) Received: from ibs.dn.ua (localhost [127.0.0.1]) by relay.ibs.dn.ua with ESMTP id q0TDKHbl056924; Sun, 29 Jan 2012 15:20:17 +0200 (EET) Message-ID: <20120129152017.56922@relay.ibs.dn.ua> Date: Sun, 29 Jan 2012 15:20:17 +0200 From: Zeus Panchenko To: "Paul B Mahol" In-reply-to: Your message of Sun, 29 Jan 2012 12:05:26 +0000 References: <20120129110558.31632@relay.ibs.dn.ua> Organization: IBS LLC X-Mailer: MH-E 8.2; GNU Mailutils 2.99.94; GNU Emacs 23.3.1 X-Face: &sReWXo3Iwtqql1[My(t1Gkx; y?KF@KF`4X+'9Cs@PtK^y%}^.>Mtbpyz6U=,Op:KPOT.uG )Nvx`=er!l?WASh7KeaGhga"1[&yz$_7ir'cVp7o%CGbJ/V)j/=]vzvvcqcZkf; JDurQG6wTg+?/xA go`}1.Ze//K; Fk&/&OoHd'[b7iGt2UO>o(YskCT[_D)kh4!yY'<&:yt+zM=A`@`~9U+P[qS:f; #9z~ Or/Bo#N-'S'!'[3Wog'ADkyMqmGDvga?WW)qd=?)`Y&k=o}>!ST\ Fcc: +sent-messages/201201 Cc: freebsd-wireless@freebsd.org Subject: Re: BCM4313 + 9.0R amd64 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Zeus Panchenko 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, 29 Jan 2012 13:20:19 -0000 Paul B Mahol wrote: > > ... > > /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:183: error: > > 'AMD64_BUS_SPACE_IO' undeclared (first use in this function) > > *** Error code 1 > > > > so, is it because of RELEASE code? > > What branch you are using? i was trying stable from https://github.com/richardpl/NDISulator/tree/stable -- Zeus V. Panchenko IT Dpt., I.B.S. LLC GMT+2 (EET) From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 29 13:56:00 2012 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 97CC7106564A for ; Sun, 29 Jan 2012 13:56:00 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 63FBB8FC14 for ; Sun, 29 Jan 2012 13:56:00 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so4801456obc.13 for ; Sun, 29 Jan 2012 05:55:59 -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; bh=D4ndbvM3zX1zwGo0s49HnTjFoaTeo183SeFQP8Qrpu0=; b=HuyYub4jQ8j4CMJHzI3RrHD1ck8qa7dyMmGFLxVsutzebJwa7E7HwuNPsryEO/MWMW uNV61nCgGDpccJroEOS3b688R6g5HjtsRSDXARYSQSHSQ7z47cdMFbnbYcNL4ZbH0D1d /XJwp0TGfazbud/Ok77ndZsSmD7Ypc3QRLEPA= MIME-Version: 1.0 Received: by 10.182.75.65 with SMTP id a1mr20413751obw.32.1327843749084; Sun, 29 Jan 2012 05:29:09 -0800 (PST) Received: by 10.60.21.138 with HTTP; Sun, 29 Jan 2012 05:29:09 -0800 (PST) In-Reply-To: <20120129152017.56922@relay.ibs.dn.ua> References: <20120129110558.31632@relay.ibs.dn.ua> <20120129152017.56922@relay.ibs.dn.ua> Date: Sun, 29 Jan 2012 13:29:09 +0000 Message-ID: From: Paul B Mahol To: Zeus Panchenko Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: BCM4313 + 9.0R amd64 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, 29 Jan 2012 13:56:00 -0000 On 1/29/12, Zeus Panchenko wrote: > Paul B Mahol wrote: > >> > ... >> > /usr/src/sys/modules/ndis/../../compat/ndis/subr_hal.c:183: error: >> > 'AMD64_BUS_SPACE_IO' undeclared (first use in this function) >> > *** Error code 1 >> > >> > so, is it because of RELEASE code? >> >> What branch you are using? > > i was trying stable from > https://github.com/richardpl/NDISulator/tree/stable Try stable9 instead. From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 29 21:36:28 2012 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 C1E2B106564A for ; Sun, 29 Jan 2012 21:36:28 +0000 (UTC) (envelope-from ironfall_blindguardian@hotmail.com) Received: from bay0-omc1-s9.bay0.hotmail.com (bay0-omc1-s9.bay0.hotmail.com [65.54.190.20]) by mx1.freebsd.org (Postfix) with ESMTP id AA7EA8FC15 for ; Sun, 29 Jan 2012 21:36:28 +0000 (UTC) Received: from BAY169-W38 ([65.54.190.61]) by bay0-omc1-s9.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 29 Jan 2012 13:24:27 -0800 Message-ID: X-Originating-IP: [177.33.230.210] From: LuX - I like you To: Date: Sun, 29 Jan 2012 19:24:27 -0200 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 29 Jan 2012 21:24:27.0759 (UTC) FILETIME=[618347F0:01CCDECC] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Realtek 8188ce driver 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, 29 Jan 2012 21:36:28 -0000 Hello=2C I'm Luan and I'm a newer FreeBSD Lover. I am having a problem and I have found no answer anywhere=2C but I hope you= can give me a light. My notebook has an integrated wireless card (Realtek 8188ce) and the Realte= k site provides drivers only for Windows and Linux. I had read the FreeBSD manual=2C asked for help in the forum and in the IRC= ##freebsd=2C but unfortunately nobody could help me. My conclusion is that such driver does not exist in FreeBSD. Is there any projects to port such driver from Linux (I guess OpenBSD has t= hat driver as well=2C so the porting could be less painful) or some compati= ble driver to this device? Thanks in advance. --- Luan Hospodarsky = From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 30 01:00:45 2012 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 0EB53106566C for ; Mon, 30 Jan 2012 01:00:45 +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 B7EB78FC16 for ; Mon, 30 Jan 2012 01:00:44 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so3825436vbb.13 for ; Sun, 29 Jan 2012 17:00:43 -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; bh=KA1/yrzsiglNPF1pQhGX0bneKUvpThHZDHgjlHcTrZk=; b=XZnUN6rU7jpNPy4xf59xYQw3L6oV/HuDKdtfWlro7+6ft9tIIwkdkjibTAM92ngT3h v0yF0eT3Cy0JYhlEewes0TGdt2OmxLO7FHgOu0Zz75NphJKuAsif4vyGf4O9PvmwURjT b4CtBXZW+uku7zHWN+4XQo4Z16ysQgkXGnCSc= MIME-Version: 1.0 Received: by 10.52.66.166 with SMTP id g6mr7512112vdt.34.1327885243786; Sun, 29 Jan 2012 17:00:43 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Sun, 29 Jan 2012 17:00:43 -0800 (PST) In-Reply-To: References: Date: Sun, 29 Jan 2012 17:00:43 -0800 X-Google-Sender-Auth: rOE4VTb_3nlUzsWOqSIgMiGwXmE Message-ID: From: Adrian Chadd To: LuX - I like you Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: Realtek 8188ce driver 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, 30 Jan 2012 01:00:45 -0000 Hi, I think there's been some recent work to get this chipset support into shape but I don't know wehre it lives or whether the driver is in a workable setup. Does anyone know anything further? Adrian On 29 January 2012 13:24, LuX - I like you < ironfall_blindguardian@hotmail.com> wrote: > > Hello, I'm Luan and I'm a newer FreeBSD Lover. > I am having a problem and I have found no answer anywhere, but I hope you > can give me a light. > My notebook has an integrated wireless card (Realtek 8188ce) and the > Realtek site provides drivers only for Windows and Linux. > I had read the FreeBSD manual, asked for help in the forum and in the IRC > ##freebsd, but unfortunately nobody could help me. > My conclusion is that such driver does not exist in FreeBSD. > Is there any projects to port such driver from Linux (I guess OpenBSD has > that driver as well, so the porting could be less painful) or some > compatible driver to this device? > Thanks in advance. > --- > Luan Hospodarsky > > _______________________________________________ > 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 Mon Jan 30 11:07:56 2012 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 263EE1065670 for ; Mon, 30 Jan 2012 11:07:56 +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 133048FC15 for ; Mon, 30 Jan 2012 11:07:56 +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 q0UB7tV2005591 for ; Mon, 30 Jan 2012 11:07:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0UB7tUN005589 for freebsd-wireless@FreeBSD.org; Mon, 30 Jan 2012 11:07:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Jan 2012 11:07:55 GMT Message-Id: <201201301107.q0UB7tUN005589@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, 30 Jan 2012 11:07:56 -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/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 o kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath 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/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 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 67 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 30 21:41:50 2012 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 BB975106566B for ; Mon, 30 Jan 2012 21:41:50 +0000 (UTC) (envelope-from ironfall_blindguardian@hotmail.com) Received: from bay0-omc1-s11.bay0.hotmail.com (bay0-omc1-s11.bay0.hotmail.com [65.54.190.22]) by mx1.freebsd.org (Postfix) with ESMTP id A626F8FC0C for ; Mon, 30 Jan 2012 21:41:50 +0000 (UTC) Received: from BAY169-W5 ([65.54.190.61]) by bay0-omc1-s11.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 13:41:49 -0800 Message-ID: X-Originating-IP: [177.33.230.210] From: Luan Hospodarsky To: Date: Mon, 30 Jan 2012 19:41:50 -0200 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 30 Jan 2012 21:41:49.0971 (UTC) FILETIME=[F921F630:01CCDF97] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: Realtek 8188ce driver 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, 30 Jan 2012 21:41:50 -0000 Hi Adrian=2C Thanks for the reply=2C So is there some work about it? It is great! If you find anything=2C let me know! Thanks again. Date: Sun=2C 29 Jan 2012 17:00:43 -0800 Subject: Re: Realtek 8188ce driver From: adrian@freebsd.org To: ironfall_blindguardian@hotmail.com CC: freebsd-wireless@freebsd.org Hi=2C I think there's been some recent work to get this chipset support into shap= e but I don't know wehre it lives or whether the driver is in a workable se= tup. Does anyone know anything further? Adrian On 29 January 2012 13:24=2C LuX - I like you wrote: Hello=2C I'm Luan and I'm a newer FreeBSD Lover. I am having a problem and I have found no answer anywhere=2C but I hope you= can give me a light. My notebook has an integrated wireless card (Realtek 8188ce) and the Realte= k site provides drivers only for Windows and Linux. I had read the FreeBSD manual=2C asked for help in the forum and in the IRC= ##freebsd=2C but unfortunately nobody could help me. My conclusion is that such driver does not exist in FreeBSD. Is there any projects to port such driver from Linux (I guess OpenBSD has t= hat driver as well=2C so the porting could be less painful) or some compati= ble driver to this device? Thanks in advance. --- Luan Hospodarsky _________________________________= ______________ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe=2C send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" = From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 30 22:22:34 2012 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 0F481106564A for ; Mon, 30 Jan 2012 22:22:34 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 939188FC12 for ; Mon, 30 Jan 2012 22:22:33 +0000 (UTC) Received: by werm13 with SMTP id m13so3271711wer.13 for ; Mon, 30 Jan 2012 14:22:32 -0800 (PST) Received-SPF: pass (google.com: domain of kob6558@gmail.com designates 10.180.106.33 as permitted sender) client-ip=10.180.106.33; Authentication-Results: mr.google.com; spf=pass (google.com: domain of kob6558@gmail.com designates 10.180.106.33 as permitted sender) smtp.mail=kob6558@gmail.com; dkim=pass header.i=kob6558@gmail.com Received: from mr.google.com ([10.180.106.33]) by 10.180.106.33 with SMTP id gr1mr36394851wib.6.1327962152605 (num_hops = 1); Mon, 30 Jan 2012 14:22:32 -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=eiHF2RMQ1xVvJA54OnlpHJzDV0DHusKqToaA2bD1Uwo=; b=C4DUgShypLeHYifCHE0Z2GI4M5Yuf8rpoOapnvz12XTg8ls5amPTgmmT4pJGYKSfR3 cahe6wrDHZSVoJWehVdPnDnn6FIlSVrPvkVXWtOTYoT8zwVXLD4Pl118DKqk+vkY1rP9 eK8JplpPeNWsaEFfMcqEZtlkIK9N26EaIRLFI= MIME-Version: 1.0 Received: by 10.180.106.33 with SMTP id gr1mr30234835wib.6.1327960445679; Mon, 30 Jan 2012 13:54:05 -0800 (PST) Received: by 10.223.101.196 with HTTP; Mon, 30 Jan 2012 13:54:05 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 13:54:05 -0800 Message-ID: From: Kevin Oberman To: Luan Hospodarsky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Realtek 8188ce driver 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, 30 Jan 2012 22:22:34 -0000 On Mon, Jan 30, 2012 at 1:41 PM, Luan Hospodarsky wrote: > > Hi Adrian, > Thanks for the reply, > > So is there some work about it? > It is great! If you find anything, let me know! > Thanks again. > > Date: Sun, 29 Jan 2012 17:00:43 -0800 > Subject: Re: Realtek 8188ce driver > From: adrian@freebsd.org > To: ironfall_blindguardian@hotmail.com > CC: freebsd-wireless@freebsd.org > > Hi, > > I think there's been some recent work to get this chipset support into sh= ape but I don't know wehre it lives or whether the driver is in a workable = setup. > > Does anyone know anything further? > > > > Adrian > > On 29 January 2012 13:24, LuX - I like you wrote: > > > > Hello, I'm Luan and I'm a newer FreeBSD Lover. > > I am having a problem and I have found no answer anywhere, but I hope you= can give me a light. > > My notebook has an integrated wireless card (Realtek 8188ce) and the Real= tek site provides drivers only for Windows and Linux. > > I had read the FreeBSD manual, asked for help in the forum and in the IRC= ##freebsd, but unfortunately nobody could help me. > > My conclusion is that such driver does not exist in FreeBSD. > > Is there any projects to port such driver from Linux (I guess OpenBSD has= that driver as well, so the porting could be less painful) or some compati= ble driver to this device? > > Thanks in advance. > > --- > > Luan Hospodarsky > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0_______________________________________________ 1. You could try ndis. It did not work for me, but a patch to ndis looks like it may have fixed the problem. 2. The other option is to replace the card. What brand of laptop is it? Levovo locks down the wireless and will not boot with any card but one they sold. I believe HP does the same. I had to buy a card with the Lenovo PCI ID to get it to work. I found it from a place that was in Germany, but the card was shipped from Tel Aviv. It cost about 3 times what a generic Intel Centrino Advanced-N 6205 would have cost. :-( You might be able to re-write the PCI ID on a standard Intel card, but I could not figure out how to do it. You can also patch the BIOS, but that make future BIOS upgrades a real problem. 3. Write a driver --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 30 22:30:43 2012 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 2C432106564A for ; Mon, 30 Jan 2012 22:30:43 +0000 (UTC) (envelope-from ironfall_blindguardian@hotmail.com) Received: from bay0-omc1-s12.bay0.hotmail.com (bay0-omc1-s12.bay0.hotmail.com [65.54.190.23]) by mx1.freebsd.org (Postfix) with ESMTP id 1643E8FC16 for ; Mon, 30 Jan 2012 22:30:42 +0000 (UTC) Received: from BAY169-W74 ([65.54.190.61]) by bay0-omc1-s12.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 14:30:42 -0800 Message-ID: X-Originating-IP: [177.33.230.210] From: Luan Hospodarsky To: Date: Mon, 30 Jan 2012 20:30:42 -0200 Importance: Normal In-Reply-To: References: , , , MIME-Version: 1.0 X-OriginalArrivalTime: 30 Jan 2012 22:30:42.0535 (UTC) FILETIME=[CD13B770:01CCDF9E] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: Realtek 8188ce driver 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, 30 Jan 2012 22:30:43 -0000 Hi=2C I already tried ndis and the module it generated did not work. But I don't know anything about a ndis patch=2C can you tell me more about = it? Replace the device is still an alternative=2C but I want to avoid it the ma= x possible. I have never written a driver=2C but I could try. Do you have anything to s= hare that can help me give the first steps writing a driver? Thanks. > Date: Mon=2C 30 Jan 2012 13:54:05 -0800 > Subject: Re: Realtek 8188ce driver > From: kob6558@gmail.com > To: ironfall_blindguardian@hotmail.com > CC: freebsd-wireless@freebsd.org >=20 > On Mon=2C Jan 30=2C 2012 at 1:41 PM=2C Luan Hospodarsky > wrote: > > > > Hi Adrian=2C > > Thanks for the reply=2C > > > > So is there some work about it? > > It is great! If you find anything=2C let me know! > > Thanks again. > > > > Date: Sun=2C 29 Jan 2012 17:00:43 -0800 > > Subject: Re: Realtek 8188ce driver > > From: adrian@freebsd.org > > To: ironfall_blindguardian@hotmail.com > > CC: freebsd-wireless@freebsd.org > > > > Hi=2C > > > > I think there's been some recent work to get this chipset support into = shape but I don't know wehre it lives or whether the driver is in a workabl= e setup. > > > > Does anyone know anything further? > > > > > > > > Adrian > > > > On 29 January 2012 13:24=2C LuX - I like you wrote: > > > > > > > > Hello=2C I'm Luan and I'm a newer FreeBSD Lover. > > > > I am having a problem and I have found no answer anywhere=2C but I hope= you can give me a light. > > > > My notebook has an integrated wireless card (Realtek 8188ce) and the Re= altek site provides drivers only for Windows and Linux. > > > > I had read the FreeBSD manual=2C asked for help in the forum and in the= IRC ##freebsd=2C but unfortunately nobody could help me. > > > > My conclusion is that such driver does not exist in FreeBSD. > > > > Is there any projects to port such driver from Linux (I guess OpenBSD h= as that driver as well=2C so the porting could be less painful) or some com= patible driver to this device? > > > > Thanks in advance. > > > > --- > > > > Luan Hospodarsky > > > > ______________________________= _________________ >=20 > 1. You could try ndis. It did not work for me=2C but a patch to ndis > looks like it may have fixed the problem. >=20 > 2. The other option is to replace the card. What brand of laptop is > it? Levovo locks down the wireless and will not boot with any card but > one they sold. I believe HP does the same. I had to buy a card with > the Lenovo PCI ID to get it to work. I found it from a place that was > in Germany=2C but the card was shipped from Tel Aviv. It cost about 3 > times what a generic Intel Centrino Advanced-N 6205 would have cost. > :-( >=20 > You might be able to re-write the PCI ID on a standard Intel card=2C but > I could not figure out how to do it. You can also patch the BIOS=2C but > that make future BIOS upgrades a real problem. >=20 > 3. Write a driver > --=20 > R. Kevin Oberman=2C Network Engineer > E-mail: kob6558@gmail.com = From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 00:48:13 2012 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 275111065675 for ; Tue, 31 Jan 2012 00:48:13 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc1-s15.snt0.hotmail.com (snt0-omc1-s15.snt0.hotmail.com [65.55.90.26]) by mx1.freebsd.org (Postfix) with ESMTP id EC9F28FC0C for ; Tue, 31 Jan 2012 00:48:12 +0000 (UTC) Received: from SNT128-W59 ([65.55.90.9]) by snt0-omc1-s15.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 16:36:11 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Mon, 30 Jan 2012 19:36:11 -0500 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 31 Jan 2012 00:36:11.0320 (UTC) FILETIME=[54952380:01CCDFB0] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 00:48:13 -0000 Dear FreeBSD-Wireless team=2C I'd like to inform the dev teams that I just upgraded my system from 8.2-st= able to 9.0-stable using CVSUP and my wireless card SR71-A (AR9160) is no l= onger being detected. If I roll back to the old kernel=2C everything is wor= king great. Here is my kernel config for wireless: device wlan =20 device wlan_acl =20 device wlan_wep =20 device wlan_ccmp =20 device wlan_tkip =20 device wlan_amrr =20 device ath =20 device ath_hal =20 options AH_SUPPORT_AR5416 =20 #options ATH_ENABLE_11N <-- I tried enabling this and recompil= ing and it did not do any difference device ath_rate_sample =20 As always I edited the following file before recompiling: vi /usr/src/sys/dev/ath/ath_hal/ar5416/ar5416.h and changed AR5416_DEFAULT_TXCHAINMASK from 1 to 7 after compiling the 9.0 kernel=2C pciconf returns the following undetected = devices: none0@pci0:0:3:0: class=3D0x078000 card=3D0x2a448086 chip=3D0x2a44808= 6 rev=3D0x07 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Mobile 4 Series Chipset MEI Controller' class =3D simple comms none1@pci0:0:31:3: class=3D0x0c0500 card=3D0x29308086 chip=3D0x2930808= 6 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801I (ICH9 Family) SMBus Controller' class =3D serial bus subclass =3D SMBus none2@pci0:1:15:0: class=3D0x028000 card=3D0x40820777 chip=3D0x0027168= c rev=3D0x01 hdr=3D0x00 vendor =3D 'Atheros Communications Inc.' device =3D 'AR9160 802.11abgn Wireless PCI Adapter' class =3D network Any help is greatly appreciated! I upgraded to 9.0 hoping test 802.11n! Thanks! = From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 00:51:09 2012 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 D520D1065674 for ; Tue, 31 Jan 2012 00:51:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 877A68FC0C for ; Tue, 31 Jan 2012 00:51:09 +0000 (UTC) Received: by vcmm1 with SMTP id m1so5076426vcm.13 for ; Mon, 30 Jan 2012 16:51:08 -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; bh=uVLim1Q1NSNzbGwMT90kPhW7zl+o1Q+rqke2xZizWF4=; b=KrrDq27GWPf2R44KAy5uAdDwm6o037WZP/7GAfPS0F2eZeRAZEpLpb7aXrAysrEvI2 HXKfyoxSzAlxi2hq/9JBlH8mjpTzYb7veClhQ4kkLjj72vTkODjP0JLBRKDvhgStvKqJ yBYBUQPvt0uvat7O97QNbIuxzgdhBbv6hpNTM= MIME-Version: 1.0 Received: by 10.52.26.199 with SMTP id n7mr10286666vdg.17.1327971068663; Mon, 30 Jan 2012 16:51:08 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Mon, 30 Jan 2012 16:51:08 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 16:51:08 -0800 X-Google-Sender-Auth: X7S0m0yv4jlHhjmmZoRgkH_Mzq8 Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 00:51:10 -0000 Hi, On 30 January 2012 16:36, Shant Kassardjian wrote: > > > Dear FreeBSD-Wireless team, > > > I'd like to inform the dev teams that I just upgraded my system from > 8.2-stable to 9.0-stable using CVSUP and my wireless card SR71-A (AR9160) > is no longer being detected. If I roll back to the old kernel, everything > is working great. Here is my kernel config for wireless: > > and changed AR5416_DEFAULT_TXCHAINMASK from 1 to 7 > > > after compiling the 9.0 kernel, pciconf returns the following undetected > devices: > > > none2@pci0:1:15:0: class=0x028000 card=0x40820777 chip=0x0027168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR9160 802.11abgn Wireless PCI Adapter' > class = network > Can you please boot verbosely (eg type "boot -v" at the loader prompt, or select the relevant option) and post the entire boot log? I test frqeuently with AR9160's and I've had zero issues, both on MIPS and i386. It's quite likely it's a cardbus/pci resource allocation issue. Adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 00:53:01 2012 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 EB27D1065679 for ; Tue, 31 Jan 2012 00:53:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id A3B808FC14 for ; Tue, 31 Jan 2012 00:53:01 +0000 (UTC) Received: by vcmm1 with SMTP id m1so5078045vcm.13 for ; Mon, 30 Jan 2012 16:53:01 -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; bh=TSbJ+ypeUOsgYw5NNB1qd+8NSxkl3RdKPmVulGKw/HE=; b=aRcpnnoPW2JUsA83AOyTGoMPyu2CNIRO7or7RLkqoNQdHm/ketVdpxBo/HExM2caxb npRGUg4cefZ8geJr2Am229VsFRdFcz4bjHefUCJ87BHRxyEb38+9tJYjclFSvFlSfMG7 uhMNBUcWpr9NKZrF8tbhg0Sv6DyOt6GzvEM0Y= MIME-Version: 1.0 Received: by 10.220.156.201 with SMTP id y9mr11852248vcw.22.1327971181069; Mon, 30 Jan 2012 16:53:01 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Mon, 30 Jan 2012 16:53:01 -0800 (PST) In-Reply-To: <1327732446.16659@da3m0n8t3r.com> References: <1327732446.16659@da3m0n8t3r.com> Date: Mon, 30 Jan 2012 16:53:01 -0800 X-Google-Sender-Auth: jDh_1EHo-qkUV35gvAooV6kpmq8 Message-ID: From: Adrian Chadd To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Wireless Subject: Re: AR9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 00:53:02 -0000 Just drop me line and we can try to pick a time to meet up and hack on wireless stuff. (The offer is open to anyone else, btw.) Adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 01:07:22 2012 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 129E7106564A for ; Tue, 31 Jan 2012 01:07:22 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 97C1D8FC0C for ; Tue, 31 Jan 2012 01:07:21 +0000 (UTC) Received: by werm13 with SMTP id m13so3412543wer.13 for ; Mon, 30 Jan 2012 17:07:20 -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=FYBcVd87hcdiOi9pdURPyG3KqxDxF7FTheEG8FFAwmE=; b=KtYYbldBGgvsQEclr+PxzRdL7pBUr+sMdA/EIE2kXsn98LsJxJLvIoWm7z34CWsVYX cXvI/CtY7QxHqJXGzpqrHeMHkFCoxFKXoHilxMRe1z92/kK9MQPf+EYVUJQKXwYWHVMs RisjerzLWxevXA2G0XMspI7634t+e4uG7EazQ= MIME-Version: 1.0 Received: by 10.216.135.214 with SMTP id u64mr7802913wei.58.1327972040496; Mon, 30 Jan 2012 17:07:20 -0800 (PST) Received: by 10.223.101.196 with HTTP; Mon, 30 Jan 2012 17:07:20 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 17:07:20 -0800 Message-ID: From: Kevin Oberman To: Luan Hospodarsky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Realtek 8188ce driver X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 01:07:22 -0000 On Mon, Jan 30, 2012 at 2:30 PM, Luan Hospodarsky wrote: > > Hi, > I already tried ndis and the module it generated did not work. > But I don't know anything about a ndis patch, can you tell me more about = it? > Replace the device is still an alternative, but I want to avoid it the ma= x possible. > I have never written a driver, but I could try. Do you have anything to s= hare that can help me give the first steps writing a driver? > Thanks. > >> Date: Mon, 30 Jan 2012 13:54:05 -0800 >> Subject: Re: Realtek 8188ce driver >> From: kob6558@gmail.com >> To: ironfall_blindguardian@hotmail.com >> CC: freebsd-wireless@freebsd.org >> >> On Mon, Jan 30, 2012 at 1:41 PM, Luan Hospodarsky >> wrote: >> > >> > Hi Adrian, >> > Thanks for the reply, >> > >> > So is there some work about it? >> > It is great! If you find anything, let me know! >> > Thanks again. >> > >> > Date: Sun, 29 Jan 2012 17:00:43 -0800 >> > Subject: Re: Realtek 8188ce driver >> > From: adrian@freebsd.org >> > To: ironfall_blindguardian@hotmail.com >> > CC: freebsd-wireless@freebsd.org >> > >> > Hi, >> > >> > I think there's been some recent work to get this chipset support into= shape but I don't know wehre it lives or whether the driver is in a workab= le setup. >> > >> > Does anyone know anything further? >> > >> > >> > >> > Adrian >> > >> > On 29 January 2012 13:24, LuX - I like you wrote: >> > >> > >> > >> > Hello, I'm Luan and I'm a newer FreeBSD Lover. >> > >> > I am having a problem and I have found no answer anywhere, but I hope = you can give me a light. >> > >> > My notebook has an integrated wireless card (Realtek 8188ce) and the R= ealtek site provides drivers only for Windows and Linux. >> > >> > I had read the FreeBSD manual, asked for help in the forum and in the = IRC ##freebsd, but unfortunately nobody could help me. >> > >> > My conclusion is that such driver does not exist in FreeBSD. >> > >> > Is there any projects to port such driver from Linux (I guess OpenBSD = has that driver as well, so the porting could be less painful) or some comp= atible driver to this device? >> > >> > Thanks in advance. >> > >> > --- >> > >> > Luan Hospodarsky >> > >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0_______________________________________________ >> >> 1. You could try ndis. It did not work for me, but a patch to ndis >> looks like it may have fixed the problem. >> >> 2. The other option is to replace the card. What brand of laptop is >> it? Levovo locks down the wireless and will not boot with any card but >> one they sold. I believe HP does the same. I had to buy a card with >> the Lenovo PCI ID to get it to work. I found it from a place that was >> in Germany, =A0but the card was shipped from Tel Aviv. =A0It cost about = 3 >> times what a generic Intel Centrino Advanced-N 6205 would have cost. >> :-( >> >> You might be able to re-write the PCI ID on a standard Intel card, but >> I could not figure out how to do it. You can also patch the BIOS, but >> that make future BIOS upgrades a real problem. >> >> 3. Write a driver >> -- If the documentation for the interface is available, it's not too hard, but from what I've seen, wireless is one of the trickier ones. While I hope someone gets around to writing one, even with the Linux driver to work from, I don't think I'd want to try it. It's been years since I last wrote a driver and it was not on FreeBSD, so I am not the best source of an opinion. Sorry ndis failed. It cause my system to panic when it loaded the module, but a patch to NDIS to fix either my problems or something very similar was committed to HEAD several months ago and should be in 9.0 and maybe even 8.2. Sounds unlikely to fix the problem. If you don't have a Lenovo or HP, swapping is easy and supported half-height mini-PCIe cards are in the 20-25 USD range from multiple vendors. I know it's annoying to have to do it, but it is probably the only way you will get wireless on that system in even reasonably soon. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 01:38:02 2012 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 9DB021065672 for ; Tue, 31 Jan 2012 01:38:02 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s35.snt0.hotmail.com (snt0-omc4-s35.snt0.hotmail.com [65.55.90.238]) by mx1.freebsd.org (Postfix) with ESMTP id 49B2A8FC0A for ; Tue, 31 Jan 2012 01:38:02 +0000 (UTC) Received: from SNT128-W49 ([65.55.90.199]) by snt0-omc4-s35.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 17:38:01 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: , Date: Mon, 30 Jan 2012 20:38:00 -0500 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 31 Jan 2012 01:38:01.0373 (UTC) FILETIME=[F7F24CD0:01CCDFB8] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 01:38:02 -0000 Hi Adrian! Good to see you again! Here is the verbose boot log=2C (had to manually cut= paste from console window) as a quick summary=2C the only thing weird I could find was: Jan 30 07:51:56 core kernel: pci0: at device 3.0 (no driver = attached) Jan 30 07:51:56 core kernel: pci1: at device 15.0 (no driver atta= ched) [START] Jan 30 07:51:56 core syslogd: kernel boot file is /boot/kernel/kernel Jan 30 07:51:56 core kernel: Waiting (max 60 seconds) for system process `v= nlru' to stop...done Jan 30 07:51:56 core kernel: Waiting (max 60 seconds) for system process `b= ufdaemon' to stop...done Jan 30 07:51:56 core kernel: Waiting (max 60 seconds) for system process `s= yncer' to stop... Jan 30 07:51:56 core kernel: Syncing disks=2C vnodes remaining...2 2 2 0 0 = 0 done Jan 30 07:51:56 core kernel: All buffers synced. Jan 30 07:51:56 core kernel: Table 'FACP' at 0xbbc80290 Jan 30 07:51:56 core kernel: Table 'APIC' at 0xbbc80390 Jan 30 07:51:56 core kernel: APIC: Found table at 0xbbc80390 Jan 30 07:51:56 core kernel: APIC: Using the MADT enumerator. Jan 30 07:51:56 core kernel: MADT: Found CPU APIC ID 0 ACPI ID 1: enabled Jan 30 07:51:56 core kernel: SMP: Added CPU 0 (AP) Jan 30 07:51:56 core kernel: MADT: Found CPU APIC ID 1 ACPI ID 2: enabled Jan 30 07:51:56 core kernel: SMP: Added CPU 1 (AP) Jan 30 07:51:56 core kernel: MADT: Found CPU APIC ID 130 ACPI ID 3: disable= d Jan 30 07:51:56 core kernel: MADT: Found CPU APIC ID 131 ACPI ID 4: disable= d Jan 30 07:51:56 core kernel: Copyright (c) 1992-2012 The FreeBSD Project. Jan 30 07:51:56 core kernel: Copyright (c) 1979=2C 1980=2C 1983=2C 1986=2C = 1988=2C 1989=2C 1991=2C 1992=2C 1993=2C 1994 Jan 30 07:51:56 core kernel: The Regents of the University of California. A= ll rights reserved. Jan 30 07:51:56 core kernel: FreeBSD is a registered trademark of The FreeB= SD Foundation. Jan 30 07:51:56 core kernel: FreeBSD 9.0-STABLE #0: Sun Jan 29 20:48:03 EST= 2012 Jan 30 07:51:56 core kernel: root@core.skylab.ca:/usr/obj/usr/src/sys/SKYLA= B amd64 Jan 30 07:51:56 core kernel: Preloaded elf kernel "/boot/kernel/kernel" at = 0xffffffff80e13000. Jan 30 07:51:56 core kernel: Preloaded elf obj module "/boot/kernel/aio.ko"= at 0xffffffff80e13230. Jan 30 07:51:56 core kernel: Calibrating TSC clock ... TSC clock: 120002439= 6 Hz Jan 30 07:51:56 core kernel: CPU: Intel(R) Core(TM)2 Duo CPU U9300 @ 1= .20GHz (1200.02-MHz K8-class CPU) Jan 30 07:51:56 core kernel: Origin =3D "GenuineIntel" Id =3D 0x10676 Fam= ily =3D 6 Model =3D 17 Stepping =3D 6 Jan 30 07:51:56 core kernel: Features=3D0xbfebfbff Jan 30 07:51:56 core kernel: Features2=3D0x8e3fd Jan 30 07:51:56 core kernel: AMD Features=3D0x20000800 Jan 30 07:51:56 core kernel: AMD Features2=3D0x1 Jan 30 07:51:56 core kernel: AMD Features=3D0x20000800 Jan 30 07:51:56 core kernel: AMD Features2=3D0x1 Jan 30 07:51:56 core kernel: TSC: P-state invariant=2C performance statisti= cs Jan 30 07:51:56 core kernel: real memory =3D 4294967296 (4096 MB) Jan 30 07:51:56 core kernel: Physical memory chunk(s): Jan 30 07:51:56 core kernel: 0x0000000000001000 - 0x0000000000099fff=2C 626= 688 bytes (153 pages) Jan 30 07:51:56 core kernel: 0x0000000000100000 - 0x00000000001fffff=2C 104= 8576 bytes (256 pages) Jan 30 07:51:56 core kernel: 0x0000000000e43000 - 0x00000000b27cffff=2C 297= 9581952 bytes (727437 pages) Jan 30 07:51:56 core kernel: 0x0000000100000000 - 0x000000013bfeffff=2C 100= 6567424 bytes (245744 pages) Jan 30 07:51:56 core kernel: avail memory =3D 3954380800 (3771 MB) Jan 30 07:51:56 core kernel: Event timer "LAPIC" quality 400 Jan 30 07:51:56 core kernel: ACPI APIC Table: <082509 APIC1730> Jan 30 07:51:56 core kernel: INTR: Adding local APIC 1 as a target Jan 30 07:51:56 core kernel: FreeBSD/SMP: Multiprocessor System Detected: 2= CPUs Jan 30 07:51:56 core kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) Jan 30 07:51:56 core kernel: cpu0 (BSP): APIC ID: 0 Jan 30 07:51:56 core kernel: cpu1 (AP): APIC ID: 1 Jan 30 07:51:56 core kernel: x86bios: IVT 0x000000-0x0004ff at 0xfffffe000= 0000000 Jan 30 07:51:56 core kernel: x86bios: SSEG 0x001000-0x001fff at 0xffffff800= 0216000 Jan 30 07:51:56 core kernel: x86bios: EBDA 0x09d000-0x09ffff at 0xfffffe000= 009d000 Jan 30 07:51:56 core kernel: x86bios: ROM 0x0a0000-0x0fefff at 0xfffffe000= 00a0000 Jan 30 07:51:56 core kernel: APIC: CPU 0 has ACPI ID 1 Jan 30 07:51:56 core kernel: APIC: CPU 1 has ACPI ID 2 Jan 30 07:51:56 core kernel: ULE: setup cpu 0 Jan 30 07:51:56 core kernel: ULE: setup cpu 1 Jan 30 07:51:56 core kernel: ACPI: RSDP 0xf93d0 00024 (v02 ACPIAM) Jan 30 07:51:56 core kernel: ACPI: XSDT 0xbbc80100 0005C (v01 082509 XSDT17= 30 20090825 MSFT 00000097) Jan 30 07:51:56 core kernel: ACPI: FACP 0xbbc80290 000F4 (v03 082509 FACP17= 30 20090825 MSFT 00000097) Jan 30 07:51:56 core kernel: ACPI: DSDT 0xbbc80440 06DBF (v01 8A812 8A8120= 22 00000022 INTL 20051117) Jan 30 07:51:56 core kernel: ACPI: FACS 0xbbc8e000 00040 Jan 30 07:51:56 core kernel: ACPI: APIC 0xbbc80390 0006C (v01 082509 APIC17= 30 20090825 MSFT 00000097) Jan 30 07:51:56 core kernel: ACPI: MCFG 0xbbc80400 0003C (v01 082509 OEMMCF= G 20090825 MSFT 00000097) Jan 30 07:51:56 core kernel: ACPI: OEMB 0xbbc8e040 00072 (v01 082509 OEMB17= 30 20090825 MSFT 00000097) Jan 30 07:51:56 core kernel: ACPI: HPET 0xbbc8a440 00038 (v01 082509 OEMHPE= T 20--More--(byte 5055) Jan 30 07:51:56 core kernel: ACPI: GSCI 0xbbc8e0c0 02024 (v01 082509 GMCHSC= I 20090825 MSFT 00000097) Jan 30 07:51:56 core kernel: ACPI: SSDT 0xbbc909f0 004F0 (v01 PmRef Cpu= Pm 00003000 INTL 20051117) Jan 30 07:51:56 core kernel: MADT: Found IO APIC ID 2=2C Interrupt 0 at 0xf= ec00000 Jan 30 07:51:56 core kernel: ioapic0: Routing external 8259A's -> intpin 0 Jan 30 07:51:56 core kernel: MADT: Interrupt override: source 0=2C irq 2 Jan 30 07:51:56 core kernel: ioapic0: Routing IRQ 0 -> intpin 2 Jan 30 07:51:56 core kernel: MADT: Interrupt override: source 9=2C irq 9 Jan 30 07:51:56 core kernel: ioapic0: intpin 9 trigger: level Jan 30 07:51:56 core kernel: ioapic0 irqs 0-23 on motherboard Jan 30 07:51:56 core kernel: cpu0 BSP: Jan 30 07:51:56 core kernel: ID: 0x00000000 VER: 0x00050014 LDR: 0x000000= 00 DFR: 0xffffffff Jan 30 07:51:56 core kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x000= 00000 SVR: 0x000001ff Jan 30 07:51:56 core kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000= 000f0 pmc: 0x00010400 Jan 30 07:51:56 core kernel: wlan: mac acl policy registered Jan 30 07:51:56 core kernel: wlan: <802.11 Link Layer> Jan 30 07:51:56 core kernel: random: Jan 30 07:51:56 core kernel: cpuctl: access to MSR registers/cpuid info. Jan 30 07:51:56 core kernel: io: Jan 30 07:51:56 core kernel: nfslock: pseudo-device Jan 30 07:51:56 core kernel: mem: Jan 30 07:51:56 core kernel: null: Jan 30 07:51:56 core kernel: acpi0: <082509 XSDT1730> on motherboard Jan 30 07:51:56 core kernel: PCIe: Memory Mapped configuration base @ 0xe00= 00000 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 9 (ISA IRQ 9) to lapic= 0 vector 48 Jan 30 07:51:56 core kernel: ACPI: Executed 1 blocks of module-level execut= able AML code Jan 30 07:51:56 core kernel: acpi0: Power Button (fixed) Jan 30 07:51:56 core kernel: acpi0: reservation of fee00000=2C 1000 (3) fai= led Jan 30 07:51:56 core kernel: acpi0: reservation of 0=2C a0000 (3) failed Jan 30 07:51:56 core kernel: acpi0: reservation of 100000=2C bbd00000 (3) f= ailed Jan 30 07:51:56 core kernel: ACPI timer: 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/= 0 1/0 -> 10 Jan 30 07:51:56 core kernel: Timecounter "ACPI-fast" frequency 3579545 Hz q= uality 900 Jan 30 07:51:56 core kernel: acpi_timer0: <24-bit timer at 3.579545MHz> por= t 0x808-0x80b on acpi0 Jan 30 07:51:56 core kernel: cpu0: on acpi0 Jan 30 07:51:56 core kernel: ACPI Warning: Incorrect checksum in table [OEM= B] - 0xAB=2C should be 0xAA (20110527/tbutils-282) Jan 30 07:51:56 core kernel: ACPI: SSDT 0xbbc901c0 001FA (v01 PmRef Cpu0I= st 00003000 INTL 20051117) Jan 30 07:51:56 core kernel: ACPI: Dynamic OEM Table Load: Jan 30 07:51:56 core kernel: ACPI: SSDT 0 001FA (v01 PmRef Cpu0Ist 000030= 00 INTL 20051117) Jan 30 07:51:56 core kernel: ACPI: SSDT 0xbbc90450 00594 (v01 PmRef Cpu0C= st 00003001 INTL 20051117) Jan 30 07:51:56 core kernel: ACPI: Dynamic OEM Table Load: Jan 30 07:51:56 core kernel: ACPI: SSDT 0 00594 (v01 PmRef Cpu0Cst 000030= 01 INTL 20051117) Jan 30 07:51:56 core kernel: cpu1: on acpi0 Jan 30 07:51:56 core kernel: ACPI: SSDT 0xbbc900f0 000CC (v01 PmRef Cpu1I= st 00003000 INTL 20051117) Jan 30 07:51:56 core kernel: ACPI: Dynamic OEM Table Load: Jan 30 07:51:56 core kernel: ACPI: SSDT 0 000CC (v01 PmRef Cpu1Ist 000030= 00 INTL 20051117) Jan 30 07:51:56 core kernel: ACPI: SSDT 0xbbc903c0 00085 (v01 PmRef Cpu1C= st 00003000 INTL 20051117) Jan 30 07:51:56 core kernel: ACPI: Dynamic OEM Table Load: Jan 30 07:51:56 core kernel: ACPI: SSDT 0 00085 (v01 PmRef Cpu1Cst 000030= 00 INTL 20051117) Jan 30 07:51:56 core kernel: pci_link0: Index IRQ Rtd Ref IRQs Jan 30 07:51:56 core kernel: Validation 0 10 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: After Disable 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: pci_link1: Index IRQ Rtd Ref IRQs Jan 30 07:51:56 core kernel: Initial Probe 0 5 N 0 5 Jan 30 07:51:56 core kernel: Validation 0 5 N 0 5 Jan 30 07:51:56 core kernel: After Disable 0 255 N 0 5 Jan 30 07:51:56 core kernel: pci_link2: Index IRQ Rtd Ref IRQs Jan 30 07:51:56 core kernel: Initial Probe 0 11 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: Validation 0 11 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: After Disable 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: pci_link3: Index IRQ Rtd Ref IRQs Jan 30 07:51:56 core kernel: Initial Probe 0 3 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: Validation 0 3 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: After Disable 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: pci_link4: Index IRQ Rtd Ref IRQs Jan 30 07:51:56 core kernel: Initial Probe 0 6 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: Validation 0 6 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: After Disable 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: pci_link5: Index IRQ Rtd Ref IRQs Jan 30 07:51:56 core kernel: Initial Probe 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: Validation 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: After Disable 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: pci_link6: Index IRQ Rtd Ref IRQs Jan 30 07:51:56 core kernel: Initial Probe 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: Validation 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: After Disable 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: pci_link7: Index IRQ Rtd Ref IRQs Jan 30 07:51:56 core kernel: Validation 0 7 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: After Disable 0 255 N 0 3 4 6 7 = 10 11 12 14 15 Jan 30 07:51:56 core kernel: pcib0: port 0xcf8-0xcff= on acpi0 Jan 30 07:51:56 core kernel: pcib0: decoding 4 range 0-0xcf7 Jan 30 07:51:56 core kernel: pcib0: decoding 4 range 0xd00-0xffff Jan 30 07:51:56 core kernel: pcib0: decoding 3 range 0xa0000-0xbffff Jan 30 07:51:56 core kernel: pcib0: decoding 3 range 0xd0000-0xdffff Jan 30 07:51:56 core kernel: pcib0: decoding 3 range 0xbbe00000-0xdfffffff Jan 30 07:51:56 core kernel: pcib0: decoding 3 range 0xf0000000-0xfed8ffff Jan 30 07:51:56 core kernel: pci0: on pcib0 Jan 30 07:51:56 core kernel: pci0: domain=3D0=2C physical bus=3D0 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2a40=2C = revid=3D0x07 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D0=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D06-00-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0006=2C statreg=3D0x2090=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2a42=2C = revid=3D0x07 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D2=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D03-00-00=2C hdrtype=3D0x00=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0090=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D10 Jan 30 07:51:56 core kernel: powerspec 3 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 64=2C base 0xfe0= 00000=2C size 22=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe000000-0xfe3fffff= ) for rid 10 of pci0:0:2:0 Jan 30 07:51:56 core kernel: map[18]: type Prefetchable Memory=2C range 64= =2C base 0xd0000000=2C size 28=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd0000000-0xdfffffff= ) for rid 18 of pci0:0:2:0 Jan 30 07:51:56 core kernel: map[20]: type I/O Port=2C range 32=2C base 0x8= 080=2C size 3=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x8080-0x8087) for ri= d 20 of pci0:0:2:0 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.2.INTA Jan 30 07:51:56 core kernel: pcib0: slot 2 INTA hardwired to IRQ 16 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2a43=2C = revid=3D0x07 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D2=2C func=3D1 Jan 30 07:51:56 core kernel: class=3D03-80-00=2C hdrtype=3D0x00=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0090=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: powerspec 3 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 64=2C base 0xfe4= 00000=2C size 20=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe400000-0xfe4fffff= ) for rid 10 of pci0:0:2:1 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2a44=2C = revid=3D0x07 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D3=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D07-80-00=2C hdrtype=3D0x00=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0006=2C statreg=3D0x0010=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D10 Jan 30 07:51:56 core kernel: powerspec 3 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message=2C 64 bit Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 64=2C base 0xfe5= ff000=2C size 4=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe5ff000-0xfe5ff00f= ) for rid 10 of pci0:0:3:0 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.3.INTA Jan 30 07:51:56 core kernel: pcib0: slot 3 INTA hardwired to IRQ 16 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x10f5=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D25=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D02-00-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0010=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D6 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message=2C 64 bit Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 32=2C base 0xfe5= c0000=2C size 17=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe5c0000-0xfe5dffff= ) for rid 10 of pci0:0:25:0 Jan 30 07:51:56 core kernel: map[14]: type Memory=2C range 32=2C base 0xfe5= fe000=2C size 12=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe5fe000-0xfe5fefff= ) for rid 14 of pci0:0:25:0 Jan 30 07:51:56 core kernel: map[18]: type I/O Port=2C range 32=2C base 0x8= 400=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x8400-0x841f) for ri= d 18 of pci0:0:25:0 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.25.INTA Jan 30 07:51:56 core kernel: pcib0: slot 25 INTA hardwired to IRQ 20 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2937=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D26=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D0c-03-00=2C hdrtype=3D0x00=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0005=2C statreg=3D0x0290=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D10 Jan 30 07:51:56 core kernel: map[20]: type I/O Port=2C range 32=2C base 0x8= 480=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x8480-0x849f) for ri= d 20 of pci0:0:26:0 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.26.INTA Jan 30 07:51:56 core kernel: pcib0: slot 26 INTA hardwired to IRQ 16 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x293c=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D26=2C func=3D7 Jan 30 07:51:56 core kernel: class=3D0c-03-20=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0006=2C statreg=3D0x0290=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Dc=2C irq=3D11 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe5ff400-0xfe5ff7ff= ) for rid 10 of pci0:0:26:7 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.26.INTC Jan 30 07:51:56 core kernel: pcib0: slot 26 INTC hardwired to IRQ 18 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2940=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D28=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D06-04-00=2C hdrtype=3D0x01=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0107=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x02 (500 n= s)=2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D5 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.28.INTA Jan 30 07:51:56 core kernel: pcib0: slot 28 INTA hardwired to IRQ 17 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2942=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D28=2C func=3D1 Jan 30 07:51:56 core kernel: class=3D06-04-00=2C hdrtype=3D0x01=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0107=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x02 (500 n= s)=2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Db=2C irq=3D10 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.28.INTB Jan 30 07:51:56 core kernel: pcib0: slot 28 INTB hardwired to IRQ 16 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2944=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D28=2C func=3D2 Jan 30 07:51:56 core kernel: class=3D06-04-00=2C hdrtype=3D0x01=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0107=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x02 (500 n= s)=2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Dc=2C irq=3D11 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.28.INTC Jan 30 07:51:56 core kernel: pcib0: slot 28 INTC hardwired to IRQ 18 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2946=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D28=2C func=3D3 Jan 30 07:51:56 core kernel: class=3D06-04-00=2C hdrtype=3D0x01=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0107=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x02 (500 n= s)=2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Dd=2C irq=3D3 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.28.INTD Jan 30 07:51:56 core kernel: pcib0: slot 28 INTD hardwired to IRQ 19 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2948=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D28=2C func=3D4 Jan 30 07:51:56 core kernel: class=3D06-04-00=2C hdrtype=3D0x01=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0107=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x02 (500 n= s)=2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D5 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.28.INTA Jan 30 07:51:56 core kernel: pcib0: slot 28 INTA hardwired to IRQ 17 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2934=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D29=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D0c-03-00=2C hdrtype=3D0x00=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0005=2C statreg=3D0x0290=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D7 Jan 30 07:51:56 core kernel: map[20]: type I/O Port=2C range 32=2C base 0x8= c00=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x8c00-0x8c1f) for ri= d 20 of pci0:0:29:0 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.29.INTA Jan 30 07:51:56 core kernel: pcib0: slot 29 INTA hardwired to IRQ 23 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2935=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D29=2C func=3D1 Jan 30 07:51:56 core kernel: class=3D0c-03-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0005=2C statreg=3D0x0290=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Db=2C irq=3D3 Jan 30 07:51:56 core kernel: map[20]: type I/O Port=2C range 32=2C base 0x8= 880=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x8880-0x889f) for ri= d 20 of pci0:0:29:1 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.29.INTB Jan 30 07:51:56 core kernel: pcib0: slot 29 INTB hardwired to IRQ 19 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2936=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D29=2C func=3D2 Jan 30 07:51:56 core kernel: class=3D0c-03-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0005=2C statreg=3D0x0290=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Dc=2C irq=3D11 Jan 30 07:51:56 core kernel: map[20]: type I/O Port=2C range 32=2C base 0x8= 800=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x8800-0x881f) for ri= d 20 of pci0:0:29:2 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.29.INTC Jan 30 07:51:56 core kernel: pcib0: slot 29 INTC hardwired to IRQ 18 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x293a=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D29=2C func=3D7 Jan 30 07:51:56 core kernel: class=3D0c-03-20=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0006=2C statreg=3D0x0290=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D7 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 32=2C base 0xfe5= ff800=2C size 10=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe5ff800-0xfe5ffbff= ) for rid 10 of pci0:0:29:7 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.29.INTA Jan 30 07:51:56 core kernel: pcib0: slot 29 INTA hardwired to IRQ 23 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2448=2C = revid=3D0x93 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D30=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D06-04-01=2C hdrtype=3D0x01=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0106=2C statreg=3D0x0010=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x02 (500 n= s)=2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2917=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D31=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D06-01-00=2C hdrtype=3D0x00=2C mfdev=3D= 1 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0210=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2928=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D31=2C func=3D2 Jan 30 07:51:56 core kernel: class=3D01-01-8a=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0005=2C statreg=3D0x02b0=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Db=2C irq=3D255 Jan 30 07:51:56 core kernel: powerspec 3 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x1f0-0x1f7) for rid = 10 of pci0:0:31:2 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x3f6-0x3f6) for rid = 14 of pci0:0:31:2 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x376-0x376) for rid = 1c of pci0:0:31:2 Jan 30 07:51:56 core kernel: map[20]: type I/O Port=2C range 32=2C base 0xf= f90=2C size 4=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0xff90-0xff9f) for ri= d 20 of pci0:0:31:2 Jan 30 07:51:56 core kernel: map[24]: type I/O Port=2C range 32=2C base 0xf= fa0=2C size 4=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0xffa0-0xffaf) for ri= d 24 of pci0:0:31:2 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x2930=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D31=2C func=3D3 Jan 30 07:51:56 core kernel: class=3D0c-05-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0003=2C statreg=3D0x0280=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Dc=2C irq=3D11 Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 64=2C base 0xfe5= ffc00=2C size 8=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe5ffc00-0xfe5ffcff= ) for rid 10 of pci0:0:31:3 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x400-0x41f) for rid = 20 of pci0:0:31:3 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.31.INTC Jan 30 07:51:56 core kernel: pcib0: slot 31 INTC hardwired to IRQ 18 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x292d=2C = revid=3D0x03 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D0=2C slot=3D31=2C func=3D5 Jan 30 07:51:56 core kernel: class=3D01-01-85=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0005=2C statreg=3D0x02b0=2C cacheln= sz=3D0 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Db=2C irq=3D3 Jan 30 07:51:56 core kernel: powerspec 3 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: map[10]: type I/O Port=2C range 32=2C base 0x9= 880=2C size 3=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x9880-0x9887) for ri= d 10 of pci0:0:31:5 Jan 30 07:51:56 core kernel: map[14]: type I/O Port=2C range 32=2C base 0x9= 800=2C size 2=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x9800-0x9803) for ri= d 14 of pci0:0:31:5 Jan 30 07:51:56 core kernel: map[18]: type I/O Port=2C range 32=2C base 0x9= 480=2C size 3=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x9480-0x9487) for ri= d 18 of pci0:0:31:5 Jan 30 07:51:56 core kernel: map[1c]: type I/O Port=2C range 32=2C base 0x9= 400=2C size 2=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x9400-0x9403) for ri= d 1c of pci0:0:31:5 Jan 30 07:51:56 core kernel: map[20]: type I/O Port=2C range 32=2C base 0x9= 080=2C size 4=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x9080-0x908f) for ri= d 20 of pci0:0:31:5 Jan 30 07:51:56 core kernel: map[24]: type I/O Port=2C range 32=2C base 0x9= 000=2C size 4=2C enabled Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x9000-0x900f) for ri= d 24 of pci0:0:31:5 Jan 30 07:51:56 core kernel: pcib0: matched entry for 0.31.INTB Jan 30 07:51:56 core kernel: pcib0: slot 31 INTB hardwired to IRQ 19 Jan 30 07:51:56 core kernel: vgapci0: port 0x8080-= 0x8087 mem 0xfe000000-0xfe3fffff=2C0xd0000000-0xdfffffff irq 16 at device 2= .0 on pci0 Jan 30 07:51:56 core kernel: vgapci1: mem 0xfe4000= 00-0xfe4fffff at device 2.1 on pci0 Jan 30 07:51:56 core kernel: pci0: at device 3.0 (no driver = attached) Jan 30 07:51:56 core kernel: em0: attempting to allocate 1 MSI vectors (1 s= upported) Jan 30 07:51:56 core kernel: msi: routing MSI IRQ 256 to local APIC 0 vecto= r 49 Jan 30 07:51:56 core kernel: em0: using IRQ 256 for MSI Jan 30 07:51:56 core kernel: em0: Using an MSI interrupt Jan 30 07:51:56 core kernel: em0: bpf attached Jan 30 07:51:56 core kernel: em0: Ethernet address: 88:55:88:55:88:55 Jan 30 07:51:56 core kernel: uhci0: po= rt 0x8480-0x849f irq 16 at device 26.0 on pci0 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 16 (PCI IRQ 16) to lap= ic 0 vector 50 Jan 30 07:51:56 core kernel: usbus0: o= n uhci0 Jan 30 07:51:56 core kernel: usbus0: bpf attached Jan 30 07:51:56 core kernel: uhci0: usbpf: Attached Jan 30 07:51:56 core kernel: ehci0: mem 0xfe5ff400-0xfe5ff7ff irq 18 at device 26.7 on pci0 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 18 (PCI IRQ 18) to lap= ic 0 vector 51 Jan 30 07:51:56 core kernel: usbus1: EHCI version 1.0 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 18 (PCI IRQ 18) to lap= ic 0 vector 51 Jan 30 07:51:56 core kernel: usbus1: EHCI version 1.0 ehci0 Jan 30 07:51:56 core kernel: usbus1: bpf attached Jan 30 07:51:56 core kernel: ehci0: usbpf: Attached Jan 30 07:51:56 core kernel: pcib1: irq 17 at device = 28.0 on pci0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0xa000-0xafff) for ri= d 1c of pcib1 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe700000-0xfe7fffff= ) for rid 20 of pcib1 Jan 30 07:51:56 core kernel: pcib1: domain 0 Jan 30 07:51:56 core kernel: pcib1: secondary bus 2 Jan 30 07:51:56 core kernel: pcib1: subordinate bus 2 Jan 30 07:51:56 core kernel: pcib1: I/O decode 0xa000-0xafff Jan 30 07:51:56 core kernel: pcib1: memory decode 0xfe700000-0xfe7fff= ff Jan 30 07:51:56 core kernel: pcib1: no prefetched decode Jan 30 07:51:56 core kernel: pci2: on pcib1 Jan 30 07:51:56 core kernel: pci2: domain=3D0=2C physical bus=3D2 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x10d3=2C = revid=3D0x00 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D2=2C slot=3D0=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D02-00-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D10 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message=2C 64 bit Jan 30 07:51:56 core kernel: MSI-X supports 5 messages in map 0x1c Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 32=2C base 0xfe7= e0000=2C size 17=2C enabled Jan 30 07:51:56 core kernel: pcib1: allocated memory range (0xfe7e0000-0xfe= 7fffff) for rid 10 of pci0:2:0:0 Jan 30 07:51:56 core kernel: map[18]: type I/O Port=2C range 32=2C base 0xa= c00=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib1: allocated I/O port range (0xac00-0xac1f= ) for rid 18 of pci0:2:0:0 Jan 30 07:51:56 core kernel: map[1c]: type Memory=2C range 32=2C base 0xfe7= dc000=2C size 14=2C enabled Jan 30 07:51:56 core kernel: pcib1: allocated memory range (0xfe7dc000-0xfe= 7dffff) for rid 1c of pci0:2:0:0 Jan 30 07:51:56 core kernel: pcib1: matched entry for 2.0.INTA Jan 30 07:51:56 core kernel: pcib1: slot 0 INTA hardwired to IRQ 16 Jan 30 07:51:56 core kernel: em1: port 0xac00-0xac1f mem 0xfe7e0000-0xfe7fffff=2C0xfe7dc000-0xfe7dffff ir= q 16 at device 0.0 on pci2 Jan 30 07:51:56 core kernel: em1: attempting to allocate 3 MSI-X vectors (5= supported) Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 257 to local APIC 0 vec= tor 52 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 258 to local APIC 0 vec= tor 53 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 259 to local APIC 0 vec= tor 54 Jan 30 07:51:56 core kernel: em1: using IRQs 257-259 for MSI-X Jan 30 07:51:56 core kernel: em1: Using MSIX interrupts with 3 vectors Jan 30 07:51:56 core kernel: em1: bpf attached Jan 30 07:51:56 core kernel: em1: Ethernet address: 00:60:e0:47:1b:7f Jan 30 07:51:56 core kernel: pcib2: irq 16 at device = 28.1 on pci0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0xb000-0xbfff) for ri= d 1c of pcib2 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe800000-0xfe8fffff= ) for rid 20 of pcib2 Jan 30 07:51:56 core kernel: pcib2: domain 0 Jan 30 07:51:56 core kernel: pcib2: secondary bus 3 Jan 30 07:51:56 core kernel: pcib2: subordinate bus 3 Jan 30 07:51:56 core kernel: pcib2: I/O decode 0xb000-0xbfff Jan 30 07:51:56 core kernel: pcib2: memory decode 0xfe800000-0xfe8fff= ff Jan 30 07:51:56 core kernel: pcib2: no prefetched decode Jan 30 07:51:56 core kernel: pci3: on pcib2 Jan 30 07:51:56 core kernel: pci3: domain=3D0=2C physical bus=3D3 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x10d3=2C = revid=3D0x00 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D3=2C slot=3D0=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D02-00-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D5 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message=2C 64 bit Jan 30 07:51:56 core kernel: MSI-X supports 5 messages in map 0x1c Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 32=2C base 0xfe8= e0000=2C size 17=2C enabled Jan 30 07:51:56 core kernel: pcib2: allocated memory range (0xfe8e0000-0xfe= 8fffff) for rid 10 of pci0:3:0:0 Jan 30 07:51:56 core kernel: map[18]: type I/O Port=2C range 32=2C base 0xb= c00=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib2: allocated I/O port range (0xbc00-0xbc1f= ) for rid 18 of pci0:3:0:0 Jan 30 07:51:56 core kernel: map[1c]: type Memory=2C range 32=2C base 0xfe8= dc000=2C size 14=2C enabled Jan 30 07:51:56 core kernel: pcib2: allocated memory range (0xfe8dc000-0xfe= 8dffff) for rid 1c of pci0:3:0:0 Jan 30 07:51:56 core kernel: pcib2: matched entry for 3.0.INTA Jan 30 07:51:56 core kernel: pcib2: slot 0 INTA hardwired to IRQ 17 Jan 30 07:51:56 core kernel: em2: port 0xbc00-0xbc1f mem 0xfe8e0000-0xfe8fffff=2C0xfe8dc000-0xfe8dffff ir= q 17 at device 0.0 on pci3 Jan 30 07:51:56 core kernel: em2: attempting to allocate 3 MSI-X vectors (5= supported) Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 260 to local APIC 0 vec= tor 55 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 261 to local APIC 0 vec= tor 56 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 262 to local APIC 0 vec= tor 57 Jan 30 07:51:56 core kernel: em2: using IRQs 260-262 for MSI-X Jan 30 07:51:56 core kernel: em2: Using MSIX interrupts with 3 vectors Jan 30 07:51:56 core kernel: em2: bpf attached Jan 30 07:51:56 core kernel: em2: Ethernet address: 00:60:e0:47:1b:80 Jan 30 07:51:56 core kernel: pcib3: irq 18 at device = 28.2 on pci0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0xc000-0xcfff) for ri= d 1c of pcib3 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfe900000-0xfe9fffff= ) for rid 20 of pcib3 Jan 30 07:51:56 core kernel: pcib3: domain 0 Jan 30 07:51:56 core kernel: pcib3: secondary bus 4 Jan 30 07:51:56 core kernel: pcib3: subordinate bus 4 Jan 30 07:51:56 core kernel: pcib3: I/O decode 0xc000-0xcfff Jan 30 07:51:56 core kernel: pcib3: memory decode 0xfe900000-0xfe9fff= ff Jan 30 07:51:56 core kernel: pcib3: no prefetched decode Jan 30 07:51:56 core kernel: pci4: on pcib3 Jan 30 07:51:56 core kernel: pci4: domain=3D0=2C physical bus=3D4 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x10d3=2C = revid=3D0x00 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D4=2C slot=3D0=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D02-00-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D11 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message=2C 64 bit Jan 30 07:51:56 core kernel: MSI-X supports 5 messages in map 0x1c Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 32=2C base 0xfe9= e0000=2C size 17=2C enabled Jan 30 07:51:56 core kernel: pcib3: allocated memory range (0xfe9e0000-0xfe= 9fffff) for rid 10 of pci0:4:0:0 Jan 30 07:51:56 core kernel: pcib3: allocated I/O port range (0xcc00-0xcc1f= ) for rid 18 of pci0:4:0:0 Jan 30 07:51:56 core kernel: map[1c]: type Memory=2C range 32=2C base 0xfe9= dc000=2C size 14=2C enabled Jan 30 07:51:56 core kernel: pcib3: allocated memory range (0xfe9dc000-0xfe= 9dffff) for rid 1c of pci0:4:0:0 Jan 30 07:51:56 core kernel: pcib3: matched entry for 4.0.INTA Jan 30 07:51:56 core kernel: pcib3: slot 0 INTA hardwired to IRQ 18 Jan 30 07:51:56 core kernel: em3: port 0xcc00-0xcc1f mem 0xfe9e0000-0xfe9fffff=2C0xfe9dc000-0xfe9dffff ir= q 18 at device 0.0 on pci4 Jan 30 07:51:56 core kernel: em3: attempting to allocate 3 MSI-X vectors (5= supported) Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 263 to local APIC 0 vec= tor 58 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 264 to local APIC 0 vec= tor 59 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 265 to local APIC 0 vec= tor 60 Jan 30 07:51:56 core kernel: em3: using IRQs 263-265 for MSI-X Jan 30 07:51:56 core kernel: em3: Using MSIX interrupts with 3 vectors Jan 30 07:51:56 core kernel: em3: bpf attached Jan 30 07:51:56 core kernel: em3: Ethernet address: 00:60:e0:47:1b:81 Jan 30 07:51:56 core kernel: pcib4: irq 19 at device = 28.3 on pci0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0xd000-0xdfff) for ri= d 1c of pcib4 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfea00000-0xfeafffff= ) for rid 20 of pcib4 Jan 30 07:51:56 core kernel: pcib4: domain 0 Jan 30 07:51:56 core kernel: pcib4: secondary bus 5 Jan 30 07:51:56 core kernel: pcib4: subordinate bus 5 Jan 30 07:51:56 core kernel: pcib4: I/O decode 0xd000-0xdfff Jan 30 07:51:56 core kernel: pcib4: memory decode 0xfea00000-0xfeafff= ff Jan 30 07:51:56 core kernel: pcib4: no prefetched decode Jan 30 07:51:56 core kernel: pci5: on pcib4 Jan 30 07:51:56 core kernel: pci5: domain=3D0=2C physical bus=3D5 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x10d3=2C = revid=3D0x00 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D5=2C slot=3D0=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D02-00-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D3 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message=2C 64 bit Jan 30 07:51:56 core kernel: MSI-X supports 5 messages in map 0x1c Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 32=2C base 0xfea= e0000=2C size 17=2C enabled Jan 30 07:51:56 core kernel: pcib4: allocated memory range (0xfeae0000-0xfe= afffff) for rid 10 of pci0:5:0:0 Jan 30 07:51:56 core kernel: map[18]: type I/O Port=2C range 32=2C base 0xd= c00=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib4: allocated I/O port range (0xdc00-0xdc1f= ) for rid 18 of pci0:5:0:0 Jan 30 07:51:56 core kernel: map[1c]: type Memory=2C range 32=2C base 0xfea= dc000=2C size 14=2C enabled Jan 30 07:51:56 core kernel: pcib4: allocated memory range (0xfeadc000-0xfe= adffff) for rid 1c of pci0:5:0:0 Jan 30 07:51:56 core kernel: pcib4: matched entry for 5.0.INTA Jan 30 07:51:56 core kernel: pcib4: slot 0 INTA hardwired to IRQ 19 Jan 30 07:51:56 core kernel: em4: port 0xdc00-0xdc1f mem 0xfeae0000-0xfeafffff=2C0xfeadc000-0xfeadffff ir= q 19 at device 0.0 on pci5 Jan 30 07:51:56 core kernel: em4: attempting to allocate 3 MSI-X vectors (5= supported) Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 266 to local APIC 0 vec= tor 61 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 267 to local APIC 0 vec= tor 62 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 268 to local APIC 0 vec= tor 63 Jan 30 07:51:56 core kernel: em4: using IRQs 266-268 for MSI-X Jan 30 07:51:56 core kernel: em4: Using MSIX interrupts with 3 vectors Jan 30 07:51:56 core kernel: em4: bpf attached Jan 30 07:51:56 core kernel: em4: Ethernet address: 00:60:e0:47:1b:82 Jan 30 07:51:56 core kernel: pcib5: irq 17 at device = 28.4 on pci0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0xe000-0xefff) for ri= d 1c of pcib5 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfeb00000-0xfebfffff= ) for rid 20 of pcib5 Jan 30 07:51:56 core kernel: pcib5: domain 0 Jan 30 07:51:56 core kernel: pcib5: secondary bus 6 Jan 30 07:51:56 core kernel: pcib5: subordinate bus 6 Jan 30 07:51:56 core kernel: pcib5: I/O decode 0xe000-0xefff Jan 30 07:51:56 core kernel: pcib5: memory decode 0xfeb00000-0xfebfff= ff Jan 30 07:51:56 core kernel: pcib5: no prefetched decode Jan 30 07:51:56 core kernel: pci6: on pcib5 Jan 30 07:51:56 core kernel: pci6: domain=3D0=2C physical bus=3D6 Jan 30 07:51:56 core kernel: found-> vendor=3D0x8086=2C dev=3D0x10d3=2C = revid=3D0x00 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D6=2C slot=3D0=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D02-00-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0007=2C statreg=3D0x0010=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x00 (0 ns)=2C mingnt=3D0x00 (0 ns)= =2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D10 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: MSI supports 1 message=2C 64 bit Jan 30 07:51:56 core kernel: MSI-X supports 5 messages in map 0x1c Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 32=2C base 0xfeb= e0000=2C size 17=2C enabled Jan 30 07:51:56 core kernel: pcib5: allocated memory range (0xfebe0000-0xfe= bfffff) for rid 10 of pci0:6:0:0 Jan 30 07:51:56 core kernel: map[18]: type I/O Port=2C range 32=2C base 0xe= c00=2C size 5=2C enabled Jan 30 07:51:56 core kernel: pcib5: allocated I/O port range (0xec00-0xec1f= ) for rid 18 of pci0:6:0:0 Jan 30 07:51:56 core kernel: map[1c]: type Memory=2C range 32=2C base 0xfeb= dc000=2C size 14=2C enabled Jan 30 07:51:56 core kernel: pcib5: allocated memory range (0xfebdc000-0xfe= bdffff) for rid 1c of pci0:6:0:0 Jan 30 07:51:56 core kernel: pcib5: matched entry for 6.0.INTA Jan 30 07:51:56 core kernel: pcib5: slot 0 INTA hardwired to IRQ 16 Jan 30 07:51:56 core kernel: em5: port 0xec00-0xec1f mem 0xfebe0000-0xfebfffff=2C0xfebdc000-0xfebdffff ir= q 16 at device 0.0 on pci6 Jan 30 07:51:56 core kernel: em5: attempting to allocate 3 MSI-X vectors (5= supported) Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 269 to local APIC 0 vec= tor 64 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 270 to local APIC 0 vec= tor 65 Jan 30 07:51:56 core kernel: msi: routing MSI-X IRQ 271 to local APIC 0 vec= tor 66 Jan 30 07:51:56 core kernel: em5: using IRQs 269-271 for MSI-X Jan 30 07:51:56 core kernel: em5: Using MSIX interrupts with 3 vectors Jan 30 07:51:56 core kernel: em5: bpf attached Jan 30 07:51:56 core kernel: em5: Ethernet address: 00:60:e0:47:1b:83 Jan 30 07:51:56 core kernel: uhci1: po= rt 0x8c00-0x8c1f irq 23 at device 29.0 on pci0 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 23 (PCI IRQ 23) to lap= ic 0 vector 67 Jan 30 07:51:56 core kernel: usbus2: o= n uhci1 Jan 30 07:51:56 core kernel: usbus2: bpf attached Jan 30 07:51:56 core kernel: uhci1: usbpf: Attached Jan 30 07:51:56 core kernel: ioapic0: routing intpin 23 (PCI IRQ 23) to lap= ic 0 vector 67 Jan 30 07:51:56 core kernel: usbus2: o= n uhci1 Jan 30 07:51:56 core kernel: usbus2: bpf attached Jan 30 07:51:56 core kernel: uhci1: usbpf: Attached Jan 30 07:51:56 core kernel: uhci2: po= rt 0x8880-0x889f irq 19 at device 29.1 on pci0 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 19 (PCI IRQ 19) to lap= ic 0 vector 68 Jan 30 07:51:56 core kernel: usbus3: o= n uhci2 Jan 30 07:51:56 core kernel: usbus3: bpf attached Jan 30 07:51:56 core kernel: uhci2: usbpf: Attached Jan 30 07:51:56 core kernel: uhci3: po= rt 0x8800-0x881f irq 18 at device 29.2 on pci0 Jan 30 07:51:56 core kernel: usbus4: o= n uhci3 Jan 30 07:51:56 core kernel: usbus4: bpf attached Jan 30 07:51:56 core kernel: uhci3: usbpf: Attached Jan 30 07:51:56 core kernel: ehci1: mem 0xfe5ff800-0xfe5ffbff irq 23 at device 29.7 on pci0 Jan 30 07:51:56 core kernel: usbus5: EHCI version 1.0 Jan 30 07:51:56 core kernel: usbus5: on ehci1 Jan 30 07:51:56 core kernel: usbus5: bpf attached Jan 30 07:51:56 core kernel: ehci1: usbpf: Attached Jan 30 07:51:56 core kernel: pcib6: at device 30.0 on= pci0 Jan 30 07:51:56 core kernel: pcib6: domain 0 Jan 30 07:51:56 core kernel: pcib6: secondary bus 1 Jan 30 07:51:56 core kernel: pcib6: subordinate bus 1 Jan 30 07:51:56 core kernel: pcib6: memory decode 0xfe600000-0xfe6fff= ff Jan 30 07:51:56 core kernel: pcib6: no prefetched decode Jan 30 07:51:56 core kernel: pcib6: Subtractively decoded bridge. Jan 30 07:51:56 core kernel: pci1: on pcib6 Jan 30 07:51:56 core kernel: pci1: domain=3D0=2C physical bus=3D1 Jan 30 07:51:56 core kernel: found-> vendor=3D0x168c=2C dev=3D0x0027=2C = revid=3D0x01 Jan 30 07:51:56 core kernel: domain=3D0=2C bus=3D1=2C slot=3D15=2C func=3D0 Jan 30 07:51:56 core kernel: class=3D02-80-00=2C hdrtype=3D0x00=2C mfdev=3D= 0 Jan 30 07:51:56 core kernel: cmdreg=3D0x0016=2C statreg=3D0x02b0=2C cacheln= sz=3D8 (dwords) Jan 30 07:51:56 core kernel: lattimer=3D0x40 (1920 ns)=2C mingnt=3D0x00 (0 = ns)=2C maxlat=3D0x00 (0 ns) Jan 30 07:51:56 core kernel: intpin=3Da=2C irq=3D3 Jan 30 07:51:56 core kernel: powerspec 2 supports D0 D3 current D0 Jan 30 07:51:56 core kernel: map[10]: type Memory=2C range 32=2C base 0xfe6= f0000=2C size 16=2C enabled Jan 30 07:51:56 core kernel: pcib6: allocated memory range (0xfe6f0000-0xfe= 6fffff) for rid 10 of pci0:1:15:0 Jan 30 07:51:56 core kernel: pcib6: matched entry for 1.15.INTA Jan 30 07:51:56 core kernel: pcib6: slot 15 INTA hardwired to IRQ 19 Jan 30 07:51:56 core kernel: pci1: at device 15.0 (no driver atta= ched) Jan 30 07:51:56 core kernel: isab0: at device 31.0 on pci0 Jan 30 07:51:56 core kernel: isa0: on isab0 Jan 30 07:51:56 core kernel: atapci0: port= 0x1f0-0x1f7=2C0x3f6=2C0x170-0x177=2C0x376=2C0xff90-0xff9f=2C0xffa0-0xffaf = at device 31.2 on pci0 Jan 30 07:51:56 core kernel: ata0: at channel 0 on atapci0 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 14 (ISA IRQ 14) to lap= ic 0 vector 69 Jan 30 07:51:56 core kernel: ata1: at channel 1 on atapci0 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 15 (ISA IRQ 15) to lap= ic 0 vector 70 Jan 30 07:51:56 core kernel: pci0: at device 31.3 (no= driver attached) Jan 30 07:51:56 core kernel: atapci1: port= 0x9880-0x9887=2C0x9800-0x9803=2C0x9480-0x9487=2C0x9400-0x9403=2C0x9080-0x9= 08f=2C0x9000-0x900f irq 19 at device 31.5 on pci0 Jan 30 07:51:56 core kernel: ata2: at channel 0 on atapci1 Jan 30 07:51:56 core kernel: ata3: at channel 1 on atapci1 Jan 30 07:51:56 core kernel: acpi_button0: on acpi0 Jan 30 07:51:56 core kernel: attimer0: port 0x40-0x43 irq 0 on a= cpi0 Jan 30 07:51:56 core kernel: Timecounter "i8254" frequency 1193182 Hz quali= ty 0 Jan 30 07:51:56 core kernel: Event timer "i8254" frequency 1193182 Hz quali= ty 100 Jan 30 07:51:56 core kernel: atrtc0: port 0x70-0x71 irq= 8 on acpi0 Jan 30 07:51:56 core kernel: atrtc0: registered as a time-of-day clock (res= olution 1000000us=2C adjustment 0.500000000s) Jan 30 07:51:56 core kernel: ioapic0: routing intpin 8 (ISA IRQ 8) to lapic= 0 vector 72 Jan 30 07:51:56 core kernel: Event timer "RTC" frequency 32768 Hz quality 0 Jan 30 07:51:56 core kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff = irq 4 flags 0x10 on acpi0 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 4 (ISA IRQ 4) to lapic= 0 vector 73 Jan 30 07:51:56 core kernel: uart0: fast interrupt Jan 30 07:51:56 core kernel: uart0: console (9600=2Cn=2C8=2C1) Jan 30 07:51:56 core kernel: hpet0: iomem 0xfe= d00000-0xfed003ff on acpi0 Jan 30 07:51:56 core kernel: hpet0: vendor 0x8086=2C rev 0x1=2C 14318180Hz = 64bit=2C 4 timers=2C legacy route Jan 30 07:51:56 core kernel: hpet0: t0: irqs 0x00f00000 (0)=2C 64bit=2C pe= riodic Jan 30 07:51:56 core kernel: hpet0: t1: irqs 0x00f00000 (0) Jan 30 07:51:56 core kernel: hpet0: t2: irqs 0x00f00800 (0) Jan 30 07:51:56 core kernel: hpet0: t2: irqs 0x00f00800 (0) Jan 30 07:51:56 core kernel: hpet0: t3: irqs 0x00f01000 (0) Jan 30 07:51:56 core kernel: Timecounter "HPET" frequency 14318180 Hz quali= ty 950 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 20 (PCI IRQ 20) to lap= ic 0 vector 74 Jan 30 07:51:56 core kernel: Event timer "HPET" frequency 14318180 Hz quali= ty 450 Jan 30 07:51:56 core kernel: Event timer "HPET1" frequency 14318180 Hz qual= ity 440 Jan 30 07:51:56 core kernel: Event timer "HPET2" frequency 14318180 Hz qual= ity 440 Jan 30 07:51:56 core kernel: Event timer "HPET3" frequency 14318180 Hz qual= ity 440 Jan 30 07:51:56 core kernel: acpi0: wakeup code va 0xffffff8110e1f000 pa 0x= 4000 Jan 30 07:51:56 core kernel: isab0: found ICH9 or equivalent chipset: Intel= ICH9M-E watchdog timer Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa0000-0xa07ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa0800-0xa0fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa1000-0xa17ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa2000-0xa27ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa2800-0xa2fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa3000-0xa37ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa3800-0xa3fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa4000-0xa47ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa4800-0xa4fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa5000-0xa57ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa5800-0xa5fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa6000-0xa67ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa6800-0xa6fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa7000-0xa77ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa7800-0xa7fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa8000-0xa87ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa8800-0xa8fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa9000-0xa97ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa9800-0xa9fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xaa000-0xaa7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xaa800-0xaafff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xab000-0xab7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xab800-0xabfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xac000-0xac7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xac800-0xacfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xad800-0xadfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xae000-0xae7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xae800-0xaefff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xaf000-0xaf7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xaf800-0xaffff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb0000-0xb07ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb0800-0xb0fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb1000-0xb17ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb1800-0xb1fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb2000-0xb27ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb2800-0xb2fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb3000-0xb37ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb3800-0xb3fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb4000-0xb47ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb4800-0xb4fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb5000-0xb57ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb5800-0xb5fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb6000-0xb67ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb6800-0xb6fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb7000-0xb77ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb7800-0xb7fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb8000-0xb87ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb9000-0xb97ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xb9800-0xb9fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xba000-0xba7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xba800-0xbafff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbb000-0xbb7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbb800-0xbbfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbc000-0xbc7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbc800-0xbcfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbd000-0xbd7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbd800-0xbdfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbe000-0xbe7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbe800-0xbefff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbf000-0xbf7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xbf800-0xbffff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd0000-0xd07ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd0800-0xd0fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd1000-0xd17ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd1800-0xd1fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd2000-0xd27ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd2800-0xd2fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd3000-0xd37ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd3800-0xd3fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd4800-0xd4fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd5000-0xd57ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd5800-0xd5fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd6000-0xd67ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd6800-0xd6fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd7000-0xd77ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd7800-0xd7fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd8000-0xd87ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd8800-0xd8fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd9000-0xd97ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xd9800-0xd9fff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xda000-0xda7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xda800-0xdafff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xdb000-0xdb7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xdb800-0xdbfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xdc000-0xdc7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xdc800-0xdcfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xdd000-0xdd7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xdd800-0xddfff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xde000-0xde7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xde800-0xdefff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xdf000-0xdf7ff) for = rid 0 of orm0 Jan 30 07:51:56 core kernel: isa_probe_children: disabling PnP devices Jan 30 07:51:56 core kernel: ichwd0: on isa0 Jan 30 07:51:56 core kernel: isab0: found ICH9 or equivalent chipset: Intel= ICH9M-E watchdog timer Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x830-0x837) for rid = 0 of ichwd0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x860-0x87f) for rid = 1 of ichwd0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xfed1f410-0xfed1f413= ) for rid 0 of isab0 Jan 30 07:51:56 core kernel: ichwd0: Intel ICH9M-E watchdog timer (ICH9 or = equivalent) Jan 30 07:51:56 core kernel: ichwd0: timer disabled Jan 30 07:51:56 core kernel: atrtc: atrtc0 already exists=3B skipping it Jan 30 07:51:56 core kernel: sc: sc0 already exists=3B skipping it Jan 30 07:51:56 core kernel: uart: uart0 already exists=3B skipping it Jan 30 07:51:56 core kernel: isa_probe_children: probing non-PnP devices Jan 30 07:51:56 core kernel: sc0: at flags 0x100 on isa0 Jan 30 07:51:56 core kernel: sc0: VGA <16 virtual consoles=2C flags=3D0x300= > Jan 30 07:51:56 core kernel: sc0: fb0=2C kbd0=2C terminal emulator: scteken= (teken terminal) Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x3c0-0x3df) for rid = 0 of vga0 Jan 30 07:51:56 core kernel: pcib0: allocated type 3 (0xa0000-0xbffff) for = rid 0 of vga0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x60-0x60) for rid 0 = of atkbdc0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x64-0x64) for rid 1 = of atkbdc0 Jan 30 07:51:56 core kernel: atkbdc0: at port= 0x60=2C0x64 on isa0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x60-0x60) for rid 0 = of atkbdc0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x64-0x64) for rid 1 = of atkbdc0 Jan 30 07:51:56 core kernel: atkbd0: irq 1 on atkbdc0 Jan 30 07:51:56 core kernel: kbd0 at atkbd0 Jan 30 07:51:56 core kernel: kbd0: atkbd0=2C generic (0)=2C config:0x0=2C f= lags:0x3f0000 Jan 30 07:51:56 core kernel: ioapic0: routing intpin 1 (ISA IRQ 1) to lapic= 0 vector 75 Jan 30 07:51:56 core kernel: atkbd0: [GIANT-LOCKED] Jan 30 07:51:56 core kernel: ppc0 failed to probe at irq 7 on isa0 Jan 30 07:51:56 core kernel: pcib0: allocated type 4 (0x2f8-0x2ff) for rid = 0 of uart1 Jan 30 07:51:56 core kernel: uart1: failed to probe at port 0x2f8-= 0x2ff irq 3 on isa0 Jan 30 07:51:56 core kernel: isa_probe_children: probing PnP devices Jan 30 07:51:56 core kernel: coretemp0: on cpu= 0 Jan 30 07:51:56 core kernel: coretemp0: Setting TjMax=3D105 Jan 30 07:51:56 core kernel: est0: o= n cpu0 Jan 30 07:51:56 core kernel: p4tcc0: on cpu= 0 Jan 30 07:51:56 core kernel: coretemp1: on cpu= 1 Jan 30 07:51:56 core kernel: coretemp1: Setting TjMax=3D105 Jan 30 07:51:56 core kernel: est1: o= n cpu1 Jan 30 07:51:56 core kernel: p4tcc1: on cpu= 1 Jan 30 07:51:56 core kernel: Device configuration finished. Jan 30 07:51:56 core kernel: procfs registered Jan 30 07:51:56 core kernel: Timecounters tick every 1.000 msec Jan 30 07:51:56 core kernel: vlan: initialized=2C using hash tables with ch= aining Jan 30 07:51:56 core kernel: pflog0: bpf attached Jan 30 07:51:56 core kernel: lo0: bpf attached Jan 30 07:51:56 core kernel: usbus0: 12Mbps Full Speed USB v1.0 Jan 30 07:51:56 core kernel: usbus1: 480Mbps High Speed USB v2.0 Jan 30 07:51:56 core kernel: ugen0.1: at usbus0 Jan 30 07:51:56 core kernel: uhub0: on usbus0 Jan 30 07:51:56 core kernel: ugen1.1: at usbus1 Jan 30 07:51:56 core kernel: uhub1: on usbus1 Jan 30 07:51:56 core kernel: usbus2: 12Mbps Full Speed USB v1.0 Jan 30 07:51:56 core kernel: usbus3: 12Mbps Full Speed USB v1.0 Jan 30 07:51:56 core kernel: ugen2.1: at usbus2 Jan 30 07:51:56 core kernel: uhub2: on usbus2 Jan 30 07:51:56 core kernel: ugen3.1: at usbus3 Jan 30 07:51:56 core kernel: uhub3: on usbus3 Jan 30 07:51:56 core kernel: usbus4: 12Mbps Full Speed USB v1.0 Jan 30 07:51:56 core kernel: usbus5: 480Mbps High Speed USB v2.0 Jan 30 07:51:56 core kernel: ugen4.1: at usbus4 Jan 30 07:51:56 core kernel: uhub4: on usbus4 Jan 30 07:51:56 core kernel: ugen5.1: at usbus5 Jan 30 07:51:56 core kernel: uhub4: on usbus4 Jan 30 07:51:56 core kernel: ugen5.1: at usbus5 00=2C addr 1> on usbus5 Jan 30 07:51:56 core kernel: uhub0: 2 ports with 2 removable=2C self powere= d Jan 30 07:51:56 core kernel: ata0: SATA reset: ports status=3D0x01 Jan 30 07:51:56 core kernel: ata0: p0: SATA connect time=3D0ms status=3D000= 00123 Jan 30 07:51:56 core kernel: ata0: reset tp1 mask=3D01 ostat0=3D50 ostat1= =3D00 Jan 30 07:51:56 core kernel: ata0: stat0=3D0x50 err=3D0x01 lsb=3D0x00 msb= =3D0x00 Jan 30 07:51:56 core kernel: ata0: reset tp2 stat0=3D50 stat1=3D00 devices= =3D0x1 Jan 30 07:51:56 core kernel: (aprobe0:ata0:0:0:0): SIGNATURE: 0000 Jan 30 07:51:56 core kernel: uhub2: 2 ports with 2 removable=2C self powere= d Jan 30 07:51:56 core kernel: ata1: SATA reset: ports status=3D0x00 Jan 30 07:51:56 core kernel: ata1: p0: SATA connect timeout status=3D000000= 00 Jan 30 07:51:56 core kernel: uhub3: 2 ports with 2 removable=2C self powere= d Jan 30 07:51:56 core kernel: uhub1: 2 ports with 2 removable=2C self powere= d Jan 30 07:51:56 core kernel: uhub4: 2 ports with 2 removable=2C self powere= d Jan 30 07:51:56 core kernel: ata2: SATA reset: ports status=3D0x00 Jan 30 07:51:56 core kernel: ata2: p0: SATA connect timeout status=3D000000= 00 Jan 30 07:51:56 core kernel: uhub5: 6 ports with 6 removable=2C self powere= d Jan 30 07:51:56 core kernel: ata3: SATA reset: ports status=3D0x00 Jan 30 07:51:56 core kernel: ata3: p0: SATA connect timeout status=3D000000= 00 Jan 30 07:51:56 core kernel: ada0 at ata0 bus 0 scbus0 target 0 lun 0 Jan 30 07:51:56 core kernel: GEOM: new disk ada0 Jan 30 07:51:56 core kernel: ada0: ATA-7 SATA 2.x d= evice Jan 30 07:51:56 core kernel: ada0: Serial Number C1M8H6PW47SRNQNR5UW8 Jan 30 07:51:56 core kernel: ada0: 300.000MB/s transfers (SATA 2.x=2C UDMA5= =2C PIO 8192bytes) Jan 30 07:51:56 core kernel: ada0: 30533MB (62533296 512 byte sectors: 16H = 63S/T 16383C) Jan 30 07:51:56 core kernel: ada0: Previously was known as ad0 Jan 30 07:51:56 core kernel: pass0 at ata0 bus 0 scbus0 target 0 lun 0 Jan 30 07:51:56 core kernel: pass0: ATA-7 SATA 2.x = device Jan 30 07:51:56 core kernel: pass0: Serial Number C1M8H6PW47SRNQNR5UW8 Jan 30 07:51:56 core kernel: pass0: 300.000MB/s transfers (SATA 2.x=2C UDMA= 5=2C PIO 8192bytes) Jan 30 07:51:56 core kernel: SMP: AP CPU #1 Launched! Jan 30 07:51:56 core kernel: cpu1 AP: Jan 30 07:51:56 core kernel: ID: 0x01000000 VER: 0x00050014 LDR: 0x000000= 00 DFR: 0xffffffff Jan 30 07:51:56 core kernel: lint0: 0x00010700 lint1: 0x00000400 TPR: 0x000= 00000 SVR: 0x000001ff Jan 30 07:51:56 core kernel: timer: 0x000100ef therm: 0x00010000 err: 0x000= 000f0 pmc: 0x00010400 Jan 30 07:51:56 core kernel: SMP: passed TSC synchronization test Jan 30 07:51:56 core kernel: TSC timecounter discards lower 7 bit(s) Jan 30 07:51:56 core kernel: Timecounter "TSC-low" frequency 9375190 Hz qua= lity 1000 Jan 30 07:51:56 core kernel: Trying to mount root from ufs:/dev/ada0s1a [ro= =2Cnoatime]... Jan 30 07:51:56 core kernel: start_init: trying /sbin/init Jan 30 07:51:56 core kernel: bridge0: bpf attached Jan 30 07:51:56 core kernel: bridge0: Ethernet address: 02:81:f4:ec:68:00 Jan 30 07:51:57 core kernel: ichwd0: timer enabled Jan 30 07:51:57 core kernel: ichwd0: timeout set to 28 ticks Jan 30 07:51:57 core kernel: ichwd0: timer reloaded Jan 30 07:52:13 core last message repeated 17 times Jan 30 07:52:13 core login: ROOT LOGIN (root) ON ttyu0 Jan 30 07:52:14 core kernel: ichwd0: timer reloaded Date: Mon=2C 30 Jan 2012 16:51:08 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Hi=2C On 30 January 2012 16:36=2C Shant Kassardjian wrote: Dear FreeBSD-Wireless team=2C I'd like to inform the dev teams that I just upgraded my system from 8.2-st= able to 9.0-stable using CVSUP and my wireless card SR71-A (AR9160) is no l= onger being detected. If I roll back to the old kernel=2C everything is wor= king great. Here is my kernel config for wireless: and changed AR5416_DEFAULT_TXCHAINMASK from 1 to 7 after compiling the 9.0 kernel=2C pciconf returns the following undetected = devices: none2@pci0:1:15:0: class=3D0x028000 card=3D0x40820777 chip=3D0x0027168= c rev=3D0x01 hdr=3D0x00 vendor =3D 'Atheros Communications Inc.' device =3D 'AR9160 802.11abgn Wireless PCI Adapter' class =3D network Can you please boot verbosely (eg type "boot -v" at the loader prompt=2C or= select the relevant option) and post the entire boot log? I test frqeuently with AR9160's and I've had zero issues=2C both on MIPS an= d i386. It's quite likely it's a cardbus/pci resource allocation issue. Adrian = From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 01:51:06 2012 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 2AD36106564A for ; Tue, 31 Jan 2012 01:51:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id D697B8FC14 for ; Tue, 31 Jan 2012 01:51:05 +0000 (UTC) Received: by vcmm1 with SMTP id m1so5123955vcm.13 for ; Mon, 30 Jan 2012 17:51:05 -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; bh=yVlnzh18piSPF6bs3Rfi+/RnznCzGzsN9291jPflJm4=; b=c+zhKYUZ+fYVfqNyx+84NfIkXsfdt1SLUooqgOA6sJVxosIQkkKWNB71hnIV9ehFxZ sc1KbKzY4/tBJxMcL7Erd4BvNeqlSg2kSqTOTEju5Y7kjzvd5rcTE+kjgygcWJIsb7xE RzUeUqk4ghCuliqii1srbk7KjPvDIobhN1+88= MIME-Version: 1.0 Received: by 10.220.156.201 with SMTP id y9mr11934345vcw.22.1327974665254; Mon, 30 Jan 2012 17:51:05 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Mon, 30 Jan 2012 17:51:05 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 17:51:05 -0800 X-Google-Sender-Auth: NV7IzmedlVWX1a80CoNiA2Qy4Hs Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 01:51:06 -0000 Hi, Try including the ath_pci device in your kernel config file. Sorry about that! :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 02:03:38 2012 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 D42C11065670; Tue, 31 Jan 2012 02:03:38 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s8.snt0.hotmail.com (snt0-omc4-s8.snt0.hotmail.com [65.55.90.211]) by mx1.freebsd.org (Postfix) with ESMTP id A45168FC0C; Tue, 31 Jan 2012 02:03:38 +0000 (UTC) Received: from SNT128-W9 ([65.55.90.200]) by snt0-omc4-s8.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 18:03:37 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Mon, 30 Jan 2012 21:03:37 -0500 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 31 Jan 2012 02:03:37.0925 (UTC) FILETIME=[8BCD8750:01CCDFBC] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 02:03:38 -0000 Hi Adrian=2C I can't believe I forgot to include that! weird that it was working without= it in 8.2! I added back: options ATH_ENABLE_11N and device ath_pci and r= ecompiling! :) btw=2C do you know if AR9160 can support multiple SSIDs in hostap mode? Exa= mple=2C I would like to create one 802.11a SSID network and another 802.11n= or 802.11g network... Shant K. Date: Mon=2C 30 Jan 2012 17:51:05 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Hi=2C Try including the ath_pci device in your kernel config file. Sorry about that! :) Adrian = From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 02:12:41 2012 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 2595C106566B for ; Tue, 31 Jan 2012 02:12:41 +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 D00238FC08 for ; Tue, 31 Jan 2012 02:12:40 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so5156206vbb.13 for ; Mon, 30 Jan 2012 18:12:40 -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; bh=Uenn2gJuuy7vALQ1ZUU+GDL13iDWDHGTvdgG38dku94=; b=Xq7Nvco9GkArWMvYfQzp0t8UOXaCwtu21c7qSXLIA9MnNLc5wEmgmH33s5T43THCJw LlAakP2yX12/DjfNXgh212aoHgWXJLzTroztbOW9CQ5tIX48gHPiDS8jUSloYxngh3EQ Z9piNj6S/AmZg4IqocRofYfT0U0uDSh6cqsBo= MIME-Version: 1.0 Received: by 10.52.26.199 with SMTP id n7mr10385171vdg.17.1327975960304; Mon, 30 Jan 2012 18:12:40 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Mon, 30 Jan 2012 18:12:40 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 18:12:40 -0800 X-Google-Sender-Auth: NRqHRacKorI-T-hjnN8DJO45neY Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 02:12:41 -0000 Yes, it will support that. Please note - 802.11n TX is not gonig to work in 9.0 - you have to disable ampdutx. Adrian On 30 January 2012 18:03, Shant Kassardjian wrote: > Hi Adrian, > > > I can't believe I forgot to include that! weird that it was working > without it in 8.2! > > > > I added back: options ATH_ENABLE_11N and device ath_pci and recompiling! > :) > > > btw, do you know if AR9160 can support multiple SSIDs in hostap mode? > Example, I would like to create one 802.11a SSID network and another > 802.11n or 802.11g network... > > > Shant K. > > > ------------------------------ > Date: Mon, 30 Jan 2012 17:51:05 -0800 > > Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 > From: adrian@freebsd.org > To: shant@skylab.ca > CC: freebsd-wireless@freebsd.org > > Hi, > > Try including the ath_pci device in your kernel config file. > > Sorry about that! :) > > > Adrian > > From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 02:17:04 2012 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 9B883106564A; Tue, 31 Jan 2012 02:17:04 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s17.snt0.hotmail.com (snt0-omc4-s17.snt0.hotmail.com [65.55.90.220]) by mx1.freebsd.org (Postfix) with ESMTP id 6B97B8FC17; Tue, 31 Jan 2012 02:17:04 +0000 (UTC) Received: from SNT128-W14 ([65.55.90.199]) by snt0-omc4-s17.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 18:17:03 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Mon, 30 Jan 2012 21:17:03 -0500 Importance: Normal In-Reply-To: References: , , , MIME-Version: 1.0 X-OriginalArrivalTime: 31 Jan 2012 02:17:03.0935 (UTC) FILETIME=[6C38E4F0:01CCDFBE] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 02:17:04 -0000 I can not find any documentation on how to disable ampdutx=2C is it a comma= nd or a patch that I need to apply? I would be willing to test out. Date: Mon=2C 30 Jan 2012 18:12:40 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Yes=2C it will support that. Please note - 802.11n TX is not gonig to work in 9.0 - you have to disable = ampdutx. Adrian On 30 January 2012 18:03=2C Shant Kassardjian wrote: Hi Adrian=2C I can't believe I forgot to include that! weird that it was working without= it in 8.2! I added back: options ATH_ENABLE_11N and device ath_pci and r= ecompiling! :) btw=2C do you know if AR9160 can support multiple SSIDs in hostap mode? Exa= mple=2C I would like to create one 802.11a SSID network and another 802.11n= or 802.11g network... Shant K. Date: Mon=2C 30 Jan 2012 17:51:05 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Hi=2C Try including the ath_pci device in your kernel config file. Sorry about that! :) Adrian =20 = From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 02:19:51 2012 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 DB8F6106566C for ; Tue, 31 Jan 2012 02:19:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8E59B8FC08 for ; Tue, 31 Jan 2012 02:19:51 +0000 (UTC) Received: by vcmm1 with SMTP id m1so6238vcm.13 for ; Mon, 30 Jan 2012 18:19:50 -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; bh=EBWvPWAh0WPAA08PvUA9kIuwo/Rer7fM/nl4smZubWE=; b=Ho01md9tojTbkEzAzDkUp+SU2v4n9vArD7CBhYFz+Ur3Pj/iJg752d8AfAbUpTNpoB ak2hnSa7L7qzXC+Ue/izWWjkIfoxUwo7++7qTuCCd0iQZQ8V5+6LIAYEVXLSNnm3xJQd whFsiZG/zqKY1JSUF9qyiiLLoplZv5Gf3qcYU= MIME-Version: 1.0 Received: by 10.220.156.199 with SMTP id y7mr8473643vcw.2.1327976390794; Mon, 30 Jan 2012 18:19:50 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Mon, 30 Jan 2012 18:19:50 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 18:19:50 -0800 X-Google-Sender-Auth: HLI9NjUseuME7-qOFJL2Vmbcwko Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 02:19:51 -0000 ifconfig wlanX -ampdutx Adrian On 30 January 2012 18:17, Shant Kassardjian wrote: > I can not find any documentation on how to disable ampdutx, is it a > command or a patch that I need to apply? I would be willing to test out. > > ------------------------------ > Date: Mon, 30 Jan 2012 18:12:40 -0800 > > Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 > From: adrian@freebsd.org > To: shant@skylab.ca > CC: freebsd-wireless@freebsd.org > > Yes, it will support that. > > Please note - 802.11n TX is not gonig to work in 9.0 - you have to disable > ampdutx. > > Adrian > > On 30 January 2012 18:03, Shant Kassardjian wrote: > > Hi Adrian, > > > I can't believe I forgot to include that! weird that it was working > without it in 8.2! > > > > I added back: options ATH_ENABLE_11N and device ath_pci and recompiling! > :) > > > btw, do you know if AR9160 can support multiple SSIDs in hostap mode? > Example, I would like to create one 802.11a SSID network and another > 802.11n or 802.11g network... > > > Shant K. > > > ------------------------------ > Date: Mon, 30 Jan 2012 17:51:05 -0800 > > Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 > From: adrian@freebsd.org > To: shant@skylab.ca > CC: freebsd-wireless@freebsd.org > > Hi, > > Try including the ath_pci device in your kernel config file. > > Sorry about that! :) > > > Adrian > > > From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 02:22:30 2012 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 174F3106566C; Tue, 31 Jan 2012 02:22:30 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s7.snt0.hotmail.com (snt0-omc4-s7.snt0.hotmail.com [65.55.90.210]) by mx1.freebsd.org (Postfix) with ESMTP id DA8AF8FC19; Tue, 31 Jan 2012 02:22:29 +0000 (UTC) Received: from SNT128-W41 ([65.55.90.201]) by snt0-omc4-s7.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 18:22:29 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Mon, 30 Jan 2012 21:22:29 -0500 Importance: Normal In-Reply-To: References: , , , , , MIME-Version: 1.0 X-OriginalArrivalTime: 31 Jan 2012 02:22:29.0184 (UTC) FILETIME=[2E15F400:01CCDFBF] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 02:22:30 -0000 thanks Adrian! You're the man btw! Best regards=2C Shant K. Date: Mon=2C 30 Jan 2012 18:19:50 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org ifconfig wlanX -ampdutx Adrian On 30 January 2012 18:17=2C Shant Kassardjian wrote: I can not find any documentation on how to disable ampdutx=2C is it a comma= nd or a patch that I need to apply? I would be willing to test out. Date: Mon=2C 30 Jan 2012 18:12:40 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Yes=2C it will support that. Please note - 802.11n TX is not gonig to work in 9.0 - you have to disable = ampdutx. Adrian On 30 January 2012 18:03=2C Shant Kassardjian wrote: Hi Adrian=2C I can't believe I forgot to include that! weird that it was working without= it in 8.2! I added back: options ATH_ENABLE_11N and device ath_pci and r= ecompiling! :) btw=2C do you know if AR9160 can support multiple SSIDs in hostap mode? Exa= mple=2C I would like to create one 802.11a SSID network and another 802.11n= or 802.11g network... Shant K. Date: Mon=2C 30 Jan 2012 17:51:05 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Hi=2C Try including the ath_pci device in your kernel config file. Sorry about that! :) Adrian =20 =20 = From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 02:28:44 2012 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 4A6DA106566C; Tue, 31 Jan 2012 02:28:44 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s48.snt0.hotmail.com (snt0-omc4-s48.snt0.hotmail.com [65.54.51.99]) by mx1.freebsd.org (Postfix) with ESMTP id 18E148FC17; Tue, 31 Jan 2012 02:28:43 +0000 (UTC) Received: from SNT128-W62 ([65.55.90.199]) by snt0-omc4-s48.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 18:28:43 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Mon, 30 Jan 2012 21:28:43 -0500 Importance: Normal In-Reply-To: References: , , , , , MIME-Version: 1.0 X-OriginalArrivalTime: 31 Jan 2012 02:28:43.0260 (UTC) FILETIME=[0D0D6BC0:01CCDFC0] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 02:28:44 -0000 Just to make sure I got everything right: ifconfig_wlan0=3D"inet 172.25.2.1 netmask 255.255.255.224 ssid test mode 11= na channel 64:ht/40 txpower 5 -ampdutx mac:allow" does this look right to you? I would like to run 802.11n only @ 5ghz frequencies... Date: Mon=2C 30 Jan 2012 18:19:50 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org ifconfig wlanX -ampdutx Adrian On 30 January 2012 18:17=2C Shant Kassardjian wrote: I can not find any documentation on how to disable ampdutx=2C is it a comma= nd or a patch that I need to apply? I would be willing to test out. Date: Mon=2C 30 Jan 2012 18:12:40 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Yes=2C it will support that. Please note - 802.11n TX is not gonig to work in 9.0 - you have to disable = ampdutx. Adrian On 30 January 2012 18:03=2C Shant Kassardjian wrote: Hi Adrian=2C I can't believe I forgot to include that! weird that it was working without= it in 8.2! I added back: options ATH_ENABLE_11N and device ath_pci and r= ecompiling! :) btw=2C do you know if AR9160 can support multiple SSIDs in hostap mode? Exa= mple=2C I would like to create one 802.11a SSID network and another 802.11n= or 802.11g network... Shant K. Date: Mon=2C 30 Jan 2012 17:51:05 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Hi=2C Try including the ath_pci device in your kernel config file. Sorry about that! :) Adrian =20 =20 = From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 03:14:02 2012 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 A1E671065673 for ; Tue, 31 Jan 2012 03:14:02 +0000 (UTC) (envelope-from ironfall_blindguardian@hotmail.com) Received: from bay0-omc1-s20.bay0.hotmail.com (bay0-omc1-s20.bay0.hotmail.com [65.54.190.31]) by mx1.freebsd.org (Postfix) with ESMTP id 87FCE8FC13 for ; Tue, 31 Jan 2012 03:14:02 +0000 (UTC) Received: from BAY169-W26 ([65.54.190.61]) by bay0-omc1-s20.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 30 Jan 2012 19:14:02 -0800 Message-ID: X-Originating-IP: [177.33.230.210] From: Luan Hospodarsky To: Date: Tue, 31 Jan 2012 01:14:01 -0200 Importance: Normal In-Reply-To: References: , , , , , MIME-Version: 1.0 X-OriginalArrivalTime: 31 Jan 2012 03:14:02.0055 (UTC) FILETIME=[61949D70:01CCDFC6] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: Realtek 8188ce driver X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 03:14:02 -0000 Hello Kevin=2C I understood almost everything you said=2C only one more question: This patch that was updated to HEAD=2C how do I do to get it? Is it include= d in the ndis port/package? Write the driver I think is almost impossible for me=2C I am not engineer= =2C only programmer. So I guess it is hard to deal with the hardware. Anyway=2C thanks for the attention and if anyone in anywhere find (or make)= any solution for it I will be very grateful. I will try to find some old drivers from realtek to this device and test. I= f everything get wrong I'll buy another...Not from Realtek. Luan. > Date: Mon=2C 30 Jan 2012 17:07:20 -0800 > Subject: Re: Realtek 8188ce driver > From: kob6558@gmail.com > To: ironfall_blindguardian@hotmail.com > CC: freebsd-wireless@freebsd.org >=20 > On Mon=2C Jan 30=2C 2012 at 2:30 PM=2C Luan Hospodarsky > wrote: > > > > Hi=2C > > I already tried ndis and the module it generated did not work. > > But I don't know anything about a ndis patch=2C can you tell me more ab= out it? > > Replace the device is still an alternative=2C but I want to avoid it th= e max possible. > > I have never written a driver=2C but I could try. Do you have anything = to share that can help me give the first steps writing a driver? > > Thanks. > > > >> Date: Mon=2C 30 Jan 2012 13:54:05 -0800 > >> Subject: Re: Realtek 8188ce driver > >> From: kob6558@gmail.com > >> To: ironfall_blindguardian@hotmail.com > >> CC: freebsd-wireless@freebsd.org > >> > >> On Mon=2C Jan 30=2C 2012 at 1:41 PM=2C Luan Hospodarsky > >> wrote: > >> > > >> > Hi Adrian=2C > >> > Thanks for the reply=2C > >> > > >> > So is there some work about it? > >> > It is great! If you find anything=2C let me know! > >> > Thanks again. > >> > > >> > Date: Sun=2C 29 Jan 2012 17:00:43 -0800 > >> > Subject: Re: Realtek 8188ce driver > >> > From: adrian@freebsd.org > >> > To: ironfall_blindguardian@hotmail.com > >> > CC: freebsd-wireless@freebsd.org > >> > > >> > Hi=2C > >> > > >> > I think there's been some recent work to get this chipset support in= to shape but I don't know wehre it lives or whether the driver is in a work= able setup. > >> > > >> > Does anyone know anything further? > >> > > >> > > >> > > >> > Adrian > >> > > >> > On 29 January 2012 13:24=2C LuX - I like you wrote: > >> > > >> > > >> > > >> > Hello=2C I'm Luan and I'm a newer FreeBSD Lover. > >> > > >> > I am having a problem and I have found no answer anywhere=2C but I h= ope you can give me a light. > >> > > >> > My notebook has an integrated wireless card (Realtek 8188ce) and the= Realtek site provides drivers only for Windows and Linux. > >> > > >> > I had read the FreeBSD manual=2C asked for help in the forum and in = the IRC ##freebsd=2C but unfortunately nobody could help me. > >> > > >> > My conclusion is that such driver does not exist in FreeBSD. > >> > > >> > Is there any projects to port such driver from Linux (I guess OpenBS= D has that driver as well=2C so the porting could be less painful) or some = compatible driver to this device? > >> > > >> > Thanks in advance. > >> > > >> > --- > >> > > >> > Luan Hospodarsky > >> > > >> > ___________________________= ____________________ > >> > >> 1. You could try ndis. It did not work for me=2C but a patch to ndis > >> looks like it may have fixed the problem. > >> > >> 2. The other option is to replace the card. What brand of laptop is > >> it? Levovo locks down the wireless and will not boot with any card but > >> one they sold. I believe HP does the same. I had to buy a card with > >> the Lenovo PCI ID to get it to work. I found it from a place that was > >> in Germany=2C but the card was shipped from Tel Aviv. It cost about = 3 > >> times what a generic Intel Centrino Advanced-N 6205 would have cost. > >> :-( > >> > >> You might be able to re-write the PCI ID on a standard Intel card=2C b= ut > >> I could not figure out how to do it. You can also patch the BIOS=2C bu= t > >> that make future BIOS upgrades a real problem. > >> > >> 3. Write a driver > >> -- >=20 > If the documentation for the interface is available=2C it's not too > hard=2C but from what I've seen=2C wireless is one of the trickier ones. > While I hope someone gets around to writing one=2C even with the Linux > driver to work from=2C I don't think I'd want to try it. It's been years > since I last wrote a driver and it was not on FreeBSD=2C so I am not the > best source of an opinion. >=20 > Sorry ndis failed. It cause my system to panic when it loaded the > module=2C but a patch to NDIS to fix either my problems or something > very similar was committed to HEAD several months ago and should be in > 9.0 and maybe even 8.2. Sounds unlikely to fix the problem. >=20 > If you don't have a Lenovo or HP=2C swapping is easy and supported > half-height mini-PCIe cards are in the 20-25 USD range from multiple > vendors. I know it's annoying to have to do it=2C but it is probably the > only way you will get wireless on that system in even reasonably soon. > --=20 > R. Kevin Oberman=2C Network Engineer > E-mail: kob6558@gmail.com = From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 04:15:16 2012 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 44641106566C; Tue, 31 Jan 2012 04:15:16 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 0E9C18FC0C; Tue, 31 Jan 2012 04:15:15 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q0V4FFX7012627; Mon, 30 Jan 2012 20:15:15 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q0V4FFDw012626; Mon, 30 Jan 2012 20:15:15 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Adrian Chadd Message-Id: <1327983314.12621@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 In-Reply-To: Date: Mon, 30 Jan 2012 20:15:15 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1327983315" Cc: FreeBSD Wireless Subject: Re: AR9280 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 04:15:16 -0000 This is a multi-part message in MIME format. --bound1327983315 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adrian Chadd wrote .. > Just drop me line and we can try to pick a time to meet up and hack on > wireless stuff. > > (The offer is open to anyone else, btw.) > > > Adrian Cool looking forward to it. I'll have to brush up, it's been a few years since my hardware addiction. :) -- Waitman Gobble San Jose California USA --bound1327983315-- From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 04:48:54 2012 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 9BF74106564A for ; Tue, 31 Jan 2012 04:48:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 24FA58FC08 for ; Tue, 31 Jan 2012 04:48:53 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so5297746wgb.31 for ; Mon, 30 Jan 2012 20:48:53 -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; bh=rTQzKdn42FEnaetAwvwGDRrOEw8MGJeMYBPVTRi6myk=; b=beX4hzZXoPOKpiZVih7ei/0pA661dFjmCzwwQ9Zzc2Q+5jOZOrXypIez4smW5GpMmv lvWbbA+74zQosuhW+SwMP4LNmxz1tB0/AxHEHmlLyluR1kxbCaAgZk0LLAIhzm3YHCGp oSBPaakspbXst/JrIWAp4Ac+P0Rx4tw0vc27g= MIME-Version: 1.0 Received: by 10.180.95.131 with SMTP id dk3mr1159939wib.6.1327985332985; Mon, 30 Jan 2012 20:48:52 -0800 (PST) Received: by 10.223.101.196 with HTTP; Mon, 30 Jan 2012 20:48:52 -0800 (PST) In-Reply-To: References: Date: Mon, 30 Jan 2012 20:48:52 -0800 Message-ID: From: Kevin Oberman To: Luan Hospodarsky Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: Realtek 8188ce driver X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 04:48:54 -0000 On Mon, Jan 30, 2012 at 7:14 PM, Luan Hospodarsky wrote: > > Hello Kevin, > I understood almost everything you said, only one more question: > > This patch that was updated to HEAD, how do I do to get it? Is it included in the ndis port/package? > Write the driver I think is almost impossible for me, I am not engineer, only programmer. So I guess it is hard to deal with the hardware. > Anyway, thanks for the attention and if anyone in anywhere find (or make) any solution for it I will be very grateful. > I will try to find some old drivers from realtek to this device and test. If everything get wrong I'll buy another...Not from Realtek. ndis is part of the base FreeBSD, not a port. If you run 9.0, 9-stable or 8-stable, it's part of the OS. The patch was to fix a potential panic, so unless te ndis module was crashing your system, it's not going to help. It is quite possible that getting the latest ndis sources for the main version of FreeBSD you are running from cvs or svn, but version mis-match in the kernel could cause it to fail either to compile or work. This a a rather new device from Realtek. I don't think that there are any "old" drivers. We have lots of drivers for wired Realtek drivers in FreeBSD, but no wireless drivers that I am aware of. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 22:34:18 2012 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 8903D1065674 for ; Tue, 31 Jan 2012 22:34:18 +0000 (UTC) (envelope-from reed@reedmedia.net) Received: from c-0500.emailmediator.com (c-0500.emailmediator.com [64.85.162.118]) by mx1.freebsd.org (Postfix) with ESMTP id 59CA68FC18 for ; Tue, 31 Jan 2012 22:34:18 +0000 (UTC) Received: from pool-71-164-190-204.dllstx.fios.verizon.net ([71.164.190.204] helo=reedmedia.net) by c-0500.emailmediator.com with esmtpa (Exim 4.69) (envelope-from ) id 1RsLrl-0004SN-Dc for freebsd-wireless@freebsd.org; Tue, 31 Jan 2012 17:07:53 -0500 Received: from reed@reedmedia.net by reedmedia.net with local (mailout 0.17) id 28558-1328047674; Tue, 31 Jan 2012 16:07:54 -0600 Date: Tue, 31 Jan 2012 16:07:53 -0600 (CST) From: "Jeremy C. Reed" X-X-Sender: reed@t1.m.reedmedia.net To: freebsd-wireless@freebsd.org Message-ID: User-Agent: Alpine 2.01 (NEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 22:34:18 -0000 Anyone using the following? iwn0: mem 0xf0600000-0xf0601fff irq 17 at device 0.0 on pci2 iwn0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 257 to local APIC 0 vector 51 iwn0: using IRQ 257 for MSI iwn0: MIMO 1T2R, BGN, address ac:72:89:ec:3b:1e iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 1T2R iwn0: 11ng MCS 20MHz iwn0: MCS 0-7: 6.5Mbps - 65Mbps iwn0: 11ng MCS 20MHz SGI iwn0: MCS 0-7: 7Mbps - 72Mbps iwn0: 11ng MCS 40MHz: iwn0: MCS 0-7: 13.5Mbps - 135Mbps iwn0: 11ng MCS 40MHz SGI: iwn0: MCS 0-7: 15Mbps - 150Mbps ... wlan: <802.11 Link Layer> ... wlan0: bpf attached wlan0: bpf attached wlan0: Ethernet address: ac:72:89:ec:3b:1e firmware: 'iwn6000g2bfw' version 0: 460912 bytes loaded at 0xffffffff816120b0 ubt0: on usbus2 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() I am using FreeBSD 9.0-RELEASE on amd64. ifconfig shows the interfaces: iwn0: flags=8843 metric 0 mtu 2290 ether ac:72:89:ec:3b:1e nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether ac:72:89:ec:3b:1e inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11g status: associated ssid 5FYA8 channel 11 (2462 MHz 11g) bssid 00:18:01:e0:8a:57 country US authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpower 11 bmiss 10 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme roaming MANUAL The installer did see other networks to when scanning. But the installer and after the install never gets any address when using dhclient. It just does its DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 .... and then No DHCPOFFERS received. I am not sure if is a wireless issue or a dhcp issue. Running wpa_supplicant with debugging shows it is associated too: work1# wpa_supplicant -i wlan0 -dddd -c /etc/wpa_supplicant.conf Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant.conf' ctrl_interface='/var/run/wpa_supplicant' eapol_version=2 ap_scan=1 fast_reauth=1 Line: 6 - start of a new network block ssid - hexdump_ascii(len=5): 35 46 59 41 38 5FYA8 key_mgmt: 0x4 wep_key0 - hexdump(len=10): [REMOVED] wep_tx_keyidx=0 (0x0) priority=5 (0x5) Line: 13 - start of a new network block priority=5 (0x5) key_mgmt: 0x4 Priority group 5 id=0 ssid='5FYA8' id=1 ssid='' Own MAC address: ac:72:89:ec:3b:1e wpa_driver_bsd_del_key: keyidx=0 wpa_driver_bsd_del_key: keyidx=1 wpa_driver_bsd_del_key: keyidx=2 wpa_driver_bsd_del_key: keyidx=3 wpa_driver_bsd_set_countermeasures: enabled=0 RSN: flushing PMKID list in the driver Setting scan request: 0 sec 100000 usec EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: Supplicant port status: Unauthorized EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: Supplicant port status: Unauthorized EAPOL: Supplicant port status: Unauthorized Using existing control interface directory. Added interface wlan0 State: DISCONNECTED -> SCANNING Starting AP scan for wildcard SSID Received 472 bytes of scan results (5 BSSes) BSS: Start scan result update 1 BSS: Add new id 0 BSSID 00:18:01:e0:8a:57 SSID '5FYA8' BSS: Add new id 1 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Add new id 2 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Add new id 3 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' BSS: Add new id 4 BSSID 00:1f:90:ea:5e:d4 SSID 'QKJQ1' New scan results available Selecting BSS from priority group 5 Try to find WPA-enabled AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 skip - no WPA/RSN IE 1: e8:39:df:d8:92:2b ssid='3CSHT' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:1f:90:e2:aa:61 ssid='stix' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 3: e8:39:df:f8:a3:50 ssid='3GQH7' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 4: 00:1f:90:ea:5e:d4 ssid='QKJQ1' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE Try to find non-WPA AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 selected non-WPA AP 00:18:01:e0:8a:57 ssid='5FYA8' Trying to associate with 00:18:01:e0:8a:57 (SSID='5FYA8' freq=2462 MHz) Cancelling scan request WPA: clearing own WPA/RSN IE Automatic auth_alg selection: 0x1 WPA: clearing AP WPA IE WPA: clearing AP RSN IE WPA: clearing own WPA/RSN IE No keys have been configured - skip key clearing wpa_driver_bsd_set_key: alg=WEP addr=ff:ff:ff:ff:ff:ff key_idx=0 set_tx=1 seq_len=0 key_len=10 State: SCANNING -> ASSOCIATING wpa_driver_bsd_associate: ssid '5FYA8' wpa ie len 0 pairwise 4 group 4 key mgmt 2 wpa_driver_bsd_set_drop_unencrypted: enabled=1 wpa_driver_bsd_set_auth_alg alg 0x1 authmode 1 wpa_driver_bsd_associate: set PRIVACY 1 Setting authentication timeout: 10 sec 0 usec EAPOL: External notification - EAP success=0 EAPOL: Supplicant port status: Unauthorized EAPOL: External notification - EAP fail=0 EAPOL: Supplicant port status: Unauthorized EAPOL: External notification - portControl=ForceAuthorized EAPOL: Supplicant port status: Unauthorized State: ASSOCIATING -> ASSOCIATED Associated to a new BSS: BSSID=00:18:01:e0:8a:57 Associated with 00:18:01:e0:8a:57 WPA: Association event - clear replay counter WPA: Clear old PTK EAPOL: External notification - portEnabled=0 EAPOL: Supplicant port status: Unauthorized EAPOL: External notification - portValid=0 EAPOL: Supplicant port status: Unauthorized EAPOL: External notification - portEnabled=1 EAPOL: SUPP_PAE entering state S_FORCE_AUTH EAPOL: Supplicant port status: Authorized EAPOL: SUPP_BE entering state IDLE Cancelling authentication timeout State: ASSOCIATED -> COMPLETED CTRL-EVENT-CONNECTED - Connection to 00:18:01:e0:8a:57 completed (auth) [id=0 id_str=] Cancelling scan request EAPOL: disable timer tick BSS: Expire BSS 1 due to age BSS: Remove id 1 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Expire BSS 2 due to age BSS: Remove id 2 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Expire BSS 3 due to age BSS: Remove id 3 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' BSS: Expire BSS 4 due to age BSS: Remove id 4 BSSID 00:1f:90:ea:5e:d4 SSID 'QKJQ1' Received 472 bytes of scan results (5 BSSes) BSS: Start scan result update 2 BSS: Add new id 5 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Add new id 6 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Add new id 7 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' BSS: Add new id 8 BSSID 00:1f:90:ea:5e:d4 SSID 'QKJQ1' New scan results available Selecting BSS from priority group 5 Try to find WPA-enabled AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 skip - no WPA/RSN IE 1: e8:39:df:d8:92:2b ssid='3CSHT' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:1f:90:e2:aa:61 ssid='stix' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 3: e8:39:df:f8:a3:50 ssid='3GQH7' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 4: 00:1f:90:ea:5e:d4 ssid='QKJQ1' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE Try to find non-WPA AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 selected non-WPA AP 00:18:01:e0:8a:57 ssid='5FYA8' Considering within-ESS reassociation Current BSS: 00:18:01:e0:8a:57 level=0 Selected BSS: 00:18:01:e0:8a:57 level=0 Skip roam - too small difference in signal level ^[[5~    BSS: Expire BSS 5 due to age BSS: Remove id 5 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Expire BSS 6 due to age BSS: Remove id 6 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Expire BSS 7 due to age BSS: Remove id 7 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' BSS: Expire BSS 8 due to age BSS: Remove id 8 BSSID 00:1f:90:ea:5e:d4 SSID 'QKJQ1' Received 472 bytes of scan results (5 BSSes) BSS: Start scan result update 3 BSS: Add new id 9 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Add new id 10 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Add new id 11 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' BSS: Add new id 12 BSSID 00:1f:90:ea:5e:d4 SSID 'QKJQ1' New scan results available Selecting BSS from priority group 5 Try to find WPA-enabled AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 skip - no WPA/RSN IE 1: e8:39:df:d8:92:2b ssid='3CSHT' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:1f:90:e2:aa:61 ssid='stix' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 3: e8:39:df:f8:a3:50 ssid='3GQH7' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 4: 00:1f:90:ea:5e:d4 ssid='QKJQ1' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE Try to find non-WPA AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 selected non-WPA AP 00:18:01:e0:8a:57 ssid='5FYA8' Considering within-ESS reassociation Current BSS: 00:18:01:e0:8a:57 level=0 Selected BSS: 00:18:01:e0:8a:57 level=0 Skip roam - too small difference in signal level BSS: Expire BSS 9 due to age BSS: Remove id 9 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Expire BSS 10 due to age BSS: Remove id 10 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Expire BSS 11 due to age BSS: Remove id 11 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' BSS: Expire BSS 12 due to age BSS: Remove id 12 BSSID 00:1f:90:ea:5e:d4 SSID 'QKJQ1' Received 468 bytes of scan results (5 BSSes) BSS: Start scan result update 4 BSS: Add new id 13 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Add new id 14 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Add new id 15 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' BSS: Add new id 16 BSSID 00:1f:90:ea:5e:d4 SSID 'QKJQ1' New scan results available Selecting BSS from priority group 5 Try to find WPA-enabled AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 skip - no WPA/RSN IE 1: e8:39:df:d8:92:2b ssid='3CSHT' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:1f:90:e2:aa:61 ssid='stix' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 3: e8:39:df:f8:a3:50 ssid='3GQH7' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 4: 00:1f:90:ea:5e:d4 ssid='QKJQ1' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE Try to find non-WPA AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 selected non-WPA AP 00:18:01:e0:8a:57 ssid='5FYA8' Considering within-ESS reassociation Current BSS: 00:18:01:e0:8a:57 level=0 Selected BSS: 00:18:01:e0:8a:57 level=0 Skip roam - too small difference in signal level BSS: Expire BSS 13 due to age BSS: Remove id 13 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Expire BSS 14 due to age BSS: Remove id 14 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Expire BSS 15 due to age BSS: Remove id 15 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' BSS: Expire BSS 16 due to age BSS: Remove id 16 BSSID 00:1f:90:ea:5e:d4 SSID 'QKJQ1' Received 356 bytes of scan results (4 BSSes) BSS: Start scan result update 5 BSS: Add new id 17 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Add new id 18 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Add new id 19 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' New scan results available Selecting BSS from priority group 5 Try to find WPA-enabled AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 skip - no WPA/RSN IE 1: e8:39:df:d8:92:2b ssid='3CSHT' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:1f:90:e2:aa:61 ssid='stix' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 3: e8:39:df:f8:a3:50 ssid='3GQH7' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE Try to find non-WPA AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 selected non-WPA AP 00:18:01:e0:8a:57 ssid='5FYA8' Considering within-ESS reassociation Current BSS: 00:18:01:e0:8a:57 level=0 Selected BSS: 00:18:01:e0:8a:57 level=0 Skip roam - too small difference in signal level BSS: Expire BSS 17 due to age BSS: Remove id 17 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Expire BSS 18 due to age BSS: Remove id 18 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Expire BSS 19 due to age BSS: Remove id 19 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' Received 356 bytes of scan results (4 BSSes) BSS: Start scan result update 6 BSS: Add new id 20 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Add new id 21 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Add new id 22 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' New scan results available Selecting BSS from priority group 5 Try to find WPA-enabled AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 skip - no WPA/RSN IE 1: e8:39:df:d8:92:2b ssid='3CSHT' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:1f:90:e2:aa:61 ssid='stix' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 3: e8:39:df:f8:a3:50 ssid='3GQH7' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE Try to find non-WPA AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 selected non-WPA AP 00:18:01:e0:8a:57 ssid='5FYA8' Considering within-ESS reassociation Current BSS: 00:18:01:e0:8a:57 level=0 Selected BSS: 00:18:01:e0:8a:57 level=0 Skip roam - too small difference in signal level BSS: Expire BSS 20 due to age BSS: Remove id 20 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Expire BSS 21 due to age BSS: Remove id 21 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Expire BSS 22 due to age BSS: Remove id 22 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' Received 348 bytes of scan results (4 BSSes) BSS: Start scan result update 7 BSS: Add new id 23 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Add new id 24 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Add new id 25 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' New scan results available Selecting BSS from priority group 5 Try to find WPA-enabled AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 skip - no WPA/RSN IE 1: e8:39:df:d8:92:2b ssid='3CSHT' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:1f:90:e2:aa:61 ssid='stix' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 3: e8:39:df:f8:a3:50 ssid='3GQH7' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE Try to find non-WPA AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 selected non-WPA AP 00:18:01:e0:8a:57 ssid='5FYA8' Considering within-ESS reassociation Current BSS: 00:18:01:e0:8a:57 level=0 Selected BSS: 00:18:01:e0:8a:57 level=0 Skip roam - too small difference in signal level BSS: Expire BSS 23 due to age BSS: Remove id 23 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Expire BSS 24 due to age BSS: Remove id 24 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Expire BSS 25 due to age BSS: Remove id 25 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' Received 360 bytes of scan results (4 BSSes) BSS: Start scan result update 8 BSS: Add new id 26 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Add new id 27 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Add new id 28 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' New scan results available Selecting BSS from priority group 5 Try to find WPA-enabled AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 skip - no WPA/RSN IE 1: e8:39:df:d8:92:2b ssid='3CSHT' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 2: 00:1f:90:e2:aa:61 ssid='stix' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE 3: e8:39:df:f8:a3:50 ssid='3GQH7' wpa_ie_len=0 rsn_ie_len=0 caps=0x31 skip - no WPA/RSN IE Try to find non-WPA AP 0: 00:18:01:e0:8a:57 ssid='5FYA8' wpa_ie_len=0 rsn_ie_len=0 caps=0x11 selected non-WPA AP 00:18:01:e0:8a:57 ssid='5FYA8' Considering within-ESS reassociation Current BSS: 00:18:01:e0:8a:57 level=0 Selected BSS: 00:18:01:e0:8a:57 level=0 Skip roam - too small difference in signal level RTM_IFINFO: Interface 'wlan0' DOWN Configured interface was removed. State: COMPLETED -> DISCONNECTED EAPOL: External notification - portEnabled=0 EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: Supplicant port status: Unauthorized EAPOL: SUPP_BE entering state INITIALIZE EAPOL: Supplicant port status: Unauthorized EAPOL: External notification - portValid=0 EAPOL: Supplicant port status: Unauthorized Removing interface wlan0 wpa_driver_bsd_del_key: keyidx=0 wpa_driver_bsd_del_key: keyidx=1 wpa_driver_bsd_del_key: keyidx=2 wpa_driver_bsd_del_key: keyidx=3 State: DISCONNECTED -> DISCONNECTED EAPOL: External notification - portEnabled=0 EAPOL: Supplicant port status: Unauthorized EAPOL: External notification - portValid=0 EAPOL: Supplicant port status: Unauthorized wpa_driver_bsd_set_countermeasures: enabled=0 No keys have been configured - skip key clearing BSS: Remove id 0 BSSID 00:18:01:e0:8a:57 SSID '5FYA8' BSS: Remove id 26 BSSID e8:39:df:d8:92:2b SSID '3CSHT' BSS: Remove id 27 BSSID 00:1f:90:e2:aa:61 SSID 'stix' BSS: Remove id 28 BSSID e8:39:df:f8:a3:50 SSID '3GQH7' Cancelling scan request Cancelling authentication timeout wpa_driver_bsd_set_wpa_internal: wpa=0 privacy=0 ioctl[SIOCS80211, op 26, arg 0x0]: Operation not supported ELOOP: remaining socket: sock=4 eloop_data=0x80180f300 user_data=0x80185f080 handler=0x4250d0 (Those last few lines were probably when I killed it.) FWIW: it works fine with some LinuxMint 12 my son had on a live flash disk. Any ideas? Jeremy C. Reed p.s. The wpa_supplicant man page doesn't document the default options as ran via rc. From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 31 22:41:08 2012 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 1AF79106566C for ; Tue, 31 Jan 2012 22:41:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id C69D38FC08 for ; Tue, 31 Jan 2012 22:41:07 +0000 (UTC) Received: by vcmm1 with SMTP id m1so698485vcm.13 for ; Tue, 31 Jan 2012 14:41:07 -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; bh=al/2bIBbYIL7oJs6JYGXG45PxOhqZ6O3oYXgGN6TZCY=; b=cV7zJNjNKQZZRuJapsGyfnDdRs9gg0tVje6g/ral8oshiXgA4GoBeN8qHTVj16MSgq 2N+0nI9iulC25cg99jDj76jCxaKweuTG7MRpQOSS04Yto7RcYTfhy1qJUpKtoz/dYiNn SN9Ob4i4PHlAMuvyn3KONDT5Gzyi1IZmhwHx4= MIME-Version: 1.0 Received: by 10.220.156.199 with SMTP id y7mr11398540vcw.2.1328049667293; Tue, 31 Jan 2012 14:41:07 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Tue, 31 Jan 2012 14:41:07 -0800 (PST) In-Reply-To: References: Date: Tue, 31 Jan 2012 14:41:07 -0800 X-Google-Sender-Auth: 0RR4fk69PprA-8LLb_9jn6DwxDA Message-ID: From: Adrian Chadd To: "Jeremy C. Reed" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 22:41:08 -0000 Hi, try it with an open AP for now, see if it can exchange data fine? I'm not really going to be more helpful than that on the intel NICs I'm afraid :( Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:01:00 2012 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 30B3F106566B; Wed, 1 Feb 2012 02:01:00 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s41.snt0.hotmail.com (snt0-omc4-s41.snt0.hotmail.com [65.54.51.92]) by mx1.freebsd.org (Postfix) with ESMTP id 0271E8FC1C; Wed, 1 Feb 2012 02:00:59 +0000 (UTC) Received: from SNT128-W49 ([65.55.90.199]) by snt0-omc4-s41.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 31 Jan 2012 18:00:59 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Tue, 31 Jan 2012 21:00:58 -0500 Importance: Normal In-Reply-To: References: , , , , , , MIME-Version: 1.0 X-OriginalArrivalTime: 01 Feb 2012 02:00:59.0005 (UTC) FILETIME=[577E02D0:01CCE085] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:01:00 -0000 Hi Adrian=2C After recompiling the kernel with device ath_pci=2C atheros got redetected= =2C however 802.11n seems to not be working with the following errors: ifconfig wlan0 destroy ifconfig wlan0 create wlandev ath0 wlanmode hostap wlan0: Ethernet address: 00:15:6d:84:70:d5 core# ath0: unable to reset hardware=3B hal status 14 =20 core# ifconfig wlan0 channel 6:ht/40 = =20 ifconfig: SIOCS80211: Invalid argument core# ifconfig wlan0 172.25.2.1 ssid test mode 11n channel 6:ht/40 -ampdutx= ~ ifconfig: SIOCS80211: Invalid argument core# ath0: stuck beacon=3B resetting (bmiss count 4) I tried adding the following in /etc/rc.conf: wlans_ath0=3D"wlan0" create_args_wlan0=3D"wlanmode hostap" ifconfig_wlan0=3D"inet 172.25.2.1 netmask 255.255.255.224 ssid test mode 11= na channel 6:ht/40 txpower 5 -ampdutx mac:allow" ifconfig shows the following=2C still can't force it to do N. wlan0: flags=3D8843 metric = 0 mtu 1500 ether 00:15:6d:84:70:d5 nd6 options=3D1 media: IEEE 802.11 Wireless Ethernet autoselect mode 11na status: running ssid test channel 52 (5260 MHz 11a ht/40+) bssid 00:15:6d:84:70:d5 country US ecm authmode OPEN privacy OFF txpower 23 mcastrate 6 mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 -dfs here is my dmesg for atheros: ath0: mem 0xfe6f0000-0xfe6fffff irq 19 at device 15.0 on pci= 1 ath0: [HT] enabling HT modes ath0: [HT] 2 RX streams=3B 2 TX streams ath0: AR9160 mac 64.0 RF5133 phy 11.0 wlan0: flags=3D8843 metric = 0 mtu 1500 ether 00:15:6d:84:70:d5 nd6 options=3D1 media: IEEE 802.11 Wireless Ethernet autoselect (autoselec= t ) status: no carrier ssid test channel 161 (5805 MHz 11a) country US ecm authmode OPEN privacy OFF txpower 30 mcastrate 6 mgmtrate 6 scanvalid 60 wme burst dtimperiod 1 -dfs core# ifconfig wlan0 inet 172.25.2.1 netmask 255.255.255.248 mode 11n ssid = test channel 6:ht/40 ifconfig: SIOCSIFMEDIA (media): Device not configured core# ath0: stuck beacon=3B resetting (bmiss count 4) = ~ ath0: stuck beacon=3B resetting (bmiss count 0) If you need more information just let me know=2C I'd be glad to help out. Regards=2C Shant K. From: shant@skylab.ca To: adrian@freebsd.org CC: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 Date: Mon=2C 30 Jan 2012 21:28:43 -0500 Just to make sure I got everything right: ifconfig_wlan0=3D"inet 172.25.2.1 netmask 255.255.255.224 ssid test mode 11= na channel 64:ht/40 txpower 5 -ampdutx mac:allow" does this look right to you? I would like to run 802.11n only @ 5ghz frequencies... Date: Mon=2C 30 Jan 2012 18:19:50 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org ifconfig wlanX -ampdutx Adrian On 30 January 2012 18:17=2C Shant Kassardjian wrote: I can not find any documentation on how to disable ampdutx=2C is it a comma= nd or a patch that I need to apply? I would be willing to test out. Date: Mon=2C 30 Jan 2012 18:12:40 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Yes=2C it will support that. Please note - 802.11n TX is not gonig to work in 9.0 - you have to disable = ampdutx. Adrian On 30 January 2012 18:03=2C Shant Kassardjian wrote: Hi Adrian=2C I can't believe I forgot to include that! weird that it was working without= it in 8.2! I added back: options ATH_ENABLE_11N and device ath_pci and r= ecompiling! :) btw=2C do you know if AR9160 can support multiple SSIDs in hostap mode? Exa= mple=2C I would like to create one 802.11a SSID network and another 802.11n= or 802.11g network... Shant K. Date: Mon=2C 30 Jan 2012 17:51:05 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Hi=2C Try including the ath_pci device in your kernel config file. Sorry about that! :) Adrian =20 =20 = From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:06:40 2012 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 9E348106566C for ; Wed, 1 Feb 2012 02:06:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 50BA28FC0A for ; Wed, 1 Feb 2012 02:06:40 +0000 (UTC) Received: by vcmm1 with SMTP id m1so882146vcm.13 for ; Tue, 31 Jan 2012 18:06:39 -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; bh=DT2ZR7UjWvOnDhHKw87xdN05FhSRXoi0o1gesmQga1o=; b=dELezU6Hz6DQ017xcNedYKGfiKeY1ynQwscwGrfEY85WF0e2X8IuG+lkjwkmEV9ypP 9Y9JeOzyI8LeIJT7+J5Qh8cRtwKc7gsGOuktMZAJJLolen429KoXib6H845B8i/e+le/ /GlZjJIYF0qPk9qrnOaG5w/Tt8fc3ELRD26Yo= MIME-Version: 1.0 Received: by 10.220.156.201 with SMTP id y9mr15207156vcw.22.1328061999785; Tue, 31 Jan 2012 18:06:39 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Tue, 31 Jan 2012 18:06:39 -0800 (PST) In-Reply-To: References: Date: Tue, 31 Jan 2012 18:06:39 -0800 X-Google-Sender-Auth: ufKLB30f8RB0oVj3pNV7aUfDh-4 Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:06:40 -0000 On 31 January 2012 18:00, Shant Kassardjian wrote: > Hi Adrian, > > > After recompiling the kernel with device ath_pci, atheros got redetected, > however 802.11n seems to not be working with the following errors: > > > ifconfig wlan0 destroy > ifconfig wlan0 create wlandev ath0 wlanmode hostap > wlan0: Ethernet address: 00:15:6d:84:70:d5 > core# ath0: unable to reset hardware; hal status 14 > .. that's worrying. That's HAL_ESELFTEST, if that fails, bad juju. This same thing works on 8.x, right? Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:14:19 2012 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 C8A621065674; Wed, 1 Feb 2012 02:14:19 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s24.snt0.hotmail.com (snt0-omc4-s24.snt0.hotmail.com [65.55.90.227]) by mx1.freebsd.org (Postfix) with ESMTP id 9B0D68FC12; Wed, 1 Feb 2012 02:14:19 +0000 (UTC) Received: from SNT128-W19 ([65.55.90.201]) by snt0-omc4-s24.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 31 Jan 2012 18:14:18 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Tue, 31 Jan 2012 21:14:18 -0500 Importance: Normal In-Reply-To: References: , , , , , , , , MIME-Version: 1.0 X-OriginalArrivalTime: 01 Feb 2012 02:14:18.0888 (UTC) FILETIME=[34427880:01CCE087] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:14:20 -0000 Yes=2C in 8.x it worked perfectly fine. I just restarted the machine and "ath0: unable to reset hardware=3B hal sta= tus 14 " error is gone but still can't enable N. core# ifconfig wlan0 channel 6:ht/40 = =20 ifconfig: SIOCS80211: Invalid argument Date: Tue=2C 31 Jan 2012 18:06:39 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org On 31 January 2012 18:00=2C Shant Kassardjian wrote: Hi Adrian=2C After recompiling the kernel with device ath_pci=2C atheros got redetected= =2C however 802.11n seems to not be working with the following errors: ifconfig wlan0 destroy ifconfig wlan0 create wlandev ath0 wlanmode hostap wlan0: Ethernet address: 00:15:6d:84:70:d5 core# ath0: unable to reset hardware=3B hal status 14 =20 .. that's worrying. That's HAL_ESELFTEST=2C if that fails=2C bad juju. This same thing works on 8.x=2C right? Adrian = From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:14:45 2012 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 5721B106566C for ; Wed, 1 Feb 2012 02:14:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0AACF8FC08 for ; Wed, 1 Feb 2012 02:14:44 +0000 (UTC) Received: by vcmm1 with SMTP id m1so889495vcm.13 for ; Tue, 31 Jan 2012 18:14:44 -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; bh=AsvL9S2LzqaF6L00U01bqZKQuWrBsJWdODwuOAgmKUU=; b=ALaL4sx//PZE8egN3/hei684RH1TIZiuZKdV/PqOk5GrahIaqYcF1W3YIpBo0eiaSr fRc+XerYwAvM7irdX9vSCgZRmdbWTbYTrIVG/CrbYcKT3Z70kDIHVI6mfUnELgCGFCme OzQTBcmAJ29S8PuOLruB++PCqBZd1T66sm4U0= MIME-Version: 1.0 Received: by 10.220.140.196 with SMTP id j4mr15146406vcu.12.1328062484558; Tue, 31 Jan 2012 18:14:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Tue, 31 Jan 2012 18:14:44 -0800 (PST) In-Reply-To: References: Date: Tue, 31 Jan 2012 18:14:44 -0800 X-Google-Sender-Auth: rYAMnJ7t1ka1XX1mjK5aeoq10GM Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:14:45 -0000 Do ifconfig -v wlan0 list channel Adrian On 31 January 2012 18:14, Shant Kassardjian wrote: > Yes, in 8.x it worked perfectly fine. > > > I just restarted the machine and "ath0: unable to reset hardware; hal > status 14 " error is gone but still can't enable N. > > > > core# ifconfig wlan0 channel 6:ht/40 > ifconfig: SIOCS80211: Invalid argument > > > > > > > ------------------------------ > Date: Tue, 31 Jan 2012 18:06:39 -0800 > > Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 > From: adrian@freebsd.org > To: shant@skylab.ca > CC: freebsd-wireless@freebsd.org > > > > On 31 January 2012 18:00, Shant Kassardjian wrote: > > Hi Adrian, > > > After recompiling the kernel with device ath_pci, atheros got redetected, > however 802.11n seems to not be working with the following errors: > > > ifconfig wlan0 destroy > ifconfig wlan0 create wlandev ath0 wlanmode hostap > wlan0: Ethernet address: 00:15:6d:84:70:d5 > core# ath0: unable to reset hardware; hal status 14 > > > .. that's worrying. That's HAL_ESELFTEST, if that fails, bad juju. > > This same thing works on 8.x, right? > > > > Adrian > > From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:18:22 2012 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 A011F1065670; Wed, 1 Feb 2012 02:18:22 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s5.snt0.hotmail.com (snt0-omc4-s5.snt0.hotmail.com [65.55.90.208]) by mx1.freebsd.org (Postfix) with ESMTP id 7236E8FC1D; Wed, 1 Feb 2012 02:18:22 +0000 (UTC) Received: from SNT128-W26 ([65.55.90.200]) by snt0-omc4-s5.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 31 Jan 2012 18:18:21 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Tue, 31 Jan 2012 21:18:21 -0500 Importance: Normal In-Reply-To: References: , , , , , , , , , , MIME-Version: 1.0 X-OriginalArrivalTime: 01 Feb 2012 02:18:21.0662 (UTC) FILETIME=[C4F6D7E0:01CCE087] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:18:22 -0000 Here's what it outputs=2C no N support? I double checked and I compiled wit= h options ATH_ENABLE_11N # 802.11N support.... core# ifconfig -v wlan0 list channel = ~ Channel 1 : 2412 MHz 11b Channel 11 : 2462 MHz 11b Channel 1 : 2412 MHz 11g Channel 11 : 2462 MHz 11g Channel 1 : 2412 MHz 11g ht/20 Channel 11 : 2462 MHz 11g ht= /20 Channel 1 : 2412 MHz 11g ht/40+ Channel 11 : 2462 MHz 11g ht= /40- Channel 2 : 2417 MHz 11b Channel 36 : 5180 MHz 11a Channel 2 : 2417 MHz 11g Channel 36 : 5180 MHz 11a ht= /20 Channel 2 : 2417 MHz 11g ht/20 Channel 36 : 5180 MHz 11a ht= /40+ Channel 2 : 2417 MHz 11g ht/40+ Channel 40 : 5200 MHz 11a Channel 3 : 2422 MHz 11b Channel 40 : 5200 MHz 11a ht= /20 Channel 3 : 2422 MHz 11g Channel 40 : 5200 MHz 11a ht= /40- Channel 3 : 2422 MHz 11g ht/20 Channel 44 : 5220 MHz 11a Channel 3 : 2422 MHz 11g ht/40+ Channel 44 : 5220 MHz 11a ht= /20 Channel 4 : 2427 MHz 11b Channel 44 : 5220 MHz 11a ht= /40+ Channel 4 : 2427 MHz 11g Channel 48 : 5240 MHz 11a Channel 4 : 2427 MHz 11g ht/20 Channel 48 : 5240 MHz 11a ht= /20 Channel 4 : 2427 MHz 11g ht/40+ Channel 48 : 5240 MHz 11a ht= /40- Channel 5 : 2432 MHz 11b Channel 52 : 5260 MHz 11a Channel 5 : 2432 MHz 11g Channel 52 : 5260 MHz 11a ht= /20 Channel 5 : 2432 MHz 11g ht/20 Channel 52 : 5260 MHz 11a ht= /40+ Channel 5 : 2432 MHz 11g ht/40+ Channel 56 : 5280 MHz 11a Channel 5 : 2432 MHz 11g ht/40- Channel 56 : 5280 MHz 11a ht= /20 Channel 6 : 2437 MHz 11b Channel 56 : 5280 MHz 11a ht= /40- Channel 6 : 2437 MHz 11g Channel 60 : 5300 MHz 11a Channel 6 : 2437 MHz 11g ht/20 Channel 60 : 5300 MHz 11a ht= /20 Channel 6 : 2437 MHz 11g ht/40+ Channel 60 : 5300 MHz 11a ht= /40+ Channel 6 : 2437 MHz 11g ht/40- Channel 64 : 5320 MHz 11a Channel 7 : 2442 MHz 11b Channel 64 : 5320 MHz 11a ht= /20 Channel 7 : 2442 MHz 11g Channel 64 : 5320 MHz 11a ht= /40- Channel 7 : 2442 MHz 11g ht/20 Channel 149 : 5745 MHz 11a Channel 7 : 2442 MHz 11g ht/40+ Channel 149 : 5745 MHz 11a ht= /20 Channel 7 : 2442 MHz 11g ht/40- Channel 149 : 5745 MHz 11a ht= /40+ Channel 8 : 2447 MHz 11b Channel 153 : 5765 MHz 11a Channel 8 : 2447 MHz 11g Channel 153 : 5765 MHz 11a ht= /20 Channel 8 : 2447 MHz 11g ht/20 Channel 153 : 5765 MHz 11a ht= /40- Channel 8 : 2447 MHz 11g ht/40- Channel 157 : 5785 MHz 11a Channel 9 : 2452 MHz 11b Channel 157 : 5785 MHz 11a ht= /20 Channel 9 : 2452 MHz 11g Channel 157 : 5785 MHz 11a ht= /40+ Channel 9 : 2452 MHz 11g ht/20 Channel 161 : 5805 MHz 11a Channel 9 : 2452 MHz 11g ht/40- Channel 161 : 5805 MHz 11a ht= /20 Channel 10 : 2457 MHz 11b Channel 161 : 5805 MHz 11a ht= /40- Channel 10 : 2457 MHz 11g Channel 165 : 5825 MHz 11a Channel 10 : 2457 MHz 11g ht/20 Channel 165 : 5825 MHz 11a ht= /20 Channel 10 : 2457 MHz 11g ht/40- Date: Tue=2C 31 Jan 2012 18:14:44 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Do ifconfig -v wlan0 list channel Adrian On 31 January 2012 18:14=2C Shant Kassardjian wrote: Yes=2C in 8.x it worked perfectly fine. I just restarted the machine and "ath0: unable to reset hardware=3B hal sta= tus 14 " error is gone but still can't enable N. core# ifconfig wlan0 channel 6:ht/40 = =20 ifconfig: SIOCS80211: Invalid argument Date: Tue=2C 31 Jan 2012 18:06:39 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org On 31 January 2012 18:00=2C Shant Kassardjian wrote: Hi Adrian=2C After recompiling the kernel with device ath_pci=2C atheros got redetected= =2C however 802.11n seems to not be working with the following errors: ifconfig wlan0 destroy ifconfig wlan0 create wlandev ath0 wlanmode hostap wlan0: Ethernet address: 00:15:6d:84:70:d5 core# ath0: unable to reset hardware=3B hal status 14 =20 .. that's worrying. That's HAL_ESELFTEST=2C if that fails=2C bad juju. This same thing works on 8.x=2C right? Adrian =20 = From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:19:39 2012 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 27876106566C for ; Wed, 1 Feb 2012 02:19:39 +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 C5C808FC0A for ; Wed, 1 Feb 2012 02:19:38 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so855293vbb.13 for ; Tue, 31 Jan 2012 18:19:38 -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; bh=tcIWXoVaTdp+vGuLAraGJrK1f/imQjwNYDzKSGtoZi0=; b=L9KJmdt3SBupOvalhVEWez7hN5VkmosiTNVkqIiTRn7+n8gCSy8Yd0A4jMY6Vj1UfL Bdc/viveKAnMmT5wMbRPykWD1WV9/ylg0VeQL4vbpjSkPbQ+KjTWAjaq5alzKuQSJxHN Q56HLlNiffygzeaglXkas4dQBRlOxHXLPDG0A= MIME-Version: 1.0 Received: by 10.52.26.206 with SMTP id n14mr13098514vdg.51.1328062777991; Tue, 31 Jan 2012 18:19:37 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Tue, 31 Jan 2012 18:19:37 -0800 (PST) In-Reply-To: References: Date: Tue, 31 Jan 2012 18:19:37 -0800 X-Google-Sender-Auth: ckOf7ic2e3KbxQOSIRYTS3_qNCo Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:19:39 -0000 .. that looks fine. Just try: ifconfig wlan0 channel 6:ht/40 Adrian On 31 January 2012 18:18, Shant Kassardjian wrote: > Here's what it outputs, no N support? I double checked and I compiled > with options ATH_ENABLE_11N # 802.11N support.... > > > > > > core# ifconfig -v wlan0 list channel ~ > Channel 1 : 2412 MHz 11b Channel 11 : 2462 MHz 11b > Channel 1 : 2412 MHz 11g Channel 11 : 2462 MHz 11g > Channel 1 : 2412 MHz 11g ht/20 Channel 11 : 2462 MHz 11g ht/20 > Channel 1 : 2412 MHz 11g ht/40+ Channel 11 : 2462 MHz 11g ht/40- > Channel 2 : 2417 MHz 11b Channel 36 : 5180 MHz 11a > Channel 2 : 2417 MHz 11g Channel 36 : 5180 MHz 11a ht/20 > Channel 2 : 2417 MHz 11g ht/20 Channel 36 : 5180 MHz 11a ht/40+ > Channel 2 : 2417 MHz 11g ht/40+ Channel 40 : 5200 MHz 11a > Channel 3 : 2422 MHz 11b Channel 40 : 5200 MHz 11a ht/20 > Channel 3 : 2422 MHz 11g Channel 40 : 5200 MHz 11a ht/40- > Channel 3 : 2422 MHz 11g ht/20 Channel 44 : 5220 MHz 11a > Channel 3 : 2422 MHz 11g ht/40+ Channel 44 : 5220 MHz 11a ht/20 > Channel 4 : 2427 MHz 11b Channel 44 : 5220 MHz 11a ht/40+ > Channel 4 : 2427 MHz 11g Channel 48 : 5240 MHz 11a > Channel 4 : 2427 MHz 11g ht/20 Channel 48 : 5240 MHz 11a ht/20 > Channel 4 : 2427 MHz 11g ht/40+ Channel 48 : 5240 MHz 11a ht/40- > Channel 5 : 2432 MHz 11b Channel 52 : 5260 MHz 11a > Channel 5 : 2432 MHz 11g Channel 52 : 5260 MHz 11a ht/20 > Channel 5 : 2432 MHz 11g ht/20 Channel 52 : 5260 MHz 11a ht/40+ > Channel 5 : 2432 MHz 11g ht/40+ Channel 56 : 5280 MHz 11a > Channel 5 : 2432 MHz 11g ht/40- Channel 56 : 5280 MHz 11a ht/20 > Channel 6 : 2437 MHz 11b Channel 56 : 5280 MHz 11a ht/40- > Channel 6 : 2437 MHz 11g Channel 60 : 5300 MHz 11a > Channel 6 : 2437 MHz 11g ht/20 Channel 60 : 5300 MHz 11a ht/20 > Channel 6 : 2437 MHz 11g ht/40+ Channel 60 : 5300 MHz 11a ht/40+ > Channel 6 : 2437 MHz 11g ht/40- Channel 64 : 5320 MHz 11a > Channel 7 : 2442 MHz 11b Channel 64 : 5320 MHz 11a ht/20 > Channel 7 : 2442 MHz 11g Channel 64 : 5320 MHz 11a ht/40- > Channel 7 : 2442 MHz 11g ht/20 Channel 149 : 5745 MHz 11a > Channel 7 : 2442 MHz 11g ht/40+ Channel 149 : 5745 MHz 11a ht/20 > Channel 7 : 2442 MHz 11g ht/40- Channel 149 : 5745 MHz 11a ht/40+ > Channel 8 : 2447 MHz 11b Channel 153 : 5765 MHz 11a > Channel 8 : 2447 MHz 11g Channel 153 : 5765 MHz 11a ht/20 > Channel 8 : 2447 MHz 11g ht/20 Channel 153 : 5765 MHz 11a ht/40- > Channel 8 : 2447 MHz 11g ht/40- Channel 157 : 5785 MHz 11a > Channel 9 : 2452 MHz 11b Channel 157 : 5785 MHz 11a ht/20 > Channel 9 : 2452 MHz 11g Channel 157 : 5785 MHz 11a ht/40+ > Channel 9 : 2452 MHz 11g ht/20 Channel 161 : 5805 MHz 11a > Channel 9 : 2452 MHz 11g ht/40- Channel 161 : 5805 MHz 11a ht/20 > Channel 10 : 2457 MHz 11b Channel 161 : 5805 MHz 11a ht/40- > Channel 10 : 2457 MHz 11g Channel 165 : 5825 MHz 11a > Channel 10 : 2457 MHz 11g ht/20 Channel 165 : 5825 MHz 11a ht/20 > Channel 10 : 2457 MHz 11g ht/40- > > > > ------------------------------ > Date: Tue, 31 Jan 2012 18:14:44 -0800 > > Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 > From: adrian@freebsd.org > To: shant@skylab.ca > CC: freebsd-wireless@freebsd.org > > Do > > ifconfig -v wlan0 list channel > > > > Adrian > > On 31 January 2012 18:14, Shant Kassardjian wrote: > > Yes, in 8.x it worked perfectly fine. > > > I just restarted the machine and "ath0: unable to reset hardware; hal > status 14 " error is gone but still can't enable N. > > > > core# ifconfig wlan0 channel 6:ht/40 > ifconfig: SIOCS80211: Invalid argument > > > > > > > ------------------------------ > Date: Tue, 31 Jan 2012 18:06:39 -0800 > > Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 > From: adrian@freebsd.org > To: shant@skylab.ca > CC: freebsd-wireless@freebsd.org > > > > On 31 January 2012 18:00, Shant Kassardjian wrote: > > Hi Adrian, > > > After recompiling the kernel with device ath_pci, atheros got redetected, > however 802.11n seems to not be working with the following errors: > > > ifconfig wlan0 destroy > ifconfig wlan0 create wlandev ath0 wlanmode hostap > wlan0: Ethernet address: 00:15:6d:84:70:d5 > core# ath0: unable to reset hardware; hal status 14 > > > .. that's worrying. That's HAL_ESELFTEST, if that fails, bad juju. > > This same thing works on 8.x, right? > > > > Adrian > > > From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:23:40 2012 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 A7CC4106566C; Wed, 1 Feb 2012 02:23:40 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s1.snt0.hotmail.com (snt0-omc4-s1.snt0.hotmail.com [65.55.90.204]) by mx1.freebsd.org (Postfix) with ESMTP id 7841B8FC16; Wed, 1 Feb 2012 02:23:40 +0000 (UTC) Received: from SNT128-W11 ([65.55.90.200]) by snt0-omc4-s1.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 31 Jan 2012 18:23:39 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Tue, 31 Jan 2012 21:23:39 -0500 Importance: Normal In-Reply-To: References: , , , , , , , , , , , , MIME-Version: 1.0 X-OriginalArrivalTime: 01 Feb 2012 02:23:39.0711 (UTC) FILETIME=[828944F0:01CCE088] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:23:40 -0000 core# ifconfig wlan0 channel 6:ht/40 /usr/src/sys/amd64/= conf ifconfig: SIOCS80211: Invalid argument it gave me an error. out of curiosity I did this: core# ifconfig wlan0 channel 157:ht/40 <-- looks like it = took it! core# ifconfig wlan0 =20 wlan0: flags=3D8802 metric 0 mtu 1500 ether 00:15:6d:84:70:d5 inet 172.25.2.1 netmask 0xffffffe0 broadcast 172.25.2.31 nd6 options=3D1 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: no carrier ssid GateKeeper channel 157 (5785 MHz 11a) country US ecm authmode OPEN privacy OFF txpower 5 mcastrate 6 mgmtrate 6 scanvalid 60 wme burst dtimperiod 1 -dfs channel is now set=2C I guess next step is to start hostapd with N ? Date: Tue=2C 31 Jan 2012 18:19:37 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org .. that looks fine. Just try: ifconfig wlan0 channel 6:ht/40 Adrian On 31 January 2012 18:18=2C Shant Kassardjian wrote: Here's what it outputs=2C no N support? I double checked and I compiled wit= h options ATH_ENABLE_11N # 802.11N support.... core# ifconfig -v wlan0 list channel = ~ Channel 1 : 2412 MHz 11b Channel 11 : 2462 MHz 11b Channel 1 : 2412 MHz 11g Channel 11 : 2462 MHz 11g Channel 1 : 2412 MHz 11g ht/20 Channel 11 : 2462 MHz 11g ht= /20 Channel 1 : 2412 MHz 11g ht/40+ Channel 11 : 2462 MHz 11g ht= /40- Channel 2 : 2417 MHz 11b Channel 36 : 5180 MHz 11a Channel 2 : 2417 MHz 11g Channel 36 : 5180 MHz 11a ht= /20 Channel 2 : 2417 MHz 11g ht/20 Channel 36 : 5180 MHz 11a ht= /40+ Channel 2 : 2417 MHz 11g ht/40+ Channel 40 : 5200 MHz 11a Channel 3 : 2422 MHz 11b Channel 40 : 5200 MHz 11a ht= /20 Channel 3 : 2422 MHz 11g Channel 40 : 5200 MHz 11a ht= /40- Channel 3 : 2422 MHz 11g ht/20 Channel 44 : 5220 MHz 11a Channel 3 : 2422 MHz 11g ht/40+ Channel 44 : 5220 MHz 11a ht= /20 Channel 4 : 2427 MHz 11b Channel 44 : 5220 MHz 11a ht= /40+ Channel 4 : 2427 MHz 11g Channel 48 : 5240 MHz 11a Channel 4 : 2427 MHz 11g ht/20 Channel 48 : 5240 MHz 11a ht= /20 Channel 4 : 2427 MHz 11g ht/40+ Channel 48 : 5240 MHz 11a ht= /40- Channel 5 : 2432 MHz 11b Channel 52 : 5260 MHz 11a Channel 5 : 2432 MHz 11g Channel 52 : 5260 MHz 11a ht= /20 Channel 5 : 2432 MHz 11g ht/20 Channel 52 : 5260 MHz 11a ht= /40+ Channel 5 : 2432 MHz 11g ht/40+ Channel 56 : 5280 MHz 11a Channel 5 : 2432 MHz 11g ht/40- Channel 56 : 5280 MHz 11a ht= /20 Channel 6 : 2437 MHz 11b Channel 56 : 5280 MHz 11a ht= /40- Channel 6 : 2437 MHz 11g Channel 60 : 5300 MHz 11a Channel 6 : 2437 MHz 11g ht/20 Channel 60 : 5300 MHz 11a ht= /20 Channel 6 : 2437 MHz 11g ht/40+ Channel 60 : 5300 MHz 11a ht= /40+ Channel 6 : 2437 MHz 11g ht/40- Channel 64 : 5320 MHz 11a Channel 7 : 2442 MHz 11b Channel 64 : 5320 MHz 11a ht= /20 Channel 7 : 2442 MHz 11g Channel 64 : 5320 MHz 11a ht= /40- Channel 7 : 2442 MHz 11g ht/20 Channel 149 : 5745 MHz 11a Channel 7 : 2442 MHz 11g ht/40+ Channel 149 : 5745 MHz 11a ht= /20 Channel 7 : 2442 MHz 11g ht/40- Channel 149 : 5745 MHz 11a ht= /40+ Channel 8 : 2447 MHz 11b Channel 153 : 5765 MHz 11a Channel 8 : 2447 MHz 11g Channel 153 : 5765 MHz 11a ht= /20 Channel 8 : 2447 MHz 11g ht/20 Channel 153 : 5765 MHz 11a ht= /40- Channel 8 : 2447 MHz 11g ht/40- Channel 157 : 5785 MHz 11a Channel 9 : 2452 MHz 11b Channel 157 : 5785 MHz 11a ht= /20 Channel 9 : 2452 MHz 11g Channel 157 : 5785 MHz 11a ht= /40+ Channel 9 : 2452 MHz 11g ht/20 Channel 161 : 5805 MHz 11a Channel 9 : 2452 MHz 11g ht/40- Channel 161 : 5805 MHz 11a ht= /20 Channel 10 : 2457 MHz 11b Channel 161 : 5805 MHz 11a ht= /40- Channel 10 : 2457 MHz 11g Channel 165 : 5825 MHz 11a Channel 10 : 2457 MHz 11g ht/20 Channel 165 : 5825 MHz 11a ht= /20 Channel 10 : 2457 MHz 11g ht/40- Date: Tue=2C 31 Jan 2012 18:14:44 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org Do ifconfig -v wlan0 list channel Adrian On 31 January 2012 18:14=2C Shant Kassardjian wrote: Yes=2C in 8.x it worked perfectly fine. I just restarted the machine and "ath0: unable to reset hardware=3B hal sta= tus 14 " error is gone but still can't enable N. core# ifconfig wlan0 channel 6:ht/40 = =20 ifconfig: SIOCS80211: Invalid argument Date: Tue=2C 31 Jan 2012 18:06:39 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org On 31 January 2012 18:00=2C Shant Kassardjian wrote: Hi Adrian=2C After recompiling the kernel with device ath_pci=2C atheros got redetected= =2C however 802.11n seems to not be working with the following errors: ifconfig wlan0 destroy ifconfig wlan0 create wlandev ath0 wlanmode hostap wlan0: Ethernet address: 00:15:6d:84:70:d5 core# ath0: unable to reset hardware=3B hal status 14 =20 .. that's worrying. That's HAL_ESELFTEST=2C if that fails=2C bad juju. This same thing works on 8.x=2C right? Adrian =20 =20 = From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:25:34 2012 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 B02E71065674 for ; Wed, 1 Feb 2012 02:25:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5E1928FC15 for ; Wed, 1 Feb 2012 02:25:34 +0000 (UTC) Received: by vcmm1 with SMTP id m1so898471vcm.13 for ; Tue, 31 Jan 2012 18:25:33 -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; bh=Oulrs4ZSQQcyXL+VBR0AMfuoX28+tUTBoobSSMsEDug=; b=v78nQZ7zecsKhkY97gFWLcyd3Kq3JR+xRTo5HVmupr/JS+P5uZMSCjMHeOCzSzi0nh qd//3rQSLO0Vx4GelawJGVXsOCvxThyPWRHmyzZBX7g+bLyqW4G949DWaO4zKJinW9uM 59h4j8gDDROTTFcjcOIrPSAkLbJe/pHydP5Rk= MIME-Version: 1.0 Received: by 10.220.156.201 with SMTP id y9mr15235025vcw.22.1328063133692; Tue, 31 Jan 2012 18:25:33 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Tue, 31 Jan 2012 18:25:33 -0800 (PST) In-Reply-To: References: Date: Tue, 31 Jan 2012 18:25:33 -0800 X-Google-Sender-Auth: MTQcqC9_ETrXl2EWMcUlTyKbm_Q Message-ID: From: Adrian Chadd To: Shant Kassardjian Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:25:34 -0000 .. yes, that line is wrong. :) On 31 January 2012 18:23, Shant Kassardjian wrote: > core# ifconfig wlan0 channel 6:ht/40 /usr/src/sys/amd64/conf > .. tsk. That path isn't needed. :) > > channel is now set, I guess next step is to start hostapd with N ? > > Just configure it to use CCMP encryption only. nothing else is needed for 'n'. Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 02:30:09 2012 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 47412106564A; Wed, 1 Feb 2012 02:30:09 +0000 (UTC) (envelope-from pookme@hotmail.com) Received: from snt0-omc4-s18.snt0.hotmail.com (snt0-omc4-s18.snt0.hotmail.com [65.55.90.221]) by mx1.freebsd.org (Postfix) with ESMTP id 0C2518FC13; Wed, 1 Feb 2012 02:30:08 +0000 (UTC) Received: from SNT128-W63 ([65.55.90.200]) by snt0-omc4-s18.snt0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 31 Jan 2012 18:30:08 -0800 Message-ID: X-Originating-IP: [184.163.168.71] From: Shant Kassardjian Sender: To: Date: Tue, 31 Jan 2012 21:30:08 -0500 Importance: Normal In-Reply-To: References: , , , , , , , , , , , , , , MIME-Version: 1.0 X-OriginalArrivalTime: 01 Feb 2012 02:30:08.0435 (UTC) FILETIME=[6A3BD830:01CCE089] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: RE: SR71-A (AR9160) no longer detected in FreeBSD 9 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 02:30:09 -0000 Here is my ifconfig wlan0 ------------------------------ wlan0: flags=3D8843 metric = 0 mtu 1500 ether 00:15:6d:84:70:d5 inet 172.25.2.1 netmask 0xffffffe0 broadcast 172.25.2.31 nd6 options=3D1 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: running ssid GateKeeper channel 157 (5785 MHz 11a) bssid 00:15:6d:84:70:d5 country US ecm authmode WPA2/802.11i privacy MIXED deftxkey 2 AES-CCM 2:128-bit txpower 5 mcastrate 6 mgmtrate 6 scanvalid 60 wme burst dtimperiod 1 -dfs if you check this line it says: media: IEEE 802.11 Wireless Ethernet autos= elect mode 11a <-- doesn't mention 11n :( here is my hostapd.conf (very simple): core# cat /etc/hostapd.conf /usr/src/sys/amd64/= conf interface=3Dwlan0 debug=3D0 dump_file=3D/tmp/hostapd.dump ctrl_interface=3D/var/run/hostapd ctrl_interface_group=3Dwheel ssid=3DGateKeeper wpa=3D2 wpa_passphrase=3Dxxxxx wpa_key_mgmt=3DWPA-PSK wpa_pairwise=3DCCMP Date: Tue=2C 31 Jan 2012 18:25:33 -0800 Subject: Re: SR71-A (AR9160) no longer detected in FreeBSD 9 From: adrian@freebsd.org To: shant@skylab.ca CC: freebsd-wireless@freebsd.org .. yes=2C that line is wrong. :) On 31 January 2012 18:23=2C Shant Kassardjian wrote: core# ifconfig wlan0 channel 6:ht/40 /usr/src/sys/amd64/= conf .. tsk. That path isn't needed. :) =20 channel is now set=2C I guess next step is to start hostapd with N ? Just configure it to use CCMP encryption only. nothing else is needed for '= n'. Adrian = From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 08:36:58 2012 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 181551065673 for ; Wed, 1 Feb 2012 08:36:58 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id BE9E18FC13 for ; Wed, 1 Feb 2012 08:36:57 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q118av4v063817 for ; Wed, 1 Feb 2012 00:36:57 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q118avTV063816 for freebsd-wireless@freebsd.org; Wed, 1 Feb 2012 00:36:57 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: FreeBSD Wireless Message-Id: <1328085416.63811@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 Date: Wed, 01 Feb 2012 00:36:57 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1328085417" Subject: possible issue 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: Wed, 01 Feb 2012 08:36:58 -0000 This is a multi-part message in MIME format. --bound1328085417 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Hi, I installed FreeBSD-CURRENT FreeBSD p00ntang.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Tue Jan 31 07:08:58 PST 2012 waitman@p00ntang.waitman.net:/usr/obj/usr/src/sys/GENERIC i386 I have three wireless networks running. I haven't got my Atheros 9280 to make the connection yet with CURRENT (looks like it's going to autoselect 802.11a mode for some reason... I'm checking this out.) Anyway, I noticed my 2.4GHz 802.11b/g/n shows up in a scan but vanishes instantly, but my 5GHz 802.11n is still in the picture.. the scan is showing BOOTAY on channel 149, which is the 5GHz channel. it should be on 2.4GHz channel 9. here's a scan, BOOTAY will show up for about 10 secs and vanish. but the other two networks remain.. p00ntang# ifconfig wlan0 up scan | grep DA DARKNET 1c:7e:e5:de:ed:52 149 54M -76:-96 100 EP WPS HTCAP WPA RSN WME CUDAPANG 00:22:3f:9a:16:1b 6 54M -68:-96 100 EPS ATH p00ntang# ifconfig wlan0 up scan | grep BOOT BOOTAY 1c:7e:e5:de:ed:52 149 54M -73:-96 100 EP WPS HTCAP WPA RSN WME p00ntang# ifconfig wlan0 up scan | grep BOOT p00ntang# ifconfig wlan0 up scan | grep BOOT p00ntang# ifconfig wlan0 up scan | grep DA DARKNET 1c:7e:e5:de:ed:52 149 54M -77:-96 100 EP WPS HTCAP WPA RSN WME CUDAPANG 00:22:3f:9a:16:1b 6 54M -68:-96 100 EPS ATH p00ntang# ifconfig wlan0 up scan | grep BOOT I really haven't done a whole heck of alot with 5GHz wireless - but I don't believe BOOTAY is running on channel 149, unless this has something to do with "mixed mode" setting on the router. ath0: mem 0x95100000-0x9510ffff irq 16 at device 0.0 on pci1 ath0: AR9280 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 ath0: flags=8843 metric 0 mtu 2290 ether 00:23:5a:59:e1:e4 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: associated Thanks, -- Waitman Gobble San Jose California USA --bound1328085417-- From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 09:38:29 2012 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 00981106566C for ; Wed, 1 Feb 2012 09:38:29 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m020-f182.google.com (mail-lpp01m020-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7BDE08FC1A for ; Wed, 1 Feb 2012 09:38:28 +0000 (UTC) Received: by lbbgj3 with SMTP id gj3so178260lbb.13 for ; Wed, 01 Feb 2012 01:38:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.85.73 with SMTP id f9mr6560547lbz.25.1328089107175; Wed, 01 Feb 2012 01:38:27 -0800 (PST) Received: by 10.152.13.169 with HTTP; Wed, 1 Feb 2012 01:38:27 -0800 (PST) X-Originating-IP: [79.140.39.245] In-Reply-To: References: Date: Wed, 1 Feb 2012 10:38:27 +0100 Message-ID: From: Bernhard Schmidt To: "Jeremy C. Reed" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 09:38:29 -0000 On Tue, Jan 31, 2012 at 23:07, Jeremy C. Reed wrote: > Anyone using the following? > > iwn0: mem 0xf0600000-0xf0601fff irq 17 at device 0.0 on pci2 > iwn0: attempting to allocate 1 MSI vectors (1 supported) > msi: routing MSI IRQ 257 to local APIC 0 vector 51 > iwn0: using IRQ 257 for MSI > iwn0: MIMO 1T2R, BGN, address ac:72:89:ec:3b:1e Strange.. the 1030 is exactly the same as the 6230 (except some small difference like the number of mimo stream and 5GHz support). The 6230 is what I'm using daily and that one works great. Do you by any chance have a button/switch to disable bluetooth? I'd play around with that one, maybe I've did something wrong with regard to bluetooth coexistence. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 13:55:15 2012 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 F211E106566B for ; Wed, 1 Feb 2012 13:55:14 +0000 (UTC) (envelope-from reed@reedmedia.net) Received: from c-0500.emailmediator.com (c-0500.emailmediator.com [64.85.162.118]) by mx1.freebsd.org (Postfix) with ESMTP id AA4DF8FC17 for ; Wed, 1 Feb 2012 13:55:05 +0000 (UTC) Received: from pool-71-164-190-204.dllstx.fios.verizon.net ([71.164.190.204] helo=reedmedia.net) by c-0500.emailmediator.com with esmtpa (Exim 4.69) (envelope-from ) id 1RsaeO-0004ge-7g; Wed, 01 Feb 2012 08:55:05 -0500 Received: from reed@reedmedia.net by reedmedia.net with local (mailout 0.17) id 19423-1328104503; Wed, 01 Feb 2012 07:55:04 -0600 Date: Wed, 1 Feb 2012 07:55:03 -0600 (CST) From: "Jeremy C. Reed" X-X-Sender: reed@t1.m.reedmedia.net To: Bernhard Schmidt In-Reply-To: Message-ID: References: User-Agent: Alpine 2.01 (NEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-wireless@freebsd.org Subject: Re: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 13:55:15 -0000 On Wed, 1 Feb 2012, Bernhard Schmidt wrote: > > iwn0: mem 0xf0600000-0xf0601fff irq 17 at device 0.0 on pci2 > > iwn0: attempting to allocate 1 MSI vectors (1 supported) > > msi: routing MSI IRQ 257 to local APIC 0 vector 51 > > iwn0: using IRQ 257 for MSI > > iwn0: MIMO 1T2R, BGN, address ac:72:89:ec:3b:1e > > Strange.. the 1030 is exactly the same as the 6230 (except some small > difference like the number of mimo stream and 5GHz support). The 6230 > is what I'm using daily and that one works great. > > Do you by any chance have a button/switch to disable bluetooth? I'd > play around with that one, maybe I've did something wrong with regard > to bluetooth coexistence. I think the bluetooth switch is the same function button as the wireless switch. When I press it I get: ahcich1: SNTF 0x0001 ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ugen2.3: at usbus2 (disconnected) ubt0: at uhub4, port 5, addr 3 (disconnected) In the case that the wlan0 is up then I also get: iwn0: RF switch: radio disabled (But only if the wlan0 is up I think.) (That ahcich1 I only saw one time, so probably unrelated.) When I press it again (to turn it back on): ugen2.3: at usbus2 ubt0: on usbus2 When the interface wlan0 is up, I also get: iwn0: RF switch: radio enabled firmware: 'iwn6000g2bfw' version 0: 460912 bytes loaded at 0xffffffff816120b0 The complete dmesg (boot with verbose) is at: http://reedmedia.net/~reed/tmp/dmesg-dell-inspiron-14z.txt From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 14:25:06 2012 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 84E671065673 for ; Wed, 1 Feb 2012 14:25:06 +0000 (UTC) (envelope-from reed@reedmedia.net) Received: from c-0500.emailmediator.com (c-0500.emailmediator.com [64.85.162.118]) by mx1.freebsd.org (Postfix) with ESMTP id 5AB358FC28 for ; Wed, 1 Feb 2012 14:25:06 +0000 (UTC) Received: from pool-71-164-190-204.dllstx.fios.verizon.net ([71.164.190.204] helo=reedmedia.net) by c-0500.emailmediator.com with esmtpa (Exim 4.69) (envelope-from ) id 1Rsb7S-0003FP-51; Wed, 01 Feb 2012 09:25:06 -0500 Received: from reed@reedmedia.net by reedmedia.net with local (mailout 0.17) id 25691-1328106305; Wed, 01 Feb 2012 08:25:06 -0600 Date: Wed, 1 Feb 2012 08:25:05 -0600 (CST) From: "Jeremy C. Reed" X-X-Sender: reed@t1.m.reedmedia.net To: Adrian Chadd In-Reply-To: Message-ID: References: User-Agent: Alpine 2.01 (NEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-wireless@freebsd.org Subject: Re: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 14:25:06 -0000 On Tue, 31 Jan 2012, Adrian Chadd wrote: > try it with an open AP for now, see if it can exchange data fine? Sorry I am new to wireless on FreeBSD. Still looking at the handbook, but I can't figure out how to get it associated with an open access point. (On a different laptop at same location, when I boot a different BSD it automatically connects to it with no wireless configuration.) When I use ifconfig wlan0 scan it shows it. When I run wpa_supplicant and then wpa_cli and scan and then scan_results it shows it. I can use ifconfig to configure it, but it always says status: no carrier. (When I configure it to use my local access point with the nwkey then it is associated, but dhclient doesn't work.) Any pointers to any docs on how to use ifconfig or other (non X11) tool to automatically scan and connect to a local AP? (The handbook, as far as I see for this, discusses configuring rc.conf so doesn't show me the exact commands lines, and I don't want to yet read all through the rc.d scripts and network.subr.) (By the way, the handbook shows "ifconfig wlan0 up scan" but that outputs nothing in the case where the interface needs to brought up first. Run it again and then it does output the results.) > I'm not really going to be more helpful than that on the intel NICs I'm > afraid :( Any suggestions on a cheap USB wifi adapter to use? (Maybe there is a webpage with suggested hardware to use?) From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 14:34:40 2012 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 5459C106566B; Wed, 1 Feb 2012 14:34:40 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id A76B48FC17; Wed, 1 Feb 2012 14:34:39 +0000 (UTC) Received: by lagz14 with SMTP id z14so875939lag.13 for ; Wed, 01 Feb 2012 06:34:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.85.137 with SMTP id h9mr6655335lbz.51.1328106878529; Wed, 01 Feb 2012 06:34:38 -0800 (PST) Received: by 10.152.13.169 with HTTP; Wed, 1 Feb 2012 06:34:38 -0800 (PST) X-Originating-IP: [79.140.39.245] In-Reply-To: References: Date: Wed, 1 Feb 2012 15:34:38 +0100 Message-ID: From: Bernhard Schmidt To: "Jeremy C. Reed" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 14:34:40 -0000 On Wed, Feb 1, 2012 at 15:25, Jeremy C. Reed wrote: > On Tue, 31 Jan 2012, Adrian Chadd wrote: > >> try it with an open AP for now, see if it can exchange data fine? > > Sorry I am new to wireless on FreeBSD. Still looking at the handbook, > but I can't figure out how to get it associated with an open access > point. (On a different laptop at same location, when I boot a different > BSD it automatically connects to it with no wireless configuration.) > > When I use ifconfig wlan0 scan it shows it. When I run wpa_supplicant > and then wpa_cli and scan and then scan_results it shows it. I can use > ifconfig to configure it, but it always says status: no carrier. (When I > configure it to use my local access point with the nwkey then it is > associated, but dhclient doesn't work.) > > Any pointers to any docs on how to use ifconfig or other (non X11) tool > to automatically scan and connect to a local AP? =A0(The handbook, as far > as I see for this, discusses configuring rc.conf so doesn't show me the > exact commands lines, and I don't want to yet read all through the rc.d > scripts and network.subr.) Given an empty rc.conf (no wlan configuration) simply typing ifconfig wlan0 create wlandev iwn0 ifconfig wlan0 up should be enough, the rc.conf counterpart should look like wlans_iwn0=3D"wlan0" ifconfig_wlan0=3D"up" (no IP in both cases obviously) Be aware, if you have something configured related to wlan0 in rc.conf, creating the wlan0 interface will invoke devd which will invoke /etc/rc.d/netif which will load the configuration. Just so you don't have to wonder why wpa_supplicant gets started without it being started explicitly. So.. if ifconfig wlan0 create wlandev iwn0 ifconfig wlan0 up doesn't connect to any open network around, enable debugging with wlandebug 0xffffffff and post the results please. --=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 14:46:59 2012 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 C87F7106566B for ; Wed, 1 Feb 2012 14:46:59 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 53CEA8FC13 for ; Wed, 1 Feb 2012 14:46:59 +0000 (UTC) Received: by lagz14 with SMTP id z14so885015lag.13 for ; Wed, 01 Feb 2012 06:46:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.122.240 with SMTP id lv16mr13620893lab.34.1328107618265; Wed, 01 Feb 2012 06:46:58 -0800 (PST) Received: by 10.152.13.169 with HTTP; Wed, 1 Feb 2012 06:46:58 -0800 (PST) X-Originating-IP: [79.140.39.245] In-Reply-To: References: Date: Wed, 1 Feb 2012 15:46:58 +0100 Message-ID: From: Bernhard Schmidt To: "Jeremy C. Reed" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 14:46:59 -0000 On Wed, Feb 1, 2012 at 14:55, Jeremy C. Reed wrote: > On Wed, 1 Feb 2012, Bernhard Schmidt wrote: > >> > iwn0: mem 0xf0600000-0xf0601fff irq 17 at device 0.0 on pci2 >> > iwn0: attempting to allocate 1 MSI vectors (1 supported) >> > msi: routing MSI IRQ 257 to local APIC 0 vector 51 >> > iwn0: using IRQ 257 for MSI >> > iwn0: MIMO 1T2R, BGN, address ac:72:89:ec:3b:1e >> >> Strange.. the 1030 is exactly the same as the 6230 (except some small >> difference like the number of mimo stream and 5GHz support). The 6230 >> is what I'm using daily and that one works great. >> >> Do you by any chance have a button/switch to disable bluetooth? I'd >> play around with that one, maybe I've did something wrong with regard >> to bluetooth coexistence. > > I think the bluetooth switch is the same function button as the wireless > switch. Right, which makes sense as the device is a combined BT+WLAN device. Though, my 6230 has 2 buttons, one for BT and one for WLAN and I was thinking you might have that too. Anyways, was just looking for a quick test to rule BTcoex out, which didn't work. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 15:03:20 2012 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 C9B9F1065670 for ; Wed, 1 Feb 2012 15:03:20 +0000 (UTC) (envelope-from reed@reedmedia.net) Received: from c-0500.emailmediator.com (c-0500.emailmediator.com [64.85.162.118]) by mx1.freebsd.org (Postfix) with ESMTP id A28868FC1D for ; Wed, 1 Feb 2012 15:03:20 +0000 (UTC) Received: from pool-71-164-190-204.dllstx.fios.verizon.net ([71.164.190.204] helo=reedmedia.net) by c-0500.emailmediator.com with esmtpa (Exim 4.69) (envelope-from ) id 1RsbiS-0004N2-1X; Wed, 01 Feb 2012 10:03:20 -0500 Received: from reed@reedmedia.net by reedmedia.net with local (mailout 0.17) id 1847-1328108599; Wed, 01 Feb 2012 09:03:20 -0600 Date: Wed, 1 Feb 2012 09:03:19 -0600 (CST) From: "Jeremy C. Reed" X-X-Sender: reed@t1.m.reedmedia.net To: Bernhard Schmidt In-Reply-To: Message-ID: References: User-Agent: Alpine 2.01 (NEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-wireless@freebsd.org Subject: Re: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 15:03:20 -0000 On Wed, 1 Feb 2012, Bernhard Schmidt wrote: > Given an empty rc.conf (no wlan configuration) simply typing > ifconfig wlan0 create wlandev iwn0 > ifconfig wlan0 up > should be enough, the rc.conf counterpart should look like > wlans_iwn0="wlan0" > ifconfig_wlan0="up" > (no IP in both cases obviously) > > Be aware, if you have something configured related to wlan0 in > rc.conf, creating the wlan0 interface will invoke devd which will > invoke /etc/rc.d/netif which will load the configuration. Just so you > don't have to wonder why wpa_supplicant gets started without it being > started explicitly. > > So.. if > ifconfig wlan0 create wlandev iwn0 > ifconfig wlan0 up > doesn't connect to any open network around, enable debugging with > wlandebug 0xffffffff > and post the results please. Thanks. I commented out the related configurations from rc.conf (that the sysinstall created) and rebooted. After creating it, this was shown on console: wlan0: Ethernet address: 72:89:ec:3b:1e ifconfig wlan0 up didn't appear to bring anything up (even after waiting some time): $ ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether ac:72:89:ec:3b:1e nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 12 (2467 MHz 11g) country US authmode OPEN privacy OFF txpower 15 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme bintval 0 I did the wlandebug. The parts of /var/log/messages for this is at: http://reedmedia.net/~reed/tmp/wlandebug.20120201a.txt Less than one minute is over 3700 log entries. From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 1 16:17:46 2012 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 388F51065672 for ; Wed, 1 Feb 2012 16:17:46 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id B5C458FC17 for ; Wed, 1 Feb 2012 16:17:45 +0000 (UTC) Received: by lagz14 with SMTP id z14so957285lag.13 for ; Wed, 01 Feb 2012 08:17:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.125.12 with SMTP id mm12mr13895669lab.48.1328113064483; Wed, 01 Feb 2012 08:17:44 -0800 (PST) Received: by 10.152.13.169 with HTTP; Wed, 1 Feb 2012 08:17:44 -0800 (PST) X-Originating-IP: [79.140.39.245] In-Reply-To: References: Date: Wed, 1 Feb 2012 17:17:44 +0100 Message-ID: From: Bernhard Schmidt To: "Jeremy C. Reed" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: iwn Centrino N-1030 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 16:17:46 -0000 On Wed, Feb 1, 2012 at 16:03, Jeremy C. Reed wrote: > On Wed, 1 Feb 2012, Bernhard Schmidt wrote: > >> Given an empty rc.conf (no wlan configuration) simply typing >> ifconfig wlan0 create wlandev iwn0 >> ifconfig wlan0 up >> should be enough, the rc.conf counterpart should look like >> wlans_iwn0=3D"wlan0" >> ifconfig_wlan0=3D"up" >> (no IP in both cases obviously) >> >> Be aware, if you have something configured related to wlan0 in >> rc.conf, creating the wlan0 interface will invoke devd which will >> invoke /etc/rc.d/netif which will load the configuration. Just so you >> don't have to wonder why wpa_supplicant gets started without it being >> started explicitly. >> >> So.. if >> ifconfig wlan0 create wlandev iwn0 >> ifconfig wlan0 up >> doesn't connect to any open network around, enable debugging with >> wlandebug 0xffffffff >> and post the results please. > > Thanks. I commented out the related configurations from rc.conf (that > the sysinstall created) and rebooted. > > After creating it, this was shown on console: > wlan0: Ethernet address: 72:89:ec:3b:1e > > ifconfig wlan0 up didn't appear to bring anything up (even after waiting > some time): > > $ ifconfig wlan0 > wlan0: flags=3D8843 metric 0 mtu = 1500 > =A0 =A0 =A0 =A0ether ac:72:89:ec:3b:1e > =A0 =A0 =A0 =A0nd6 options=3D29 > =A0 =A0 =A0 =A0media: IEEE 802.11 Wireless Ethernet autoselect (autoselec= t) > =A0 =A0 =A0 =A0status: no carrier > =A0 =A0 =A0 =A0ssid "" channel 12 (2467 MHz 11g) > =A0 =A0 =A0 =A0country US authmode OPEN privacy OFF txpower 15 bmiss 10 s= canvalid 60 > =A0 =A0 =A0 =A0bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rat= e 5 > =A0 =A0 =A0 =A0protmode CTS wme bintval 0 > > I did the wlandebug. The parts of /var/log/messages for this is at: > http://reedmedia.net/~reed/tmp/wlandebug.20120201a.txt > Less than one minute is over 3700 log entries. Quoting from the log: Feb 1 08:49:28 work1 kernel: wlan0: macaddr bssid chan rssi rate flag wep essid Feb 1 08:49:28 work1 kernel: - e8:39:df:f8:a3:50 e8:39:df:f8:a3:50 1 7! 54M ess wep! "3GQH7" Feb 1 08:49:28 work1 kernel: - 00:1f:90:e2:aa:61 00:1f:90:e2:aa:61 1 12 54M ess wep! "stix" Feb 1 08:49:28 work1 kernel: - 00:18:01:e0:8a:57 00:18:01:e0:8a:57 11 36 54M ess wep! "5FYA8" Feb 1 08:49:28 work1 kernel: - e8:39:df:d8:92:2b e8:39:df:d8:92:2b 1 22 54M ess wep! "3CSHT" Feb 1 08:49:28 work1 kernel: ^ 00:1f:90:e5:01:e3 00:1f:90:e5:01:e3 11 6! 54M ess wep! "2O6P0" Feb 1 08:49:28 work1 kernel: ^ 00:13:10:95:25:9c 00:13:10:95:25:9c 6 5! 54M ess no "linksys" Feb 1 08:49:28 work1 kernel: - 90:00:4e:0a:ed:a6 02:2b:3b:c0:a9:bf 6 4! 54M ibss! no "HPCP1525-0aeda6" Feb 1 08:49:28 work1 kernel: - 00:21:63:83:71:de 00:21:63:83:71:de 11 5! 54M ess wep! "N9DW4" Feb 1 08:49:28 work1 kernel: - 68:7f:74:45:e6:46 68:7f:74:45:e6:46 11 5! 54M ess no "Scentsytx-guest" Feb 1 08:49:28 work1 kernel: - 68:7f:74:45:e6:44 68:7f:74:45:e6:44 11 6! 54M ess wep! "Scentsytx" Feb 1 08:49:28 work1 kernel: - 00:1f:90:e3:9a:41 00:1f:90:e3:9a:41 6 5! 54M ess wep! "CR9D0" Feb 1 08:49:28 work1 kernel: ^ 00:1f:90:ea:5e:d4 00:1f:90:ea:5e:d4 11 3! 54M ess wep! "QKJQ1" quite a few networks to choose from, but.. those with a ! on the rssi column aren't considered because the signal is too low and all others are encrypted not open. Do you by any chance have some scan results from Linux or something available to compare too? if there is a significant diff in the signal quality I might have to look into the antenna setup. --=20 Bernhard From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 05:38:20 2012 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 D55DC106564A for ; Thu, 2 Feb 2012 05:38:20 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id B2AF28FC16 for ; Thu, 2 Feb 2012 05:38:20 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q125cJQV092638; Wed, 1 Feb 2012 21:38:20 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q125cJi5092637; Wed, 1 Feb 2012 21:38:19 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: "Waitman Gobble" Message-Id: <1328161099.92628@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 In-Reply-To: <1328085416.63811@da3m0n8t3r.com> Date: Wed, 01 Feb 2012 21:38:19 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1328161099" Cc: FreeBSD Wireless Subject: Re: possible issue 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, 02 Feb 2012 05:38:21 -0000 This is a multi-part message in MIME format. --bound1328161099 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Waitman Gobble wrote .. > Hi, > > I installed FreeBSD-CURRENT > > FreeBSD p00ntang.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Tue Jan 31 07:08:58 > PST 2012 waitman@p00ntang.waitman.net:/usr/obj/usr/src/sys/GENERIC i386 > > I have three wireless networks running. I haven't got my Atheros 9280 to make the > connection yet with CURRENT (looks like it's going to autoselect 802.11a mode for > some reason... I'm checking this out.) > > Anyway, I noticed my 2.4GHz 802.11b/g/n shows up in a scan but vanishes instantly, > but my 5GHz 802.11n is still in the picture.. the scan is showing BOOTAY on channel > 149, which is the 5GHz channel. it should be on 2.4GHz channel 9. > > here's a scan, BOOTAY will show up for about 10 secs and vanish. but the other > two networks remain.. > > p00ntang# ifconfig wlan0 up scan | grep DA > DARKNET 1c:7e:e5:de:ed:52 149 54M -76:-96 100 EP WPS HTCAP WPA RSN > WME > CUDAPANG 00:22:3f:9a:16:1b 6 54M -68:-96 100 EPS ATH > p00ntang# ifconfig wlan0 up scan | grep BOOT > BOOTAY 1c:7e:e5:de:ed:52 149 54M -73:-96 100 EP WPS HTCAP WPA RSN > WME > p00ntang# ifconfig wlan0 up scan | grep BOOT > p00ntang# ifconfig wlan0 up scan | grep BOOT > p00ntang# ifconfig wlan0 up scan | grep DA > DARKNET 1c:7e:e5:de:ed:52 149 54M -77:-96 100 EP WPS HTCAP WPA RSN > WME > CUDAPANG 00:22:3f:9a:16:1b 6 54M -68:-96 100 EPS ATH > p00ntang# ifconfig wlan0 up scan | grep BOOT > > > I really haven't done a whole heck of alot with 5GHz wireless - but I don't believe > BOOTAY is running on channel 149, unless this has something to do with "mixed mode" > setting on the router. > > > > ath0: mem 0x95100000-0x9510ffff irq 16 at device 0.0 on pci1 > ath0: AR9280 mac 128.2 RF5133 phy 13.0 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > ath0: flags=8843 metric 0 mtu 2290 > ether 00:23:5a:59:e1:e4 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11a > status: associated > > Thanks, > > -- > Waitman Gobble > San Jose California USA I got 802.11g working with my AR9280. woo p00ntang# ifconfig wlan0 create wlandev ath0 ssid BOOTAY mode 11g p00ntang# wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf p00ntang# ifconfig wlan0 inet 10.0.0.20 netmask 255.255.255.0 p00ntang# ifconfig wlan0 scan | grep DA CUDAPANG 00:22:3f:9a:16:1b 6 54M -70:-96 100 EPS ATH p00ntang# ifconfig wlan0 scan | grep BO BOOTAY 1c:7e:e5:de:ed:52 9 54M -69:-96 100 EP MESHCONF MESHCONF WPS WPA RSN WME p00ntang# route add default 10.0.0.1 p00ntang# ping somewhereoutside.com PING somewhereoutside.com (209.237.152.13): 56 data bytes 64 bytes from 209.237.152.13: icmp_seq=0 ttl=241 time=77.087 ms 64 bytes from 209.237.152.13: icmp_seq=1 ttl=241 time=76.928 ms now BOOTAY is reported on channel 9. still not sure about the channel 149 deal from last night. lagg failover doesn't seem to be working properly, still checking. not having luck with 11n, arrggh still fiddling with it. :) -- Waitman Gobble San Jose California USA --bound1328161099-- From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 15:58:03 2012 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 DFAB41065670; Thu, 2 Feb 2012 15:58:03 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id A34E48FC12; Thu, 2 Feb 2012 15:58:03 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:24ed:86dc:9f3b:9149]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 6D7124AC2D; Thu, 2 Feb 2012 19:58:01 +0400 (MSK) Date: Thu, 2 Feb 2012 19:57:57 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <743722267.20120202195757@serebryakov.spb.ru> To: freebsd-wireless@freebsd.org, Adrian Chadd MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Subject: "ath0: device timeout" when environment is clear 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, 02 Feb 2012 15:58:04 -0000 Hello, Freebsd-wireless. Today something strange happens: my noisy environment becomes clear for several hours and my WiFi connection to notebook gives 2.5MiB/s of real file transfer. But I was unable to copy 2GiB file in one piece: ath0 on AP gives "device timeout" every 3-4 minutes! When environment is really noisy (as usual), I have only 400-500KiB/s of real file transfer, but "ath0: device timeout" occurs only 1-2 times a day or even less. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 19:09:53 2012 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 1C462106564A; Thu, 2 Feb 2012 19:09:53 +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 AE9578FC12; Thu, 2 Feb 2012 19:09:52 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so3073984vbb.13 for ; Thu, 02 Feb 2012 11:09:51 -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; bh=rlSZMqWEZ0IPh6uHicwGIUTsjMNiYO8fexqylVAZ0ds=; b=rTT2N80BjWK+eZBg68kC5Z8xAS0QU9novhSh9hbFfrn3vVJ+NRUQz24e+nkWxTEwMK JSubA0Db7NJLMhLQiGp205fxWj+kWwQPKkKqNsvImfcrmSV6054u0Or4OXiDHyPdxVjN LkDPEwA4yfKGmoA5iKL7V2zTrKpYnfsaqyqWY= MIME-Version: 1.0 Received: by 10.52.66.166 with SMTP id g6mr1919242vdt.34.1328209791750; Thu, 02 Feb 2012 11:09:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Thu, 2 Feb 2012 11:09:51 -0800 (PST) In-Reply-To: <743722267.20120202195757@serebryakov.spb.ru> References: <743722267.20120202195757@serebryakov.spb.ru> Date: Thu, 2 Feb 2012 11:09:51 -0800 X-Google-Sender-Auth: SmjwfVqyf58UG5BfuOKI4BmzulU Message-ID: From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: "ath0: device timeout" when environment is clear 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, 02 Feb 2012 19:09:53 -0000 2012/2/2 Lev Serebryakov > Hello, Freebsd-wireless. > > Today something strange happens: my noisy environment becomes clear > for several hours and my WiFi connection to notebook gives 2.5MiB/s > of real file transfer. But I was unable to copy 2GiB file in one > piece: ath0 on AP gives "device timeout" every 3-4 minutes! > > When environment is really noisy (as usual), I have only > 400-500KiB/s of real file transfer, but "ath0: device timeout" > occurs only 1-2 times a day or even less. Are you using 11n? There may be some more TX handling issues that show up as "device timeout" but arent' really that. adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 19:28:17 2012 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 92A871065673; Thu, 2 Feb 2012 19:28:17 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2EA2B8FC13; Thu, 2 Feb 2012 19:28:17 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:24ed:86dc:9f3b:9149]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 5EA8D4AC2D; Thu, 2 Feb 2012 23:28:15 +0400 (MSK) Date: Thu, 2 Feb 2012 23:28:10 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1292923023.20120202232810@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <743722267.20120202195757@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: "ath0: device timeout" when environment is clear 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, 02 Feb 2012 19:28:17 -0000 Hello, Adrian. You wrote 2 =F4=E5=E2=F0=E0=EB=FF 2012 =E3., 23:09:51: > Today something strange happens: my noisy environment becomes clear > for several hours and my WiFi connection to notebook gives 2.5MiB/s > of real file transfer. But I was unable to copy 2GiB file in one > piece: ath0 on AP gives "device timeout" every 3-4 minutes! > When environment is really noisy (as usual), I have only > 400-500KiB/s of real file transfer, but "ath0: device timeout" > occurs only 1-2 times a day or even less. > Are you using 11n? AP in 11ng mode: media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid home.serebryakov.spb.ru channel 9 (2452 MHz 11g ht/20) bssid f4:ec:38:= a3:10:6d But client 802.11g only (Intel 3945ABG) > There may be some more TX handling issues that show up as "device > timeout" but arent' really that. Maybe, it is possible to add additional debug output in such situations? = I'm not able to run `athstat' ASAP manually in most of these cases, because= I didn't look at notebook's screen when copy files to it and notice such s= ituations post-factum. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 19:32:18 2012 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 56EA21065672 for ; Thu, 2 Feb 2012 19:32:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 107ED8FC08 for ; Thu, 2 Feb 2012 19:32:17 +0000 (UTC) Received: by vcmm1 with SMTP id m1so3178047vcm.13 for ; Thu, 02 Feb 2012 11:32:17 -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; bh=0P2sXeU2BMGzjsXiE1xJYuQeNcnsqwDaIhleQtb4pN8=; b=O15JAGVkRs8FmHsBTcKPrPsSvrfbyXay9JQuO01OtxhIwbAXaoOcc6c7IxVf6qh+gi 7Os5vTkusuIZjbG8TdSAh2EJthTUb7RlmecNWRASj8AgSShLSqKY60KdGmBo2I4VfiKX pADiCndsp8DQkaunJIqNA1R566qnj3vHFq46c= MIME-Version: 1.0 Received: by 10.220.156.201 with SMTP id y9mr2333358vcw.22.1328211137332; Thu, 02 Feb 2012 11:32:17 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Thu, 2 Feb 2012 11:32:17 -0800 (PST) In-Reply-To: <1292923023.20120202232810@serebryakov.spb.ru> References: <743722267.20120202195757@serebryakov.spb.ru> <1292923023.20120202232810@serebryakov.spb.ru> Date: Thu, 2 Feb 2012 11:32:17 -0800 X-Google-Sender-Auth: A6MdF5YiKAjHq2UTaN723gxJ9Cw Message-ID: From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: "ath0: device timeout" when environment is clear 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, 02 Feb 2012 19:32:18 -0000 Please file a bug so I don't forget. What you can do is flip on reset debugging in the driver (look at if_ath_debug.h for ATH_DEBUG_RESET) - not the HAL debugging, just the reset debugging) - that should make ath_draintxq() print out the contents of the TX queue before its drained. I'd like to see if there's anything in the TX queue when the NIC is reset. Chances are there are; I'd like to see what it is and whether it's completed or not. Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 20:27:32 2012 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 ED4081065670; Thu, 2 Feb 2012 20:27:32 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 716818FC0C; Thu, 2 Feb 2012 20:27:32 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:24ed:86dc:9f3b:9149]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id F30DF4AC2D; Fri, 3 Feb 2012 00:27:30 +0400 (MSK) Date: Fri, 3 Feb 2012 00:27:26 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <208667374.20120203002726@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <743722267.20120202195757@serebryakov.spb.ru> <1292923023.20120202232810@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: "ath0: device timeout" when environment is clear 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, 02 Feb 2012 20:27:33 -0000 Hello, Adrian. You wrote 2 =F4=E5=E2=F0=E0=EB=FF 2012 =E3., 23:32:17: > Please file a bug so I don't forget. I'll do this several hours later. > What you can do is flip on reset debugging in the driver (look at > if_ath_debug.h for ATH_DEBUG_RESET) - not the HAL debugging, just > the reset debugging) - that should make ath_draintxq() print out the > contents of the TX queue before its drained. > I'd like to see if there's anything in the TX queue when the NIC is > reset. Chances are there are; I'd like to see what it is and whether > it's completed or not. Here it is ath0: stuck beacon; resetting (bmiss count 4) ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x212fb40, link 0 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0x20beb40, link 0 ar5212StopDmaReceive: dma failed to stop in 10ms AR_CR=3D0x00000024 AR_DIAG_SW=3D0x42000020 ath_stoprecv: rx queue 0x1b96480, link 0xcdb96420 ath0: stuck beacon; resetting (bmiss count 4) ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20bc780, link 0xd58c6420 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0x20fe3c0, link 0 ath_stoprecv: rx queue 0x1b90660, link 0xcdb90600 ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20c63c0, link 0xd58b5060 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0, link 0 ath_stoprecv: rx queue 0x1b94d20, link 0xcdb94c00 R[ 0] (DS.V:0xcdb94c60 DS.P:0x1b94c60) L:01b94cc0 D:18d33000 ! aa55aa55 00000800 1b800005 0000013a ath0: ath_start: sc_inreset_cnt > 0; bailing 008b0a6d 00000100 06808080 80808080 80808080 80808080 00000005 R[ 1] (DS.V:0xcdb94cc0 DS.P:0x1b94cc0) L:01b94d20 D:137c6000 * aa55aa55 00000800 1b800b10 00000031 008b3700 00000100 11808080 80808080 80808080 80808080 00000003 ath0: ath_raw_xmit: sc_inreset_cnt > 0; bailing ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20b5000, link 0xd58c57e0 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0, link 0 ath_stoprecv: rx queue 0x1b977e0, link 0xcdb976c0 R[ 0] (DS.V:0xcdb97720 DS.P:0x1b97720) L:01b97780 D:08942000 * aa55aa55 00000800 1b800a0c 00000112 004cddcf 00000100 0e808080 80808080 80808080 80808080 00000003 R[ 1] (DS.V:0xcdb97780 DS.P:0x1b97780) L:01b977e0 D:136f1000 * aa55aa55 00000800 1b800304 000000a2 004cf785 00000100 06808080 80808080 80808080 80808080 00000003 ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20c5780, link 0xd58b2060 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0, link 0 ath_stoprecv: rx queue 0x1b8e600, link 0xcdb8e540 R[ 0] (DS.V:0xcdb8e5a0 DS.P:0x1b8e5a0) L:01b8e600 D:13706000 ! aa55aa55 00000800 1b800f0a 0000008e 004d8f1e 00000100 11808080 80808080 80808080 80808080 00000611 ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20b2000, link 0xd58cb420 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0, link 0 ath_stoprecv: rx queue 0x1b922a0, link 0xcdb92180 R[ 0] (DS.V:0xcdb921e0 DS.P:0x1b921e0) L:01b92240 D:18ced000 * aa55aa55 00000800 1b80060e 00000112 006b3c79 00000100 0f808080 80808080 80808080 80808080 00000003 R[ 1] (DS.V:0xcdb92240 DS.P:0x1b92240) L:01b922a0 D:136e0800 * aa55aa55 00000800 1b800306 000000a2 006b536b 00000100 08808080 80808080 80808080 80808080 00000003 ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20cb3c0, link 0xd58c9b40 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0, link 0 ath_stoprecv: rx queue 0x1b95420, link 0xcdb95360 R[ 0] (DS.V:0xcdb953c0 DS.P:0x1b953c0) L:01b95420 D:18d1c000 * aa55aa55 00000800 1b80040a 00000112 007aafb5 00000100 0b808080 80808080 80808080 80808080 00000003 ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20c9b40, link 0xd592f420 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0x20ca780, link 0 ath_stoprecv: rx queue 0x1b98e40, link 0xcdb98de0 ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x212f3c0, link 0xd592ab40 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0x20bcb40, link 0 ath_stoprecv: rx queue 0x1b95420, link 0xcdb95360 R[ 0] (DS.V:0xcdb953c0 DS.P:0x1b953c0) L:01b95420 D:18c5a000 * aa55aa55 00000800 1b80090e 00000112 01227240 00000100 0f808080 80808080 80808080 80808080 00000003 ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x212ab40, link 0xd58cf780 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0, link 0 ath_stoprecv: rx queue 0x1b99540, link 0xcdb99480 R[ 0] (DS.V:0xcdb994e0 DS.P:0x1b994e0) L:01b99540 D:1374a000 * aa55aa55 00000800 1b80070c 00000112 00a885b6 00000100 0d808080 80808080 80808080 80808080 00000003 ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20cf780, link 0xd58e2000 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0, link 0 ath_stoprecv: rx queue 0x1b95180, link 0xcdb95060 R[ 0] (DS.V:0xcdb950c0 DS.P:0x1b950c0) L:01b95120 D:17100000 * aa55aa55 00000800 1b80110c 00000147 01045026 00000100 12808080 80808080 80808080 80808080 00000003 R[ 1] (DS.V:0xcdb95120 DS.P:0x1b95120) L:01b95180 D:18cbf800 ! aa55aa55 00000800 1b80070a 0000006a 01045e67 00000100 0c808080 80808080 80808080 80808080 00000005 ath0: ath_tx_tid_drain: node 0xc4d8b000: tid 16: txq_depth=3D28, txq_aggr_d= epth=3D0, sched=3D0, paused=3D0, hwq_depth=3D0, incomp=3D0, baw_head=3D0, b= aw_tail=3D0 txa_start=3D-1, ni_txseqs=3D11 FRDS f4:ec:38:a3:10:6d->00:18:de:08:e8:1d(f4:ec:38:a3:10:6d) data WEP [IV 7= c 99 00 05 00 00 KID 0] 0M 0842 3a01 0018 de08 e81d f4ec 38a3 106d f4ec 38a3 106d 6000 7c99 0020 0500= 0000 aaaa 0300 0000 888e ath0: device timeout ath0: ath_reset: called ath0: ath_stoptxdma: tx queue [9] 0x1b9b000, link 0 ath0: ath_tx_stopdma: tx queue [0] 0, link 0 ath0: ath_tx_stopdma: tx queue [1] 0x20e2000, link 0xd58baba0 ath0: ath_tx_stopdma: tx queue [2] 0, link 0 ath0: ath_tx_stopdma: tx queue [3] 0, link 0 ath0: ath_tx_stopdma: tx queue [8] 0, link 0 ath_stoprecv: rx queue 0x1b98840, link 0xcdb987e0 --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 2 21:46:58 2012 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 9148E1065678 for ; Thu, 2 Feb 2012 21:46:58 +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 4C4B18FC20 for ; Thu, 2 Feb 2012 21:46:58 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so3227404vbb.13 for ; Thu, 02 Feb 2012 13:46:57 -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; bh=8DNkJRu55+QdeQTWOkyNRs7wmB8aVC6LmTqU50asPzA=; b=vBKSrvLWCW+hLwsFMyZkKv46j2Mut4kkaqwTqSXHlPo6uXt6vKo6pihIx0yiO477FQ 7ObLQBcRei8ZKX7MiYn4hoyGZEssVHbe/SbgPJhyp/uDVGuE56ZGeNlkPTYbup6XNIyi AQQcHh6ER6nEtzIsjaRIHMeGpazxULZKq9qSI= MIME-Version: 1.0 Received: by 10.52.26.199 with SMTP id n7mr2184607vdg.17.1328219217672; Thu, 02 Feb 2012 13:46:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Thu, 2 Feb 2012 13:46:57 -0800 (PST) In-Reply-To: <208667374.20120203002726@serebryakov.spb.ru> References: <743722267.20120202195757@serebryakov.spb.ru> <1292923023.20120202232810@serebryakov.spb.ru> <208667374.20120203002726@serebryakov.spb.ru> Date: Thu, 2 Feb 2012 13:46:57 -0800 X-Google-Sender-Auth: v3YWimJrXPK1c7-9UkniYx9C6BU Message-ID: From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: "ath0: device timeout" when environment is clear 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, 02 Feb 2012 21:46:58 -0000 Hi, The lack of TX buffers in that list (they're all RX buffers) means that the TX queue is empty. So, the "device timeout" is incorrect - the device didn't timeout, we just didn't queue any frames to the device but somehow the TX watchdog was set. Or, the watchdog wasn't cleared upon TX queue processing. I wonder why this is occuring. ;-) Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 3 07:00:29 2012 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 337ED1065670; Fri, 3 Feb 2012 07:00:29 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B781A8FC1B; Fri, 3 Feb 2012 07:00:28 +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 q1370SF4002404; Fri, 3 Feb 2012 07:00:28 GMT (envelope-from lev@freefall.freebsd.org) Received: (from lev@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1370SPc002400; Fri, 3 Feb 2012 07:00:28 GMT (envelope-from lev) Date: Fri, 3 Feb 2012 07:00:28 GMT Message-Id: <201202030700.q1370SPc002400@freefall.freebsd.org> To: lev@FreeBSD.org, adrian@FreeBSD.org, freebsd-wireless@FreeBSD.org From: lev@FreeBSD.org Cc: Subject: Re: kern/164721: [ath] ath device timeouts 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, 03 Feb 2012 07:00:29 -0000 Synopsis: [ath] ath device timeouts Responsible-Changed-From-To: adrian->freebsd-wireless Responsible-Changed-By: lev Responsible-Changed-When: Fri Feb 3 07:00:03 UTC 2012 Responsible-Changed-Why: Adrian's request http://www.freebsd.org/cgi/query-pr.cgi?pr=164721 From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 3 07:03:11 2012 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 A93AF106564A; Fri, 3 Feb 2012 07:03:11 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 41B558FC16; Fri, 3 Feb 2012 07:03:11 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:24ed:86dc:9f3b:9149]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 70ECC4AC2D; Fri, 3 Feb 2012 11:03:09 +0400 (MSK) Date: Fri, 3 Feb 2012 11:03:04 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1167992329.20120203110304@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <743722267.20120202195757@serebryakov.spb.ru> <1292923023.20120202232810@serebryakov.spb.ru> <208667374.20120203002726@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: "ath0: device timeout" when environment is clear X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org 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, 03 Feb 2012 07:03:11 -0000 Hello, Adrian. You wrote 3 =F4=E5=E2=F0=E0=EB=FF 2012 =E3., 1:46:57: > The lack of TX buffers in that list (they're all RX buffers) means > that the TX queue is empty. > So, the "device timeout" is incorrect - the device didn't timeout, > we just didn't queue any frames to the device but somehow the TX > watchdog was set. Or, the watchdog wasn't cleared upon TX queue > processing. > I wonder why this is occuring. =20 Is here any additional diagnostic I could do? BTW, here are a lot of "stuck beacon" too, but these don't break file tra= nsfer, only slow it. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 3 07:07:32 2012 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 437E31065670; Fri, 3 Feb 2012 07:07:32 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 1190D8FC0A; Fri, 3 Feb 2012 07:07:31 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q1377Vta070087; Thu, 2 Feb 2012 23:07:31 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q1377Vi8070086; Thu, 2 Feb 2012 23:07:31 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Adrian Chadd Message-Id: <1328252851.70081@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 In-Reply-To: Date: Thu, 02 Feb 2012 23:07:31 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1328252851" Cc: FreeBSD Wireless Subject: Re: possible issue 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: Fri, 03 Feb 2012 07:07:32 -0000 This is a multi-part message in MIME format. --bound1328252851 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adrian Chadd wrote .. > :-) Cool. 11n should just be working though! > > > Adrian > You definitely make a good point there, I totally agree. OK, I think I have 11n running over 2.4GHz(11a?) but not 5GHz/11n -- Is This Not possible? not sure going faster than 54M is happenin. this works... i found one of your test scripts online and pulled out some pieces. :) ifconfig wlan0 create wlandev ath0 ssid BOOTAY ifconfig wlan0 channel 9:ht/20 ifconfig wlan0 ampdudensity 8 wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf ifconfig wlan0 inet 10.0.0.20 netmask 255.255.255.0 ifconfig wlan0 up scan BUT this = no worky. ifconfig wlan0 create wlandev ath0 ssid DARKNET ifconfig wlan0 channel 36:ht/40 ifconfig wlan0 ampdudensity 8 wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant-darknet.conf ifconfig wlan0 inet 10.0.0.20 netmask 255.255.255.0 ifconfig wlan0 up scan SSID/MESH ID BSSID CHAN RATE S:N INT CAPS DARKNET 1c:7e:e5:de:ed:52 36 54M -76:-96 100 EP WPS HTCAP WPA RSN WME ath0: flags=8843 metric 0 mtu 2290 ether 00:22:43:19:35:21 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: associated wlan0: flags=8c43 metric 0 mtu 1500 ether 00:22:43:19:35:21 inet 10.0.0.20 netmask 0xffffff00 broadcast 10.0.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid DARKNET channel 36 (5180 MHz 11a) regdomain 96 indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF txpower 30 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 12 wme burst roaming MANUAL ath0=ass.ociated wlan0= no carrier :( Thanks! -- Waitman Gobble San Jose California USA --bound1328252851-- From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 3 07:09:26 2012 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 9C6FE106564A; Fri, 3 Feb 2012 07:09:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3A4D08FC1A; Fri, 3 Feb 2012 07:09:25 +0000 (UTC) Received: by vcmm1 with SMTP id m1so3722857vcm.13 for ; Thu, 02 Feb 2012 23:09:25 -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; bh=KnDEhU32vp1me1wa8bt8wtfG1962IMqtisvB01nhKww=; b=GV53YlFzmgoNpQORCL42/4+SQ2UHzp9f9ATAwHc6heTWd4Yg9Xq6FFutTOA5/Tgopu TkpsfxTZLALx/A5yjAc+Jo9wGIE4rey/IawyV2QLYEesDceHOjSGSR1d/Ru14em2nqaA vs7eyhit1eqH3lv2EdNpxOU+h/RCnVy/FqPG0= MIME-Version: 1.0 Received: by 10.52.66.166 with SMTP id g6mr2773872vdt.34.1328252965224; Thu, 02 Feb 2012 23:09:25 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Thu, 2 Feb 2012 23:09:25 -0800 (PST) In-Reply-To: <1167992329.20120203110304@serebryakov.spb.ru> References: <743722267.20120202195757@serebryakov.spb.ru> <1292923023.20120202232810@serebryakov.spb.ru> <208667374.20120203002726@serebryakov.spb.ru> <1167992329.20120203110304@serebryakov.spb.ru> Date: Thu, 2 Feb 2012 23:09:25 -0800 X-Google-Sender-Auth: q4HEmSYazi30aH7Y79uBvEZE2gk Message-ID: From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: "ath0: device timeout" when environment is clear 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, 03 Feb 2012 07:09:26 -0000 Hi, I'm not really able to suggest any specific diagnosis. I'd just be debugging it and trying to figure out why exactly it's occuring. There's only two places where TX "starts" - ath_start() and ath_raw_xmit(). The watchdog timer is bumped there. The questions are: * is it being bumped but no frame is being queued (eg because aggregation is somehow hanging); * is it being bumped but not cleared correctly; * is it being bumped but the TX interrupt is being missed (which would show up as frames in the TX queue, which you would've seen in previous debugging); * is there a race condition between ath_start( )/ath_raw_xmit() and the TX completion task, which is causing it to be set whe nthere's no frames queued (due to a lack of locking there..) I'm still knee deep in work code (hi radars and DFS!) so I can't really dedicate any further time to figuring this stuff out. But there's a lot of weird and wonderful locking issues in ath and net80211. Sigh. Is this running on a multi-core/CPU box, or is it single-core? Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 04:26:03 2012 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 4CA57106566C for ; Sat, 4 Feb 2012 04:26:03 +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 052048FC08 for ; Sat, 4 Feb 2012 04:26:02 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so4641029vbb.13 for ; Fri, 03 Feb 2012 20:26:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=dc07scrBAXrKMucDk6BOthm5u5wqTrwLRvTc4gb6XV8=; b=sIFwuO1vHYCxGl5q+5Cr5PW7/htKZHf+UQvHQcqxFjofhrheIYCJ5U3C3IBqaNFP8o oNkHFJE6IF/H2UPBlD3gDFlYWDkBe6oAEDpcWXbNub9rmFau7WBvkwGCw9p0I0VawqxF PaCwlmi5+SdLus/kFTRvenReCovwZuNnJzEZg= MIME-Version: 1.0 Received: by 10.52.66.166 with SMTP id g6mr5133940vdt.34.1328329562275; Fri, 03 Feb 2012 20:26:02 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Fri, 3 Feb 2012 20:26:02 -0800 (PST) Date: Fri, 3 Feb 2012 20:26:02 -0800 X-Google-Sender-Auth: xMNkvz8Z71JwLgWDGjhuFQQD9pI Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: multipart/mixed; boundary=20cf307f3092b43fc504b81bd36f Subject: [net80211] support vendor bitmap entries; teach if_ath to export PHY error code in error frames 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, 04 Feb 2012 04:26:03 -0000 --20cf307f3092b43fc504b81bd36f Content-Type: text/plain; charset=ISO-8859-1 Hi, As part of my radar project, I'm going to try and teach the BSD/Linux ath driver and radiotap API about vendor extensions and implement a (reasonably) well documented way to expose what I need. The driver already exports the whole PHY error frame payload via radiotap and you can select which PHY error types are passed up by setting bits in the dev.ath.X.monpass sysctl. The trouble is the PHY error code isn't exposed so it currently isn't possible to know whether its a data or a PHY error frame. This patch is a WIP and implements what I need. In short: * The net80211 radiotap code doesn't know about vendor extension bitmap(s), so there's currently no way to take those into account when calculating the channel state offset in the header. Since the radiotap code directly writes into that (rather than have the driver do it per frame), adding any vendor bitmaps does mess things up quite a bit. * define a vendor attribute in if_athioctl.h - this should move to ieee80211_radiotap.h at some point. * Add fields to the ath RX radiotap struct, which includes the vendor bitmap, vendor attribute and the vendor payload. * Add a vendor payload, which includes the Atheros OUI and the RX status + PHY error code. With this, userland tools can be built to read the radar and spectral scan PHY error frames in userland. It makes prototyping code much, much easier. What I'm going to do to this: * Move the vendor attribute definition into ieee80211_radiotap.h; * Finalise on the Atheros vendor attribute layout. It doesn't match what is used in the reference driver but I'll use different vendor bitmap/namespace bytes, so things won't clash. * Document the new ieee80211_radiotap_attachv() and why it exists. I'd appreciate some feedback. Thanks! Adrian --20cf307f3092b43fc504b81bd36f Content-Type: text/x-patch; charset=US-ASCII; name="net80211-ath-radiotap-phyerr.diff" Content-Disposition: attachment; filename="net80211-ath-radiotap-phyerr.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_gy8545hf0 SW5kZXg6IG5ldDgwMjExL2llZWU4MDIxMV92YXIuaAo9PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBuZXQ4MDIxMS9p ZWVlODAyMTFfdmFyLmgJKHJldmlzaW9uIDIzMDg1NSkKKysrIG5ldDgwMjExL2llZWU4MDIxMV92 YXIuaAkod29ya2luZyBjb3B5KQpAQCAtNzAwLDYgKzcwMCwxMSBAQAogCQl1aW50MzJfdCB0eF9y YWRpb3RhcCwKIAkgICAgc3RydWN0IGllZWU4MDIxMV9yYWRpb3RhcF9oZWFkZXIgKnJoLCBpbnQg cmxlbiwKIAkJdWludDMyX3QgcnhfcmFkaW90YXApOwordm9pZAlpZWVlODAyMTFfcmFkaW90YXBf YXR0YWNodihzdHJ1Y3QgaWVlZTgwMjExY29tICosCisJICAgIHN0cnVjdCBpZWVlODAyMTFfcmFk aW90YXBfaGVhZGVyICp0aCwKKwkgICAgaW50IHRsZW4sIGludCBuX3R4X3YsIHVpbnQzMl90IHR4 X3JhZGlvdGFwLAorCSAgICBzdHJ1Y3QgaWVlZTgwMjExX3JhZGlvdGFwX2hlYWRlciAqcmgsCisJ ICAgIGludCBybGVuLCBpbnQgbl9yeF92LCB1aW50MzJfdCByeF9yYWRpb3RhcCk7CiB2b2lkCWll ZWU4MDIxMV9yYWRpb3RhcF9kZXRhY2goc3RydWN0IGllZWU4MDIxMWNvbSAqKTsKIHZvaWQJaWVl ZTgwMjExX3JhZGlvdGFwX3ZhdHRhY2goc3RydWN0IGllZWU4MDIxMXZhcCAqKTsKIHZvaWQJaWVl ZTgwMjExX3JhZGlvdGFwX3ZkZXRhY2goc3RydWN0IGllZWU4MDIxMXZhcCAqKTsKSW5kZXg6IG5l dDgwMjExL2llZWU4MDIxMV9yYWRpb3RhcC5jCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIG5ldDgwMjExL2llZWU4 MDIxMV9yYWRpb3RhcC5jCShyZXZpc2lvbiAyMzA4NTUpCisrKyBuZXQ4MDIxMS9pZWVlODAyMTFf cmFkaW90YXAuYwkod29ya2luZyBjb3B5KQpAQCAtNDcsMTMgKzQ3LDI0IEBACiAKICNpbmNsdWRl IDxuZXQ4MDIxMS9pZWVlODAyMTFfdmFyLmg+CiAKLXN0YXRpYyBpbnQgcmFkaW90YXBfb2Zmc2V0 KHN0cnVjdCBpZWVlODAyMTFfcmFkaW90YXBfaGVhZGVyICosIGludCk7CitzdGF0aWMgaW50IHJh ZGlvdGFwX29mZnNldChzdHJ1Y3QgaWVlZTgwMjExX3JhZGlvdGFwX2hlYWRlciAqLCBpbnQsIGlu dCk7CiAKIHZvaWQKIGllZWU4MDIxMV9yYWRpb3RhcF9hdHRhY2goc3RydWN0IGllZWU4MDIxMWNv bSAqaWMsCiAJc3RydWN0IGllZWU4MDIxMV9yYWRpb3RhcF9oZWFkZXIgKnRoLCBpbnQgdGxlbiwg dWludDMyX3QgdHhfcmFkaW90YXAsCiAJc3RydWN0IGllZWU4MDIxMV9yYWRpb3RhcF9oZWFkZXIg KnJoLCBpbnQgcmxlbiwgdWludDMyX3QgcnhfcmFkaW90YXApCiB7CisJaWVlZTgwMjExX3JhZGlv dGFwX2F0dGFjaHYoaWMsIHRoLCB0bGVuLCAwLCB0eF9yYWRpb3RhcCwKKwkgICAgcmgsIHJsZW4s IDAsIHJ4X3JhZGlvdGFwKTsKK30KKwordm9pZAoraWVlZTgwMjExX3JhZGlvdGFwX2F0dGFjaHYo c3RydWN0IGllZWU4MDIxMWNvbSAqaWMsCisJc3RydWN0IGllZWU4MDIxMV9yYWRpb3RhcF9oZWFk ZXIgKnRoLAorCWludCB0bGVuLCBpbnQgbl90eF92LCB1aW50MzJfdCB0eF9yYWRpb3RhcCwKKwlz dHJ1Y3QgaWVlZTgwMjExX3JhZGlvdGFwX2hlYWRlciAqcmgsCisJaW50IHJsZW4sIGludCBuX3J4 X3YsIHVpbnQzMl90IHJ4X3JhZGlvdGFwKQorewogI2RlZmluZQlCKF92KQkoMTw8KF92KSkKIAlp bnQgb2ZmOwogCkBAIC02Myw5ICs3NCw5IEBACiAJLyogY2FsY3VsYXRlIG9mZnNldCB0byBjaGFu bmVsIGRhdGEgKi8KIAlvZmYgPSAtMTsKIAlpZiAodHhfcmFkaW90YXAgJiBCKElFRUU4MDIxMV9S QURJT1RBUF9DSEFOTkVMKSkKLQkJb2ZmID0gcmFkaW90YXBfb2Zmc2V0KHRoLCBJRUVFODAyMTFf UkFESU9UQVBfQ0hBTk5FTCk7CisJCW9mZiA9IHJhZGlvdGFwX29mZnNldCh0aCwgbl90eF92LCBJ RUVFODAyMTFfUkFESU9UQVBfQ0hBTk5FTCk7CiAJZWxzZSBpZiAodHhfcmFkaW90YXAgJiBCKElF RUU4MDIxMV9SQURJT1RBUF9YQ0hBTk5FTCkpCi0JCW9mZiA9IHJhZGlvdGFwX29mZnNldCh0aCwg SUVFRTgwMjExX1JBRElPVEFQX1hDSEFOTkVMKTsKKwkJb2ZmID0gcmFkaW90YXBfb2Zmc2V0KHRo LCBuX3R4X3YsIElFRUU4MDIxMV9SQURJT1RBUF9YQ0hBTk5FTCk7CiAJaWYgKG9mZiA9PSAtMSkg ewogCQlpZl9wcmludGYoaWMtPmljX2lmcCwgIiVzOiBubyB0eCBjaGFubmVsLCByYWRpb3RhcCAw eCV4IiwKIAkJICAgIF9fZnVuY19fLCB0eF9yYWRpb3RhcCk7CkBAIC03OSw5ICs5MCw5IEBACiAJ LyogY2FsY3VsYXRlIG9mZnNldCB0byBjaGFubmVsIGRhdGEgKi8KIAlvZmYgPSAtMTsKIAlpZiAo cnhfcmFkaW90YXAgJiBCKElFRUU4MDIxMV9SQURJT1RBUF9DSEFOTkVMKSkKLQkJb2ZmID0gcmFk aW90YXBfb2Zmc2V0KHJoLCBJRUVFODAyMTFfUkFESU9UQVBfQ0hBTk5FTCk7CisJCW9mZiA9IHJh ZGlvdGFwX29mZnNldChyaCwgbl9yeF92LCBJRUVFODAyMTFfUkFESU9UQVBfQ0hBTk5FTCk7CiAJ ZWxzZSBpZiAocnhfcmFkaW90YXAgJiBCKElFRUU4MDIxMV9SQURJT1RBUF9YQ0hBTk5FTCkpCi0J CW9mZiA9IHJhZGlvdGFwX29mZnNldChyaCwgSUVFRTgwMjExX1JBRElPVEFQX1hDSEFOTkVMKTsK KwkJb2ZmID0gcmFkaW90YXBfb2Zmc2V0KHJoLCBuX3J4X3YsIElFRUU4MDIxMV9SQURJT1RBUF9Y Q0hBTk5FTCk7CiAJaWYgKG9mZiA9PSAtMSkgewogCQlpZl9wcmludGYoaWMtPmljX2lmcCwgIiVz OiBubyByeCBjaGFubmVsLCByYWRpb3RhcCAweCV4IiwKIAkJICAgIF9fZnVuY19fLCByeF9yYWRp b3RhcCk7CkBAIC0yNjAsNyArMjcxLDggQEAKICAqIGtub3duIC0xIGlzIHJldHVybmVkLgogICov CiBzdGF0aWMgaW50Ci1yYWRpb3RhcF9vZmZzZXQoc3RydWN0IGllZWU4MDIxMV9yYWRpb3RhcF9o ZWFkZXIgKnJoLCBpbnQgaXRlbSkKK3JhZGlvdGFwX29mZnNldChzdHJ1Y3QgaWVlZTgwMjExX3Jh ZGlvdGFwX2hlYWRlciAqcmgsCisgICAgaW50IG5fdmVuZG9yX2F0dHJpYnV0ZXMsIGludCBpdGVt KQogewogCXN0YXRpYyBjb25zdCBzdHJ1Y3QgewogCQlzaXplX3QJYWxpZ24sIHdpZHRoOwpAQCAt MzM0LDYgKzM0Niw4IEBACiAJaW50IG9mZiwgaTsKIAogCW9mZiA9IHNpemVvZihzdHJ1Y3QgaWVl ZTgwMjExX3JhZGlvdGFwX2hlYWRlcik7CisJb2ZmICs9IG5fdmVuZG9yX2F0dHJpYnV0ZXMgKiAo c2l6ZW9mKHVpbnQzMl90KSk7CisKIAlmb3IgKGkgPSAwOyBpIDwgSUVFRTgwMjExX1JBRElPVEFQ X0VYVDsgaSsrKSB7CiAJCWlmICgocHJlc2VudCAmICgxPDxpKSkgPT0gMCkKIAkJCWNvbnRpbnVl OwpJbmRleDogZGV2L2F0aC9hdGhfaGFsL2FyNTQxNi9hcjU0MTZfbWlzYy5jCj09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0K LS0tIGRldi9hdGgvYXRoX2hhbC9hcjU0MTYvYXI1NDE2X21pc2MuYwkocmV2aXNpb24gMjMwODU1 KQorKysgZGV2L2F0aC9hdGhfaGFsL2FyNTQxNi9hcjU0MTZfbWlzYy5jCSh3b3JraW5nIGNvcHkp CkBAIC03NzAsNiArNzcwLDcgQEAKIAogCU9TX1JFR19XUklURShhaCwgQVJfUEhZX1JBREFSXzAs IHZhbCB8IEFSX1BIWV9SQURBUl8wX0VOQSk7CiAKKwkvKiBYWFggaXMgdGhpcyBhcm91bmQgdGhl IGNvcnJlY3Qgd2F5PyEgKi8KIAlpZiAocGUtPnBlX3VzZWZpcjEyOCA9PSAxKQogCQlPU19SRUdf Q0xSX0JJVChhaCwgQVJfUEhZX1JBREFSXzEsIEFSX1BIWV9SQURBUl8xX1VTRV9GSVIxMjgpOwog CWVsc2UgaWYgKHBlLT5wZV91c2VmaXIxMjggPT0gMCkKSW5kZXg6IGRldi9hdGgvaWZfYXRoaW9j dGwuaAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09Ci0tLSBkZXYvYXRoL2lmX2F0aGlvY3RsLmgJKHJldmlzaW9uIDIzMDg1 NSkKKysrIGRldi9hdGgvaWZfYXRoaW9jdGwuaAkod29ya2luZyBjb3B5KQpAQCAtMTg4LDEwICsx ODgsNTQgQEAKIAkoMSA8PCBJRUVFODAyMTFfUkFESU9UQVBfREJNX0FOVFNJR05BTCkJfCBcCiAJ KDEgPDwgSUVFRTgwMjExX1JBRElPVEFQX0RCTV9BTlROT0lTRSkJfCBcCiAJKDEgPDwgSUVFRTgw MjExX1JBRElPVEFQX1hDSEFOTkVMKQl8IFwKKwkoMSA8PCBJRUVFODAyMTFfUkFESU9UQVBfVkVO RE9SRVhUKQl8IFwKKwkoMSA8PCBJRUVFODAyMTFfUkFESU9UQVBfRVhUKQkJfCBcCiAJMCkKIAor LyoKKyAqIFRoaXMgaXMgcmVxdWlyZWQgdG8gYmUgYWxpZ25lZCB0byB0d28gYnl0ZXMuCisgKi8K K3N0cnVjdCB2ZW5kb3Jfc3BhY2UgeworCXVfaW50OF90CW91aVszXTsKKwl1X2ludDhfdAlzdWJf bmFtZXNwYWNlOworCXVfaW50MTZfdAlza2lwX2xlbmd0aDsKK30gX19wYWNrZWQ7CisKKy8qCisg KiBUaGlzIGlzIGhpZ2hlciB0aGFuIHRoZSB2ZW5kb3IgYml0bWFwIHVzZWQgaW5zaWRlCisgKiB0 aGUgQXRoZXJvcyByZWZlcmVuY2UgY29kZWJhc2UuCisgKi8KKworLyogQml0IDggKi8KKyNkZWZp bmUJQVRIX1JBRElPVEFQX1ZFTkRPUl9IRUFERVIJOAorCisvKgorICogQVRIX1JBRElPVEFQX1ZF TkRPUl9IRUFERVIKKyAqCisgKiBUaGlzIGlzIHJlcXVpcmVkIHRvIGJlIGFsaWduZWQgdG8gZm91 ciBieXRlcy4KKyAqLworc3RydWN0IGF0aF9yYWRpb3RhcF92ZW5kb3JfaGRyIHsKKwl1X2ludDhf dAl2aF92ZXJzaW9uOwkvKiAxICovCisJdV9pbnQ4X3QJdmhfcGh5ZXJyX2NvZGU7CisJdV9pbnQ4 X3QJdmhfcnN0YXR1czsKKwl1X2ludDhfdAl2aF9wYWQxWzFdOworfSBfX3BhY2tlZDsKKwogc3Ry dWN0IGF0aF9yeF9yYWRpb3RhcF9oZWFkZXIgewotCXN0cnVjdCBpZWVlODAyMTFfcmFkaW90YXBf aGVhZGVyIHdyX2loZHI7CisJc3RydWN0IGllZWU4MDIxMV9yYWRpb3RhcF9oZWFkZXIgd3JfaWhk cjsJLyogOCAqLworCS8qIFZlbmRvciBleHRlbnNpb24gaGVhZGVyIGJpdG1hcCAqLworCXVfaW50 MzJfdAl3cl9leHRfYml0bWFwOwkJLyogNCAqLworCisJLyoKKwkgKiBUaGlzIHBhZGRpbmcgaXMg bmVlZGVkIGJlY2F1c2U6CisJICogKyB0aGUgcmFkaW90YXAgaGVhZGVyIGlzIDggYnl0ZXM7CisJ ICogKyB0aGUgZXh0ZW5zaW9uIGJpdG1hcCBpcyA0IGJ5dGVzOworCSAqICsgdGhlIHRzZiBpcyA4 IGJ5dGVzLCBzbyBpdCBtdXN0IHN0YXJ0IG9uIGFuIDggYnl0ZQorCSAqICAgYm91bmRhcnkuCisJ ICovCisJdV9pbnQzMl90CXdyX3BhZDE7CisKKwkvKiBOb3JtYWwgcmFkaW90YXAgZmllbGRzICov CiAJdV9pbnQ2NF90CXdyX3RzZjsKIAl1X2ludDhfdAl3cl9mbGFnczsKIAl1X2ludDhfdAl3cl9y YXRlOwpAQCAtMjAzLDYgKzI0NywxNyBAQAogCXVfaW50MTZfdAl3cl9jaGFuX2ZyZXE7CiAJdV9p bnQ4X3QJd3JfY2hhbl9pZWVlOwogCWludDhfdAkJd3JfY2hhbl9tYXhwb3c7CisKKwkvKgorCSAq IFZlbmRvciBoZWFkZXIgc2VjdGlvbiwgYXMgcmVxdWlyZWQgYnkgdGhlCisJICogcHJlc2VuY2Ug b2YgdGhlIHZlbmRvciBleHRlbnNpb24gYml0IGFuZCBiaXRtYXAKKwkgKiBlbnRyeS4KKwkgKi8K KwlzdHJ1Y3QgdmVuZG9yX3NwYWNlCQl3cl92aDsJLyogNiBieXRlcyAqLworCisJc3RydWN0IGF0 aF9yYWRpb3RhcF92ZW5kb3JfaGRyCXdyX3Y7CS8qIDQgYnl0ZXMgKi8KKworCS8qIFhYWCBwYWRk aW5nIG5lZWRlZD8gKi8KIH0gX19wYWNrZWQ7CiAKICNkZWZpbmUgQVRIX1RYX1JBRElPVEFQX1BS RVNFTlQgKAkJXApJbmRleDogZGV2L2F0aC9pZl9hdGguYwo9PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBkZXYvYXRo L2lmX2F0aC5jCShyZXZpc2lvbiAyMzA4NTUpCisrKyBkZXYvYXRoL2lmX2F0aC5jCSh3b3JraW5n IGNvcHkpCkBAIC03NjYsMTAgKzc2NiwxNCBAQAogCWljLT5pY19hZGRiYV9zdG9wID0gYXRoX2Fk ZGJhX3N0b3A7CiAJaWMtPmljX2Jhcl9yZXNwb25zZSA9IGF0aF9iYXJfcmVzcG9uc2U7CiAKLQlp ZWVlODAyMTFfcmFkaW90YXBfYXR0YWNoKGljLAotCSAgICAmc2MtPnNjX3R4X3RoLnd0X2loZHIs IHNpemVvZihzYy0+c2NfdHhfdGgpLAorCS8qCisJICogVGhlcmUncyBvbmUgdmVuZG9yIGJpdG1h cCBlbnRyeSBpbiB0aGUgUlggcmFkaW90YXAKKwkgKiBoZWFkZXI7IG1ha2Ugc3VyZSB0aGF0J3Mg dGFrZW4gaW50byBhY2NvdW50LgorCSAqLworCWllZWU4MDIxMV9yYWRpb3RhcF9hdHRhY2h2KGlj LAorCSAgICAmc2MtPnNjX3R4X3RoLnd0X2loZHIsIHNpemVvZihzYy0+c2NfdHhfdGgpLCAwLAog CQlBVEhfVFhfUkFESU9UQVBfUFJFU0VOVCwKLQkgICAgJnNjLT5zY19yeF90aC53cl9paGRyLCBz aXplb2Yoc2MtPnNjX3J4X3RoKSwKKwkgICAgJnNjLT5zY19yeF90aC53cl9paGRyLCBzaXplb2Yo c2MtPnNjX3J4X3RoKSwgMSwKIAkJQVRIX1JYX1JBRElPVEFQX1BSRVNFTlQpOwogCiAJLyoKQEAg LTM4ODQsNiArMzg4OCwzNCBAQAogfQogCiBzdGF0aWMgdm9pZAorYXRoX3J4X3RhcF92ZW5kb3Io c3RydWN0IGlmbmV0ICppZnAsIHN0cnVjdCBtYnVmICptLAorICAgIGNvbnN0IHN0cnVjdCBhdGhf cnhfc3RhdHVzICpycywgdV9pbnQ2NF90IHRzZiwgaW50MTZfdCBuZikKK3sKKwlzdHJ1Y3QgYXRo X3NvZnRjICpzYyA9IGlmcC0+aWZfc29mdGM7CisKKwkvKiBGaWxsIGluIHRoZSBleHRlbnNpb24g Yml0bWFwICovCisJc2MtPnNjX3J4X3RoLndyX2V4dF9iaXRtYXAgPSBodG9sZTMyKDEgPDwgQVRI X1JBRElPVEFQX1ZFTkRPUl9IRUFERVIpOworCisJLyogRmlsbCBpbiB0aGUgdmVuZG9yIGhlYWRl ciAqLworCXNjLT5zY19yeF90aC53cl92aC5vdWlbMF0gPSAweDdmOworCXNjLT5zY19yeF90aC53 cl92aC5vdWlbMV0gPSAweDAzOworCXNjLT5zY19yeF90aC53cl92aC5vdWlbMl0gPSAweDAwOwor CisJLyogWFhYIHdoYXQgc2hvdWxkIHRoaXMgYmU/ICovCisJc2MtPnNjX3J4X3RoLndyX3ZoLnN1 Yl9uYW1lc3BhY2UgPSAwOworCXNjLT5zY19yeF90aC53cl92aC5za2lwX2xlbmd0aCA9CisJICAg IGh0b2xlMTYoc2l6ZW9mKHN0cnVjdCBhdGhfcmFkaW90YXBfdmVuZG9yX2hkcikpOworCisJLyog cGh5ZXJyIGluZm8gKi8KKwlzYy0+c2NfcnhfdGgud3Jfdi52aF92ZXJzaW9uID0gMTsKKwlzYy0+ c2NfcnhfdGgud3Jfdi52aF9yc3RhdHVzID0gcnMtPnJzX3N0YXR1czsKKwlpZiAocnMtPnJzX3N0 YXR1cyAmIEhBTF9SWEVSUl9QSFkpCisJCXNjLT5zY19yeF90aC53cl92LnZoX3BoeWVycl9jb2Rl ID0gcnMtPnJzX3BoeWVycjsKKwllbHNlCisJCXNjLT5zY19yeF90aC53cl92LnZoX3BoeWVycl9j b2RlID0gMDsKK30KKworc3RhdGljIHZvaWQKIGF0aF9yeF90YXAoc3RydWN0IGlmbmV0ICppZnAs IHN0cnVjdCBtYnVmICptLAogCWNvbnN0IHN0cnVjdCBhdGhfcnhfc3RhdHVzICpycywgdV9pbnQ2 NF90IHRzZiwgaW50MTZfdCBuZikKIHsKQEAgLTQxNTYsNiArNDE4OCw3IEBACiAJCQkJbS0+bV9w a3RoZHIubGVuID0gbS0+bV9sZW4gPSBsZW47CiAJCQkJYmYtPmJmX20gPSBOVUxMOwogCQkJCWF0 aF9yeF90YXAoaWZwLCBtLCBycywgcnN0YW1wLCBuZik7CisJCQkJYXRoX3J4X3RhcF92ZW5kb3Io aWZwLCBtLCBycywgcnN0YW1wLCBuZik7CiAJCQkJaWVlZTgwMjExX3JhZGlvdGFwX3J4X2FsbChp YywgbSk7CiAJCQkJbV9mcmVlbShtKTsKIAkJCX0K --20cf307f3092b43fc504b81bd36f-- From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 07:08:12 2012 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 4273F1065670 for ; Sat, 4 Feb 2012 07:08:12 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9B6108FC08 for ; Sat, 4 Feb 2012 07:08:11 +0000 (UTC) Received: by wgbgn7 with SMTP id gn7so1812322wgb.1 for ; Fri, 03 Feb 2012 23:08:10 -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; bh=lBnOjb33CurPaEnhVYzQF07cvAInD4E5AgeMri3nDt8=; b=LTbTHQ+6r30uL2bDmKRZ35CVtgR7DD0NZ1c7fCQykORkosYHFwCXxZWlQUnfKA0nox SCS9+CvT9Yi+WWKIr7hdUvjl/8+tBpWJKS68tRaLo9/EkQxIvmjYTAhY5xp9c3iEQWg9 ikqGJ3A9pnZWjsgjD5W5F3DMbsfUq6LtdcSyw= MIME-Version: 1.0 Received: by 10.180.95.131 with SMTP id dk3mr1706158wib.6.1328339290444; Fri, 03 Feb 2012 23:08:10 -0800 (PST) Received: by 10.223.101.196 with HTTP; Fri, 3 Feb 2012 23:08:10 -0800 (PST) In-Reply-To: <1328252851.70081@da3m0n8t3r.com> References: <1328252851.70081@da3m0n8t3r.com> Date: Fri, 3 Feb 2012 23:08:10 -0800 Message-ID: From: Kevin Oberman To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Wireless Subject: Re: possible issue 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: Sat, 04 Feb 2012 07:08:12 -0000 On Thu, Feb 2, 2012 at 11:07 PM, Waitman Gobble wrote: > Adrian Chadd wrote .. >> :-) Cool. 11n should just be working though! >> >> >> Adrian >> > > You definitely make a good point there, I totally agree. > > OK, I think I have 11n running over 2.4GHz(11a?) but not 5GHz/11n -- Is This Not possible? > not sure going faster than 54M is happenin. You have it wrong. 2.4GHz is 11b/g. 5GHz is 11a. 11n is orthogonal. 11n may be either 11gn or 11an. 'n' is the 802.3 implementation of MIMO, a method of improving performance by using multiple antennae and is not linked to specific frequencies. From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 07:54:11 2012 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 B8DE81065670; Sat, 4 Feb 2012 07:54:11 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 873298FC13; Sat, 4 Feb 2012 07:54:11 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q147sAHt040818; Fri, 3 Feb 2012 23:54:10 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q147sAD0040817; Fri, 3 Feb 2012 23:54:10 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Kevin Oberman Message-Id: <1328342050.40716@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 In-Reply-To: Date: Fri, 03 Feb 2012 23:54:10 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1328342050" Cc: FreeBSD Wireless Subject: Re: possible issue 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: Sat, 04 Feb 2012 07:54:11 -0000 This is a multi-part message in MIME format. --bound1328342050 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Kevin Oberman wrote .. > On Thu, Feb 2, 2012 at 11:07 PM, Waitman Gobble wrote: > > Adrian Chadd wrote .. > >> :-) Cool. 11n should just be working though! > >> > >> > >> Adrian > >> > > > > You definitely make a good point there, I totally agree. > > > > > OK, I think I have 11n running over 2.4GHz(11a?) but not 5GHz/11n -- Is This > Not possible? > > not sure going faster than 54M is happenin. > > You have it wrong. 2.4GHz is 11b/g. 5GHz is 11a. 11n is orthogonal. > 11n may be either 11gn or 11an. 'n' is the 802.3 implementation of > MIMO, a method of improving performance by using multiple antennae and > is not linked to specific frequencies. -- Thanks, I totally appreciate it. I don't know alot about wireless / radio but I'm learning a bit. Hopefully I won't get kicked out of group for being ignorant. I just read through the source code of ath9k (GNU/Linux) and then the FreeBSD ath driver code and picked up a few tidbits. I noticed in if_ath.c #ifdef ATH_ENABLE_11N and then i remembered reading - http://adrianchadd.blogspot.com/2011/09/wireless-update-80211n-development.html except I'm running 10-CURRENT so I mistakenly decided that didn't apply to me... oops. ..rebuilding the kernel now. Also going to try Adrian's recently posted patches for net80211 and ath to see what happens. Waitman Gobble San Jose California USA --bound1328342050-- From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 19:12:06 2012 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 AA067106566C for ; Sat, 4 Feb 2012 19:12:06 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 803E48FC08 for ; Sat, 4 Feb 2012 19:12:06 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q14JC5PA085990; Sat, 4 Feb 2012 11:12:05 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q14JC5Em085989; Sat, 4 Feb 2012 11:12:05 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: "Waitman Gobble" Message-Id: <1328382725.85982@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 In-Reply-To: <1328342050.40716@da3m0n8t3r.com> Date: Sat, 04 Feb 2012 11:12:05 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1328382725" Cc: FreeBSD Wireless Subject: Re: possible issue 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: Sat, 04 Feb 2012 19:12:06 -0000 This is a multi-part message in MIME format. --bound1328382725 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Waitman Gobble wrote .. > Kevin Oberman wrote .. > > On Thu, Feb 2, 2012 at 11:07 PM, Waitman Gobble wrote: > > > Adrian Chadd wrote .. > > >> :-) Cool. 11n should just be working though! > > >> > > >> > > >> Adrian > > >> > > > > > > You definitely make a good point there, I totally agree. > > > > > > > > OK, I think I have 11n running over 2.4GHz(11a?) but not 5GHz/11n -- Is This > > Not possible? > > > not sure going faster than 54M is happenin. > > > > You have it wrong. 2.4GHz is 11b/g. 5GHz is 11a. 11n is orthogonal. > > 11n may be either 11gn or 11an. 'n' is the 802.3 implementation of > > MIMO, a method of improving performance by using multiple antennae and > > is not linked to specific frequencies. > -- > > Thanks, I totally appreciate it. I don't know alot about wireless / radio but I'm > learning a bit. Hopefully I won't get kicked out of group for being ignorant. > > I just read through the source code of ath9k (GNU/Linux) and then the FreeBSD ath > driver code and picked up a few tidbits. I noticed in if_ath.c > > #ifdef ATH_ENABLE_11N > > and then i remembered reading - > > http://adrianchadd.blogspot.com/2011/09/wireless-update-80211n-development.html > > except I'm running 10-CURRENT so I mistakenly decided that didn't apply to me... > oops. > ..rebuilding the kernel now. Also going to try Adrian's recently posted patches > for net80211 and ath to see what happens. > > > > > Waitman Gobble > San Jose California USA Thanks again for your reply Kevin. I think you might be like a founding father of the internet :) For some reason, perhaps only because being a shop rat paid better than flipping burgers, I got into sheet metal in the mid-80's and ended up being in the 'right place at the right time' to design alot of the metal/skin for the stuff, for example att/lucent tdma/gsm/pcs cabs, etc and that broadcomm startup. among others :). It wasn't sexy work, like for example some engineer dude from whipany would show up with a denny's napkin with basic rackmount cabinet dimensions written in green marker, and I'd have to come up with all 130 components in a cad system, and figure out how to make the thing on a production line. I didn't pay much care or attention to the guts that were going into the things, i don't know much about electronics.. Maybe I should have been more into software and electronics then. But I humor myself..., it's kinda funny I think, perhaps a type of 'kurt vonnegut' da! rk humor.. thinking that (as an "artist") my 'work' has been 'seen' by millions of people across the globe, and even many leaders of nations. But it was all ordinary-looking grey boxes, which most people consider ugly hinderances. In this town - San Jose California - they even try to cover up the boxes with 'pretty pictures', i suppose because they are so ugly. anyway, 'glory days' i suppose. Now I'm just trying to get this cheap netbook connected to my AP. :-) and now, OK, got it to work. yay. I do still have some strangeness with ifconfig wlan0 scan.. but i'm now connected to 5GHz 11a HT/40 when I do a scan, my BSSID of 2.4GHz is showing up for 5GHz channel 149, the BSSID of 5GHz is not showing up in the scan, but i'm connected to it. BOOTAY 1c:7e:e5:de:ed:52 149 54M -71:-96 100 EP WPS HTCAP WPA RSN WME (my original email was about both BSSIDs showing in scan as 5GHz but the BOOTAY was vanishing completely.) anyhow, when i tried setting the channel/HT rate ifconfig said ath0 and wlan0 were both associated but I couldn't ping gw. ie. ifconfig wlan0 channel 149:ht/40 when i destroyed wlan0 and recreated without specifying channel/rate it associated and i could ping gw, and get out on the internet. #1 maybe i misunderstand the channel spec:ht/40 config #2 i've just rebuilt the kernel with options ATH_ENABLE_11N (gosh it takes all night to build, i think i really need to look into setting up a penny jar for an SSD drive) and tried it once, for the first time. (SO maybe it's just a weird harold.) anyhow, i'm now connected to 11a p00ntang# uname -a FreeBSD p00ntang.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Feb 4 09:08:09 PST 2012 waitman@p00ntang.waitman.net:/usr/obj/usr/src/sys/AXE i386 ifconfig wlan0 create wlandev ath0 ssid DARKNET wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf ifconfig wlan0 inet 10.0.0.20 netmask 255.255.255.0 ifconfig wlan0 up scan route add default 10.0.0.1 ping 10.0.0.1 64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=1.136 ms woo! ath0: flags=8843 metric 0 mtu 2290 ether 00:22:43:19:35:21 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11na status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:22:43:19:35:21 inet 10.0.0.20 netmask 0xffffff00 broadcast 10.0.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11na status: associated ssid DARKNET channel 149 (5745 MHz 11a ht/40+) bssid 1c:7e:e5:de:ed:52 regdomain 96 indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 30 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 ampdulimit 64k ampdudensity 4 shortgi wme burst roaming MANUAL ..now to see what's going on with those patches i put in from Adrian's email. Have fun. -- Waitman Gobble San Jose California USA --bound1328382725-- From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 20:05:02 2012 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 295EC106566C; Sat, 4 Feb 2012 20:05:02 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id C8B6E8FC1B; Sat, 4 Feb 2012 20:05:01 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q14K51Qn053906; Sat, 4 Feb 2012 12:05:01 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q14K51iE053905; Sat, 4 Feb 2012 12:05:01 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Adrian Chadd Message-Id: <1328385901.53012@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 In-Reply-To: Date: Sat, 04 Feb 2012 12:05:01 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1328385901" Cc: freebsd-wireless@freebsd.org Subject: Re: [net80211] support vendor bitmap entries; teach if_ath to export PHY error code in error frames 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, 04 Feb 2012 20:05:02 -0000 This is a multi-part message in MIME format. --bound1328385901 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adrian Chadd wrote .. > Hi, > > As part of my radar project, I'm going to try and teach the BSD/Linux > ath driver and radiotap API about vendor extensions and implement a > (reasonably) well documented way to expose what I need. > > The driver already exports the whole PHY error frame payload via > radiotap and you can select which PHY error types are passed up by > setting bits in the dev.ath.X.monpass sysctl. The trouble is the PHY > error code isn't exposed so it currently isn't possible to know > whether its a data or a PHY error frame. > > This patch is a WIP and implements what I need. In short: > > * The net80211 radiotap code doesn't know about vendor extension > bitmap(s), so there's currently no way to take those into account when > calculating the channel state offset in the header. Since the radiotap > code directly writes into that (rather than have the driver do it per > frame), adding any vendor bitmaps does mess things up quite a bit. > > * define a vendor attribute in if_athioctl.h - this should move to > ieee80211_radiotap.h at some point. > > * Add fields to the ath RX radiotap struct, which includes the vendor > bitmap, vendor attribute and the vendor payload. > > * Add a vendor payload, which includes the Atheros OUI and the RX > status + PHY error code. > > With this, userland tools can be built to read the radar and spectral > scan PHY error frames in userland. It makes prototyping code much, > much easier. > > What I'm going to do to this: > > * Move the vendor attribute definition into ieee80211_radiotap.h; > * Finalise on the Atheros vendor attribute layout. It doesn't match > what is used in the reference driver but I'll use different vendor > bitmap/namespace bytes, so things won't clash. > * Document the new ieee80211_radiotap_attachv() and why it exists. > > I'd appreciate some feedback. > > Thanks! > > > Adrian I added the patch and rebuilt the kernel, but I'm not sure what kind of feedback you are looking for. Please advise :) Thanks, -- Waitman Gobble San Jose California USA --bound1328385901-- From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 20:35:07 2012 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 8A313106566B for ; Sat, 4 Feb 2012 20:35:07 +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 4087F8FC0C for ; Sat, 4 Feb 2012 20:35:06 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so5036172vbb.13 for ; Sat, 04 Feb 2012 12:35:06 -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; bh=9sZxMGILqgwag18WCV7JkOdlNL0hRoDageJHvvGhcmg=; b=sl9kB9eNmwY1zXroqV7N9CWMU520UYKsSfXbJ35Kf65EQG9qrpGks9dYPiizYJxxmK WFGEr4Xrk+WnW7oyYrJNfP6fLAyLlioA4bNxwqRUBBdsgASdTY15Qwr9v0FCZ96vDPRd 5l4Pj+AhRvqqYbghJ+JAecWo+dnr3QAYr+8UQ= MIME-Version: 1.0 Received: by 10.52.66.166 with SMTP id g6mr6139020vdt.34.1328387706441; Sat, 04 Feb 2012 12:35:06 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Sat, 4 Feb 2012 12:35:06 -0800 (PST) In-Reply-To: <1328385901.53012@da3m0n8t3r.com> References: <1328385901.53012@da3m0n8t3r.com> Date: Sat, 4 Feb 2012 12:35:06 -0800 X-Google-Sender-Auth: 40lpiXZTdqd7W2UIRUt7fswQgcs Message-ID: From: Adrian Chadd To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: [net80211] support vendor bitmap entries; teach if_ath to export PHY error code in error frames 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, 04 Feb 2012 20:35:07 -0000 On 4 February 2012 12:05, Waitman Gobble wrote: >> I'd appreciate some feedback. >> >> Thanks! >> >> >> Adrian > > I added the patch and rebuilt the kernel, but I'm not sure what kind of feedback you are looking for. Please advise :) Just ensure it hasn't broken anything! I haven't yet released any tools to make this do anything useful (publicly), stay tuned. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 20:42:31 2012 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 B3C24106566B; Sat, 4 Feb 2012 20:42:31 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 7D34C8FC12; Sat, 4 Feb 2012 20:42:31 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q14KgUaa020056; Sat, 4 Feb 2012 12:42:30 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q14KgUEw020055; Sat, 4 Feb 2012 12:42:30 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Adrian Chadd Message-Id: <1328388150.58641@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 In-Reply-To: Date: Sat, 04 Feb 2012 12:42:30 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1328388150" Cc: freebsd-wireless@freebsd.org Subject: Re: [net80211] support vendor bitmap entries; teach if_ath to export PHY error code in error frames 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, 04 Feb 2012 20:42:31 -0000 This is a multi-part message in MIME format. --bound1328388150 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adrian Chadd wrote .. > On 4 February 2012 12:05, Waitman Gobble wrote: > > >> I'd appreciate some feedback. > >> > >> Thanks! > >> > >> > >> Adrian > > > > I added the patch and rebuilt the kernel, but I'm not sure what kind of feedback > you are looking for. Please advise :) > > Just ensure it hasn't broken anything! > > I haven't yet released any tools to make this do anything useful > (publicly), stay tuned. > > > Adrian I don't believe it has broken anything. I am getting numerous (alot) info in syslog related to ath0, which I don't recall seeing before the kernel rebuild. But after looking at the patch source code it doesn't appear to be related to the patch. ie, Feb 4 11:52:28 p00ntang kernel: ath0: ath_start: sc_inreset_cnt > 0; bailing (was getting that message alot also before rebuilding) seemingly new: but maybe these were there before and I just missed it. Feb 4 11:52:28 p00ntang kernel: TODS 00:22:43:19:35:21->1c:7e:e5:de:ed:52(1c:7e:e5:de:ed:52) data QoS [TID 0] 0M NODS 00:22:43:19:35:21->ff:ff:ff:ff:ff:ff(ff:ff:ff:ff:ff:ff) probe_req 0M 4000 0000 ffff ffff ffff 0022 4319 3521 ffff ffff ffff f040 0000 0108 8284 8b96 0c12 1824 3014 0100 000f ac04 0100 000f ac04 0100 000f ac02 0000 3204 3048 606c ath0: ath_tx_tid_drain: node 0xc9b23000: tid 16: txq_depth=0, txq_aggr_depth=0, sched=1, paused=0, hwq_depth=0, incomp=0, baw_head=0, baw_tail=0 txa_start=-1, ni_txseqs=1096 -- Waitman Gobble San Jose California USA --bound1328388150-- From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 20:43:57 2012 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 16A52106564A for ; Sat, 4 Feb 2012 20:43: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 BB2008FC0C for ; Sat, 4 Feb 2012 20:43:56 +0000 (UTC) Received: by vbbfa15 with SMTP id fa15so5039080vbb.13 for ; Sat, 04 Feb 2012 12:43: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; bh=APGco5fWygUQzTjBHGFpleOIvF7e0Xark/5FOPpgchk=; b=fuVZ1uGjptTGTdot80HLWoZ156pUtihrrod6fHxtNYV9xZa81t++0SCOzcDNY9Wirs kz+TMw0h3/3THtmejTTaGL80Zn4Hru8fjbhrkwUHlc8qKhEeXkZsiRRdvgvLPiMyD0nT +S81P6IUID7Q4GGZ4dD5NjWWIPIhQTOd8Riys= MIME-Version: 1.0 Received: by 10.52.66.166 with SMTP id g6mr6145925vdt.34.1328388236001; Sat, 04 Feb 2012 12:43:56 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.172.37 with HTTP; Sat, 4 Feb 2012 12:43:55 -0800 (PST) In-Reply-To: <1328388150.58641@da3m0n8t3r.com> References: <1328388150.58641@da3m0n8t3r.com> Date: Sat, 4 Feb 2012 12:43:55 -0800 X-Google-Sender-Auth: Pc0w5y3UPi7k-YPg87eCtE_XUA8 Message-ID: From: Adrian Chadd To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: [net80211] support vendor bitmap entries; teach if_ath to export PHY error code in error frames 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, 04 Feb 2012 20:43:57 -0000 That stuff is due to slightly incorrect handling of things when doing 802.11n. I'll eventually fix that stuff up; I just have higher priority things to fix (that cause kernel panics..) Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 4 20:46:19 2012 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 59E30106566B; Sat, 4 Feb 2012 20:46:19 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 237578FC08; Sat, 4 Feb 2012 20:46:18 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id q14KkIsJ020356; Sat, 4 Feb 2012 12:46:18 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id q14KkIdD020355; Sat, 4 Feb 2012 12:46:18 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" To: Adrian Chadd Message-Id: <1328388378.20159@da3m0n8t3r.com> X-Originating-IP: 75.36.155.21 X-Mailer: Usermin 1.500 In-Reply-To: Date: Sat, 04 Feb 2012 12:46:18 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1328388378" Cc: freebsd-wireless@freebsd.org Subject: Re: [net80211] support vendor bitmap entries; teach if_ath to export PHY error code in error frames 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, 04 Feb 2012 20:46:19 -0000 This is a multi-part message in MIME format. --bound1328388378 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Adrian Chadd wrote .. > On 4 February 2012 12:05, Waitman Gobble wrote: > > >> I'd appreciate some feedback. > >> > >> Thanks! > >> > >> > >> Adrian > > > > I added the patch and rebuilt the kernel, but I'm not sure what kind of feedback > you are looking for. Please advise :) > > Just ensure it hasn't broken anything! > > I haven't yet released any tools to make this do anything useful > (publicly), stay tuned. > > > Adrian btw, setting options ATH_ENABLE_11N (think that must have been the culprit?) and finally connecting 802.11na/5GHz/ht40 is MUCH faster, smokin'.. thanks so much. -- Waitman Gobble San Jose California USA --bound1328388378--