ipw2200 kill switch disables but won't enable (Asus M5200A)

[ 0.000000] Linux version 2.6.22-6-generic (buildd@rothera) (gcc version 4.1.3 20070528 (prerelease) (Ubuntu 4.1.2-9ubuntu2)) #1 SMP Fri Jun 1 19:24:12 GMT 2007
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000000f7c0000 (usable)
[ 0.000000] BIOS-e820: 000000000f7c0000 - 000000000f7cf000 (ACPI data)
[ 0.000000] BIOS-e820: 000000000f7cf000 - 000000000f800000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
[ 0.000000] BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 247MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000ff780
[ 0.000000] Entering add_active_range(0, 0, 63424) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 63424
[ 0.000000] HighMem 63424 -> 63424
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 63424
[ 0.000000] On node 0 totalpages: 63424
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 463 pages used for memmap
[ 0.000000] Normal zone: 58865 pages, LIFO batch:15
[ 0.000000] HighMem zone: 0 pages used for memmap
[ 0.000000] DMI 2.3 present.
[ 0.000000] ACPI: RSDP 000F6A40, 0014 (r0 ACPIAM)
[ 0.000000] ACPI: RSDT 0F7C0000, 0038 (r1 A M I OEMRSDT 3000525 MSFT 97)
[ 0.000000] ACPI: FACP 0F7C0200, 0084 (r2 A M I OEMFACP 3000525 MSFT 97)
[ 0.000000] ACPI: DSDT 0F7C0430, 7EF3 (r1 0AAAA 0AAAA000 0 INTL 2002026)
[ 0.000000] ACPI: FACS 0F7CF000, 0040
[ 0.000000] ACPI: APIC 0F7C0390, 0054 (r1 A M I OEMAPIC 3000525 MSFT 97)
[ 0.000000] ACPI: MCFG 0F7C03F0, 003C (r1 A M I OEMMCFG 3000525 MSFT 97)
[ 0.000000] ACPI: OEMB 0F7CF040, 0040 (r1 A M I AMI_OEM 3000525 MSFT 97)
[ 0.000000] ACPI: SSDT 0F7C8330, 0335 (r1 AMI CPU1PM 1 INTL 2002026)
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] Processor #0 6:13 APIC version 20
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000...

00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
        Subsystem: ASUSTeK Computer Inc. Unknown device 1997
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Capabilities: [e0] Vendor Specific Information

00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) (prog-if 00 [VGA])
        Subsystem: ASUSTeK Computer Inc. Unknown device 1882
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
        Region 1: I/O ports at ec00 [size=8]
        Region 2: Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Region 3: Memory at feb40000 (32-bit, non-prefetchable) [size=256K]
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
        Subsystem: ASUSTeK Computer Inc. Unknown device 1882
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Region 0: Memory at fea80000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [d0] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
        Subsystem: ASUSTeK Computer Inc. Unknown device 1993
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 20
        Region 0: Memory at feb38000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
                Address: 0000000000000000 Data: 0000
        Capabilities: [70] Express Unknown type IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s <64ns, L1 <1us
                Device: Errors: Correctable- Non-Fatal- Fatal- U...

hotkey ATKD 0000005f 00000000

I have the same problem with an acer Travelmate 4000.
Wireless was working perfectly in Feisty.
After an update to Gutsy, kill switch is always off. Pressing the button won't change the status.
Booting with the old 2.6.20-16 kernel works perfectly in gutsy, but the default kernel in gutsy
won't activate the card.

lspci:
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)

Same problem here with an Acer Travelmate 4000. The upgrade from Feisty was flawless but the problem first appeared after a hard restart: eth1 was disabled and "cat /sys/bus/pci/drivers/ipw2200/*/rf_kill" reported 2 instead of 0. This has always happened since the Dapper days (eth1 disabled after a hard restart, that is) but it wasn't a problem since the wireless switch button always worked so pressing it solved the issue and wireless always worked again.

However, in Gutsy the button doesn't work at all so the only way to make wireless work again is by using the acerhk module (editing /proc/driver/acerhk/wirelessled ); the weird thing is that even after the acerhk module is loaded and wireless is running, the button only works when switching off wireless, it doesn't switch it on again, therefore a new editing of /proc/driver/acerhk/wirelessled is needed to make wireless work again.

It is needless to say that this is a regression from old versions and the only solution available at the moment is a hack.

me@laptop:~% uname -a
Linux laptop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

me@laptop:~% lspci | grep -i "wireless"
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)

me@laptop:~% cat /proc/driver/acerhk/info
Acer hotkeys version 0.5.34
Model(Type) : TravelMate 4000(Dritek)
request handler : 0xc00fddc0
CMOS index : not available
kernel polling : active
autoswitch wlan : disabled
use of Dritek EC: enabled

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

It seems this is still present, but we're a lot closer to fixing this bug under Hardy/Intrepid:

The following will enable the radio after the kill switch has been pressed (fn-f2):

root@sundiver:/sys/devices/platform/asus-laptop# echo 1 > wlan

I am not sure how to bind this to Fn-F2, though...

Hi Tom,

Thanks for testing and the feedback. Can you capture and attach your entire dmesg output after doing the following:

1) first enabling the kill switch (ie disabling wireless)
2) attempting to disable the kill switch (ie re-enabling wireless)
3) and finally having to resort to doing root@sundiver:/sys/devices/platform/asus-laptop# echo 1 > wlan

I'm interested to see what gets logged for each step. Thanks.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.