Wfif disconnects throughout session and is unusualy slow during connection. RT5390 Wireless 802.11n 1T/1R PCIe rt2800pci 4.4.0-36-generic

[Brian Carrozza]

I have researched all possible solutions. The correct driver rt2800pci is installed correctly out of the box. No hardware faults. Wifi works on Ubuntu 14.04 with rt2800pci, but better with rt5390sta fixed for Ralink wlan driver found here https://github.com/wapmesquita/2011_1007_RT5390_RT5392_Linux_STA_V2.5.0.3_DPO_v2

This fix does not work for 16.04.

I can sometimes regain functionality for a limited time by using network manager to un-check "Enable Networking" and the recheck it.

I have tried connecting by Ethernet cable and get the same behavior.

Description: Ubuntu 16.04.1 LTS
Release: 16.04

Ubuntu 4.4.0-36.55-generic 4.4.16

pcilib: sysfs_read_vpd: read failed: Connection timed out

N: Unable to locate package rt2800pci

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-36-generic 4.4.0-36.55
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: c 3056 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Sep 12 23:20:43 2016
HibernationDevice: RESUME=UUID=43ee12f4-be75-44a8-8a7f-767c3d6ec102
InstallationDate: Installed on 2016-08-10 (33 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK COMPUTER INC. X45A
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=c4ae6793-3631-4ddf-9fae-7329aa048736 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware 1.157.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X45A.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X45A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX45A.209:bd09/14/2012:svnASUSTeKCOMPUTERINC.:pnX45A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX45A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X45A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

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

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the 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 upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed 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 report 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 mainline kernel does not fix the issue, 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.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

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

Thank you for your help.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Brian Carrozza (carrozza-bc)]

I recently began to suspect my disconnects were due to interference. This
weekend I installed a wireless card 5GHz capable. It's may be too soon to
say, but I think the issue is solved. If so, it seems that it may have been
an interference issue. At the same time, I have only been connecting with
5GHz.

On Sep 13, 2016 4:55 AM, "Christopher M. Penalver" <
<email address hidden>> wrote:

> Brian Carrozza, thank you for reporting this and helping make Ubuntu
> better.
>
> In order to allow additional upstream developers to examine the issue, at
> your earliest convenience, could you please test the latest upstream kernel
> available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ?
> Please keep in mind the following:
> 1) The one to test is at the very top line at the 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 upstream kernel, please comment on
> which kernel version specifically you tested. If this issue is fixed 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 report 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 mainline kernel does not fix the issue, 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.
>
> It is most helpful that after testing of the latest upstream kernel is
> complete, you mark this report Status Confirmed.
>
> Lastly, to keep this issue relevant to upstream, please continue to test
> the latest mainline kernel as it becomes available.
>
> Thank you for your help.
>
> ** Tags added: latest-bios-209
>
> ** Attachment removed: "lspci-vnvn.log"
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1622853/+attachment/4739671/+files/lspci-vnvn.log
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1622853
>
> Title:
> Wfif disconnects throughout session and is unusualy slow during
> connection....