From: bnc at netspeed.com.au <bnc@netspeed.com.au>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] getting 11n to work?
Date: Thu, 29 Oct 2009 17:22:59 +1000 [thread overview]
Message-ID: <20091029172259.33ea40cd@bnc.JUSTUS> (raw)
In-Reply-To: <20091028204321.5dee58ad@bnc.JUSTUS>
All,
Just to let you know that after downloading
wireless-testing 2.6.32-rc5-wl-1 I have managed to get a clean
compile:))
Currently running off it with no connection problems.
However, I still cannot get an 11n connection.
The details below are still current. i.e. the mcs only goes to 7.
In addition iwlist gives me
iwlist wlan0 rate
wlan0 unkn info.vendor = 'Atheros Communications Inc.'
pci.product = 'AR9285 Wireless Network Adapter (PCI-Express)'own
bit-rate information.
Current Bit Rate=54 Mb/s
while iw list gives me the details below.
Thanks,
Brian
On Wed, 28 Oct 2009 20:43:21 +1000
<bnc@astronomicalresearchaustralia.org> wrote:
> Hi,
> I have not been able to compile wireless-testing because of the
> stlc45xx error I posted.
> While waiting for a response I decided to do some more
> testing/checking.
>
> I have a laptop with an 11n card in it and running a late kernel. I
> checked the kernel and found that all the 11n stuff has been turned on
> and the ATH9K module, see below, seems to be ok too.
>
> I forced my router, dlink 655-dir, to go to ch 11
> Wireless Radio : Enabled
> 802.11 Mode : Mixed 802.11n and 802.11g
> Channel Width : 40MHz
> Channel : 11
> Secondary Channel : 9
> WISH : Inactive
> Wi-Fi Protected Setup : Disabled
>
> However, it was still connecting at 11g.
> The iw list below shows that the MCS only goes to 7 when I thought it
> should go to 15?
>
> Any thoughts?
> Thanks,
> Brian
>
> uname: 2.6.31.3-1-desktop SUSE 11.2
>
> modinfo
> ath9k
> filename: /lib/modules/2.6.31.3-1-desktop/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko
> license: Dual BSD/GPL description: Support for Atheros
> 802.11n wireless LAN cards. author: Atheros
> Communications srcversion:
> 85E386E1747D45941B8BA0C alias:
> pci:v0000168Cd0000002Bsv*sd*bc*sc*i* alias:
> pci:v0000168Cd0000002Asv*sd*bc*sc*i* alias:
> pci:v0000168Cd00000029sv*sd*bc*sc*i* alias:
> pci:v0000168Cd00000027sv*sd*bc*sc*i* alias:
> pci:v0000168Cd00000024sv*sd*bc*sc*i* alias:
> pci:v0000168Cd00000023sv*sd*bc*sc*i* depends:
> mac80211,ath,cfg80211 vermagic: 2.6.31.3-1-desktop SMP preempt
> mod_unload modversions 686 parm: nohwcrypt:Disable hardware
> encryption (int) parm: btcoex_enable:Enable Bluetooth
> coexistence support (bool)
>
> iwlist wlan0 freq
> wlan0 14 channels in total; available frequencies :
> Channel 01 : 2.412 GHz
> Channel 02 : 2.417 GHz
> Channel 03 : 2.422 GHz
> Channel 04 : 2.427 GHz
> Channel 05 : 2.432 GHz
> Channel 06 : 2.437 GHz
> Channel 07 : 2.442 GHz
> Channel 08 : 2.447 GHz
> Channel 09 : 2.452 GHz
> Channel 10 : 2.457 GHz
> Channel 11 : 2.462 GHz
> Channel 12 : 2.467 GHz
> Channel 13 : 2.472 GHz
> Channel 14 : 2.484 GHz
> Current Frequency=2.442 GHz (Channel 7)
> iw list
> Wiphy phy0
> Band 1:
> HT capabilities: 0x104e
> * 20/40 MHz operation
> * SM PS disabled
> * 40 MHz short GI
> * max A-MSDU len 3839
> * DSSS/CCK 40 MHz
> HT A-MPDU factor: 0x0003 (65535 bytes)
> HT A-MPDU density: 0x0006 (8 usec)
> HT MCS set: ff 00 00 00 00 00 00 00 00 00 00 00 01 00
> 00 00 HT TX/RX MCS rate indexes supported:
> MCS index
> 0 MCS index 1
> MCS index
> 2 MCS index 3
> MCS index
> 4 MCS index 5
> MCS index
> 6 MCS index 7
> Frequencies:
> * 2412 MHz [1] (20.0
> dBm)
> * 2417 MHz [2] (20.0
> dBm)
> * 2422 MHz [3] (20.0
> dBm)
> * 2427 MHz [4] (20.0
> dBm)
> * 2432 MHz [5] (20.0
> dBm)
> * 2437 MHz [6] (20.0
> dBm)
> * 2442 MHz [7] (20.0
> dBm)
> * 2447 MHz [8] (20.0
> dBm)
> * 2452 MHz [9] (20.0
> dBm)
> * 2457 MHz [10] (20.0
> dBm)
> * 2462 MHz [11] (20.0
> dBm)
> * 2467 MHz [12] (20.0 dBm) (passive
> scanning)
> * 2472 MHz [13] (20.0
> dBm)
> * 2484 MHz [14] (20.0 dBm) (passive
> scanning) Bitrates (non-HT):
> * 1.0
> Mbps
> * 2.0 Mbps (short preamble
> supported)
> * 5.5 Mbps (short preamble
> supported)
> * 11.0 Mbps (short preamble
> supported)
> * 6.0
> Mbps
> * 9.0
> Mbps
> * 12.0
> Mbps
> * 18.0
> Mbps
> * 24.0
> Mbps
> * 36.0
> Mbps
> * 48.0
> Mbps
> * 54.0 Mbps
> max # scan SSIDs: 4
> Supported interface modes:
> * IBSS
> * managed
> * AP
> * AP/VLAN
> * monitor
> * mesh point
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
next prev parent reply other threads:[~2009-10-29 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 10:43 [ath9k-devel] getting 11n to work? bnc at astronomicalresearchaustralia.org
2009-10-29 7:22 ` bnc at netspeed.com.au [this message]
2009-10-29 14:51 ` Luis R. Rodriguez
2009-10-30 3:29 ` bnc at netspeed.com.au
2009-10-30 14:31 ` Luis R. Rodriguez
2009-10-30 14:51 ` bnc at netspeed.com.au
2009-10-30 15:03 ` Luis R. Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091029172259.33ea40cd@bnc.JUSTUS \
--to=bnc@netspeed.com.au \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.