This is the rfkill device that the ath5k device itself implements, based on the state of an a signal connected to one of the input pins on the wireless card. It is possible that updating your bios will help, so that's might be worth a shot. Otherwise I can think of a couple of possible problems, either that your hardware is unusual and the ath5k driver isn't handling it correctly or else that there are some non- standard hooks into your bios to control rfkill that the kernel doesn't know about.
In any case, I have a workaround which should work. Try running the following commands, which should disable the ath5k rfkill device: sudo modprobe -r ath5k sudo modprobe ath5k no_hw_rfkill_switch=1 This is only temporary, and it will reset when you reboot. If it works then you can make it permanent by creating a file named /etc/modprobe.d/ath5k.conf which contains the following line: options ath5k no_hw_rfkill_switch=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495792 Title: wireless lan had blocked: yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495792/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
