Bug 1089571 - Wireless Device is not detected with Kernal 3.13.10
Summary: Wireless Device is not detected with Kernal 3.13.10
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-21 01:22 UTC by mswal28462
Modified: 2014-04-22 14:18 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-22 13:17:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg from a boot using kernal 3.13.9 (81.39 KB, text/plain)
2014-04-21 16:11 UTC, mswal28462
no flags Details
lspci output (1.71 KB, text/plain)
2014-04-21 16:12 UTC, mswal28462
no flags Details
Details on wireless (587 bytes, text/plain)
2014-04-21 16:13 UTC, mswal28462
no flags Details
info on module loaded (17.58 KB, text/plain)
2014-04-21 16:14 UTC, mswal28462
no flags Details
info on my system (10.75 KB, text/plain)
2014-04-21 16:14 UTC, mswal28462
no flags Details
dmesg after booting up with 3.13.10 (50.46 KB, text/plain)
2014-04-22 01:09 UTC, mswal28462
no flags Details
lspci command after booting 3.13.10 Kernel (1.71 KB, text/plain)
2014-04-22 01:10 UTC, mswal28462
no flags Details
Detailed lspic results after booting 3.13.10 (2.09 KB, text/plain)
2014-04-22 01:11 UTC, mswal28462
no flags Details

Description mswal28462 2014-04-21 01:22:42 UTC
Description of problem:

After installing update that brought in Kernel 3.13.10, my wireless device is no longer detected.  When I boot up 3.13.9, all is fine.


Version-Release number of selected component (if applicable): 3.13.20


How reproducible: Everytime I boot up with 3.13.10, no wireless


Steps to Reproduce:
1.Bootup using Kernel 3.13.10
2.
3.

Actual results:  No Wireless device to which to choose


Expected results:  Wireless device should start, like it does under 3.13.9


Additional info:

Comment 1 Josh Boyer 2014-04-21 13:31:42 UTC
What wireless device and driver are you using?  Can you please attach the output of dmesg from a fresh boot of both 3.13.9 and 3.13.10?

Comment 2 mswal28462 2014-04-21 16:11:59 UTC
Created attachment 888125 [details]
dmesg from a boot using kernal 3.13.9

Requested to provide info from both 3.13.9 and 3.13.10 boots.  Attached is the info from 3.13.9

Comment 3 mswal28462 2014-04-21 16:12:47 UTC
Created attachment 888127 [details]
lspci output

Requested to provide info from both 3.13.9 and 3.13.10 boots.  Attached is the info from 3.13.9

Comment 4 mswal28462 2014-04-21 16:13:30 UTC
Created attachment 888128 [details]
Details on wireless

Requested to provide info from both 3.13.9 and 3.13.10 boots.  Attached is the info from 3.13.9

Comment 5 mswal28462 2014-04-21 16:14:11 UTC
Created attachment 888129 [details]
info on module loaded

Requested to provide info from both 3.13.9 and 3.13.10 boots.  Attached is the info from 3.13.9

Comment 6 mswal28462 2014-04-21 16:14:49 UTC
Created attachment 888130 [details]
info on my system

Requested to provide info from both 3.13.9 and 3.13.10 boots.  Attached is the info from 3.13.9

Comment 7 mswal28462 2014-04-21 16:20:53 UTC
I've attached the information for 3.13.9.  I will get the 3.13.10 info when I can shut down and reboot my machine ... will be later as I'm using my machine for work.

Comment 8 mswal28462 2014-04-22 01:09:46 UTC
Created attachment 888309 [details]
dmesg after booting up with 3.13.10

Adding information requested with 3.13.10 kernel.

Comment 9 mswal28462 2014-04-22 01:10:40 UTC
Created attachment 888310 [details]
lspci command after booting 3.13.10 Kernel

Adding information requested with 3.13.10 kernel.

Comment 10 mswal28462 2014-04-22 01:11:44 UTC
Created attachment 888311 [details]
Detailed lspic results after booting 3.13.10

Adding information requested with 3.13.10 kernel.

Comment 11 mswal28462 2014-04-22 01:12:27 UTC
Ok, posted the requested information.  Please let me know what additional information you require.  Thanks!

Comment 12 Josh Boyer 2014-04-22 12:29:28 UTC
I see you're loading the virtual box drivers in the 3.13.9 kernel.  If you remove those drivers does 3.13.10 boot up as expected?

There doesn't seem to be any attempt to even load a portion of the drivers that should be loaded.  Perhaps the vbox module loading service is failing and preventing the rest of startup from working.

If you run 'modprobe iwlwifi' manually, does wireless start working?

Comment 13 mswal28462 2014-04-22 12:35:25 UTC
I did attempt to run "modprobe iwlwifi", but wireless still did not work.  I was expecting it to also.

I can try to remove vbox and see if that helps.  Obviously, though, I can not run without vbox.  So this will not be a long term solution.  But I'll try it for diagnostic purposes.

Comment 14 Josh Boyer 2014-04-22 12:43:02 UTC
Do you have anything else in your logs that might provide more info?  What does 'modprobe iwlwifi' report when you run it?  Is it loaded after that?

Comment 15 mswal28462 2014-04-22 13:10:46 UTC
Ok, so you must have been right.  I removed Virtualbox (which I had downloaded from Oracle Virtualbox web site) and booted up 3.13.10 and wireless was working.

I then reinstalled Virtualbox.  It pulled in a kernel module for 3.13.10 as a dependency.  

I was then able to reboot and everything (wireless and virtualbox) were both working.

I'm not sure why the change as I've not had to in previous kernel upgrades have to worry about Virtualbox kernel modules but apparently I do now.  Any idea on why that is?

Comment 16 Josh Boyer 2014-04-22 13:17:31 UTC
Sorry, I really don't know why you had issues because of virtualbox.  Fedora doesn't provide or support it, so you might want to discuss it with whomever you got virtualbox from.

Comment 17 mswal28462 2014-04-22 14:18:53 UTC
Ok, I understand.  THANK YOU very much for all of your help!


Note You need to log in before you can comment on or make changes to this bug.