On Wed, Jul 2, 2008 at 12:46 PM, Mark V wrote:

On Wed, Jul 2, 2008 at 3:01 PM, Fred A. Miller wrote:

...

The Intel wifi ipw2100 driver is supposed to work fine with 11.0.........but it WON'T connect when an access point is using WPA. Does anyone know if this has been reported....I can't find anything on it. 'Have an idea the driver is broken.........again.

Not sure if this is related? I couldn't see anything obvious in the current bug list - but I'm no linux guru. I don't use wireless, and have disabled/deactivated wireless. However I have always seen the following in my /var/log/messages:

Jul 2 15:39:18 localhost kernel: ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. Jul 2 15:40:12 localhost kernel: ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. Jul 2 15:40:12 localhost kernel: ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. Jul 2 15:41:53 localhost kernel: ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.

The opensuse-network@openssue.org list might give more joy?

Regards Mark

...

Fred

--

I use intel iwl3945 on 11.0. I also feel that something went wrong. I can connect to WPA2 personal. But something strange happen when i ran kismet, it seems it cannot dump / capture traffic any longer like in 10.3. Googling on the net I found this site http://linuxwireless.org/en/users/Drivers and http://ipw2100.sourceforge.net/ . Please pay attention on the kernel version. On 11.0 i think it's already include on kernel. regards, medwinz -- Diogenes - "What I like to drink most is wine that belongs to others." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, Jul 4, 2008 at 11:20 AM, Fred A. Miller wrote:

The 3945 chipset and driver is fine.....NO problems here.....with a bunch of boxen - ALL connecting with WPA/AES. But, the 2100 chipset is older...worked fine with 10.3. It's "busted", again, for 11.0. I may have to put 10.3 on that box or install a diff. distro.

Fred

Yes it works also here. Automatically connected. But I found that I should restart the driver manually to make it works better. # modprobe -r iwl3945 # modprobe iwl3945 then reconnect the AP manually. medwinz -- Bob Hope - "Middle age is when your age starts to show around your middle." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, Jul 4, 2008 at 11:43 PM, John E. Perry wrote:

...

Yes it works also here. Automatically connected. But I found that I should restart the driver manually to make it works better.

# modprobe -r iwl3945 # modprobe iwl3945

then reconnect the AP manually.

I hadn't been following this thread, but I noticed the "3945" while skipping through the messages.

Just before I installed 11.0, my wifi stopped working reliably, so I plugged in the Ethernet. I was planning to troubleshoot the wifi problem sometime RSN, but I noticed this message and tried it.

I'm back on wifi :-).

Now is it clear yet what the problem is?

John Perry

I'm still not sure, is it openSUSE 11 or kernel problem? What i know is that the kernel now implement the new driver for intel which is include on mac80211. There are so many discussion about this on the net. Including the not so well implementation on monitoring mode and so. see: http://linuxwireless.org/ http://tinyshell.be/aircrackng/forum/index.php?topic=2898 Maybe someone from opensuse or novell can give the explanation regards, medwinz -- Simone de Beauvoir - "To catch a husband is an art; to hold him is a job." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Fred A. Miller wrote:

medwinz wrote:

...

...

Yes it works also here. Automatically connected. But I found that I should restart the driver manually to make it works better.

# modprobe -r iwl3945 # modprobe iwl3945

then reconnect the AP manually.

'Works with WPA?

Yes, here. John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Fred A. Miller wrote:

John E. Perry wrote:

...

Fred A. Miller wrote:

...

medwinz wrote:

...

...

Yes it works also here. Automatically connected. But I found that I should restart the driver manually to make it works better.

# modprobe -r iwl3945 # modprobe iwl3945 ^^^^^^^^^^^^^^^^^^^

then reconnect the AP manually. 'Works with WPA?

Yes, here.

ipw2100 or the iwl3945? Of course the latter does work....very well, but the ipw2100 doesn't.

Sorry for the confusion. I thought I'd made it plain that I was crashing someone else's party, which medwinz had already crashed. jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, Jul 6, 2008 at 1:30 PM, medwinz wrote:

On Sun, Jul 6, 2008 at 8:02 AM, John E. Perry wrote:

...

Sorry for the confusion. I thought I'd made it plain that I was crashing someone else's party, which medwinz had already crashed.

jp

No you didn't :) I think it run also in ipw2100 in WPA, i will check and give Fred the result. Just wait because someone else use that laptop :)

Yesterday I update the compat-wireless > http://linuxwireless.org/en/users/Download, and it runs much better. I even can capture the traffic in monitoring mode using Kismet.

I'm sure that ipw2100 also supported on this drivers.

I confirm, even without compat-wireless driver, ipw2200 is working here. Also in WPA2. Here are the lspci, dmesg, and iwlist result linux-vevk:/home/cldk # lspci | grep 2200 06:06.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05) linux-vevk:/home/cldk # dmesg | grep 2200 ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq ipw2200: Copyright(c) 2003-2006 Intel Corporation ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels) ipw2200: Failed to send SCAN_ABORT: Command timed out. ipw2200: Failed to send CARD_DISABLE: Command timed out. ipw2200: Failed to send SCAN_ABORT: Command timed out. ipw2200: Failed to send CARD_DISABLE: Command timed out. ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq ipw2200: Copyright(c) 2003-2006 Intel Corporation ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: Radio Frequency Kill Switch is On: ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels) ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq ipw2200: Copyright(c) 2003-2006 Intel Corporation ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels) linux-vevk:/home/cldk # iwlist eth1 scan eth1 Scan completed : Cell 01 - Address: 00:1E:E5:75:D4:77 ESSID:"gandalf" Protocol:IEEE 802.11bg Mode:Master Frequency:2.462 GHz (Channel 11) Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Quality=84/100 Signal level=-45 dBm IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : CCMP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK Extra: Last beacon: 8ms ago Maybe monitor mode is not working not try yet. But I believe if I use compat-wireless it will work. :) Like iwl3945, I also manually type : # modprobe -r ipw2200 # modprobe ipw2200 reconnect the AP manually. Then it works better :) -- Simone de Beauvoir - "To catch a husband is an art; to hold him is a job." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

medwinz wrote:

.. Like iwl3945, I also manually type :

# modprobe -r ipw2200 # modprobe ipw2200

reconnect the AP manually. Then it works better :)

By the way, I don't have to reconnect anything manually. When I restarted iwl3945 and clicked on kNetworkManager, it showed my router, which, when I clicked on it, connected immediately (well, there's a 5 -- 10 second authorization process for my WPA access). Or is that what you meant by connecting manually? jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Andrew Joakimsen wrote:

insure wpa_supplicant is installed.

On Wed, Jul 2, 2008 at 1:01 AM, Fred A. Miller wrote:

...

The Intel wifi ipw2100 driver is supposed to work fine with 11.0.........but it WON'T connect when an access point is using WPA. Does anyone know if this has been reported....I can't find anything on it. 'Have an idea the driver is broken.........again.

Of course. Fred -- This message originated from a Linux computer using Open Source software: openSuSE Linux 11.0 No Gates, no Windows....just Linux - STABLE & SECURE! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Helmut Schaa wrote:

Am Mittwoch, 2. Juli 2008 07:01:45 schrieb Fred A. Miller:

...

The Intel wifi ipw2100 driver is supposed to work fine with 11.0.........but it WON'T connect when an access point is using WPA. Does anyone know if this has been reported....I can't find anything on it. 'Have an idea the driver is broken.........again.

Did you try to bring the connection up manually? Have a look at [1].

Helmut

[1] http://en.opensuse.org/Tracking_down_wireless_problems

Yes......but, I'll try that again tomorrow. Thanks, Fred -- This message originated from a Linux computer using Open Source software: openSuSE Linux 11.0 No Gates, no Windows....just Linux - STABLE & SECURE! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org