Hi All, I'm an upstream kernel developer who happened to stumble over this bug. The proper solution here is to add a dmi based quirk to the asus-nb-wmi driver to use wapf=4 by default. Note the wapf=4 not wapf=1 which everyone has been testing with sofar.
I would like to add a proper fix for this to the upstream kernel (which should then eventually find its way to the ubuntu kernels when ubuntu switches to a newer kernel). I need your help for this. First of all please adjust the workaround with the /etc/modprobe.d/asus_nb_wmi.conf file to set wapf to 4. Then reboot and test that wifi still works, and if you've bluetooth and that that also works. Once you've confirmed that everything is fine with wapf=4, run the following command: cat /sys/class/dmi/id/product_name >From a terminal and add a post here with the output of this command. Then I can add a quirk for your model to asus-nb-wmi.c and send a patch upstream. Thanks, Hans -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173681 Title: 168c:002b [asus_nb_wmi] [Asus U32U] AR9285 ath9k not working after updating to ubuntu 13.04 Raring (linux 3.8.0-19-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1173681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
