From: James Ketrenos <jketreno@linux.intel.com>
To: "Ismail Dönmez" <ismail@pardus.org.tr>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG
Date: Tue, 13 Feb 2007 14:55:45 -0800 [thread overview]
Message-ID: <45D241F1.8040606@linux.intel.com> (raw)
In-Reply-To: <200702131857.02369.ismail@pardus.org.tr>
Ismail Dönmez wrote:
> On Tuesday 13 February 2007 17:10:24 Jeff Chua wrote:
>> On 2/13/07, Ismail Dönmez <ismail@pardus.org.tr> wrote:
>>> Tried this is on a patched 2.6.20 kernel with ipw3945 device and it
>>> always puts the card in 802.11a mode instead of 802.11bg mode.
>>>
>>> Ideas?
>> Before running "iwconfig wlan0 channel 8", the card is set to
>> 802.11a mode. iwconfig shows rate at 54Mb/s. But after setting the
>> channel, it sets to 802.11b mode, and I can't find a way to change
>> from 11Mb/s to 54MB/s.
>>
>> "iwlist eth0 rate" only show up to 11Mb/s.
>>
>> So, my problem is the card is always in 802.11b mode.
>
> So I guess there is a common problem with a/bg modes?
Regardless of what iwconfig reports as the mode or rate, you should be
able to associate to an AP in either spectrum (2.4 or 5.2) using any
valid rate. Once configured and associated, iwconfig should provide
more correct information.
If association is failing, verify that 'iwlist scan' shows the AP and
that you specify everything for the association, eg:
iwconfig wlan0 channel 8 essid MyAP ap 00:13:f0:0d:ca:fe
d80211 will only attempt to associate once -- if it fails, then you need
to currently "de-configure" the device and reconfigure it back to what
you want to associate to. I do that here by chaging the AP BSSID to
something else then changing it back. If you use wpa_supplicant, it
does the re-association attempts for you.
James
next prev parent reply other threads:[~2007-02-13 23:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 21:12 [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG James Ketrenos
2007-02-09 22:14 ` Alon Bar-Lev
2007-02-09 22:26 ` Neil Brown
2007-02-09 21:52 ` James Ketrenos
2007-02-10 3:26 ` Nick Kossifidis
2007-02-09 22:37 ` Stefan Schmidt
2007-02-10 0:46 ` [ipw3945-devel] " Norbert Preining
2007-02-13 23:23 ` James Ketrenos
2007-02-10 13:23 ` Hesse, Christian
2007-02-10 14:25 ` Hesse, Christian
2007-02-12 16:32 ` [ipw3945-devel] " dragoran
2007-02-12 18:35 ` James Ketrenos
2007-02-11 13:19 ` Johannes Berg
2007-02-10 16:22 ` Theodore Tso
2007-02-10 16:39 ` John W. Linville
2007-02-10 17:53 ` [ipw3945-devel] " Pavel Roskin
2007-02-10 22:41 ` John W. Linville
2007-02-10 18:42 ` Michael Buesch
2007-02-13 13:58 ` Ismail Dönmez
2007-02-13 15:10 ` Jeff Chua
2007-02-13 16:57 ` Ismail Dönmez
2007-02-13 22:55 ` James Ketrenos [this message]
2007-02-13 18:13 ` Pavel Machek
2007-02-13 18:36 ` Johannes Berg
2007-02-13 23:18 ` James Ketrenos
2007-02-14 0:16 ` [ipw3945-devel] " James Ketrenos
2007-02-19 22:44 ` Pavel Machek
2007-02-21 6:23 ` iwlwifi warnings Stephen Hemminger
2007-02-21 7:32 ` Randy Dunlap
2007-02-21 19:38 ` Pavel Machek
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=45D241F1.8040606@linux.intel.com \
--to=jketreno@linux.intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=ismail@pardus.org.tr \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).