Hi David, David Smith wrote:
> 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 turn off the Wifi using the network-manager-kde tool, rfkill then > shows this: > > 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# [...] > However, using rfkill unblock all results in this: [...] > I can then turn the wifi on again in network-manager-kde and connect to a > network in the network-manager-kde tool because it thinks the wifi is no > longer hardware blocked. [...] > [ 3.546082] ipw2200: Radio Frequency Kill Switch is On: > [ 3.546084] Kill switch must be turned off for wireless networking to work. Thanks for reporting it, and sorry for the slow response. Some ideas: - please attach "acpidump" output. - am I correct in imagining 3.5.y from experimental behaves the same way? - does the squeeze (2.6.32.y) kernel avoid trouble? It should work fine on a wheezy/sid system. Next step will be to take this upstream, but let's try to figure out what caused the regression (e.g., which subsystem) first. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
