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
On 11/13/2013 03:32 PM, Don Levey wrote:
My wife's laptop was running fine on kernel 3.10.11-200: Linux croweflies.the-leveys.us 3.10.11-200.fc19.x86_64 #1 SMP Mon Sep 9
uname -a:
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
The new kernel has most liklely discontinued you wireless driver.
Restart your laptop and "down arrow" to the previous kernel-3.10.11-200 and boot up on that.
If you get the wireless working again, do a yum remove kernel-3.11.2-201.fc19.x86_64
Then do a yum install yum-plugin-versionlock.
Then get into your SU filemanager and go to /etc/yum/pluginconf.d/versionlock.list file and open.
Then do a rpm -qa | grep kernel and copy and paste every kernel package related to kernel-3.10.11-200 into the /etc/yum/pluginconf.d/versionlock.list file and do a Save on file.
In doing this yum will never update any kernel above kernel-3.10.11-200 and you should never have any more wireless problems until you upgrade to the next version of Fedora.
On 11/13/2013 16:20, Jim wrote:
On 11/13/2013 03:32 PM, Don Levey wrote:
My wife's laptop was running fine on kernel 3.10.11-200: Linux croweflies.the-leveys.us 3.10.11-200.fc19.x86_64 #1 SMP Mon Sep 9
...
In doing this yum will never update any kernel above kernel-3.10.11-200 and you should never have any more wireless problems until you upgrade to the next version of Fedora.
Jim, I had considered that, but am reluctant to purposely avoid new kernels with potential fixes to other problems known and unknown. If support was removed from the kernel, do you know if it was added in terms of (a)kmod support? I've not yet seen anything about it.
As a (perhaps) related question: It is my understanding that if I were to use akmod (as opposed to kmod) it would dynamically download necessary modules at startup time if an updated kernel is detected. However, if what is necessary is network drivers, that would create a sort of chicken-and-egg problem, wouldn't it? Should I avoid akmod in favor of kmod (for network components) for this reason?
-Don
On 11/14/2013 08:55 AM, Don Levey wrote:
On 11/13/2013 16:20, Jim wrote:
On 11/13/2013 03:32 PM, Don Levey wrote:
My wife's laptop was running fine on kernel 3.10.11-200: Linux croweflies.the-leveys.us 3.10.11-200.fc19.x86_64 #1 SMP Mon Sep 9
...
In doing this yum will never update any kernel above kernel-3.10.11-200 and you should never have any more wireless problems until you upgrade to the next version of Fedora.
Jim, I had considered that, but am reluctant to purposely avoid new kernels with potential fixes to other problems known and unknown. If support was removed from the kernel, do you know if it was added in terms of (a)kmod support? I've not yet seen anything about it.
As a (perhaps) related question: It is my understanding that if I were to use akmod (as opposed to kmod) it would dynamically download necessary modules at startup time if an updated kernel is detected. However, if what is necessary is network drivers, that would create a sort of chicken-and-egg problem, wouldn't it? Should I avoid akmod in favor of kmod (for network components) for this reason?
-Don
It also killed Skype ! Had an important skypecon last night, lucky I had a ubuntu install on another disk. Roger
On 11/13/2013 01:55 PM, Don Levey wrote:
As a (perhaps) related question: It is my understanding that if I were to use akmod (as opposed to kmod) it would dynamically download necessary modules at startup time if an updated kernel is detected.
No. It builds a new kmod as needed at boot. If it had to download the module, you'd be stuck if the new kmod wasn't ready yet.
On 11/13/2013 21:15, Joe Zeff wrote:
On 11/13/2013 01:55 PM, Don Levey wrote:
As a (perhaps) related question: It is my understanding that if I were to use akmod (as opposed to kmod) it would dynamically download necessary modules at startup time if an updated kernel is detected.
No. It builds a new kmod as needed at boot. If it had to download the module, you'd be stuck if the new kmod wasn't ready yet.
Ah, so it has the parts it needs already? Cool! -Don
On Wed, 2013-11-13 at 16:55 -0500, Don Levey wrote:
On 11/13/2013 16:20, Jim wrote:
On 11/13/2013 03:32 PM, Don Levey wrote:
My wife's laptop was running fine on kernel 3.10.11-200: Linux croweflies.the-leveys.us 3.10.11-200.fc19.x86_64 #1 SMP Mon Sep 9
...
In doing this yum will never update any kernel above kernel-3.10.11-200 and you should never have any more wireless problems until you upgrade to the next version of Fedora.
That was really _bad_ advice. It would be extremely rare for a device to be randomly dropped from the kernel, especially one that is still modern and available.
Jim, I had considered that, but am reluctant to purposely avoid new kernels with potential fixes to other problems known and unknown. If support was removed from the kernel, do you know if it was added in terms of (a)kmod support? I've not yet seen anything about it.
As you intuit, cutting oneself off from future kernel updates is an overreaction.
If your device has stopped working, then open a bug.
John
On 11/14/2013 09:23, John W. Linville wrote:
As you intuit, cutting oneself off from future kernel updates is an overreaction.
If your device has stopped working, then open a bug.
John, I posted a bug in the kernel Bugzilla, but as they mentioned I should open in Fedora I will do that. Thanks! -Don
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.
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
-
Don Levey -
Joe Zeff -
John W. Linville -
Mickey -
Roger -
SternData