WiFi connects to AP, but doesn't work. Setting rate to auto fixes it.

Bug #1327670 reported by Didi
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Fresh 14.04 install on a Packard Bell Notebook.

WiFi device:
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192SE Wireless LAN Controller (rev 10)

rtl8192se kernel module

If connecting to my home WiFi, it shows as connected, but there is no connectivity. I can't ping anything, not even the access point itself, althought DHCP settings are retrieved correctly.
iwconfig reports a rate stuck at 1Mb/s, although link quality is 70/70 and Signal level -28dBm.
If I set the rate to auto with "iwconfig wlan0 rate auto", it switches to 54 Mb/s (max the AP supports) and everything seems to work fine (I used it for few hours now, downloaded few 100 MB, mostly Ubuntu packages).

When connecting to an Android Hotspot, the problem doesn't occur, thus it seems to be AP dependent.
Difference in dmesg between connecting to the "bad" and the "good" AP:
When connecting to the bad one, it additionally shows this 2 lines:
[10961.059621] rtl8192se 0000:02:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[10961.059626] rtl8192se 0000:02:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
Don't know if that's related.

I've been connected to this AP with a lot of devices (mainly mobile) without any issues.

The AP is a Linksys WRT54GL with Tomato 1.28 firmware.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-firmware 1.127.2
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Sun Jun 8 02:20:45 2014
Dependencies:

InstallationDate: Installed on 2014-06-07 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aida 1849 F.... pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=3b1b248a-c783-4dca-a900-1c7aa27863e5
InstallationDate: Installed on 2014-06-07 (11 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0402:9665 ALi Corp. Gateway Webcam
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Packard Bell EasyNote TK85
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=ab640bfe-9bc6-4e2d-a1a9-747545b2e0db ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-29-generic N/A
 linux-backports-modules-3.13.0-29-generic N/A
 linux-firmware 1.127.2
Tags: trusty
Uname: Linux 3.13.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 08/24/2010
dmi.bios.vendor: Packard Bell
dmi.bios.version: V1.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: EasyNote TK85
dmi.board.vendor: Packard Bell
dmi.board.version: V1.05
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V1.05
dmi.modalias: dmi:bvnPackardBell:bvrV1.05:bd08/24/2010:svnPackardBell:pnEasyNoteTK85:pvrV1.05:rvnPackardBell:rnEasyNoteTK85:rvrV1.05:cvnPackardBell:ct10:cvrV1.05:
dmi.product.name: EasyNote TK85
dmi.product.version: V1.05
dmi.sys.vendor: Packard Bell

Changed in linux-firmware (Ubuntu):
importance: Undecided → Medium
affects: linux-firmware (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 1327670

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/

Revision history for this message
Didi (d10r) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Didi (d10r) wrote : BootDmesg.txt

apport information

Revision history for this message
Didi (d10r) wrote : CRDA.txt

apport information

Revision history for this message
Didi (d10r) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Didi (d10r) wrote : IwConfig.txt

apport information

Revision history for this message
Didi (d10r) wrote : Lspci.txt

apport information

Revision history for this message
Didi (d10r) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Didi (d10r) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Didi (d10r) wrote : ProcModules.txt

apport information

Revision history for this message
Didi (d10r) wrote : RfKill.txt

apport information

Revision history for this message
Didi (d10r) wrote : UdevDb.txt

apport information

Revision history for this message
Didi (d10r) wrote : UdevLog.txt

apport information

Revision history for this message
Didi (d10r) wrote : WifiSyslog.txt

apport information

Revision history for this message
Didi (d10r) wrote :

Tested with 3.15.0-031500-generic as requested. Same issue.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Chris Nappin (3-chris-f) wrote :

Hi, this bug also affects me. The work around above (set rate to auto) lets me work around it but is a pain to run every time I login.

I have a Packard Bell Easy Note TM laptop with an in-place upgrade of Ubuntu 14.04, kernel 3.13.0-35, and am using the rtl8192se driver. My wifi AP is a Virgin Media (a UK ISP) re-badged Netgear device. I've used this laptop and router for about 6 years without problems, including Ubuntu 10 and onwards, and there are plenty of other devices (Windows/iOS/Android) in the house that also work fine. The fault started on upgrade to 14.04.

Can this fault please be prioritised, until I found this bug report my only other option was to stop using Ubuntu and move to a different distro...

Revision history for this message
Didi (d10r) wrote :

It would already help/ fix it for me if somebody could tell me where to put the mentioned iwconfig command in order to have it fix the issue automatically on every reboot.
I tried in /etc/rc.local and as a script in /etc/network/if-up.d/, but both don't have effect. I guess the timing is the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.