https://bugzilla.novell.com/show_bug.cgi?id=330995#c29
--- Comment #29 from Dave Rosky
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 -- 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.