Bug#684352: Wifi kill switch always on unless ACPI=off is used

[David Smith]

With acpi=off

Miho:/home/david# rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no


Without using acpi=off

Miho:/home/david# rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
Miho:/home/david#

This where it says the wireless is hard blocked, which is incorrect as I
can just do this with software...

Miho:/home/david# rfkill unblock all
Miho:/home/david# rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

Then it shows that it is not hard blocked.



After that, the wireless now seems to be working.  I press the hardware
switch to disable the wireless and then I get...

Miho:/home/david# rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
Miho:/home/david#


Which is correct as expected... Aside from the fact that it appears I have
two wireless devices when I do not.

1) The problem seems to be that every time the PC is started for the first
time, rfkill says the wireless is both hardware and software blocked, but
really it is just software blocked.
2) rfkill seems to suggest I have two wireless LAN network cards, this is
incorrect.  One of my wireless LAN connections disappears when I boot with
ACPI=off, the wireless is not hardware or software blocked, and the
wireless works.

Bug#684352: Wifi kill switch always on unless ACPI=off is used

[Ben Hutchings]

On Wed, 2012-08-08 at 23:19 -0400, David Smith wrote:
 Package: linux-image-3.2.0-3-686-pae
 Version: 3.2.21-3
 Architecture: i386
 
 Hardware: 6-year old laptop with Pentium-M CPU and Intel 2200
 wireless.
 
 
 This is a problem that just started happening after I updated to
 Wheezy.
 
 When I boot my PC with the default Debian kernel for Wheezy and the
 ipw2x00 firmware package, I get a message saying my wireless
 killswitch is on. Pressing the Wifi button on my laptop and
 rebooting gives the same results.  I pressed the Wifi button and it
 doesn't light up like it did in Squeeze or Lenny.  The button
 stays dark.
 
 When I boot the kernel with ACPI=off, the Wifi button immediately
 starts slowly blinking right after grub indicating that the Wifi is on
 and waiting for me to specify a wireless network.  When it gets to my
 Desktop, I am easily able to connect to a Wifi network.I've tried
 half a dozen times to get Wifi working without having to use ACPI=off,
 but it just doesn't work anymore unless I use ACPI=off everytime I
 boot.
[...]

Please provide the full boot messages (/var/log/dmesg) from the old and
new kernel versions.

Ben.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.


signature.asc
Description: This is a digitally signed message part

Bug#684352: Wifi kill switch always on unless ACPI=off is used

[David Smith]

Package: linux-image-3.2.0-3-686-pae
Version: 3.2.21-3
Architecture: i386

Hardware: 6-year old laptop with Pentium-M CPU and Intel 2200 wireless.


This is a problem that just started happening after I updated to Wheezy.

When I boot my PC with the default Debian kernel for Wheezy and the ipw2x00
firmware package, I get a message saying my wireless killswitch is on.
Pressing the Wifi button on my laptop and rebooting gives the same
results.  I pressed the Wifi button and it doesn't light up like it did
in Squeeze or Lenny.  The button stays dark.

When I boot the kernel with ACPI=off, the Wifi button immediately starts
slowly blinking right after grub indicating that the Wifi is on and waiting
for me to specify a wireless network.  When it gets to my Desktop, I am
easily able to connect to a Wifi network.I've tried half a dozen times
to get Wifi working without having to use ACPI=off, but it just doesn't
work anymore unless I use ACPI=off everytime I boot.



david@Miho:~$ dmesg | grep ipw
[2.941208] libipw: 802.11 data/management/control stack, git-1.1.13
[2.941211] libipw: Copyright (C) 2004-2005 Intel Corporation 
jketr...@linux.intel.com
[2.955322] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver,
1.2.2kmprq
[2.955325] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[3.194528] ipw2200 :06:05.0: PCI INT A - GSI 20 (level, low) -
IRQ 20
[3.194550] ipw2200: Detected Intel PRO/Wireless 2200BG Network
Connection
[3.729545] ipw2200: Radio Frequency Kill Switch is On:
[3.740907] ipw2200: Detected geography ZZM (11 802.11bg channels, 0
802.11a channels)
[   11.992040] ipw2200: Failed to send POWER_MODE: Command timed out.

The above is the results I get in the log.  It says the Kill Switch is ON,
but I know for a fact that it is not as I can just reboot and choose
ACPI=off and it will work just fine.


david@Miho:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express
Processor to DRAM Controller (rev 04)
00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express
Root Port (rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
PCI Express Port 1 (rev 04)
00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #1 (rev 04)
00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #2 (rev 04)
00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #3 (rev 04)
00:1d.3 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB UHCI #4 (rev 04)
00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) USB2 EHCI Controller (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4)
00:1e.2 Multimedia audio controller: Intel Corporation
82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 04)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97
Modem Controller (rev 04)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge
(rev 04)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
Family) IDE Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus
Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
Radeon Mobility X700 (PCIE)
06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG
[Calexico2] Network Connection (rev 05)
06:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
06:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394
Host Controller
06:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated
FlashMedia Controller
06:06.4 SD Host controller: Texas Instruments
PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
david@Miho:~$


david@Miho:~$ dpkg -l | grep ipw
ii  firmware-ipw2x00
0.36Binary firmware for Intel Pro Wireless
2100, 2200 and 2915

david@Miho:/mnt/320GB/home/david$ dpkg -l | grep linux-image
ii  linux-image-3.2.0-3-686-pae
3.2.21-3Linux 3.2 for modern PCs



Please excuse me if this is a firmware-ipw2x00 bug instead of a kernel bug,
I really don't know where to put this.  Since setting ACPI=off in the boot
options fixes it, I'm assuming it's a kernel bug.