Bug#705586: linux-image-3.2.0-4-amd64: ath9k_htc fails to initialize with tl-wn722n; regression vs sqeeze backport
On Wed, 2013-04-17 at 19:36 +0100, Ben Hutchings wrote:
> This is unlikely to be a regression between squeeze-backports
> and wheezy, because they should be functionally the same
> (aside from some ARM configurations).
>
> What was the previous working kernel package version, as shown by
> 'dpkg -s linux-image-3.2.0-0.bpo.4-amd64' ?
It appears to work just fine on my desktop running Sqeeze with
backports. Even just updated it.
$ dpkg -s linux-image-3.2.0-0.bpo.4-amd64
Package: linux-image-3.2.0-0.bpo.4-amd64
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 114460
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: amd64
Source: linux
Version: 3.2.41-2~bpo60+1
Provides: linux-image, linux-modules-3.2.0-0.bpo.4-amd64
Depends: kmod | module-init-tools, linux-base (>= 3~), initramfs-tools
(>= 0.99~) | linux-initramfs-tool
Pre-Depends: debconf | debconf-2.0
Recommends: firmware-linux-free (>= 3~)
Suggests: linux-doc-3.2, debian-kernel-handbook, grub-pc | extlinux |
lilo
Breaks: at (<< 3.1.12-1+squeeze1), initramfs-tools (<< 0.99~)
Description: Linux 3.2 for 64-bit PCs
The Linux kernel 3.2 and modules for use on PCs with AMD64, Intel 64 or
VIA Nano processors.
.
This kernel also runs on a Xen hypervisor. It supports both privileged
(dom0) and unprivileged (domU) operation.
And dmesg shows it initialize without errors.
[ 50.352145] usb 4-5: new high-speed USB device number 2 using
ehci_hcd
[ 50.501338] usb 4-5: New USB device found, idVendor=0cf3,
idProduct=9271
[ 50.501347] usb 4-5: New USB device strings: Mfr=16, Product=32,
SerialNumber=48
[ 50.501355] usb 4-5: Product: USB2.0 WLAN
[ 50.501360] usb 4-5: Manufacturer: ATHEROS
[ 50.501365] usb 4-5: SerialNumber: 12345
[ 50.556687] cfg80211: Calling CRDA to update world regulatory domain
[ 50.660211] usb 4-5: firmware: agent loaded htc_9271.fw into memory
[ 50.943846] usb 4-5: ath9k_htc: Transferred FW: htc_9271.fw, size:
51272
[ 51.178754] ath9k_htc 4-5:1.0: ath9k_htc: HTC initialized with 33
credits
[ 51.369986] ath9k_htc 4-5:1.0: ath9k_htc: FW Version: 1.3
[ 51.369993] ath: EEPROM regdomain: 0x809c
[ 51.369998] ath: EEPROM indicates we should expect a country code
[ 51.370004] ath: doing EEPROM country->regdmn map search
[ 51.370009] ath: country maps to regdmn code: 0x52
[ 51.370014] ath: Country alpha2 being used: CN
[ 51.370018] ath: Regpair used: 0x52
[ 51.383550] ieee80211 phy0: Atheros AR9271 Rev:1
[ 51.384420] Registered led device: ath9k_htc-phy0
[ 51.384427] usb 4-5: ath9k_htc: USB layer initialized
[ 51.384475] usbcore: registered new interface driver ath9k_htc
I guess this could also be an issue with the laptop I'm trying to get
this to work on. Would it be helpful if I were to install Sqeeze on my
laptop and see if it works that way?
>
> On Wed, Apr 17, 2013 at 02:33:17AM -0600, Steven Hystad wrote:
> > Package: src:linux
> > Version: 3.2.41-2
> > Severity: normal
> > Tags: lfs
> >
> > Dear Maintainer,
> >
> > I have a few TL-WN722N usb wireless networking devices that I use on a few
> > systems running Dabian Sqweeze backports. On testing Weezy the driver
> > encounters an error and doesn't complete setting up the wlan interface.
> >
> > I did try compiling and installing a standard kernel bassed on the config
> > included in Debian, however I encountered issues with the graphics and didn't
> > test the networking.
> >
> > In the data below you'll see that the builtin wireless device does startup
> > correctly, but the usb wireless device, while it is recognised correctly, fails
> > after inserting firmware.
> [...]
> > [ 388.299820] usb 3-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> > [ 388.300155] xhci_hcd 0000:00:14.0: ERROR no room on ep ring
> > [ 388.303268] usb 3-1: ath9k_htc: Unable to allocate URBs
> [...]
>
> This seems to indicate a problem (maybe a bug) in allocation of USB
> bandwidth. Is this device connected directly to the USB port, or
> through a hub?
>
> Ben.
>
Direct connection; no hubs are used.
Reply to: