iwi3945abg will NOT associate with my UNSECURE wireless connection

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Installing the iwi3945 packges
2. Rebooting and following instructions as given
3. Using the network selector to find and associate with my UNSECURE
connection.

Other details I can give on this is that it's installed in my HP Compaq
6720s and works perfectly with windows, which it obviously will. But I've
seen and read on forums that these, even though they ARE beta drivers, have
the ability to let it connect using unsecure networks.

I applied the eth0 in the network preferences that pop up after the
installation as I'm supposed to, and I run the networkSelector.app to scan
for networks. It sees all the networks my PC see's as well as the card
see's in Windows, but upon trying to connect to any of these say for
instance, the network I want to connect to is listed as:

1)--:--:--:--:-- "Network" (etc)

And I press "1" then press enter as instructed it says "Trying to
associate" underneath but INSTANTLY goes back to the:

1)Turn Card On/Off
2)Scan for Connections
5)Refresh
0)Close Program

(Something to that effect)

Meaning that it never ACTUALLY associates itself with my network, other
important information I can give is that I'm using iDeneb v1.3 on 10.5.5 on
9.5.0 Vanilla Kernel. 

I have also tried the "iDeneb Combo Update Package" to go to 10.5.6 and see
if it worked then but I started to get more kernel panics than anything
else, even after removing and re-installing the iwi3945abg drivers.

If any other information is needed please leave me an e-mail at:
samuel_munro@hotmail.com

I would like to help as much as I can to get this working because this is
the only piece of hardware I need to be functional on Unsecure networks at
least to become my main OS.

Thank you for reading my extensive, yet concise, report on this.

Sam Munro
What version of iwi are you using?

Use the getlogscommand (see downloads) script to capture the driver logs
and post it here.

If you get a kernel panic (driver load or using networkselector):
- boot with option -s
- type sh etc/rc
- wait for the driver finish loading
- call networkselector
- take a picture of the screen and post it

Original issue reported on code.google.com by samuel.m...@gmail.com on 10 Mar 2009 at 3:11

[GoogleCodeExporter]

Any luck with it? I couldn't get the NetworkSelector to do anything with mine 
as well.

Original comment by drumthra...@gmail.com on 15 Mar 2009 at 6:21

[GoogleCodeExporter]

Original comment by jalav...@gmail.com on 12 Jun 2009 at 1:08

• Changed state: Duplicate