I'm experiencing a similar problem and was going to report it as a new bug, but found this one instead. I hope my version of the problem fits.
I used Hardy Heron for the last 3 weeks or so and noticed that my wireless kill switch doesn't work when I boot my laptop after a complete shutdown. So I recently updated to Intrepid Ibex and will in the future update to "whatever the next version is called" ;-) but the problem is still present. By not working I mean that "nothing" happens when I move the kill switch into the ON or OFF position (I observed the usual log files dmesg, messages, syslog and kern.log). The only thing I do notice every time I get into that state are the following two lines during boot in the kern.log and messages log: Mar 23 07:46:03 snibril kernel: [ 20.363271] ipw2200: Radio Frequency Kill Switch is On: Mar 23 07:46:03 snibril kernel: [ 20.363274] Kill switch must be turned off for wireless networking to work. In order to get my wireless to work, I have to: * boot into Windows XP * log in * activate wireless (which means turning the kill switch OFF I guess?) * reboot into Ubuntu Funny enough if I have my wireless kill switch working in Ubuntu and do a reboot into Ubuntu the kill switch still works as intended. Only a complete shutdown gets me back to square one where I have to boot into Windows XP first. I haven't tested suspend to RAM or suspend to disk. That's it basically. Info that might be helpfull: Laptop: Acer TravelMate 290 (I think the exact version is something like TravelMate 292LMI but I'm not sure) Ubuntu: Intrepid Ibex Linux Kernel version: 2.6.27-11-generic I also attached an "lspci -vv" output of my laptop in case it is needed. If anything else is needed just tell me! I'd really like to get this fixed so I'll be checking this report daily Thanks for reading ** Attachment added: "lspci -vv output of my laptop" http://launchpadlibrarian.net/24285625/lspci_-vv.txt -- Acer laptop & ipw2200: Recent upgrade breaks radio kill-switch https://bugs.launchpad.net/bugs/145290 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
