https://bugzilla.novell.com/show_bug.cgi?id=330995#c30
--- Comment #30 from Ben Kevan
(In reply to comment #28 from Ben Kevan)
Hi Dave,
Thanks for giving it a try..
Hi Ben,
I had only just begun looking at the src RPM when I noticed that you had already done the work, and I had noticed that they do use vanilla code + patches, but I hadn't gotten far enough to notice that some of the patches weren't being applied correctly.
I just tried your fixed version at my client site where the connection has been OK sometimes but flaky other times, and it now does connect much faster. So, the summary is as follows:
1) home network: WPA, always connected before, but now connects faster
2) Parents home: open, did not connect before, cannot test new module there now.
3) Client network: WEP 64/128-bit passphrase: sometimes connected slowly sometimes not at all, now connects quickly.
As for the LED, the main difference is that in 10.2, Ubuntu, and with your fixed module, the LED issues brief, infrequent flashes when not connected and would be on continuously when connected, whereas with the faulty module, the LED would sometimes be on constantly even when not connected. I did not pay too much attention to signal strength, except that at my parent's house (open network), in Ubuntu the reported signal strength was several dBm stronger than in SuSE 10.3.
I only tried the iwl driver briefly. It connects faster at home and at my client's office, but would not connect to my parent's open AP. Also, at home, it seems to disconnect frequently, so I stopped bothering with it since it is still only development code.
Since you mention it, and since you've gone through the work of creating it, it might be a good idea to post your source RPM. I am planning to try the 2.6.23 kernel, which supposedly addresses another issue I am having in SuSE 10.3 with high current consumption due to the ehci_hcd driver. With the source RPM, it should be easy to generate a binary RPM for any running kernel.
-Dave
Hey Dave, Thanks for the awesome update. The src.rpm is included on this bug report: https://bugzilla.novell.com/attachment.cgi?id=179369 Above is the attachment. I am actually working with Zhu Yi (ipw3945 maintainer, unrelated to suse) to try to get an updated fix (he's going to have me try a trimmed version of the patch orignally applied) to see if it works. Here are his proposed changes: diff --git a/ipw3945.c b/ipw3945.c index ee67e38..605a64f 100644 --- a/ipw3945.c +++ b/ipw3945.c @@ -11774,10 +11774,10 @@ static int ipw_wx_set_essid(struct net_device *dev, IPW_DEBUG_WX("Setting ESSID to ANY\n"); priv->config &= ~CFG_STATIC_ESSID; priv->config |= CFG_ASSOCIATE; - if (!(priv->status & (STATUS_ASSOCIATED | STATUS_ASSOCIATING))) { - IPW_DEBUG_ASSOC - ("Attempting to associate with new " - "parameters.\n"); + if ((priv->config & CFG_ASSOCIATE) && + !(priv->status & (STATUS_ASSOCIATED |STATUS_ASSOCIATING))) { + IPW_DEBUG_ASSOC("Attempting to associate with new " + "parameters.\n"); ipw_associate(priv); } mutex_unlock(&priv->mutex); Also, I have the 2.6.23 Kernel installed from the "Head" repo, and used the KOTD_HEAD ipw3945-kmp, and it seems to work (although I have also turned on WPA on my Wireless Router, just to test if the issue was open encryption vs closed encryption, but I got too busy surf'ing the net and watching tv to test, and forgot to un-install my rpm first.. oh well.. I hope something gets incorporated later, all I know is .. it works for me now :D and hope it's helped you. Also, if you have ssh access to your "parents" computer, you can easily just do a wget --> rpm -Uvh --> and tada.. :o) .. See ya.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.