[Surface Pro 3] Marvell 88W8897 wifi (module mwifiex) does not work

[PaulSchulz]

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-13-generic 5.0.0-13.14
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: paul 2763 F.... pulseaudio
 /dev/snd/controlC1: paul 2763 F.... pulseaudio
Date: Wed May 8 16:35:11 2019
InstallationDate: Installed on 2018-01-13 (480 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Microsoft Corporation Surface Pro 3
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=2aaa6b5c-4cbb-4d78-92b5-b8f96f30eb4f ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic N/A
 linux-firmware 1.178
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-04-23 (14 days ago)
dmi.bios.date: 06/12/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.11.2550
dmi.board.asset.tag: 0
dmi.board.name: Surface Pro 3
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: 0
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 1
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2550:bd06/12/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
dmi.product.family: Surface
dmi.product.name: Surface Pro 3
dmi.product.sku: Surface_Pro_3
dmi.product.version: 1
dmi.sys.vendor: Microsoft Corporation

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[penalvch (penalvch)]

PaulSchulz, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the Bug Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

In addition, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

[PaulSchulz (paulschulz)]

(My apologies for the delay. I needed to turn off SecureBoot to do this testing.)

Still occurs in packages for:

v5.2.0-rc1
modprobe mwifiex_pcie

tail -f /var/log/syslog -n 1000 | grep mwifiex_pcie
May 20 22:27:52 darkblue kernel: [ 157.644559] mwifiex_pcie: try set_consistent_dma_mask(32)
May 20 22:27:52 darkblue kernel: [ 157.644586] mwifiex_pcie: PCI memory map Virt0: 00000000623c6410 PCI memory map Virt2: 00000000ac5a8033
May 20 22:27:52 darkblue kernel: [ 157.749558] mwifiex_pcie 0000:01:00.0: PCI-E is not the winner <0x6>
May 20 22:27:52 darkblue kernel: [ 157.749561] mwifiex_pcie 0000:01:00.0: WLAN is not the winner! Skip FW dnld
May 20 22:28:08 darkblue kernel: [ 173.953407] mwifiex_pcie 0000:01:00.0: FW failed to be active in time
May 20 22:28:08 darkblue kernel: [ 173.953414] mwifiex_pcie 0000:01:00.0: info: _mwifiex_fw_dpc: unregister device

[penalvch (penalvch)]

PaulSchulz, the issue you are reporting is an upstream one. Could you please report this problem following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Amitkumar Karwar, Nishant Sarmukadam, Ganapathi Bhat, and Xinming Hu CC linux-wireless)?

This article was written for folks who don't know anything about linux, so it's easy to follow.

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your help.

[PaulSchulz (paulschulz)]

Just linking here for future reference. Work on additional support for Surface Pro 3 hardware can be found here: https://github.com/jakeday/linux-surface