Chatre, Reinette schrieb: >> Which doesn't help anyone if it does not work. ipw3945 may be >> deprecated in your eyes, but for me it is the only way to make my >> wireless NIC work >> reliably. From my point of view ipw3945 is stable and iwl3945 >> is _alpha_ >> software. > > Please understand that we need to focus limited resources. ipw3945 is deprecated and we focus on iwlwifi, which supports both 3945 and 4965. Unfortunately we have been unable to reproduce your problem. Your unability to reproduce the bug is weird, as I can reproduce this bug every time I try iwl3945, with every version I ever tried and with every kernel I ever tried. Are there different revisions of the 3945 chip which behave differently and maybe you are trying another one? [x86_64][11:24:49][thomas@artin ~]$ (lspci; lspci -n)|grep ^03\:00 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) 03:00.0 0280: 8086:4227 (rev 02) Jerone suggested that it may be something in my software (although a Debian user posted in the bug report that he is also affected, and his "works for me" comment is based on iwl4965, not 3945). Which components of my system are inolved here? - wpa_supplicant: tried versions 0.5.7 to 0.5.9, all the same. Associating always works (only data transmission after that fails), so this seems unlikely. - openssl (which wpa_supplicant depends on): unlikely, as it is only involved in key negotiation - once the connection has been established, it does not do anything related to the actual networking. - glibc: I think I have had more than 5 different versions of glibc installed since I first saw this bug, so a problem here seems unlikely. - gcc: It is used to compile linux and the iwlwifi driver, I am currently using version 4.2.2, I had some 4.1 releases before, all of them with the same results. May compiling with a different version of gcc make the bug go away? Which version are you using in your tests? - linux: tried versions from 2.6.21 (with the Intel mac80211 patch) to 2.6.24, vanilla versions as well as the Archlinux kernel (which includes some patches), all with the same results. - the udev firmware loader: if the firmware is not loaded properly, it may lead to bugs. However, it is simply a script that gives the kernel the firmware data into sysfs, so if there is a problem here, it is in linux. - The firmware files: I have these firmware files installed in /lib/firmware: (with md5sums) 26d10014b09439dc5a8573c2a6f85b0a /lib/firmware/iwlwifi-3945-1.ucode 3afbb112ade3ede3d02e03892ff8a201 /lib/firmware/iwlwifi-3945.ucode I guess iwlwifi uses the first one now. So what other problems could there be on my end? When you test your driver, do you even try if actual data is transmitted after the association process completed? I may have time to test this with the Ubuntu Live CD soon (as he suggested), but I don't think it will make a difference. I am eager to solve this problem, but I don't know where to look anymore.
Attachment:
signature.asc
Description: OpenPGP digital signature
