[Surface Pro 2] WLAN not working

[uboot fanat]

When I boot the surface pro 2 device with a fresh installation of ubuntu (the gnome favour) with current updates, I expect NetworkManager to show me a wireless device.

What happens:
NetworkManager shows me an empty list.

Note:
since I do not have an internet connection from the device in question, I cannot provide you with the requested ubuntu-bug output.

Question:
I attached anything I can think of which might be helpful to resolve the issue. Please point me in the right direction on how I can debug this further.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1248917

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Quinn Balazs (qbalazs)]

Relevant outputs here would be "sudo lshw -class network" which will tell you how your wifi card(s) are recognized by the kernel, and "rfkill list all" which will tell if a wifi card is soft/hard blocked. If you are able to upload those, please set the status of this report back to new, and someone will take a look at it.

[uboot fanat (ubootfanat)]

"sudo lshw -class network" does not give any output.
"rfkill list all" only states a double "no" for the bluetooth device, no wifi devices are mentioned.

A bit of a surprise because the hardware should be the Marvell chip listed in the lsusb output. And the Wifi chip should be the same as in the surface pro v1. For the v1, people reported that ubuntu 13.10 just lists to many ethernet adapters in the network manager.

Please also find attached a full copy of Xorg.0.log and a dmesg dump to complement the log excerpt already posted before.

[uboot fanat (ubootfanat)]

Due to the fact that the wifi is the only buildin option to reach the internet I cannot use any automated tools that need internet access. Sorry. I therefore confirm the bug as it is.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1248917

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[uboot fanat (ubootfanat)]

there is a duplicate for this bug in fedora: https://bugzilla.kernel.org/show_bug.cgi?id=64111

as far as I can see the driver is directly compiled into ubuntu kernel?

[penalvch (penalvch)]

uboot fanat, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please just make a comment to this?

[goepfling (goepfling)]

Ubuntu shipped kernel:
Linux version 3.11.0-15-generic

lsusb:
Bus 002 Device 003: ID 1286:2043 Marvell Semiconductor, Inc.

kernel dmesg:
[ 2.762855] usb 2-2: new high-speed USB device number 3 using xhci_hcd
[ 2.781386] usb 2-2: New USB device found, idVendor=1286, idProduct=2043
[ 2.781390] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.781392] usb 2-2: Product: Marvell Wireless Device
[ 2.781393] usb 2-2: Manufacturer: Marvell
[ 2.781394] usb 2-2: SerialNumber: 0000000000000000
(and nothing more)

Note that kernel does never report "WLAN FW is active". Thus it is a mwifiex firmware problem.

[penalvch (penalvch)]

geopfling, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs