[Bug 330995] New: Intel Wireless 3945 Not commecting
https://bugzilla.novell.com/show_bug.cgi?id=330995 Summary: Intel Wireless 3945 Not commecting Product: openSUSE 10.3 Version: Final Platform: i386 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ben.kevan@bio-rad.com QAContact: qa@suse.de Found By: Customer I have a wireless Intel 3945 and have all packages installed: rpm -qa | grep ipw ipw-firmware-8-44 ipw3945d-1.7.22-8 ipw3945-kmp-default-1.2.2_2.6.22.5_31-3 However, I am unable to get onto the wireless router (which works on a Windows Box, and worked right before upgrading to openSUSE 10.3). uname -r 2.6.22.5-31-default What the delio.. ? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c1
--- Comment #1 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995
Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c2
Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=330995#c3
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=330995#c4
--- Comment #4 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c5
Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=330995#c6
--- Comment #6 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c7
John Ellis
https://bugzilla.novell.com/show_bug.cgi?id=330995#c8
--- Comment #8 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c9
--- Comment #9 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c10
--- Comment #10 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c11
--- Comment #11 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c12
Chrisopher Heck
https://bugzilla.novell.com/show_bug.cgi?id=330995#c13
--- Comment #13 from Ben Kevan
I had the same problem with the Intel PRO/Wireless 3945ABG in my HP dv2415us laptop. It worked fine with openSUSE 10.2 and locks up at 28% while connecting using 10.3. I read some forum entries suggesting the Network Manager (or KNetWork Manager) that is bundled with 10.3 does not work well with wireless networks in which the SSID is not broadcast. My network SSID was not broadcasting; when I turned the broadcasting on, I was immediately able to connect to the wireless network with my laptop. Even though I now can connect wirelessly to my network and the internet, I would still classify this as CRITICAL, as I would really prefer not to broadcast my SSID, even though I am encrypting it with WPA2.
My SSID is brodcasted, and I don't have any WEP / WPA2 Encryption.. Just locked down via MAC Address -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c14
--- Comment #14 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c15
--- Comment #15 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c16
Dave Rosky
https://bugzilla.novell.com/show_bug.cgi?id=330995#c17
--- Comment #17 from Dave Rosky
https://bugzilla.novell.com/show_bug.cgi?id=330995#c18
--- Comment #18 from Ben Kevan
Ben,
Can you describe briefly how to compile the kernel module? I'm a relative newbie when it comes to compiling kernels/kernel modules.
This bug has been open for 10 days and it's somewhat surprising that there is very little commentary from SuSE personnel. It's hard to believe this isn't affecting a lot of people unless it is hardware dependent.
Dave
Download the tarball source for ieee80211 and ipw3945 go into the ieee80211 folder, type make .. say y to replacing the modules go into the ipw3945 folder and type make copy the new ipw3945.ko file into where it currently is in your kernel (do a locate ipw3945.ko) Then your set. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c19
--- Comment #19 from Dave Rosky
Download the tarball source for ieee80211 and ipw3945
go into the ieee80211 folder, type make .. say y to replacing the modules
go into the ipw3945 folder and type make
copy the new ipw3945.ko file into where it currently is in your kernel (do a locate ipw3945.ko)
Then your set.
Thanks for this info. I've been out of town and fairly busy for a few days but will try it soon. In the interim I also thought of the idea of downloading the source RPM for the ipw3945 kernel module, since SuSE packages it as a separate RPM (as opposed to the source tarball), substituting your source file, and recompiling the RPM. If that works, it would be possible to post an RPM, which might make it a little easier for people to get up and running. I might give this a try and use the source tarballs if it doesn't work. For some reason, the network connects fine on my home WPA network, but it's been a show stopper on my parent's open network. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c20
--- Comment #20 from Ben Kevan
(In reply to comment #18 from Ben Kevan)
Download the tarball source for ieee80211 and ipw3945
go into the ieee80211 folder, type make .. say y to replacing the modules
go into the ipw3945 folder and type make
copy the new ipw3945.ko file into where it currently is in your kernel (do a locate ipw3945.ko)
Then your set.
Thanks for this info. I've been out of town and fairly busy for a few days but will try it soon. In the interim I also thought of the idea of downloading the source RPM for the ipw3945 kernel module, since SuSE packages it as a separate RPM (as opposed to the source tarball), substituting your source file, and recompiling the RPM. If that works, it would be possible to post an RPM, which might make it a little easier for people to get up and running. I might give this a try and use the source tarballs if it doesn't work.
For some reason, the network connects fine on my home WPA network, but it's been a show stopper on my parent's open network.
Yes, I will be doing the same once I have some time.. Do you have a link to the src rpm? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c21
--- Comment #21 from Ben Kevan
priv->config |= CFG_ASSOCIATE; if (!(priv->status & (STATUS_ASSOCIATED | STATUS_ASSOCIATING))) {
12237c12230 < "parameters because auto association is enabled.\n"); ---
"parameters.\n");
12249d12241 < queue_work(priv->workqueue, &priv->link_up); 12260,12261c12252,12253 < ipw_disassociate(priv); < ipw_associate(priv); ---
if (!ipw_disassociate(priv)) ipw_associate(priv);
-- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c22
--- Comment #22 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c23
--- Comment #23 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c24
--- Comment #24 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c25
--- Comment #25 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c26
--- Comment #26 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c27
--- Comment #27 from Dave Rosky
Created an attachment (id=179370) --> (https://bugzilla.novell.com/attachment.cgi?id=179370) [details] Modified rpm note version: ipw3945-kmp-default-1.2.2_2.6.22.5_31-5.18.i586.rpm
Here is the one I am using, i've tested and working great.
Ben, I just got back home and was going to play with the source RPM, but checked here first and saw that you have done that. I downloaded your RPM and the module seems to work fine. The problem is that for some reason it has always been able to connect on my home network (WPA), and I'm no longer at my parents' house where it did not work, so I can't draw a firm conclusion. It does seem to connect faster, however, and the behavior of the light is different, more like in Ubuntu or SuSE 10.2. The connection has been a little flaky at one of my client's sites, however, so I will test that early next week and see if it is more reliable. Many thanks for spending the time working on this, I really hope the developers pick this up and issue an update. It's hard to believe we are the only people affected by this bug, but it does seem to be dependent on the AP since I can connect to several networks OK, so many people may not notice it. BTW, I tried the iwl driver as well, and it seemed to have the same problem. 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c28
--- Comment #28 from Ben Kevan
(In reply to comment #25 from Ben Kevan)
Created an attachment (id=179370) --> (https://bugzilla.novell.com/attachment.cgi?id=179370) [details] [details] Modified rpm note version: ipw3945-kmp-default-1.2.2_2.6.22.5_31-5.18.i586.rpm
Here is the one I am using, i've tested and working great.
Ben,
I just got back home and was going to play with the source RPM, but checked here first and saw that you have done that. I downloaded your RPM and the module seems to work fine. The problem is that for some reason it has always been able to connect on my home network (WPA), and I'm no longer at my parents' house where it did not work, so I can't draw a firm conclusion. It does seem to connect faster, however, and the behavior of the light is different, more like in Ubuntu or SuSE 10.2. The connection has been a little flaky at one of my client's sites, however, so I will test that early next week and see if it is more reliable.
Many thanks for spending the time working on this, I really hope the developers pick this up and issue an update. It's hard to believe we are the only people affected by this bug, but it does seem to be dependent on the AP since I can connect to several networks OK, so many people may not notice it. BTW, I tried the iwl driver as well, and it seemed to have the same problem.
Dave
Hi Dave, Thanks for giving it a try.. I have open security (locked down by MAC) on my AP, and had the issue you stated you are having are other locations. The patches applied did resolve the issue. As for the light, what was it doing compared to what it is doing now? (Mine is just a solid light, and not blinking, I think it used to blink.. don't remember, that thing annoys me when it blinks though). I'll look at the iwl driver when I have a chance, but I typically just use ipw... so a little lack of motivation and time there. Also, it seems like alot of people are effected by it (there are several other bugs out there, and still doesn't seem to be much movement). My connection after the updates is faster, and signal strength seems to be better also (I thought it was in my head, but you also noted it connected faster). I have not checked if it worked with WPA, but thanks for doing so. Lastly as you see by the scribbles above, I also did other changes and not just apply the newest patch (I didn't just replace the ipw3945.c file, since I wanted to follow the standard Novell uses and keep the vanilla source, and just apply patches). I was very suprised to see that there were many other patches that were there, that weren't applying because it was pointing to the incorrect source folder (1.2.1 instead of 1.2.2). I think I pasted all the diffs.. .. If you want them to look more into.. just let me know and i'll throw your way.. Thanks -- 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.
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.
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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c31
--- Comment #31 from Dave Rosky
The src.rpm is included on this bug report: https://bugzilla.novell.com/attachment.cgi?id=179369
Ben, Thanks, I will look at that. I will also be trying the 2.6.23 kernel as you did, but I'm not sure when I'll get to that. Sounds good that you are working with upstream. I was thinking of suggesting that, but I figured the Ubuntu people would have already reported this upstream since they had already found and fixed the problem, but it sounds like maybe they didn't. I agree, it's great that it works now, and I also have a work-around for the battery drain problem. It would be nice if they incorporate the fixes, though, so it works for everyone. I imagine there are people who installed SuSE 10.3, couldn't connect to their network, and just gave up. I really like SuSE because of the great software repositories and the fact that it has a good feel once you get it running, which is why I'm willing to work through these issues, but right now Ubuntu clearly is better at running well right out of the box. Thanks again for all the info. 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c32
--- Comment #32 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c33
Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c34
Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c35
Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c36
Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c37
--- Comment #37 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c38
--- Comment #38 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=330995#c41
Dominik Borkowski
https://bugzilla.novell.com/show_bug.cgi?id=330995#c42
--- Comment #42 from Ben Kevan
Just a side comment: the same bug seems to occur on Dell XPS M1210 laptop, with Intel 3945ABG card. I originally documented the details of my setup and problems in this post to the suse usenet group:
http://groups.google.com/group/alt.os.linux.suse/msg/ecda0e4436d1e76c
Long story short, every 2-4 minutes my laptop would briefly disconnect from any access point I was connected to, and then it would reconnect.
However, I did not notice the networkmanager logs until I found this bug. Indeed, after switching to the traditional method with kinternet, my connection is now stable.
Unfortunately, using the latest rpm for ipw3945-kmp provided in this bug report, ipw3945-kmp-default-1.2.2_2.6.22.5_31-5.18.i586.rpm, did not fix my problems. What kind of information can I provide to assist with tracking issues in this driver?
sincerely, dom
Hey Dom, When you were experiencing the issue with NetworkManager did it get stuck at 28%? Also, I may have accidently messed up with the ipw3945-kmp-default.. I may have built it for 2.6.23, what kernel version do you have? uname -r. Can you try the obsoleted rpm: https://bugzilla.novell.com/attachment.cgi?id=179370 Please uninstall your current ipw driver and install the one downloaded from the link above. Thank you. Ben -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c43
--- Comment #43 from Dave Rosky
Long story short, every 2-4 minutes my laptop would briefly disconnect from any access point I was connected to, and then it would reconnect.
I wonder if there might be multiple problems. When I was having the connect problems with ipw3945 (similar to Ben's), one thing I did was to try the beta iwl3945 driver, which SuSE also includes. It didn't solve the original connection problem, but in addition to that it would randomly disconnect from the AP every few minutes. My recollection was that it did not automatically re-connect as yours does, I believe I had to go to the network manager icon (I'm using Gnome) and click on the network again. It would then be OK for another few minutes and then disconnect. I only tried this on my home network which uses WPA. I attributed the problem to the iwl driver, but perhaps there is really some other interaction with NetworkManager. 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c44
--- Comment #44 from Dominik Borkowski
Unfortunately, using the latest rpm for ipw3945-kmp provided in this bug report, ipw3945-kmp-default-1.2.2_2.6.22.5_31-5.18.i586.rpm, did not fix my problems.
Small, yet important, correction here. It seems the fix couldn't have worked, since I was already running the updated 10.3 kernel: ~> uname -r 2.6.22.9-0.4-default
When you were experiencing the issue with NetworkManager did it get stuck at 28%?
Very often it would get stuck at 28%, but more frequently it would connect, then lose connection after a couple of minutes.
Also, I may have accidently messed up with the ipw3945-kmp-default.. I may have built it for 2.6.23, what kernel version do you have? uname -r.
In light of my blatant mistake, I downloaded the source rpm bug-330995_ipw3945-kmp-1.2.2-5.18.src.rpm and built it for my kernel: # rpm -qa | grep -i ipw ipw3945d-1.7.22-8.2 ipw-firmware-8-44 ipw3945-kmp-default-1.2.2_2.6.22.9_0.4-5.18 # modinfo ipw3945 filename: /lib/modules/2.6.22.9-0.4-default/updates/ipw3945.ko license: GPL author: Copyright(c) 2003-2006 Intel Corporation version: 1.2.2dmpr description: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux srcversion: 428A6D5C8D816F11D5F7673 alias: pci:v00008086d00004227sv*sd*bc*sc*i* alias: pci:v00008086d00004222sv*sd*bc*sc*i* depends: firmware_class,ieee80211 vermagic: 2.6.22.9-0.4-default SMP mod_unload 586 parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int) parm: disable:manually disable the radio (default 0 [radio on]) (int) parm: associate:auto associate when scanning (default 0 off) (int) parm: auto_create:auto create adhoc network (default 1 on) (int) parm: led:enable led control (default 1 on) (int) parm: debug:debug output mask (int) parm: channel:channel to limit associate to (default 0 [ANY]) (int) parm: rtap_iface:create the rtap interface (1 - create, default 0) (int) parm: mode:network mode (0=BSS,1=IBSS,2=Monitor) (int) Unfortunately, it still behaves the same way: it disconnects me every couple of minutes, then connects back. The following is a combination of /var/log/messages and /var/log/NetworkManager, sorted by time. This is actually 2 minutes from the laptop being rebooted with the new driver, and logged in: Oct 30 06:55:17 frodo NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete. Oct 30 06:55:17 frodo NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Oct 30 06:55:17 frodo NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Oct 30 06:55:18 frodo NetworkManager: <info> Activation (wlan0) Finish handler scheduled. Oct 30 06:55:18 frodo NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete. Oct 30 06:55:18 frodo NetworkManager: <info> Activation (wlan0) successful, device activated. Oct 30 06:55:18 frodo NetworkManager: <info> Clearing nscd hosts cache. Oct 30 06:55:19 frodo NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported Oct 30 06:55:19 frodo NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported Oct 30 06:55:31 frodo NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported Oct 30 06:55:52 frodo kernel: wlan0: No ProbeResp from current AP 00:09:5b:dc:fa:aa - assume out of range Oct 30 06:55:56 frodo kernel: wlan0: Initial auth_alg=0 Oct 30 06:55:56 frodo kernel: wlan0: Initial auth_alg=0 Oct 30 06:55:56 frodo kernel: wlan0: No STA entry for own AP 00:09:5b:dc:fa:aa Oct 30 06:55:56 frodo kernel: wlan0: RX ReassocResp from 00:09:5b:dc:fa:aa (capab=0x21 status=0 aid=1) Oct 30 06:55:56 frodo kernel: wlan0: RX ReassocResp from 00:09:5b:dc:fa:aa (capab=0x21 status=0 aid=1) Oct 30 06:55:56 frodo kernel: wlan0: RX authentication from 00:09:5b:dc:fa:aa (alg=0 transaction=2 status=0) Oct 30 06:55:56 frodo kernel: wlan0: RX authentication from 00:09:5b:dc:fa:aa (alg=0 transaction=2 status=0) Oct 30 06:55:56 frodo kernel: wlan0: associate with AP 00:09:5b:dc:fa:aa Oct 30 06:55:56 frodo kernel: wlan0: associate with AP 00:09:5b:dc:fa:aa Oct 30 06:55:56 frodo kernel: wlan0: associated Oct 30 06:55:56 frodo kernel: wlan0: associated Oct 30 06:55:56 frodo kernel: wlan0: authenticate with AP 00:09:5b:dc:fa:aa Oct 30 06:55:56 frodo kernel: wlan0: authenticate with AP 00:09:5b:dc:fa:aa Oct 30 06:55:56 frodo kernel: wlan0: authenticated Oct 30 06:55:56 frodo kernel: wlan0: authenticated Oct 30 06:56:27 frodo syslog-ng[2629]: last message repeated 9 times Oct 30 06:56:29 frodo kernel: wlan0: No ProbeResp from current AP 00:09:5b:dc:fa:aa - assume out of range Oct 30 06:56:31 frodo NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported Oct 30 06:56:32 frodo kernel: wlan0: Initial auth_alg=0 Oct 30 06:56:32 frodo kernel: wlan0: Initial auth_alg=0 Oct 30 06:56:32 frodo kernel: wlan0: No STA entry for own AP 00:09:5b:dc:fa:aa Oct 30 06:56:32 frodo kernel: wlan0: RX ReassocResp from 00:09:5b:dc:fa:aa (capab=0x21 status=0 aid=1) Oct 30 06:56:32 frodo kernel: wlan0: RX ReassocResp from 00:09:5b:dc:fa:aa (capab=0x21 status=0 aid=1) Oct 30 06:56:32 frodo kernel: wlan0: RX authentication from 00:09:5b:dc:fa:aa (alg=0 transaction=2 status=0) Oct 30 06:56:32 frodo kernel: wlan0: RX authentication from 00:09:5b:dc:fa:aa (alg=0 transaction=2 status=0) Oct 30 06:56:32 frodo kernel: wlan0: associate with AP 00:09:5b:dc:fa:aa Oct 30 06:56:32 frodo kernel: wlan0: associate with AP 00:09:5b:dc:fa:aa Oct 30 06:56:32 frodo kernel: wlan0: associated Oct 30 06:56:32 frodo kernel: wlan0: associated Oct 30 06:56:32 frodo kernel: wlan0: authenticate with AP 00:09:5b:dc:fa:aa Oct 30 06:56:32 frodo kernel: wlan0: authenticate with AP 00:09:5b:dc:fa:aa Oct 30 06:56:32 frodo kernel: wlan0: authenticated Oct 30 06:56:32 frodo kernel: wlan0: authenticated -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c45
--- Comment #45 from Dominik Borkowski
My recollection was that it did not automatically re-connect as yours does, I believe I had to go to the network manager icon (I'm using Gnome) and click on the network again. It would then be OK for another few minutes and then disconnect. I only tried this on my home network which uses WPA.
That's also correct :) I've been having the disconnect issue with any kind of AP I tried. At home I have currently two APs set up: one with WPA and one without. Networkmanager automatically reconnects if I use the one _without_ WPA, yet it won't reconnect if I use the AP _with_ WPA. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c46
--- Comment #46 from Dave Rosky
I've been having the disconnect issue with any kind of AP I tried. At home I have currently two APs set up: one with WPA and one without. Networkmanager automatically reconnects if I use the one _without_ WPA, yet it won't reconnect if I use the AP _with_ WPA.
Does the NetworkManager log show anything interesting at the times that the network randomly disconnects? 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c47
Crispin Cowan
To note, it seems to be a problem with KNetWork Manager.
When I switch to "Traditional if up" then all works well and I can connect, but I prefer Knetwork manager
I can confirm, FWIW, that the ipw3945 driver does not work on my Thinkpad T61 under Network Manager, but when I switched to Traditional, it worked like a champ. I also prefer Network Manager, and it is sad that Ubuntu has had this shipped since July, and openSUSE 10.3 shipped with it broken. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c48
David Rak
https://bugzilla.novell.com/show_bug.cgi?id=330995#c49
--- Comment #49 from Ben Kevan
Is there an idea of how long it'll take to hit the update repositories?
Hi David, Some ipw updates came out today but I didn't see any for the default kernel, I have not downloaded the source to check the fixes either. I've sent an email to JG to find out about an update. Ben -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c52
Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995#c53
--- Comment #53 from Crispin Cowan
I am not sure what the status of this is upstream but I have been following the iwl driver and it's doing pretty well right now. I hope that in openSUSE 11.0 the iwl driver will be default as the ipw is buggy and doesn't have much if any movement.
JG, any thoughts on that / this?
Boggle. I haven't tried upstream lately, but every time I have tried iwl it has been a horrible failure. It has a lifespan of a few minutes to a few hours (random) and when it fails, a reboot is the only thing that fixes it. In contrast, I switched to using the ipw driver, and while it totally fails under Network Manager, it works perfectly under traditional ifup network controls. So I would really hope that SUSE 11.0 goes the other way, fixes Network Manager, and uses the ipw3945 driver. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c54
--- Comment #54 from Ben Kevan
(In reply to comment #52 from Ben Kevan)
I am not sure what the status of this is upstream but I have been following the iwl driver and it's doing pretty well right now. I hope that in openSUSE 11.0 the iwl driver will be default as the ipw is buggy and doesn't have much if any movement.
JG, any thoughts on that / this?
Boggle.
I haven't tried upstream lately, but every time I have tried iwl it has been a horrible failure. It has a lifespan of a few minutes to a few hours (random) and when it fails, a reboot is the only thing that fixes it.
In contrast, I switched to using the ipw driver, and while it totally fails under Network Manager, it works perfectly under traditional ifup network controls.
So I would really hope that SUSE 11.0 goes the other way, fixes Network Manager, and uses the ipw3945 driver.
Yes it used to be like that for me but the recent 1.2.22 from (http://www.intellinuxwireless.org/?p=iwlwifi) is pretty darn good. As for the ipw fix you can fix with a patched version of the ipw3945 driver.. I can help you out with that if you wanted (give you some steps). I am just disappointed they haven't applied the patch and released a fixed ipw3945 driver. I would also expect it to later be included into a GM version that includes the "Blocker" repair fix. Oh well.. We shall see. Ben -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c55
--- Comment #55 from Crispin Cowan
Yes it used to be like that for me but the recent 1.2.22 from (http://www.intellinuxwireless.org/?p=iwlwifi) is pretty darn good.
Does "pretty darn good" mean that it crashes less often? Or that it has stopped crashing? Because the ipw driver has been extremely stable, staying up for the last 2 weeks while transferring at least 100GB of data for me (running my nightly laptop backups over wifi). Reliable wifi is a new experience for me :( as the ipw2100 in my old hardware never worked right, and the ipw3945 and openSUSE 10.2 were never stable either. So having just got it to work well for the first time in a long time, I want to keep it this way :) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c56
--- Comment #56 from Helmut Schaa
I am not sure what the status of this is upstream but I have been following the iwl driver and it's doing pretty well right now. I hope that in openSUSE 11.0 the iwl driver will be default as the ipw is buggy and doesn't have much if any movement.
JG, any thoughts on that / this?
Ben, you're right, ipw3945 will be dropped soon due to iwl3945 slowly getting better :) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c57
--- Comment #57 from Ben Kevan
(In reply to comment #54 from Ben Kevan)
Yes it used to be like that for me but the recent 1.2.22 from (http://www.intellinuxwireless.org/?p=iwlwifi) is pretty darn good.
Does "pretty darn good" mean that it crashes less often? Or that it has stopped crashing? Because the ipw driver has been extremely stable, staying up for the last 2 weeks while transferring at least 100GB of data for me (running my nightly laptop backups over wifi).
Reliable wifi is a new experience for me :( as the ipw2100 in my old hardware never worked right, and the ipw3945 and openSUSE 10.2 were never stable either. So having just got it to work well for the first time in a long time, I want to keep it this way :)
It is reliable on me (no crashing) using WPA on a Dell D820 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995#c58
--- Comment #58 from Ben Kevan
(In reply to comment #52 from Ben Kevan)
I am not sure what the status of this is upstream but I have been following the iwl driver and it's doing pretty well right now. I hope that in openSUSE 11.0 the iwl driver will be default as the ipw is buggy and doesn't have much if any movement.
JG, any thoughts on that / this?
Ben, you're right, ipw3945 will be dropped soon due to iwl3945 slowly getting better :)
"Slowly" getting better? That's an awkward way to put it. I think in the last few months they have made some great strides to improving it. Do you have a openSUSE 10.3 Buildservice that gives the latest iwl driver for some people to test and give feedback on stability etc? I think this would be VERY important to iron out before openSUSE 11.0 (Beta stages). Why? Because to me it is actually a blocker bug since you have to go through hoops to get it to work, and you cannot even do the initial installation using wireless. Ben -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c60
Casual J. Programmer
https://bugzilla.novell.com/show_bug.cgi?id=330995
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c62
--- Comment #62 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=330995
User d_rosky@nccn.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c63
--- Comment #63 from Dave Rosky
"Slowly" getting better? That's an awkward way to put it. I think in the last few months they have made some great strides to improving it.
I agree completely with this. I just installed Fedora 8 on the same laptop with SuSE 10.3 (I like to play around with distros), and Fedora now *only* ships iwl and it works absolutely great - it connects much faster, it stays connected even under heavy load, and it comes back from suspend and resume every time. The LED is still dark, but that's pretty minor, and I'm glad they're working on functionality first anyway. This is a little disappointing because SuSE has always been pretty bullet-proof in the past (from my experience), but this time on wireless they got trumped by both Ubuntu and Fedora, and are slow to fix things as well. 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c64
--- Comment #64 from Ben Kevan
Just created a new Buildservice project for iwlwifi: http://download.opensuse.org/repositories/driver:/wireless:/10.3/
I will switch to these packages to test for openSUSE 11.0 Also, Please please follow up with the factory repo to make sure the latest iwl drivers can be included and tested for 11.0 (or hell even update the ones for 10.3 via non-buildservice. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c66
--- Comment #66 from Ben Kevan
(In reply to comment #58 from Ben Kevan)
"Slowly" getting better? That's an awkward way to put it. I think in the last few months they have made some great strides to improving it.
I agree completely with this. I just installed Fedora 8 on the same laptop with SuSE 10.3 (I like to play around with distros), and Fedora now *only* ships iwl and it works absolutely great - it connects much faster, it stays connected even under heavy load, and it comes back from suspend and resume every time. The LED is still dark, but that's pretty minor, and I'm glad they're working on functionality first anyway.
This is a little disappointing because SuSE has always been pretty bullet-proof in the past (from my experience), but this time on wireless they got trumped by both Ubuntu and Fedora, and are slow to fix things as well.
Dave
Yes although the old Alpha of FC8 had the bug also :) You also have to take into consideration that FC8 is shipped with NetworkManager 0.7 although when I went to install FC8 on my laptop it wouldn't install using the Wireless Drivers.. Had to do wired then get the wireless working (similar to openSUSE) Ubuntu has now fixed this issue. Also, there has been a fix for this. I uploaded the diff files, I've given tons of info, I consider it a bug yet no visible movement has been made to get the patch applied and pushed out. This kind of irks me since quite a few people have this issue (3 in my office alone all with Intel 3945 Cards). If openSUSE 11.0 does go full iwl I hope they add the newest versions (right now 1.2.22) and not some outdated version since Intel is really working on getting iwl stabalized since they realize there are many bugs in ipw. No more ranting.. I'll do my part and remove my ipw and built iwl drivers and use the iwl drivers on the wireless buildservice although the driver listed is 1.2.0 and not 1.2.22 Helmut is it seriously the 1.2.0 driver or is it really the latest 1.2.22 driver? I think having an auto buildservice for the latest would be very helpful in testing for release in 10.3 (as bug fix since it is known the shipped iwl isn't the greatest) and testing later for 11.0 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c67
Helmut Schaa
Helmut is it seriously the 1.2.0 driver or is it really the latest 1.2.22 driver? I think having an auto buildservice for the latest would be very helpful in testing for release in 10.3 (as bug fix since it is known the shipped iwl isn't the greatest) and testing later for 11.0
It is 1.2.0 as this is the candidate for a 10.3 update. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c70
--- Comment #70 from Ben Kevan
Helmut is it seriously the 1.2.0 driver or is it really the latest 1.2.22 driver? I think having an auto buildservice for the latest would be very helpful in testing for release in 10.3 (as bug fix since it is known the shipped iwl isn't the greatest) and testing later for 11.0
It is 1.2.0 as this is the candidate for a 10.3 update.
Wouldn't 1.2.22 be considered 1.2.X family? Or do the build services not work that way? Do you only work on 1.2.0 and do bug fixes for that version and make 1.2.0-3 etc? Sorry just wanted to get a better understanding for myself since currently I am running 1.2.22 which was released on 11-28-07 with the following fixes: avoid firmware command sending if rfkill is enabled fix ucode assertion for RX queue overrun enhance WPA authenication stability document 4965 rate scaling add comments to Tx commands add comments to QOS and ADD_STA commands add comments to RXON command and txpower formats document command header and "alive" responses document 4965 Tx scheduler document shared Tx structures document Tx registers document Rx registers document keep-warm buffer document txpower calculations document temperature calculation move HT_IE_EXT_CHANNEL_* driver definitions to iwl-4965.h move uCode API definitions to iwl-4965-commands.h clean up unused definitions in iwl-4965-hw.h Clean up unused definitions in iwl-3945-hw.h Makefile (top level): enable set KSRC_OUTPUT from command line fix possibly NULL dereference in iwl_set_rate() add comments to iwlXXXX-base.c add comments, mostly on Tx queues clean up some unused definitions in iwl-4965.h and iwl-3945.h Partially clean-up, add comments to iwl-XXXX-hw.h Document Rx calibration Document 4965 rate_n_flags bits Add comments to some driver data structures Move is_legacy() macro family from iwl-4965-hw.h to iwl-4965-rs.h fix incorrect error return due to hot unplug clean up and clarify some comments after 3945/4965 split iwl-4965-hw.h: clean up unused eeprom structures and definitions add comments to EEPROM stuff iwl4965: add comments to rate scaling code iwl3945: re-align 3945 event log data iwl3945: place CCK rates in front of OFDM for supported rates continue namespace changes - fix CONFIG variables Support for uCode without init and bsm section iwl Thanks for your quick responses -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c72
--- Comment #72 from Ben Kevan
Helmut is it seriously the 1.2.0 driver or is it really the latest 1.2.22 driver? I think having an auto buildservice for the latest would be very helpful in testing for release in 10.3 (as bug fix since it is known the shipped iwl isn't the greatest) and testing later for 11.0
It is 1.2.0 as this is the candidate for a 10.3 update.
One last thing.. On the build service can you update to the latest "SUSE Updated Kernel"? uname -r 2.6.22.13-0.3-default Lastely any thoughts on getting it added to: http://download.opensuse.org/repositories/Kernel:/KMP/openSUSE_Factory_KOTD_... ? Sorry for all the mails going around I just really would like a nice realible wireless and I think iwl is the way to go and would like to make sure the proper movement is in place for current 10.3 packages and latter 11.0 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User jtellis@alumni.indiana.edu added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c73
--- Comment #73 from John Ellis
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c74
--- Comment #74 from Ben Kevan
Just tried the attached kernel module and can confirm this does indeed fix NetworkManager issues with ipw3945 on my Inspiron 9400. I can now connect to my AP/router that doesn't broadcast an SSID - whereas before I had to use the traditional ifup method.
Thanks Ben! Novell should definitely be distributing your patch in the update repository.
Thank you for giving it a shot. Not only does it fix the issue it actually seems to be faster and the "Wireless Light" actually reports correctly (stays on when connected) which the iwl 1.1.0 does NOT do (ships with Novell). I can't remember if the iwl 1.2.22 did it. I wish Novell would apply some type of fix. Even if it isn't the one I supplied just anything to fix the darn thing other then pushing it off basicly saying that "iwl" is the way they are going. It's clear iwl is the way they are going (as is intel) but right now in openSUSE 10.3 ipw was default and they should fix it since it was shipped as default. As for the iwl driver, right now I am running on 1.1.0 driver since the kmp packages given by Helmut are actually only for the default kernel. I may just download the source and build for 2.6.22.13-0.3 Kernel. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User jg@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c77
--- Comment #77 from Joachim Gleissner
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c78
--- Comment #78 from Ben Kevan
Ben, a newer iwlwifi version is available through the buildservice, in case you want to give it a try: http://download.opensuse.org/repositories/driver:/wireless:/10.3/
Hey JG any thoughts on updating for the 2.6.22.13-0.3-default kernel? I checked in both openSUSE_10.3 and openSUSE_10.3 update and both are for 2.6.22.5-31.4.1. I could just download source and build for my kernel version but I think it would be advisable to do it in the buildservice in case someone else uses it. What are your thoughts on that? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c83
Helmut Schaa
Hey JG any thoughts on updating for the 2.6.22.13-0.3-default kernel? I checked in both openSUSE_10.3 and openSUSE_10.3 update and both are for 2.6.22.5-31.4.1. I could just download source and build for my kernel version but I think it would be advisable to do it in the buildservice in case someone else uses it.
What are your thoughts on that?
Strange, I thought "openSUSE_10.3 update" should use the current update kernel. I'll have a look at it soon. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c84
--- Comment #84 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=330995
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c85
--- Comment #85 from Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c86
--- Comment #86 from Ben Kevan
https://bugzilla.novell.com/show_bug.cgi?id=330995
User dmoore316@cfu.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c87
--- Comment #87 from David Moore
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c88
--- Comment #88 from Ben Kevan
Thanks Ben. I've added using the ipw kernel module from the repository you give to the opensuse.org wiki to help others.
David, Do you have a link to the wiki page for others that are cc'ed on this bug report? Also I can try to add a "how-to" portion if one isn't included. Thanks Ben -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User dmoore316@cfu.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c89
--- Comment #89 from David Moore
https://bugzilla.novell.com/show_bug.cgi?id=330995
User brunofr@ioda.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c90
Bruno Friedmann
https://bugzilla.novell.com/show_bug.cgi?id=330995
User rcoo@free.fr added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c91
Robert Cabane
https://bugzilla.novell.com/show_bug.cgi?id=330995
User kdejaeger@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c92
Koen De Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c93
--- Comment #93 from Ben Kevan
I just wanted to say that I had the same problem too. Updating the drivers from the link that Ben Kevan provided, solved the problem for me. I am using opensuse 10.3 64 bit on a thinkpad x61 tablet.
Just a note to the people trailing this bug report. The iwl driver found: http://download.opensuse.org/repositories/driver:/wireless:/10.3/openSUSE_10... for the newest Kernel is working great. (1.2.23 and not 1.2.0 or 1.2.2). I do not get dropped like past 1.1.0 or 1.2.0 etc. Thanks Koen for testing and I am glad the x64 is working for you. Ben -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c94
Helmut Schaa
https://bugzilla.novell.com/show_bug.cgi?id=330995
User jrobiso2@ford.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c95
Jonathon Robison
https://bugzilla.novell.com/show_bug.cgi?id=330995
User kdejaeger@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c96
--- Comment #96 from Koen De Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c97
--- Comment #97 from Ben Kevan
I agree. I tried so many things to get it working. And thank god I also checked here in the end (months later).
I've been saying the same since the beginning.. I really wish it were out there. I still have people with D630's D620's that need to add this extra repo just to get wireless connectivity :o( I think they don't want to update a dying ipw since iwl will be out. But why not fix the dying product while it is still the default in the current "stable" version.. sheesh -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User jrobiso2@ford.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c98
--- Comment #98 from Jonathon Robison
https://bugzilla.novell.com/show_bug.cgi?id=330995
User behlert@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c99
Stefan Behlert
https://bugzilla.novell.com/show_bug.cgi?id=330995
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c100
--- Comment #100 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=330995
User ben.kevan@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c101
--- Comment #101 from Ben Kevan
The driver does NOT improve the situation on all machines. On some it's causing more troubles, afaik. We recommend normally to use the iwl-driver if problems occur with the ipw one. But the finally decision for an update is with the project manager of course. Coolo?
I would like to see the actual reports of it breaking a machine. Everyone I've known that has the ipw driver didn't work prior to this fix and this is across multiple machine arch's and vendors. If 100% of ipw users were broken, and this fix helped 50% of them, wouldn't it be better to only now have 50% broken? Or lets say 75% were broken, another 25% became fixed, but it broke for 12% again, wouldn't that still be a better percentage? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=330995
User kairo@kairo.at added comment
https://bugzilla.novell.com/show_bug.cgi?id=330995#c102
--- Comment #102 from Robert Kaiser
participants (1)
-
bugzilla_noreply@novell.com