Re: Kernel update causes wireless to disable [UPDATE - SOLVED]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/13/2013 17:09, Steven Stern wrote:
> On 11/13/2013 02:32 PM, Don Levey wrote:
>> My wife's laptop was running fine on kernel 3.10.11-200:
>>
>> uname -a:
>> Linux croweflies.the-leveys.us 3.10.11-200.fc19.x86_64 #1 SMP Mon Sep 9
>> 13:03:01 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>
>> lspci -s 03:00.0:
>> 03:00.0 Network controller: Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe
>>
>> rfkill list wlan:
>> 1: phy0: Wireless LAN
>> 	Soft blocked: no
>> 	Hard blocked: no
>>
>> I neither had nor needed any additional kernel modules.  However, when I
>> upgraded kernels:
>>
>> uname -a:
>> Linux croweflies.the-leveys.us 3.11.2-201.fc19.x86_64 #1 SMP Fri Sep 27
>> 19:20:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>
>> lspci -s 03:00.0:
>> 03:00.0 Network controller: Ralink corp. RT5390 Wireless 802.11n 1T/1R PCIe
>>
>>
>> rfkill list wlan:
>> 0: asus-wlan: Wireless LAN
>> 	Soft blocked: no
>> 	Hard blocked: no
>> 1: phy0: Wireless LAN
>> 	Soft blocked: no
>> 	Hard blocked: yes
>>
>> Now I've got "asus-wlan" while my original one is listed as "hard
>> blocked." The problem is that the "asus-wlan" doesn's show as an
>> available interface, and I cannot connect.  Any suggestions?
>>  -Don
>>
> This should be posted in Bugzilla. I've had excellent responses when
> posting kernel-related wireless issues there.
> 
Indeed, they were very helpful.  The first proposed solution (wapf=4)
worked for me:
https://bugzilla.redhat.com/show_bug.cgi?id=1030504

"Things work because, asus-rfkill is not created due some APCI problems.
On updated 3.11 kernel, ACPI problems were fixed and we have new asus
rfkill interface.

Phy 0 hard blocked is result of reading RFKILL bit from PCI register on
RT5390 device, it could be bug on rt2x00 driver, but more probable is
that ACPI/BIOS set that bit on PCI device as we have also similar
problem with Broadcom device in bug 1028737. Hence this issue is most
likely either bug on ACPI/BIOS or asus_wmi driver.

Dan, could you check if adding wapf=4 module option helps:

echo 'options asus-nb-wmi wapf=4' > /etc/modprobe.d/asus.conf

(you have to restart system to make new option take effect).

If not, you can blacklist asus_wmi driver, but that will also stop all
special keys functionality on your laptop."

 -Don
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org




[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux