[Bug 464805] New: WLAN Firmware errors with 11.1
https://bugzilla.novell.com/show_bug.cgi?id=464805 Summary: WLAN Firmware errors with 11.1 Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: axel.braun@gmx.de QAContact: qa@suse.de Found By: --- Hi, I'm running since about 3 years Linux on the ThinkPad Z60m, an I upgraded from 10.3 to 11.1 beginning of the year. Since then I get frequent firmware errors: Jan 7 12:23:48 z60m dhclient: DHCPACK from 192.168.1.1 Jan 7 12:23:48 z60m dhclient: bound to 192.168.1.35 -- renewal in 1541 seconds. Jan 7 12:40:25 z60m kernel: ipw2200: device failed to start within 500ms Jan 7 12:40:25 z60m kernel: ipw2200: Unable to load firmware: -62 Jan 7 12:40:25 z60m kernel: ipw2200: Failed to up device Or Jan 9 12:15:15 z60m dhclient: DHCPACK from 192.168.1.1 Jan 9 12:15:15 z60m dhclient: bound to 192.168.1.33 -- renewal in 1557 seconds. Jan 9 12:21:28 z60m kernel: ipw2200: Firmware error detected. Restarting. Jan 9 12:21:29 z60m kernel: ipw2200: Firmware error detected. Restarting. Jan 9 12:41:12 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Jan 9 12:41:12 z60m dhclient: DHCPACK from 192.168.1.1 The later message is uncritical, the first one requires a reboot to get the WLAN up and running again. Just switching it off is not sufficient -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c1 --- Comment #1 from Axel Braun <axel.braun@gmx.de> 2009-01-12 08:08:06 MST --- Update: Looks like this happens preferred - after the WLAN was switched off and LAN/eth0 was used - suspend to RAM (what I use nearly exclusive. reboot is very rarely) rcnetwork restart does not fix it. Reboot required -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c2 --- Comment #2 from Axel Braun <axel.braun@gmx.de> 2009-01-14 07:15:12 MST --- Created an attachment (id=264998) --> (https://bugzilla.novell.com/attachment.cgi?id=264998) /var/log/messages Log file from: Boot: Usage of eth0, Suspend to RAM, turning WLAN on (via Killswitch), attempt to use WLAN. Actually it was not possible to connect, although no Firmware problems were shown. Same was working perfectly for SuSE 10.3 -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c3 --- Comment #3 from Axel Braun <axel.braun@gmx.de> 2009-01-14 07:35:45 MST --- Created an attachment (id=265005) --> (https://bugzilla.novell.com/attachment.cgi?id=265005) Network manager log -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c4 --- Comment #4 from Axel Braun <axel.braun@gmx.de> 2009-01-14 07:40:38 MST --- Created an attachment (id=265010) --> (https://bugzilla.novell.com/attachment.cgi?id=265010) network manager log around time of firmware problem -- 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=464805 Robert Vojcik <rvojcik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- 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=464805 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |kkeil@novell.com |ovo.novell.com | -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c5 --- Comment #5 from Axel Braun <axel.braun@gmx.de> 2009-02-02 06:45:41 MST --- anybody interested in that bug? as it happens regulary, I think about returning to 10.3 otherwise -- 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=464805 User kkeil@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c6 Karsten Keil <kkeil@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kkeil@novell.com |jslaby@novell.com --- Comment #6 from Karsten Keil <kkeil@novell.com> 2009-02-02 11:59:41 MST --- sorry bug was assigned to the wrong person. -- 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=464805 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c7 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #7 from Jiri Slaby <jslaby@novell.com> 2009-02-13 14:29:42 MST --- Could you try *both* kernels from: http://labs.suse.cz/jslaby/bug-464805/ if anything changes? -- 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=464805 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c8 --- Comment #8 from Jiri Slaby <jslaby@novell.com> 2009-02-15 12:52:12 MST --- z60m:/home/axel/bug-464805%%2fold # rpm -Uhv *rpm Preparing... ########################################### [100%] 1:kernel-default-base ########################################### [ 25%] 2:kernel-default ########################################### [ 50%] 3:kernel-default-extra ########################################### [ 75%] 4:kernel-source ########################################### [100%] z60m:/home/axel/bug-464805%%2fold # With that kernel it was running until a firmware error came up again. That let the network crash and NOT restart again alone: Feb 15 16:30:52 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 15 16:30:52 z60m dhclient: DHCPACK from 192.168.1.1 Feb 15 16:30:52 z60m dhclient: bound to 192.168.1.37 -- renewal in 1687 seconds. Feb 15 16:38:28 z60m syslog-ng[2368]: Log statistics; dropped='pipe(/dev/xconsole)=0', dropped='pipe(/dev/tty10)=0', processed='center(queued)=495', processed='center(received)=456', processed='destination(newsnotice)=0', processed='destination(acpid)=3', processed='destination(firewall)=38', processed='destination(null)=4', processed='destination(mail)=2', processed='destination(mailinfo)=2', processed='destination(console)=11', processed='destination(newserr)=0', processed='destination(newscrit)=0', processed='destination(messages)=151', processed='destination(mailwarn)=0', processed='destination(localmessages)=0', processed='destination(netmgm)=258', processed='destination(mailerr)=0', processed='destination(xconsole)=11', processed='destination(warn)=15', processed='source(src)=456' Feb 15 16:41:19 z60m avahi-daemon[3084]: Withdrawing address record for 192.168.1.37 on eth1. Feb 15 16:41:19 z60m avahi-daemon[3084]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.37. Feb 15 16:41:19 z60m avahi-daemon[3084]: Interface eth1.IPv4 no longer relevant for mDNS. Feb 15 16:41:19 z60m nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1. Feb 15 16:41:21 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 15 16:41:21 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 15 16:41:30 z60m dhclient: Internet Systems Consortium DHCP Client V3.1.1 Feb 15 16:41:30 z60m dhclient: Copyright 2004-2008 Internet Systems Consortium. Feb 15 16:41:30 z60m dhclient: All rights reserved. Feb 15 16:41:30 z60m dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Feb 15 16:41:30 z60m dhclient: Feb 15 16:41:30 z60m dhclient: Listening on LPF/eth1/00:13:ce:c7:09:dd Feb 15 16:41:30 z60m dhclient: Sending on LPF/eth1/00:13:ce:c7:09:dd Feb 15 16:41:30 z60m dhclient: Sending on Socket/fallback Feb 15 16:41:31 z60m dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2 Feb 15 16:41:31 z60m dhclient: DHCPOFFER from 192.168.1.1 Feb 15 16:41:36 z60m dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Feb 15 16:41:38 z60m dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Feb 15 16:41:42 z60m dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Feb 15 16:41:47 z60m dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2 Feb 15 16:41:49 z60m dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3 Feb 15 16:41:52 z60m dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 Feb 15 16:41:57 z60m dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 Feb 15 16:42:05 z60m dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 Feb 15 16:42:13 z60m dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10 Feb 15 17:02:15 z60m -- MARK -- Feb 15 17:22:15 z60m -- MARK -- Feb 15 17:38:28 z60m syslog-ng[2368]: Log statistics; dropped='pipe(/dev/xconsole)=0', dropped='pipe(/dev/tty10)=0', processed='center(queued)=643', processed='center(received)=597', processed='destination(newsnotice)=0', processed='destination(acpid)=3', processed='destination(firewall)=38', processed='destination(null)=4', processed='destination(mail)=2', processed='destination(mailinfo)=2', processed='destination(console)=13', processed='destination(newserr)=0', processed='destination(newscrit)=0', processed='destination(messages)=179', processed='destination(mailwarn)=0', processed='destination(localmessages)=0', processed='destination(netmgm)=371', processed='destination(mailerr)=0', processed='destination(xconsole)=13', processed='destination(warn)=18', processed='source(src)=597' Afterwards I installed the kernel from the new-directory. Up to now one error Feb 15 18:52:49 z60m kernel: ipw2200: Firmware error detected. Restarting. .but the net survived. The reported error was not seen so far, but I will check during the week. -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c9 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|axel.braun@gmx.de | --- Comment #9 from Axel Braun <axel.braun@gmx.de> 2009-02-17 01:42:55 MST --- I get these errors with the new kernel as well: Feb 17 09:36:30 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 17 09:36:30 z60m kernel: ipw2200: Firmware error detected. Restarting. -- 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=464805 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c10 --- Comment #10 from Jiri Slaby <jslaby@novell.com> 2009-02-17 04:44:24 MST --- (In reply to comment #9)
I get these errors with the new kernel as well:
I suppose the device gets stuck too? In that case I don't understand, since old kernel contains a driver from 10.3. Could you recheck with 10.3 kernel: ftp://ftp.suse.com/pub/projects/kernel/kotd/SL103_BRANCH/i386/ that the problem isn't there with 11.1 system? -- 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=464805 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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=464805 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c11 --- Comment #11 from Axel Braun <axel.braun@gmx.de> 2009-02-19 23:52:33 MST --- Update: I was unsure as the system bootet by default 11.1-standard, but with the new kernel I had this problem as well (see below). I will check the 10.3 kernel over the weekend. Or can that be a hardware problem? Feb 19 23:46:43 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 19 23:46:43 z60m dhclient: DHCPACK from 192.168.1.1 Feb 19 23:46:43 z60m dhclient: bound to 192.168.1.33 -- renewal in 1487 seconds. Feb 20 00:04:37 z60m avahi-daemon[2936]: Withdrawing address record for 192.168.1.33 on eth1. Feb 20 00:04:37 z60m avahi-daemon[2936]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.33. Feb 20 00:04:37 z60m avahi-daemon[2936]: Interface eth1.IPv4 no longer relevant for mDNS. Feb 20 00:04:39 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 20 00:04:39 z60m nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1. Feb 20 00:04:40 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 20 00:05:04 z60m kernel: ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c12 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #12 from Axel Braun <axel.braun@gmx.de> 2009-02-21 00:35:56 MST --- (In reply to comment #10)
(In reply to comment #9)
I get these errors with the new kernel as well:
I suppose the device gets stuck too?
yes... unfortunately the same problem: Feb 20 21:21:55 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 20 21:21:56 z60m kernel: ipw2200: Firmware error detected. Restarting. Feb 20 21:25:53 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 20 21:25:58 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 20 21:26:12 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 20 21:26:12 z60m dhclient: DHCPACK from 192.168.1.1 Feb 20 21:26:12 z60m dhclient: bound to 192.168.1.33 -- renewal in 1435 seconds. [...] Feb 20 22:14:22 z60m dhclient: DHCPREQUEST on eth1 to 192.168.1.1 port 67 Feb 20 22:14:22 z60m dhclient: DHCPACK from 192.168.1.1 Feb 20 22:14:22 z60m dhclient: bound to 192.168.1.33 -- renewal in 1603 seconds Feb 20 22:27:28 z60m avahi-daemon[3296]: Withdrawing address record for 192.168.1.33 on eth1. Feb 20 22:27:28 z60m avahi-daemon[3296]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.1.33. (k)networkmanager still shows full connection, but that is a different story. Is the firmware shipped with the 11.1 kernel the same as the one with 10.3? Could this be a hardware-problem then? -- 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=464805 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c13 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |hschaa@novell.com --- Comment #13 from Jiri Slaby <jslaby@novell.com> 2009-02-21 06:09:51 MST --- (In reply to comment #12)
Is the firmware shipped with the 11.1 kernel the same as the one with 10.3?
Helmut, any ideas here, please? -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c14 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hschaa@novell.com Info Provider|hschaa@novell.com |axel.braun@gmx.de --- Comment #14 from Helmut Schaa <hschaa@novell.com> 2009-02-21 09:20:07 MST --- AFAIK the firmware should be the same as shipped with 10.3. However, I already saw other reports that mentioned that turning off the led by editing /etc/modprobe.d/ipw2200 fixes the firmware restarts on _some_ machines. Just exchange "options ipw2200 hwcrypto=0 led=1 associate=0" with "options ipw2200 hwcrypto=0 led=0 associate=0". Could you please try if that helps? -- 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=464805 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|WLAN Firmware errors with |ipw2200: WLAN Firmware |11.1 |errors with 11.1 -- 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=464805 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #265010|application/octet-stream |text/plain mime type| | -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c15 --- Comment #15 from Helmut Schaa <hschaa@novell.com> 2009-02-21 09:26:35 MST --- Another question: what type of AP are you using? Is it already 11n capable? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c16 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #16 from Axel Braun <axel.braun@gmx.de> 2009-02-22 06:00:10 MST --- (In reply to comment #14)
Just exchange "options ipw2200 hwcrypto=0 led=1 associate=0" with "options ipw2200 hwcrypto=0 led=0 associate=0".
No change in results...still FW errors. And the LED is still blinking...
Another question: what type of AP are you using? Is it already 11n capable?
I doubt that. It is sold as Arcor 200 DSL Modem, in fact it is s Zyxel Modem: ZyNOS Firmware-Version: V3.40(AHS.0) | 4/7/2006 DSL Firmware-Version:DMT FwVer: 3.5.10.0_B_TC, HwVer: T14F7_1.0 Standard:ADSL_G.dmt -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c17 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #17 from Helmut Schaa <hschaa@novell.com> 2009-02-23 04:24:28 MST --- (In reply to comment #16)
(In reply to comment #14)
Just exchange "options ipw2200 hwcrypto=0 led=1 associate=0" with "options ipw2200 hwcrypto=0 led=0 associate=0".
No change in results...still FW errors. And the LED is still blinking...
Did you reload the module after editing modprobe file? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c18 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #18 from Axel Braun <axel.braun@gmx.de> 2009-02-23 04:43:43 MST ---
Did you reload the module after editing modprobe file? I rebooted, as I changed the kernel back to 2.6.27.7-9-default
-- 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=464805 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c19 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |hschaa@novell.com --- Comment #19 from Jiri Slaby <jslaby@novell.com> 2009-03-03 09:26:59 MST --- Any ideas? -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c20 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|hschaa@novell.com | --- Comment #20 from Helmut Schaa <hschaa@novell.com> 2009-03-03 09:42:56 MST --- Not really. I tested an ipw2200 some time ago and wasn't able to trigger any firmware restarts :( The debug output of the driver sometimes contains valuable information. However, we don't have debug enabled by default. Let's build a kernel with CONFIG_IPW2200_DEBUG (and maybe CONFIG_IEEE80211_DEBUG too). Afterwards loading ipw2200 with debug=0x61FFC6F should give some more details why the fw failed (and lots of other debugging messages). Jiri, are you going to build a kernel with ipw2200 debugging enabled for Axel? -- 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=464805 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c21 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #21 from Jiri Slaby <jslaby@novell.com> 2009-03-06 14:58:53 MST --- (In reply to comment #20)
Jiri, are you going to build a kernel with ipw2200 debugging enabled for Axel?
Yes, ready at: http://labs.suse.cz/jslaby/bug-464805/ Axel, could you try it with the debug enabled as written in comment #20? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c22 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #22 from Axel Braun <axel.braun@gmx.de> 2009-03-08 04:52:24 MST --- Created an attachment (id=277872) --> (https://bugzilla.novell.com/attachment.cgi?id=277872) logfile I got a withdraw, but the network came back afterwards. An you please check if this withdraw has relevant information for you? Mar 7 23:03:38 z60m avahi-daemon[3170]: Withdrawing address record for 192.168.1.37 on eth2. -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c23 --- Comment #23 from Helmut Schaa <hschaa@novell.com> 2009-03-09 02:01:52 MST --- Thanks Axel. There is at least one firmware restart in the log, and it contains quite some useful information.
Mar 7 23:03:07 z60m kernel: ipw2200: I ipw_handle_missed_beacon Missed beacon: 9 - initiate roaming
Ok, here the driver recognizes 9 missed beacons and tries to initiate roaming, which triggers a scan.
Mar 7 23:03:12 z60m kernel: ipw2200: U ipw_scan_check Scan completion watchdog resetting adapter after (5000ms).
The scan did not finish after 5 seconds. Hence, the driver thinks the card is stuck and triggers a restart. I'm not sure why the scan did not finish within 5 seconds. I counted 18 scan notifications (=#scanned channel) on 11a channels which should not be more than 18 * 120 <= 3 sec. However, the ipw2200 firmware does some scan magic and switches back to the operating channel once in a while. That could explain the timeout.
Mar 7 23:03:12 z60m kernel: ipw2200: Firmware error detected. Restarting.
I guess this one can safely be ignored as it happens during adapter shutdown. Jiri, my suggestion is to simply increase the IPW_SCAN_CHECK_WATCHDOG to something around 10 seconds. I already made such a patch a while ago (see [1]) but it turned out to be a different issue (see [2]) and thus I dropped that patch again. [1] http://sourceforge.net/mailarchive/forum.php?thread_name=200811251809.55461.helmut.schaa%40gmail.com&forum_name=ipw2100-devel [2] http://sourceforge.net/mailarchive/forum.php?thread_name=200811261805.39953.helmut.schaa%40gmail.com&forum_name=ipw2100-devel -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c24 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #24 from Helmut Schaa <hschaa@novell.com> 2009-03-09 02:17:11 MST --- Axel, do you only have one AP around or do you have an environment with multiple APs that allow roaming? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c25 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #25 from Axel Braun <axel.braun@gmx.de> 2009-03-09 03:04:42 MST --- There are tons of other WLAN/different SSID around, but only one AP to which I have access. -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c26 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #26 from Helmut Schaa <hschaa@novell.com> 2009-03-09 03:36:29 MST --- (In reply to comment #25)
There are tons of other WLAN/different SSID around, but only one AP to which I have access.
So, I guess you are not moving around that much ;) Hmm, ok, that means when the scenario described in comment #23 happens 1) the signal strength is horrible (9 consecutive missed beacons is really bad) 2) or something jams your signal once in a while 3) or there are too much APs interfering with yours Apart from the firmware restarts, is your signal strong and do you get good throughput? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c27 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #27 from Axel Braun <axel.braun@gmx.de> 2009-03-09 04:02:37 MST --- Well, I'm no 8 m away from the AP, normally the signal is between 65 and 90%. No metal in between, just two thin doors -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c28 --- Comment #28 from Helmut Schaa <hschaa@novell.com> 2009-03-09 04:06:31 MST --- Ok, so it is only a short-term phenomenon. Let's just see if increasing IPW_SCAN_CHECK_WATCHDOG avoids the firmware restarts but I guess you might still have spurious disconnects then, but at least the driver should reconnect quickly. -- 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=464805 User jslaby@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c29 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #29 from Jiri Slaby <jslaby@novell.com> 2009-03-09 16:09:24 MST --- Kernel with increased watchdog time is in http://labs.suse.cz/jslaby/bug-464805/ Could you try it? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c30 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #30 from Axel Braun <axel.braun@gmx.de> 2009-03-10 14:36:59 MST --- Created an attachment (id=278588) --> (https://bugzilla.novell.com/attachment.cgi?id=278588) /var/log/messages looks like it is even worse: Took only a short ime until the first drop, then the net came back, and finally (before I killed the module around 21:30) ths networkmanager was showing full field strength, but in fact the Network/DNS was not working -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c31 --- Comment #31 from Helmut Schaa <hschaa@novell.com> 2009-03-11 03:48:29 MST --- Thanks, but at least the firmware restart is gone :) and there is at least one scan in your log that took longer then 5 seconds. However, the following appears several times in your log:
Mar 10 19:35:22 z60m kernel: ipw2200: I ipw_handle_missed_beacon Missed beacon: 1
[...]
Mar 10 19:35:23 z60m kernel: ipw2200: I ipw_handle_missed_beacon Missed beacon: 9 - initiate roaming
[...]
Mar 10 19:35:24 z60m kernel: ipw2200: I ipw_handle_missed_beacon Missed beacon: 25 - disassociate
[...]
Mar 10 19:35:24 z60m kernel: ipw2200: U ipw_send_disassociate Disassocation attempt from 00:13:49:9a:e6:93 on channel 6.
Unfortunately, there's no valuable debug output before this beacon-miss storm happens. I'm not sure if it is the firmware/driver here that misbehaves or if there something jams your wireless signal or your AP behaves incorrect. The only way to be sure that beacons still arrive but are dropped by the firmware would be to sniff the traffic with a seconds wireless card while ipw2200 prints the messages about beacon misses. -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c32 --- Comment #32 from Axel Braun <axel.braun@gmx.de> 2009-03-11 08:57:31 MST --- (In reply to comment #31)
The only way to be sure that beacons still arrive but are dropped by the firmware would be to sniff the traffic with a seconds wireless card while ipw2200 prints the messages about beacon misses.
You mean with kismet or something? -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c33 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #33 from Helmut Schaa <hschaa@novell.com> 2009-03-11 09:05:48 MST --- Yep, you can also use plain wireshark for that. Do you have a second wireless card? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c34 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #34 from Axel Braun <axel.braun@gmx.de> 2009-03-11 16:10:21 MST --- Created an attachment (id=278963) --> (https://bugzilla.novell.com/attachment.cgi?id=278963) wireshark - logfile Indeed, at Mar 11 22:56:49 z60m avahi-daemon[3016]: Withdrawing address record for 192.168.1.36 on eth2. DNS got lost again, although networkmanager was recording full signal strength. This is the log file I recorded with wireshark -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c35 --- Comment #35 from Axel Braun <axel.braun@gmx.de> 2009-03-11 16:14:26 MST --- Created an attachment (id=278964) --> (https://bugzilla.novell.com/attachment.cgi?id=278964) /var/log/messages to the wireshark -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c36 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #36 from Helmut Schaa <hschaa@novell.com> 2009-03-12 02:16:48 MST --- Hmm, unfortunately the wireshark dump does not contain any frames sent by your AP. Seems like you've sniffed the ethernet port :) Could you please try again to dump the wireless traffic using a second wireless card (called wlan1 here) using the following steps: - ifconfig wlan1 down - iwconfig wlan1 mode monitor - ifconfig wlan1 up - wireshark -i wlan1 -k -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c37 --- Comment #37 from Axel Braun <axel.braun@gmx.de> 2009-03-12 02:22:32 MST --- (In reply to comment #36)
Hmm, unfortunately the wireshark dump does not contain any frames sent by your AP. Seems like you've sniffed the ethernet port :)
Hm...I used a second machine, and saw at least some packets from the 192.168.1.* network...anyway, will try again, probably on the weekend. 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c38 --- Comment #38 from Helmut Schaa <hschaa@novell.com> 2009-03-12 02:29:35 MST --- Great, thanks Axel. -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c39 --- Comment #39 from Helmut Schaa <hschaa@novell.com> 2009-03-12 02:32:34 MST --- Of course the channel has to be set to the same as your AP is using: - iwconfig wlan1 channel X -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c40 --- Comment #40 from Axel Braun <axel.braun@gmx.de> 2009-03-12 02:51:33 MST --- (In reply to comment #39)
Of course the channel has to be set to the same as your AP is using: - iwconfig wlan1 channel X
How can I find out which channel is used by the AP? Thx! -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c41 --- Comment #41 from Helmut Schaa <hschaa@novell.com> 2009-03-12 03:43:32 MST --- Just run "iwlist wlan0 scan" and look for your AP: Cell 05 - Address: XX:XX:XX:XX:XX:XX Channel:5 Frequency:2.432 GHz (Channel 5) Quality=31/70 Signal level=-79 dBm Encryption key:on ESSID:"your essid" -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c42 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #278963|0 |1 is obsolete| | --- Comment #42 from Axel Braun <axel.braun@gmx.de> 2009-03-15 04:18:56 MST --- Created an attachment (id=279639) --> (https://bugzilla.novell.com/attachment.cgi?id=279639) wireshark - logfile II Finger crossed i did it right this time ;-) -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c43 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #278964|0 |1 is obsolete| | Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #43 from Axel Braun <axel.braun@gmx.de> 2009-03-15 07:07:30 MST --- Created an attachment (id=279644) --> (https://bugzilla.novell.com/attachment.cgi?id=279644) messages to the wireshark some withdrawals, but network came back -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c45 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #45 from Helmut Schaa <hschaa@novell.com> 2009-03-30 01:30:14 MDT --- Axel, I could not open the wireshark capture file. How did you save the log from within wireshark? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c46 Axel Braun <axel.braun@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | --- Comment #46 from Axel Braun <axel.braun@gmx.de> 2009-03-30 03:41:38 MDT --- Yes, I saved it from within wireshark, as XML full package log (or something similar name) -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c47 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #47 from Helmut Schaa <hschaa@novell.com> 2009-03-30 03:47:02 MDT --- Argh, it seems like wireshark cannot open the XML file :( even if it was created by itself. I'm sorry, but could you please try again to capture the beacon miss storm and just use "Save as" instead of "Export" to save the log? That would be great. One other thing that might be interesting: Intel released a new firmware for ipw2200 only a few days ago at [1]. You might want to try firmware version 3.1? [1] http://ipw2200.sourceforge.net/firmware.php -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c48 --- Comment #48 from Axel Braun <axel.braun@gmx.de> 2009-03-30 03:53:36 MDT --- yes, can do that, but I will need some days for this...i have abused the machine for a knoppix 6.1 harddisk-installation...but cant get the netgear wg511 Cardbus card up and running with WPA encryption. need to install 11.1 again beforehand -- 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=464805 User hschaa@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c49 --- Comment #49 from Helmut Schaa <hschaa@novell.com> 2009-03-30 03:55:59 MDT --- Sure. Just provide the info once you have it. Btw. did you experience similar issues if you use a different wireless network? Could you check that as well? -- 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=464805 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=464805#c50 --- Comment #50 from Axel Braun <axel.braun@gmx.de> 2009-03-30 15:11:38 MDT --- I had a Netgear Router beforehand, that worked without problems. But unfortunately I cant check it, as I left it in the old flat.... -- 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.
participants (1)
-
bugzilla_noreply＠novell.com