Intel pro wireless 3945 Suse 11.0

[todos27]

I forgot to mention that I'm using:

uname -a
Linux linux-juan 2.6.25.16-0.1-default #1 SMP 2008-08-21 00:34:25 +0200 x86_64 x86_64 x86_64 GNU/Linux

In advance thanks for your help.

[mnatiello]

Dear forum participants

I have done further tests on my problem. It puzzles me that
nobody encountered this issue before, there are a number of
similar complaints on other forums (ubuntu, etc).

I don't repeat my data, It's in the first post.
The problem with wireless seems to be the following:
Apart from the annoying missing green light and the erratic answers from iwlist, the network configuration using the
standard method with ifup seems to do its job properly:
iwconfig shows the correct access point, and it has spoken with
somebody since it shows also the signal quality, etc.
ifconfig shows the correct associations.
BUT... it doesn't work. Why? I believe that the problem is
that /sbin/route takes over one minute to display the routing
table. Other programs may get tired and timeout? Why route does
this? I don't know. Knowing this may be the solution?
Restarting the network with /etc/init.d/network restart
fixes the route problem and the wireless is up, still with the
erratic iwlist and no green light of course.

With the compat drivers I have green light, correct answer from
iwlist, correct configuration as given by iwconfig and ifconfig
but still slow response from route. It is however worse, because
it does not get better after restarting the network: It is
always slow response and no connection.

Is it possible that nobody has seen this before?
How did everybody else with the same card fix this problem?
Can anybody suggest some path of action?

Thanks,

mnatiello

[Magic31]

I'm not sure if this is mentioned here already.. but good news for the iwl3945 driver in openSUSE 11.1.

With kernel 2.6.27 there is an updated driver. This does support led activity again and the wireless issues that seem to have started with openSUSE 11.0 (switch from ipl3945 to iwl3945) also have been addressed.

I'd urge all that can to test the openSUSE 11.1 Beta 3 coming out this weekend so any issues still in the driver can be reported so we can get a solid iwl driver in 11.1!

Cheers,
Wj

[msharnden]

When you said you loaded the compat-wireless drivers, you followed all the steps listed here - Compat-Wireless Install - especially the make load part. I was experiencing the same issues on a Compaq Presario with the 3945 drivers. The write-up references the wrong download -
Compat-Wireless Drivers (old)

[todos27]

I just tried with ipw-firmware, but didn't work.

I also tried with another ap without any security and didn't work either...

my wireless card can see the aps, but it can't connect to them!

[todos27]

I reinstall Suse 11, made the test for the Internet connection during installantion, updates and now the wireless works.

My advice, re-install!

Good luck and have fun.

[mnatiello]

[QUOTE=msharnden;1883399]When you said you loaded the compat-wireless drivers, you followed all the steps listed here - Compat-Wireless Install - especially the make load part.

Hallo

Thank you for answering. Yes, I followed everything there. I installed-deinstalled-reinstalled the compat drivers some 10-12 times without any success.

To todos27: I also reinstalled suse11.0 without success.

I didn't succeed in installing kernel 2.6.27, I'll wait until
11.1 for that. To upgrade the kernel seems to me like burning
the forest because I can't kill the mosquito. Some sound reason
should exist behind the fact that route takes too long to answer
although it behaves fine after a network restart. Also there
should be a reason behind the erratic response of iwlist. I enabled/disabled hardware scan a couple of times, without
improvement.

Hope somebody sees a way out.

[ecarrow]

I am experiencing similar problems - the interface is functional but will not associate - is this problem associated around the WPA2 standard? It is imperative for security considerations that the iw3945 support WPA2 considering the latest vulnerabilities identified with WPA