realtek 8172 wireless controller nonfunctional

[Matt Price]

On a Lenovo Thinpad T410 equipped with realtek 8172 wireless controler, the wireless runs *very* poorly under the stock lucid kernel. manually deleting the rtl8192*ko drivers and installing rtl8192se drivers from source using dkms(version 2.6.0015.0127.2010) solves the problem, even though the git changelog suggests that these drivers are already present in the 2.6.32-17 kernel. Has source been modified in some way?

apologies for the duplication of lp:550120. couldnt get ubuntu-bug to add these attachments to an existing bug.

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: matt 1664 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 17'
   Mixer name : 'Intel G45 DEVIBX'
   Components : 'HDA:14f15069,17aa214c,00100302 HDA:80862804,17aa21b5,00100000'
   Controls : 10
   Simple ctrls : 5
Date: Sun Mar 28 05:23:38 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8bc30640-587d-41e8-a9bd-8833b3836ece
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Lsusb:
 Bus 002 Device 002: ID 8087:0020
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 17ef:480f Lenovo
 Bus 001 Device 002: ID 8087:0020
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 2516CTO
NonfreeKernelModules: r8192se_pci
Package: linux-image-2.6.32-17-generic 2.6.32-17.26
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=08517b2d-d32a-45d4-b574-a6d38f0dde9c ro quiet splash
ProcEnviron:
 LANG=en_CA.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Regression: No
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
RfKill:

SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-17-generic x86_64
dmi.bios.date: 01/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET49WW (1.09 )
dmi.board.name: 2516CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6IET49WW(1.09):bd01/07/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2516CTO
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO

[Matt Price (matt-price)]

i think this should be the relevant commit, not sure why it doesn't work for me:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=commit;h=76e2d54ef7f79e7dd9048ac3c88ee943f275135f

[Matt Price (matt-price)]

some of these log files are a little misleading as I expeimented w/ 2.6.33 mainline kernel & with the stock drivers before installing the upstream driver from source. Error messages in WifiSyslog.tx at March 28 04:03 are from the stock kernel; successful association thereafter occurs after the upstream driver has been installed and manually loaded with modprobe r812se_pci.

[Jeremy Foshee (jeremyfoshee)]

Hi Matt,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Rogerio Luz Coelho (rogerio-luz-coelho)]

This bug is DUPLICATED of a bug we are discussing in #215802

Please update your links