[karmic][iwlagn][dell-wifi] MASTER "wireless disabled" for IWL 3945 4965 5100 and 5300 devices if booted with killswitch/rfkill enabled

[Sam Vilain]

Binary package hint: network-manager

After a fresh Karmic Koala install, Network Manager is showing Wireless as disabled, and it is not possible to enable it. However the device does work with the kernel.

My workaround: install an /etc/wpa_supplicant.conf file and running wpa_supplicant manually from /etc/network/interfaces

 samv@maia:~$ cat /etc/network/interfaces
 auto lo
 iface lo inet loopback

 #auto eth0
 iface eth0 inet dhcp

 #auto wlan0
 iface wlan0 inet dhcp
   pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B -s
   down killall wpa_supplicant

 samv@maia:~$ cat /etc/wpa_supplicant.conf
           ctrl_interface=/var/run/wpa_supplicant
           ctrl_interface_group=users

 #ap_scan=2

           #
           # home network; allow all valid ciphers
           network={
                ssid="MyNetwork"
                scan_ssid=1
         proto=WPA
         pairwise=TKIP
                key_mgmt=WPA-PSK
                psk="SecretPassword"
           }

 samv@maia:~$ sudo ifup wlan0

related kernel messages:

[ 11.573058] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27k
[ 11.573061] iwlagn: Copyright(c) 2003-2009 Intel Corporation
[ 11.573421] iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 11.573453] iwlagn 0000:0c:00.0: setting latency timer to 64
[ 11.573506] iwlagn 0000:0c:00.0: Detected Intel Wireless WiFi Link 4965AGN REV=0x4
[ 11.581549] Synaptics Touchpad, model: 1, fw: 6.2, id: 0xfa0b1, caps: 0xa04713/0x200000
[ 11.617029] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8
[ 11.626880] iwlagn 0000:0c:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
[ 11.626955] alloc irq_desc for 28 on node 0
[ 11.626957] alloc kstat_irqs on node 0
[ 11.626981] iwlagn 0000:0c:00.0: irq 28 for MSI/MSI-X
[ 11.724623] phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 11.848705] cfg80211: World regulatory domain updated:
[ 11.848708] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 11.848711] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 11.848714] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 11.848717] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 11.848719] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 11.848722] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

I think this was logged when I manually tried to 'iwlist wlan0 scanning';

[ 839.672238] iwlagn 0000:0c:00.0: firmware: requesting iwlwifi-4965-2.ucode
[ 839.743563] iwlagn 0000:0c:00.0: loaded firmware version 228.61.2.24
[ 839.962427] Registered led device: iwl-phy0::radio
[ 839.962465] Registered led device: iwl-phy0::assoc
[ 839.962500] Registered led device: iwl-phy0::RX
[ 839.962533] Registered led device: iwl-phy0::TX
[ 840.006024] ADDRCONF(NETDEV_UP): wlan0: link is not ready

With wpa_supplicant, logged:

[ 1756.714143] wlan0: authenticate with AP 00:1c:10:22:0f:e6
[ 1756.715971] wlan0: authenticated
[ 1756.715976] wlan0: associate with AP 00:1c:10:22:0f:e6
[ 1756.718684] wlan0: RX AssocResp from 00:1c:10:22:0f:e6 (capab=0x411 status=0 aid=1)
[ 1756.718690] wlan0: associated
[ 1756.742052] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1766.964090] wlan0: no IPv6 routers present
[ 1775.084236] wlan0: deauthenticating by local choice (reason=3)
[ 1775.116132] wlan0: deauthenticating by local choice (reason=3)
[ 1850.198667] Registered led device: iwl-phy0::radio
[ 1850.198705] Registered led device: iwl-phy0::assoc
[ 1850.198742] Registered led device: iwl-phy0::RX
[ 1850.198775] Registered led device: iwl-phy0::TX
[ 1850.235886] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1851.891766] wlan0: authenticate with AP 00:1c:10:22:0f:e6
[ 1851.893977] wlan0: authenticated
[ 1851.893984] wlan0: associate with AP 00:1c:10:22:0f:e6
[ 1851.896781] wlan0: RX AssocResp from 00:1c:10:22:0f:e6 (capab=0x411 status=0 aid=1)
[ 1851.896789] wlan0: associated
[ 1851.922217] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1862.244046] wlan0: no IPv6 routers present
[ 2409.221414] CE: hpet increasing min_delta_ns to 22500 nsec
[ 2738.508056] wlan0: deauthenticating by local choice (reason=3)

ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Sat Oct 3 21:08:11 2009
DistroRelease: Ubuntu 9.10
Gconf:

InterestingModules: b44
IpRoute:
 192.168.69.0/24 dev wlan0 proto kernel scope link src 192.168.69.233
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.69.1 dev wlan0 metric 100
Package: network-manager 0.8~a~git.20090923t064445.b20cef2-0ubuntu2
ProcEnviron:
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: network-manager
Tags: driver-b44
Uname: Linux 2.6.31-11-generic x86_64

[Sam Vilain (sam-vilain)]

I just saw another amd64 machine show the same problem - network manager just not wanting to control interfaces, even hard-wired. Again I had to revert to /etc/network/interfaces. The network manager daemon was running. I'm nominating this for release, because it seems serious to me.

[Alexander Sack (asac)]

1. ensure that you have nothing about your wlan in /etc/network/interfaces

please stopnm by running: sudo stop network-manager

Then start it from console:

sudo NetworkManager --no-daemon

and wait till all output has settled; attach the complete output it produced

(also be sure that you dont have connman installed.)

[Alexander Sack (asac)]

please confirm that this is still broken with the nm bits i uploaded now (wait ~5-10 hours and then upgrade).

If thats still a problem i need you to a) clean your /etc/network/interfaces (remove everything but 'lo' related stuff); reboot your system and attach your complete syslog to this bug.

[Andrew Allen (achew22-gmail)]

I updated a few hours ago and ever since I have been on wifi. No problems at all. I'm going to unsubscribe from this ticket as it seems to be fixed for me.

[Alexander Sack (asac)]

Sam, since you reported this bug initially, could you please upgrade to latest and check if this is fixed for you too? If not, please follow instructions i gave in comment #4

[Mohegan (jack-mohegan)]

I have the same problem with my dell inspiron 6400. My wireless card is also intel 4965 agn.
Network-manager don't see my card but I have this in the file /etc/udev/rules.d/70-persistent-net.rules :

# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x14e4:0x170c (b44)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:19:b9:72:a1:97", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x4229 (iwlagn)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:e8:21:ae:a7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"

So, I think the card is detected by the system but it doesn't work.

[Mohegan (jack-mohegan)]

I use Karmic (new install, 6 oct.).

[ With Jaunty, it was OK. ]

[Alexander Sack (asac)]

marking as dupe of new master bug 441161

[Alexander Sack (asac)]

looking at the RfKill.txt attached by all dupes it seems that NM does not touch your devices because they are listed as rfkilled.

Since you said you checked that the kill switch is off, i wonder if this might happen if you boot with kill switch on? Please try if its better if you keep the kill switch off when booting.

[Luca Cavalli (luca-cavalli)]

Indeed booting with rf switch on makes NM correctly handle the wireless connection. If the switch is off at boot time then NM will refuse to wakeup the wifi card. Note that bluetooth works always correctly and can be switched on and off with the very same switch.

[Alexander Sack (asac)]

can you check if booting with rfkill on, then turning it off, on and off again helps? (e.g. turn it on and off one more time).

[Luca Cavalli (luca-cavalli)]

If the rfkill switch is off at boot time it doesn't metter how many times you switch it. The wifi will never work. If the switch is on at boot time the rfkill switch will always works as expected, turning the wifi on and off.

[Emanuele Gissi (emanuele-gissi-gmail)]

In my Dell Vostro 1320 with Intel Wifi link 5100 the wifi does not work if I boot with rf switch on.
I dist-upgraded ten minutes ago.

[Mohegan (jack-mohegan)]

It is ok now. I did this :
1) Command : rfkill list

0: dell-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: yes
1: dell-bluetooth: Bluetooth
 Soft blocked: yes
 Hard blocked: yes
2: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

2) Command : sudo rfkill unblock all

3) Command : rfkill list

0: dell-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: yes
1: dell-bluetooth: Bluetooth
 Soft blocked: yes
 Hard blocked: yes
2: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

3) Turn on the hardware switch and it is OK.

4) Command : rfkill list

0: dell-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: dell-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
2: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: hci0: Bluetooth
 Soft blocked: no

BUT why it doesn't work after the installation ?

[Mohegan (jack-mohegan)]

1) If I reboot with the hardware switch ON, the wifi is OK

2) If I reboot with the hardware switch OFF, the wifi is NOT OK.

3) Command : rfkill list

0: dell-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: yes
1: dell-bluetooth: Bluetooth
 Soft blocked: yes
 Hard blocked: yes
2: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

4) Command : sudo rfkill unblock all.

5) Turn on the hardware switch and it is OK.

BUT the wireless switch only controls the bluetooth (bios configuration).
Any idea ?

[Mohegan (jack-mohegan)]

If the wifi is OK (with the command rfkill and the hardware switch), I can turn off the hardware switch and
the wifi works until the pc is not stopped.

[Emanuele Gissi (emanuele-gissi-gmail)]

I tried that, but it does not work on my Dell Vostro 1320.
Emanuele

On Wed, Oct 7, 2009 at 5:41 PM, Mohegan <email address hidden> wrote:

> 1) If I reboot with the hardware switch ON, the wifi is OK
>
> 2) If I reboot with the hardware switch OFF, the wifi is NOT OK.
>
> 3) Command : rfkill list
>
> 0: dell-wifi: Wireless LAN
> Soft blocked: no
> Hard blocked: yes
> 1: dell-bluetooth: Bluetooth
> Soft blocked: yes
> Hard blocked: yes
> 2: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 3: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
>
> 4) Command : sudo rfkill unblock all.
>
> 5) Turn on the hardware switch and it is OK.
>
> BUT the wireless switch only controls the bluetooth (bios configuration).
> Any idea ?
>
> --
> [karmic][iwlagn] MASTER "wireless disabled" for some IWL 4965 5100 and 5300
> devices
> https://bugs.launchpad.net/bugs/441161
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
My blog: http://www.corbezzolo.org/

[Noel J. Bergman (noeljb)]

On my Thinkpad T61p 6457-7WU, booting with the kill switch enabled (radios disabled) and then enabling the radios, it works fine. Attached, as a data point, is a log of udevadm monitor --env, and you can see what notices are sent to which NM reacted.

[Alexander Sack (asac)]

is anyone seeing this _not_ running a dell? also if you check output of "rfkill list" ... does something dell related show up?

[Alexander Sack (asac)]

for the record: we also have bug 445462 which is about "dell" + "rfkill" + "bluetooth" confusion. But since rfkill for wifi and bluetooth is implemented in the same dell-laptop.c code I get the feeling that this is related.

[Alexander Sack (asac)]

moving to kernel; kernel team, please check out whether bug 445326 (rfkill confusion for bluetooth) could be related. IMO both regressions are fall outs from the dell-laptop.c rewrite in 2.6.31; in particular see my comment here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/445326/comments/13

[Alexander Sack (asac)]

bug 445326 was the dupe ... i meant bug 445462

[Janne Hyötylä (janne-hyotyla)]

Added iwl 3945ABG to subject; this problem occurs on my Dell D630 Latitude with said intel chip.

[Alexander Sack (asac)]

milestoning as this seems to affect a lot of dell laptops.

[Boban Aleksov (aleksovboban)]

Again, this is not intel wlan problem, i have same problem with broadcom wifi. I can confirm same situation like Mohegan's.
However i installed http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.31.3/ this kernel and it appears that there are no problems with switch( it had normal logic ).

[Janne Hyötylä (janne-hyotyla)]

I confirm that with mainline 2.6.31.3 everything works as it should here, specifically:
If I have configured in BIOS that the killswitch only acts on bluetooth, WLAN stays on whether the killswitch is on or off during boot.

With the current karmic kernel, I have the same behaviour as in comment 16

[Alexander Sack (asac)]

this is a duplicate of bug 430809 which was just fixed in latest kernel

[Boban Aleksov (aleksovboban)]

Sadly but i must say new kernel didn't fix the bug.

On Fri, Oct 9, 2009 at 3:03 PM, Alexander Sack <email address hidden> wrote:

> this is a duplicate of bug 430809 which was just fixed in latest kernel
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Fix Released
>
> --
> [karmic][iwlagn][dell-wifi] MASTER "wireless disabled" for IWL 3945 4965
> 5100 and 5300 devices if booted with killswitch/rfkill enabled
> https://bugs.launchpad.net/bugs/441161
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: network-manager
>
> After a fresh Karmic Koala install, Network Manager is showing Wireless as
> disabled, and it is not possible to enable it. However the device does work
> with the kernel.
>
> My workaround: install an /etc/wpa_supplicant.conf file and running
> wpa_supplicant manually from /etc/network/interfaces
>
> samv@maia:~$ cat /etc/network/interfaces
> auto lo
> iface lo inet loopback
>
> #auto eth0
> iface eth0 inet dhcp
>
> #auto wlan0
> iface wlan0 inet dhcp
> pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B -s
> down killall wpa_supplicant
>
> samv@maia:~$ cat /etc/wpa_supplicant.conf
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=users
>
> #ap_scan=2
>
> #
> # home network; allow all valid ciphers
> network={
> ssid="MyNetwork"
> scan_ssid=1
> proto=WPA
> pairwise=TKIP
> key_mgmt=WPA-PSK
> psk="SecretPassword"
> }
>
> samv@maia:~$ sudo ifup wlan0
>
> related kernel messages:
>
> [ 11.573058] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux,
> 1.3.27k
> [ 11.573061] iwlagn: Copyright(c) 2003-2009 Intel Corporation
> [ 11.573421] iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ
> 17
> [ 11.573453] iwlagn 0000:0c:00.0: setting latency timer to 64
> [ 11.573506] iwlagn 0000:0c:00.0: Detected Intel Wireless WiFi Link
> 4965AGN REV=0x4
> [ 11.581549] Synaptics Touchpad, model: 1, fw: 6.2, id: 0xfa0b1, caps:
> 0xa04713/0x200000
> [ 11.617029] input: SynPS/2 Synaptics TouchPad as
> /devices/platform/i8042/serio1/input/input8
> [ 11.626880] iwlagn 0000:0c:00.0: Tunable channels: 11 802.11bg, 13
> 802.11a channels
> [ 11.626955] alloc irq_desc for 28 on node 0
> [ 11.626957] alloc kstat_irqs on node 0
> [ 11.626981] iwlagn 0000:0c:00.0: irq 28 for MSI/MSI-X
> [ 11.724623] phy0: Selected rate control algorithm 'iwl-agn-rs'
> [ 11.848705] cfg80211: World regulatory domain updated:
> [ 11.848708] (start_freq - end_freq @ bandwidth), (max_antenna_gain,
> max_eirp)
> [ 11.848711] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000
> mBm)
> [ 11.848714] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000
> mBm)
> [ 11.848717] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000
> mBm)
> [ 11.848719] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000
> mBm)
> [ 11.848722] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000
> mBm...

[Darin Miller (darinmiller)]

The latest patches (evening of 10/09/09) do not fix the wireless connection on Dell Vostro 1720 w/ Intel 5100 card.

rfkill with switch on:

0: phy0: Wireless LAN
      Soft blocked: no
      Hard blocked: no
1: dell: wifi: Wireless LAN
      Soft blocked: yes
      Hard blocked: yes

rfkill with switch off:

0: phy0: Wireless LAN
      Soft blocked: no
      Hard blocked: yes
1: dell: wifi: Wireless LAN
      Soft blocked: no
      Hard blocked: yes

rfkill unblock all and rfkill unblock wifi have no affect.

On a positive note, the latest update fixed the wireless issue on a Dell M1530 laptop w/ Intel PRO/Wireless 4965 AG or AGN card.

[Felix Geyer (debfx)]

Still doesn't work on my Desll Vostro 1320 with intel wifi 5100 (bug #413236).

When booting with killswitch on and later turning it off:
> rfkill list
0: hci0: Bluetooth
        Soft blocked: yes
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: dell-wifi: Wireless LAN
        Soft blocked: yes
        Hard blocked: yes

[wilbur.harvey (wilbur-harvey)]

I have a Sony VGN-FW373J, with the
06:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
The WiFi used to work fine a couple of days ago.
Using the .12, and .13 kernels, ( just updated this morning) the WiFi is always not ready.
I have tried booting with the RF Kill switch on and off, it doesn't matter.
test@elf-lj64:/etc/modprobe.d$ rfkill list
1: sony-wwan: Wireless WAN
 Soft blocked: no
 Hard blocked: no
2: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
9: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
Still no joy.

[andrea85 (andreabroka)]

I have a dell 6400 with a Intel (R) Wireless WiFi Link 4965AGN. Still can't switch on after switching off. The same problem even with the last update of kernel.

[Daniel Cardin (daniel-cardin)]

I have a Dell Vostro 1720 with a BCM4322 running wl on kernel 2.6.31-13 and it still exhibits the problem.

0: dell-wifi: Wireless LAN
 Soft blocked: yes
 Hard blocked: yes
1: dell-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: yes
2: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

[Mario Limonciello (superm1)]

Daniel:

Can you please test with Leann's latest kernel?

uname -a should have "#44+lp430809v3" in it.

On Sun, Oct 11, 2009 at 18:54, Daniel Cardin <email address hidden>wrote:

> I have a Dell Vostro 1720 with a BCM4322 running wl on kernel 2.6.31-13
> and it still exhibits the problem.
>
> 0: dell-wifi: Wireless LAN
> Soft blocked: yes
> Hard blocked: yes
> 1: dell-bluetooth: Bluetooth
> Soft blocked: no
> Hard blocked: yes
> 2: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
>
> --
> [karmic][iwlagn][dell-wifi] MASTER "wireless disabled" for IWL 3945 4965
> 5100 and 5300 devices if booted with killswitch/rfkill enabled
> https://bugs.launchpad.net/bugs/441161
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Mario Limonciello
<email address hidden>

[Daniel Cardin (daniel-cardin)]

I am fully updated and this is not the kernel I have ( 2.6.31-13-generic
#44-Ubuntu SMP )

How should I go about acquiring it so I can validate if it fixes the
problem?

Thanks

On Sun, Oct 11, 2009 at 8:06 PM, Mario Limonciello <email address hidden>wrote:

> Daniel:
>
> Can you please test with Leann's latest kernel?
>
> uname -a should have "#44+lp430809v3" in it.
>
> On Sun, Oct 11, 2009 at 18:54, Daniel Cardin
> <email address hidden>wrote:
>
> > I have a Dell Vostro 1720 with a BCM4322 running wl on kernel 2.6.31-13
> > and it still exhibits the problem.
> >
> > 0: dell-wifi: Wireless LAN
> > Soft blocked: yes
> > Hard blocked: yes
> > 1: dell-bluetooth: Bluetooth
> > Soft blocked: no
> > Hard blocked: yes
> > 2: hci0: Bluetooth
> > Soft blocked: no
> > Hard blocked: no
> >
> > --
> > [karmic][iwlagn][dell-wifi] MASTER "wireless disabled" for IWL 3945 4965
> > 5100 and 5300 devices if booted with killswitch/rfkill enabled
> > https://bugs.launchpad.net/bugs/441161
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> Mario Limonciello
> <email address hidden>
>
> --
> [karmic][iwlagn][dell-wifi] MASTER "wireless disabled" for IWL 3945 4965
> 5100 and 5300 devices if booted with killswitch/rfkill enabled
> https://bugs.launchpad.net/bugs/441161
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Federico Serafini (federico-serafini)]

I have a Dell Vostro 1320 laptop.
After installed new kernel 2.6.31.3 from kernel-ppa
(http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.31.3/), rfkill
switch seems to work.

Federico

On Mon, Oct 12, 2009 at 5:03 AM, Daniel Cardin <email address hidden> wrote:
> I am fully updated and this is not the kernel I have ( 2.6.31-13-generic
> #44-Ubuntu SMP  )
>
> How should I go about acquiring it so I can validate if it fixes the
> problem?
>
> Thanks
>
> On Sun, Oct 11, 2009 at 8:06 PM, Mario Limonciello
> <email address hidden>wrote:
>
>> Daniel:
>>
>> Can you please test with Leann's latest kernel?
>>
>> uname -a should have "#44+lp430809v3" in it.
>>
>> On Sun, Oct 11, 2009 at 18:54, Daniel Cardin
>> <email address hidden>wrote:
>>
>> > I have a Dell Vostro 1720 with a BCM4322 running wl on kernel 2.6.31-13
>> > and it still exhibits the problem.
>> >
>> > 0: dell-wifi: Wireless LAN
>> >        Soft blocked: yes
>> >        Hard blocked: yes
>> > 1: dell-bluetooth: Bluetooth
>> >        Soft blocked: no
>> >        Hard blocked: yes
>> > 2: hci0: Bluetooth
>> >        Soft blocked: no
>> >        Hard blocked: no
>> >
>> > --
>> > [karmic][iwlagn][dell-wifi] MASTER "wireless disabled" for IWL 3945 4965
>> > 5100 and 5300 devices if booted with killswitch/rfkill enabled
>> > https://bugs.launchpad.net/bugs/441161
>> > You received this bug notification because you are a direct subscriber
>> > of the bug.
>> >
>>
>>
>> --
>> Mario Limonciello
>> <email address hidden>
>>
>> --
>> [karmic][iwlagn][dell-wifi] MASTER "wireless disabled" for IWL 3945 4965
>> 5100 and 5300 devices if booted with killswitch/rfkill enabled
>> https://bugs.launchpad.net/bugs/441161
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
> --
> [karmic][iwlagn][dell-wifi] MASTER "wireless disabled" for IWL 3945 4965 5100 and 5300 devices if booted with killswitch/rfkill enabled
> https://bugs.launchpad.net/bugs/441161
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: network-manager
>
> After a fresh Karmic Koala install, Network Manager is showing Wireless as disabled, and it is not possible to enable it.  However the device does work with the kernel.
>
> My workaround: install an /etc/wpa_supplicant.conf file and running wpa_supplicant manually from /etc/network/interfaces
>
>  samv@maia:~$ cat /etc/network/interfaces
>  auto lo
>  iface lo inet loopback
>
>  #auto eth0
>  iface eth0 inet dhcp
>
>  #auto wlan0
>  iface wlan0 inet dhcp
>   pre-up wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B -s
>   down killall wpa_supplicant
>
>  samv@maia:~$ cat /etc/wpa_supplicant.conf
>           ctrl_interface=/var/run/wpa_supplicant
>           ctrl_interface_group=users
>
>  #ap_scan=2
>
>           #
>           # home network; allow all valid ciphers
>           network={
>                ssid="MyNetwork"
>                scan_ssid=1
>               proto=WPA
>               pairwise=TKIP
>                key_mgmt=WPA-PSK
>                psk="SecretPassword"
>           }
>
>  samv@maia:~$ sudo ...

[Janne Hyötylä (janne-hyotyla)]

Daniel: look at the comments in Bug #430809

For me (Dell Latitude D630, IWL3945) kernel #lp430809v3 + DKMS v4 package works almost perfectly, but there remains a bug in the switching logic:

Now the killswitch acts on both bluetooth and wlan although I have set in BIOS for it to only act on bluetooth.
Apart from that BT/WLAN are now perfectly and correctly switchable by hardware and software.

The mainline kernel #02063103 handles this correctly but has some small bugs that are gone in Leann's version, so Leann's would be the better one if it would respect the BIOS killswitch setting.

[Daniel Cardin (daniel-cardin)]

I have installed #lp430809v3 + DKMS v4 and I can feel it's getting close... Now wireless works properly IF and only IF I boot with the killswitch off. So this is progress for me, but it falls into the bug 441161 now.

When I boot with the killswitch on, the logic seems reversed meaning that the swithing to the OFF position triggers the wireless availability, nm-applet shows the available networks. But obviously, the hardware is turned off and it doesn't work. Reverting to the ON position, nm-applet is notified that the wireless is now disabled.

[Mohegan (jack-mohegan)]

After full upgrade, I have the same problem as Janne Hyötylä with my dell inspiron 6400.

[Daniel Cardin (daniel-cardin)]

With kernel 2.6.31.14 #47 the patches to the dell-laptop module have been committed and will probably fix the problem for many of you. I suggest you remove module dell-laptop-dkms for those of you who have installed it, and try upgrading to the new kernel.
Discussions about this are in bug 430809.

Fixes many dell laptops, including Dell Vostro 1720.

[Darin Miller (darinmiller)]

I can verify Daniel Cardin's comment, wireless is fixed on Dell Vostro 1720 (booting with wireless switch on is working perfectly). Thanks a bunch!