[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
I have this same problem with current Hardy and iwl4965. I can turn the wireless off successfully with the switch. If I turn it back on then network manager detects that but never manages to join a network (I waited 5 minutes). I can get network manager to connect to a wired network, but it will never connect to any wireless network. Even doing a hibernate doesn't work. The only thing that does work is a reboot. Lenovo Thinkpad T61, iwl4965, hardy up to date as of this posting. Here is an example. In the middle I switched to a wired network (e1000) and then tried to do the wireless network again. [ 67.180995] wlan0: associated [ 67.183580] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 74.019849] wlan0: no IPv6 routers present [ 84.867212] iwl4965: Radio Frequency Kill Switch is On: [ 84.867218] Kill switch must be turned off for wireless networking to work. [ 85.044781] wlan0: deauthenticate(reason=3) [ 88.284163] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 128.809319] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 133.015425] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 159.320463] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX [ 159.320474] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO [ 159.387511] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 169.833224] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 198.030170] ADDRCONF(NETDEV_UP): wlan0: link is not ready -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://bugs.launchpad.net/bugs/20667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
this is fixed for network-manager. If it doesn't work for your chipset its probably a driver issue. ** Changed in: network-manager (Ubuntu) Status: Confirmed = Fix Released -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://bugs.launchpad.net/bugs/20667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
We included a patch that is ment to address this in gutsy network manager. Please test if you still see it in 0.6.5-0ubuntu14 Thanks, - Alexander ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Alexander Sack (asac) -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://bugs.launchpad.net/bugs/20667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
** Changed in: acpi-support (Ubuntu) Status: Confirmed = Invalid -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://bugs.launchpad.net/bugs/20667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
** Changed in: network-manager (upstream) Status: Confirmed = Invalid -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://bugs.launchpad.net/bugs/20667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
Update: This bug doesn't happen for me anymore. The killswitch started working properly somewhere in Feisty, and it's still working on Gutsy. (But see bug #121415 for a slightly different related problem.) -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://bugs.launchpad.net/bugs/20667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
upstream head fixes this bug, if you have a hal supported rfkill switch, such as DELL's one -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://bugs.launchpad.net/bugs/20667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
Here you go: [EMAIL PROTECTED]:~$ grep . /var/lib/acpi-support/*-* /var/lib/acpi-support/bios-version:A05 /var/lib/acpi-support/system-manufacturer:Dell Inc. /var/lib/acpi-support/system-product-name:Latitude D620 /var/lib/acpi-support/system-version:Not Specified I'm not sure what you mean by stuck key business, is it related to my post? In that case, what part of it should I file as a new bug? -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://launchpad.net/bugs/20667 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
Bogdan's keycodes need going in 'hotkey-setup'. NM integrated poking (sleep and setWirelessEnabled) need going into 'acpi-support'. Bogdan: can you please include the output from: grep . /var/lib/acpi-support/*-* so that we can identify the model of your laptop. ** Changed in: acpi-support (Ubuntu) Status: Unconfirmed = Confirmed ** Changed in: hotkey-setup (Ubuntu) Status: Unconfirmed = Confirmed -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://launchpad.net/bugs/20667 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
The stuck key business needs solving in the kernel (probably easier to file separate bugs for these). -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://launchpad.net/bugs/20667 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
Hi! I have this problem too. My machine is a Dell Latitude D620. The wireless is an Intel PRO/Wireless 3945ABG using the ipw3945 driver. The laptop has a switch (on the left side, not that it matters), with three positions: off/on/signal. The first two are fixed (i.e. the switch remains there), while the third has a spring which returns it to the on position when released. I think the third position it's used by the Windows WiFi drivers to trigger some sort of return to favourites action, but I don't know for sure, I never used Windows on this machine. The switch can be set in the BIOS to control the Bluetooth/WiFi/Cellular function, or a combination thereof. It is currently set to control all of them (i.e., when turned off all wireless functions should stop). The short story is that: - if I boot-up the laptop with the switch on, WiFi works and the Network Manager configures it just right, - if I turn it off the WiFi stops (i.e. ifconfig -a doesn't show the adapter anymore) - if I boot with it off, I never get the adapter shown (as above) - if I turn it on after the system is booted it never gets activated. I looked in the device manager, the hardware is still shown after disappearing from the list given by ifconfig -a. What is rather interesting is that (after a bit of twiddling with the switch) no events concerning the WiFi hardware appear in syslog. (I think it does show something the first time it's turned off, but my syslog is to messy now to be sure. I'll look again after I reboot.) However, it _does_ generate some keyboard events! Feb 8 20:57:46 bogdanb-d620 kernel: [44072.818000] atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0). Feb 8 20:57:46 bogdanb-d620 kernel: [44072.818000] atkbd.c: Use 'setkeycodes e008 keycode' to make it known. Feb 8 20:57:49 bogdanb-d620 kernel: [44075.535000] atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0). Feb 8 20:57:49 bogdanb-d620 kernel: [44075.535000] atkbd.c: Use 'setkeycodes e008 keycode' to make it known. Feb 8 20:57:52 bogdanb-d620 kernel: [44078.099000] atkbd.c: Unknown key pressed (translated set 2, code 0x91 on isa0060/serio0). Feb 8 20:57:52 bogdanb-d620 kernel: [44078.099000] atkbd.c: Use 'setkeycodes e011 keycode' to make it known. Feb 8 20:57:52 bogdanb-d620 kernel: [44078.482000] atkbd.c: Unknown key released (translated set 2, code 0x91 on isa0060/serio0). Feb 8 20:57:52 bogdanb-d620 kernel: [44078.482000] atkbd.c: Use 'setkeycodes e011 keycode' to make it known. The above is a sequence starting in the on position; I moved the switch to off, back to on, then clicked the third (attention?) position. If you check the time-stamps, this means that moving between on and off triggers the same key-press e008 (0x88 -- not sure what each code means), with no key-release. Clicking the third position generates a key-press/release event pair with code e011/0x91. I think this is very interesting, as it can be used to notify the kernel or the network manager to do whatever it has to do to re-enable the network adapter, as someone noted earlier. We could even use the click key to notify the network adapter to do something interesting, like look for APs. As for how to do that, I don't yet know. After posting this comment, I'll do a couple of reboots and I'll look at what happens in syslog when I play with the switch. By the way, it might be relevant to note that the same switch in involved in bug #63418. Also, the kernel has a way of telling what is the current position of the switch, because it reports it during boot. -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://launchpad.net/bugs/20667 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 20667] Re: Doesn't reconnect when wireless disabled/re-enabled using kill switch
I don't know if it helps but if the hotkey is connected to a script (such as /etc/acpi/wireless.sh) this problem could easilly be resolved by adding those lines # line to pseudo disable wireless in network-manager dbus-send --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.setWirelessEnabled boolean:false # line to enable wireless dbus-send --system --type=method_call --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.setWirelessEnabled boolean:true using those lines whenever I hit the hotkey to enable wireless, the connection is brought up again (if I was previously connected). Unfortunately network manger (or at least the gnome applet, I don't know) doesn't understand that the card is off and it continues to show every wireless network that was in the range of you, before you used the hotkey to deactivate the card. -- Doesn't reconnect when wireless disabled/re-enabled using kill switch https://launchpad.net/bugs/20667 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
