From owner-freebsd-net@FreeBSD.ORG Sun Oct 7 04:36:56 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BECDE106564A; Sun, 7 Oct 2012 04:36:56 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 9F0AC8FC0A; Sun, 7 Oct 2012 04:36:55 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 15C8A5081F; Sat, 6 Oct 2012 21:36:49 -0700 (PDT) To: rpaulo@FreeBSD.org, freebsd-net@FreeBSD.org Date: Sat, 06 Oct 2012 21:36:49 -0700 Message-ID: <8299.1349584609@tristatelogic.com> From: "Ronald F. Guilmette" Cc: Subject: Support for Intel 5100 WiFi ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 04:36:56 -0000 Greetings, Could anybody tell me what the current status is of kernel support for Intel 5100 Wifi? It appears to have been undergoing testing in 2009, but... I have a not-too-terribly-old 8.2-release system installed on my laptop, which I am pretty sure has an Intel 5100 WifI chip, but nothing whatsoever is showing up in the dmesg output that would indicate that the kernel has noticed the presence of the 5100. Also, the man page for iwn(4) is a bit cryptic. It says: This driver requires the firmware built with the iwnfw module to work. OK, so where exactly do I get THAT? I looked in ports and I didn't see anything with that name. From owner-freebsd-net@FreeBSD.ORG Sun Oct 7 05:08:59 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33DE5106566C; Sun, 7 Oct 2012 05:08:59 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 11E0B8FC08; Sun, 7 Oct 2012 05:08:58 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 6FAB25081F; Sat, 6 Oct 2012 22:08:58 -0700 (PDT) To: rpaulo@FreeBSD.org, freebsd-net@FreeBSD.org In-Reply-To: <8299.1349584609@tristatelogic.com> Date: Sat, 06 Oct 2012 22:08:58 -0700 Message-ID: <8608.1349586538@tristatelogic.com> From: "Ronald F. Guilmette" Cc: Subject: Oops! (was: Support for Intel 5100 WiFi ?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 05:08:59 -0000 Regarding my immediately prior mesage... NEVERMIND! I did: kldload if_iwn (based on a suggestion I found on the next) and now, of course, the thing is properly showing up as iwn0. I do still have a couple of questions though... After the kldload, I got message showing me the various data rates available for 801.11a, 802.11b, and 802.11g... up to 54Mbps on that last one, of course. However as I understand it, the Intel 5100 chip is also capable of 802.11n, and furthermore and additionally, it is allegedly dual-band, having the capability to operate in either the 2.4GHz range or in the 5Ghz range. So I'd just like to know if the driver for this chip, either in 8.2-RELEASE or in anything later, supports either 802.11n and/or the 5GHz band. Of course, I'd also like to know if there is support for 40MHz channels, and how one would go about making use of any or all of these enhanced features, if in fact they are supported by the (recent or current) driver. Thanks in advance for any info. From owner-freebsd-net@FreeBSD.ORG Sun Oct 7 08:39:55 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 748D5106564A; Sun, 7 Oct 2012 08:39:55 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mx.techwires.net (mx.techwires.net [IPv6:2001:4d88:100f:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 0E5BD8FC08; Sun, 7 Oct 2012 08:39:54 +0000 (UTC) Received: from amy.lab.techwires.net (dslb-088-067-201-095.pools.arcor-ip.net [88.67.201.95]) by mx.techwires.net (Postfix) with ESMTPSA id 6602B2942E5; Sun, 7 Oct 2012 10:39:53 +0200 (CEST) From: Bernhard Schmidt To: "Ronald F. Guilmette" Date: Sun, 7 Oct 2012 10:40:01 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.7.4; amd64; ; ) References: <8608.1349586538@tristatelogic.com> In-Reply-To: <8608.1349586538@tristatelogic.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201210071040.01104.bschmidt@techwires.net> Cc: freebsd-net@freebsd.org, rpaulo@freebsd.org Subject: Re: Oops! (was: Support for Intel 5100 WiFi ?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 08:39:55 -0000 On Sunday 07 October 2012 07:08:58 Ronald F. Guilmette wrote: > > Regarding my immediately prior mesage... NEVERMIND! > > I did: > > kldload if_iwn > > (based on a suggestion I found on the next) and now, of course, the thing > is properly showing up as iwn0. > > I do still have a couple of questions though... > > After the kldload, I got message showing me the various data rates > available for 801.11a, 802.11b, and 802.11g... up to 54Mbps on that > last one, of course. > > However as I understand it, the Intel 5100 chip is also capable of > 802.11n, and furthermore and additionally, it is allegedly dual-band, > having the capability to operate in either the 2.4GHz range or in the > 5Ghz range. > > So I'd just like to know if the driver for this chip, either in 8.2-RELEASE > or in anything later, supports either 802.11n and/or the 5GHz band. > > Of course, I'd also like to know if there is support for 40MHz channels, > and how one would go about making use of any or all of these enhanced > features, if in fact they are supported by the (recent or current) > driver. > > Thanks in advance for any info. iwn(4) does support 11n, 5GHz and 40MHz channels. Though, it might be better to switch to 9.x as it has received many many enhancements. Using those features is rather easy, it does so by default ;) -- Bernhard From owner-freebsd-net@FreeBSD.ORG Sun Oct 7 10:38:24 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AECFA106564A for ; Sun, 7 Oct 2012 10:38:24 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.18.14]) by mx1.freebsd.org (Postfix) with ESMTP id 399068FC0A for ; Sun, 7 Oct 2012 10:38:23 +0000 (UTC) Received: from [78.35.158.73] (helo=fabiankeil.de) by smtprelay02.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1TKoFT-00072L-0h; Sun, 07 Oct 2012 12:38:15 +0200 Date: Sun, 7 Oct 2012 12:38:09 +0200 From: Fabian Keil To: "Ronald F. Guilmette" Message-ID: <20121007123809.4c6ab2d8@fabiankeil.de> In-Reply-To: <8608.1349586538@tristatelogic.com> References: <8299.1349584609@tristatelogic.com> <8608.1349586538@tristatelogic.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/OGsBBBqoUaGwY1W4xDkq/LJ"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: freebsd-net@FreeBSD.org Subject: Re: Oops! (was: Support for Intel 5100 WiFi ?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 10:38:25 -0000 --Sig_/OGsBBBqoUaGwY1W4xDkq/LJ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Ronald F. Guilmette" wrote: > After the kldload, I got message showing me the various data rates > available for 801.11a, 802.11b, and 802.11g... up to 54Mbps on that > last one, of course. >=20 > However as I understand it, the Intel 5100 chip is also capable of > 802.11n, and furthermore and additionally, it is allegedly dual-band, > having the capability to operate in either the 2.4GHz range or in the > 5Ghz range. Maybe the 11n rates are behind boot_verbose (which I have enabled), but at least on CURRENT they are included in the system messages: fk@r500 ~ $dmesg | grep iwn0: iwn0: mem 0xf4300000-0xf4301fff irq 17 at device 0.0= on pci3 iwn0: attempting to allocate 1 MSI vectors (1 supported) iwn0: using IRQ 257 for MSI iwn0: MIMO 1T2R, MoW, address 00:1e:65:25:5d:3a iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbp= s 36Mbps 48Mbps 54Mbps iwn0: 1T2R iwn0: 11na MCS 20MHz iwn0: MCS 0-7: 6.5Mbps - 65Mbps iwn0: 11na MCS 20MHz SGI iwn0: MCS 0-7: 7Mbps - 72Mbps iwn0: 11na MCS 40MHz: iwn0: MCS 0-7: 13.5Mbps - 135Mbps iwn0: 11na MCS 40MHz SGI: iwn0: MCS 0-7: 15Mbps - 150Mbps 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 Fabian --Sig_/OGsBBBqoUaGwY1W4xDkq/LJ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlBxW5cACgkQBYqIVf93VJ0jwwCeK/T+8wii8pNmqNa/83tutGpm fsgAn1Lq5CoP/CbOAjmCMJWIdAaWAeP/ =3jfX -----END PGP SIGNATURE----- --Sig_/OGsBBBqoUaGwY1W4xDkq/LJ-- From owner-freebsd-net@FreeBSD.ORG Sun Oct 7 21:28:25 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B6551065670 for ; Sun, 7 Oct 2012 21:28:25 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id DAD898FC14 for ; Sun, 7 Oct 2012 21:28:23 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id 63E555081F for ; Sun, 7 Oct 2012 14:28:23 -0700 (PDT) To: freebsd-net@freebsd.org In-Reply-To: <201210071040.01104.bschmidt@techwires.net> Date: Sun, 07 Oct 2012 14:28:23 -0700 Message-ID: <14851.1349645303@tristatelogic.com> From: "Ronald F. Guilmette" Subject: Re: Oops! (was: Support for Intel 5100 WiFi ?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 21:28:25 -0000 In message <201210071040.01104.bschmidt@techwires.net>, Bernhard Schmidt wrote: >iwn(4) does support 11n, 5GHz and 40MHz channels. Though, it might >be better to switch to 9.x as it has received many many enhancements. OK. I suspected that might be the case. I'm glad that I asked! Is the iwn(4) driver in 9.0 pretty good. Or are there some things in 9.1-RC1 (relating to iwn) that I might possibly want/need? (I prefer to stick with official releases, if possible.) >Using those features is rather easy, it does so by default ;) OK. I want to make sure that I understand what you just said. (Please note that I was almost entirely ignorant about the standards and the current state of technology with respect to ALL of this wireless stuff up until about three weeks ago, but I have tried my best to learn since then, so bear with me here.) If I have understood you correctly, then you are saying that, with respect to the decision of whether to use or, alternatively, to not use 11n (falling back to 11g if necessary), *and* with respect to the decision to use or not use 5GHz (falling back to 2.4Ghz if necessary), *and* with respect to the decision of whether to use or not use 40GHz channels (falling back to 20MHz if necessary), the client does not get to make any of its own decisions about any of these things, and it must instead just follow the lead of whatever AP it is trying to connect to. Is that correct? Have I understood you correctly? (Forgive me. I'me really just still feeling my way through all of this stuff.)