Ralink module rt5572sta isn't included in linux-image-{generic, server}
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
The TP-Link dual-band USB wireless access device TL-WDN3200 uses the Ralink RT5572 USB module, which isn't included in the standard Ubuntu linux-image-generic or linux-image-server packages.
http://
edlang@lettuce:~$ lsusb | grep Ralink
Bus 001 Device 003: ID 148f:5572 Ralink Technology, Corp.
http://
Could you please ensure it's included in future packages?
The file .../os/
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-generic 3.2.0.26.28
ProcVersionSign
Uname: Linux 3.2.0-26-generic x86_64
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Jul 4 00:49 seq
crw-rw---T 1 root audio 116, 33 Jul 4 00:49 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Wed Jul 4 02:25:46 2012
HibernationDevice: RESUME=
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
MachineType: HP ProLiant MicroServer
PciMultimedia:
ProcEnviron:
LANGUAGE=en_AU:en
TERM=screen-bce
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.79
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-04-26 (68 days ago)
dmi.bios.date: 04/02/2011
dmi.bios.vendor: HP
dmi.bios.version: O41
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:
dmi.product.name: ProLiant MicroServer
dmi.sys.vendor: HP
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
We generally ask bug reporters to first request that the driver be added to the upstream kernel. This can be done by mailing the Linux Kernel Mailing List or opening a bug at bugzilla. kernel. org.
People affected by this bug are probably wondering why the kernel team doesn't just add the driver. The reason is that the kernel team is reluctant (not opposed) to apply any patch/driver to a kernel that is not from upstream. Applying patches and adding drivers that don't come from upstream add greatly to the support of the kernel as other upstream patches/drivers may touch the same area as the non-upstream patch and may prevent them from applying cleanly.