From: Marcus Furlong <furlongm@hotmail.com>
To: linux-wireless@vger.kernel.org
Subject: RE: RE: iwl3945 problem with 2.6.25-rc9
Date: Fri, 18 Apr 2008 04:03:32 +0100 [thread overview]
Message-ID: <fu931e$k1b$1@ger.gmane.org> (raw)
In-Reply-To: D936D925018D154694D8A362EEB08920043539AE@orsmsx416.amr.corp.intel.com
On Wednesday 16 April 2008 23:55 in
<D936D925018D154694D8A362EEB08920043539AE@orsmsx416.amr.corp.intel.com>,
Chatre, Reinette wrote:
> There seems to be a lot going on through initialization scripts of your
> distribution. Could you disable all that and try to get up and running
> with as little variables as possible? It may be that the interface is
> automatically brought up when the module is loaded - this script should
> be among your network init scripts. Can you disable that? You can load
> the driver with debugging and see through the logs if anything is trying
> to use it. The first goal is to load the driver and not have it do any
> work after initial load.
Ok, I did this now. iwl3945 is now only loaded manually by modprobe, and the
initscript is disabled for wlan0.
> After this follow the following steps (I am assuming you are not using
> security):
> $ /sbin/ip link set dev wlan0 up
> $ iwlist wlan0 scan
> Search for your AP in the above output - should match with your
> wpa_supplicant conf file.
> $ iwconfig wlan0 channel <channel of your AP> ap <MAC of your AP> essid
> <essid of your AP>
> $ iwconfig
> check above output to see if you are associated
> next use your usual net app to get an IP (dhclient?)
>
> Can you associate with the above steps? What do the logs look like?
The dmesg output is here:
https://www.cs.tcd.ie/~furlongm/iwlwifi/2.6.25-dmesg-wirelesstools-only
iwconfig wlan0 said it was associated (connecting to the AP with no security
now):
wlan0 IEEE 802.11g ESSID:"testing"
Mode:Managed Frequency:2.417 GHz Access Point: 00:0F:CC:5E:86:00
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Link Quality=84/100 Signal level=-49 dBm Noise level=-88 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
but it never got an IP address, no matter what timeout I set for the dhcp
client.
iwlist wlan0 scan showed the AP a few times, but mostly found nothing at
all. When it did find APs, it found at most 2-3 APs, whereas the ipw driver
finds 10 or more APs on the same machine.
Marcus.
next prev parent reply other threads:[~2008-04-18 3:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 22:24 iwl3945 problem with 2.6.25-rc9 Marcus Furlong
2008-04-16 18:28 ` Chatre, Reinette
2008-04-16 19:01 ` Marcus Furlong
2008-04-16 19:26 ` Dan Williams
2008-04-16 19:48 ` Marcus Furlong
2008-04-16 20:04 ` Dan Williams
2008-04-16 21:22 ` Chatre, Reinette
2008-04-16 22:05 ` Marcus Furlong
2008-04-16 22:55 ` Chatre, Reinette
2008-04-17 0:06 ` Marcus Furlong
2008-04-18 3:03 ` Marcus Furlong [this message]
2008-04-18 21:46 ` Chatre, Reinette
2008-04-18 21:57 ` Johannes Berg
2008-04-18 22:12 ` Chatre, Reinette
2008-04-18 22:23 ` Brian Morrison
2008-04-18 22:35 ` Chatre, Reinette
2008-04-18 22:38 ` Brian Morrison
2008-04-18 22:37 ` Johannes Berg
2008-04-18 22:39 ` Johannes Berg
2008-04-19 0:28 ` Tomas Winkler
2008-04-19 8:32 ` Johannes Berg
2008-04-19 12:39 ` Vincent C Jones
2008-04-19 13:09 ` Johannes Berg
2008-04-19 13:44 ` Vincent C Jones
2008-04-19 13:48 ` Johannes Berg
2008-04-19 13:51 ` Johannes Berg
2008-04-20 15:33 ` Dan Williams
2008-04-20 15:24 ` Dan Williams
2008-04-20 20:39 ` Tomas Winkler
2008-04-21 0:14 ` Dan Williams
2008-04-21 18:39 ` Tomas Winkler
2008-04-21 19:20 ` Dan Williams
2008-04-21 20:47 ` Tomas Winkler
2008-04-20 15:28 ` Dan Williams
2008-04-19 2:32 ` Marcus Furlong
2008-04-22 23:02 ` Chatre, Reinette
2008-04-23 13:23 ` Marcus Furlong
2008-04-16 23:01 ` Marcus Furlong
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='fu931e$k1b$1@ger.gmane.org' \
--to=furlongm@hotmail.com \
--cc=linux-wireless@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).