Package: linux-image-2.6.29-2-686
Version: 2.6.29-4
Severity: normal
When using network-manager, I cannot connect to wifi if I reactivate wirelless
after having switched it off with the hardware kill-switch of my Dell Latitude
D820.
I noticed some weird things after trying to debug the cause of the problem.
I have the following kill-switch information appearing in /sys at boot if
kill-switch is off (meaning wireless activated) :
# for i in $(find /sys | grep -i kill | grep /state ); do echo -n $i : ; cat
$i; done
/sys/devices/virtual/rfkill/rfkill0/state : 1
/sys/devices/virtual/rfkill/rfkill1/state : 1
/sys/devices/pci:00/:00:1c.1/:03:00.0/rfkill/rfkill2/state : 1
After I activate the kill-switch to disable networking, it gives :
# for i in $(find /sys | grep -i kill | grep /state ); do echo -n $i : ; cat
$i; done
/sys/devices/virtual/rfkill/rfkill0/state : 2
/sys/devices/virtual/rfkill/rfkill1/state : 2
/sys/devices/pci:00/:00:1c.1/:03:00.0/rfkill/rfkill2/state : 2
However, after reactivating network (kill switch switched to off), I get only :
# for i in $(find /sys | grep -i kill | grep /state ); do echo -n $i : ; cat
$i; done
/sys/devices/virtual/rfkill/rfkill0/state : 1
/sys/devices/virtual/rfkill/rfkill1/state : 1
/sys/devices/pci:00/:00:1c.1/:03:00.0/rfkill/rfkill2/state : 2
This probably explains the problem with network-manager (which is btw reflected
in the killswitch.state shown with lshal :
--- hal-on.log 2009-05-25 19:17:06.0 +0200
+++ hal-back-on.log 2009-05-25 19:20:01.0 +0200
@@ -80,18 +80,18 @@
udi = '/org/freedesktop/Hal/devices/pci_8086_4222_rfkill_3945ABG_wlan'
info.addons.singleton = {'hald-addon-rfkill-killswitch'} (string list)
info.capabilities = {'killswitch'} (string list)
info.category = 'killswitch' (string)
info.interfaces = {'org.freedesktop.Hal.Device.KillSwitch'} (string list)
info.parent = '/org/freedesktop/Hal/devices/pci_8086_4222' (string)
info.product = '3945ABG wlan Killswitch' (string)
info.subsystem = 'rfkill' (string)
info.udi = '/org/freedesktop/Hal/devices/pci_8086_4222_rfkill_3945ABG_wlan'
(string)
info.vendor = 'Intel Corporation' (string)
killswitch.access_method = 'rfkill' (string)
killswitch.name = '3945ABG' (string)
- killswitch.state = 1 (0x1) (int)
+ killswitch.state = 2 (0x2) (int)
killswitch.type = 'wlan' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'rfkill' (string)
linux.sysfs_path =
'/sys/devices/pci:00/:00:1c.1/:03:00.0/rfkill/rfkill2' (string)
This used to work fine with Network-Manager over 2.6.26, though.
Thanks in advance.
-- Package-specific info:
** Version:
Linux version 2.6.29-2-686 (Debian 2.6.29-4) (wa...@debian.org) (gcc version
4.3.3 (Debian 4.3.3-8) ) #1 SMP Sun May 3 12:46:00 UTC 2009
** Command line:
root=/dev/sda5 ro pci=assign-busses vga=791
** Tainted: P (1)
** Kernel log:
[ 10.456549] coretemp coretemp.0: Using relative temperature scale!
[ 10.472451] coretemp coretemp.1: Using relative temperature scale!
[ 14.423356] fuse init (API version 7.11)
[ 14.531429] kjournald starting. Commit interval 5 seconds
[ 14.546631] EXT3 FS on sda3, internal journal
[ 14.561588] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.611015] kjournald starting. Commit interval 5 seconds
[ 14.626346] EXT3 FS on dm-3, internal journal
[ 14.641141] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.685104] kjournald starting. Commit interval 5 seconds
[ 14.699952] EXT3 FS on dm-2, internal journal
[ 14.714364] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.752134] kjournald starting. Commit interval 5 seconds
[ 14.766460] EXT3 FS on dm-0, internal journal
[ 14.780224] EXT3-fs: mounted filesystem with ordered data mode.
[ 14.841000] kjournald starting. Commit interval 5 seconds
[ 14.854725] EXT3 FS on dm-1, internal journal
[ 14.868207] EXT3-fs: mounted filesystem with ordered data mode.
[ 15.013563] kjournald starting. Commit interval 5 seconds
[ 15.027303] EXT3 FS on dm-4, internal journal
[ 15.040477] EXT3-fs: mounted filesystem with ordered data mode.
[ 15.141855] kjournald starting. Commit interval 5 seconds
[ 15.155362] EXT3 FS on dm-6, internal journal
[ 15.168501] EXT3-fs: mounted filesystem with ordered data mode.
[ 18.961074] kjournald starting. Commit interval 5 seconds
[ 18.974645] EXT3 FS on dm-5, internal journal
[ 18.987999] EXT3-fs: mounted filesystem with ordered data mode.
[ 22.853875] platform microcode: firmware: requesting intel-ucode/06-0f-02
[ 22.920562] platform microcode: firmware: requesting intel-ucode/06-0f-02
[ 22.942887] Microcode Update Driver: v2.00 tig...@aivazian.fsnet.co.uk,
Peter Oruba
[ 25.550273] NET: Registered protocol family 10
[ 25.564710] lo: Disabled Privacy Extensions
[ 52.027501] Bluetooth: L2CAP ver 2.11
[ 52.040834] Bluetooth: L2CAP
