Package: linux-2.6
Version: 2.6.34-1~experemental.2
Severity: normal

This device should be supported (at least it says that on the cover, and
supplied driver, which does not compile anymore).
It is detected, but then returns: unknown rf chip, can't set channel map
in function:rtl819x_set_channel_map() in dmesg

Seems to be a related problem to the recently fixed #580740
The device gets an interface, but no rf signals seem to be detected
(compared to a wifi card next to it, right next to the AP).

Full dmesg output is:
[ 996.420056] usb 3-2: new full speed USB device using uhci_hcd and
address 7
[ 996.563524] usb 3-2: not running at top speed; connect to a high
speed hub
[ 996.586066] usb 3-2: New USB device found, idVendor=0bda,
idProduct=8192
[ 996.586074] usb 3-2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 996.586082] usb 3-2: Product: 802.11n WLAN Adapter
[ 996.586087] usb 3-2: Manufacturer: Realtek
[ 996.595937] ==>ep_num:6, in_ep_num:1, out_ep_num:5
[ 996.595943] ==>RtInPipes:3
[ 996.595949] ==>RtOutPipes:4 5 6 7 13
[ 996.595959] ==>txqueue_to_outpipemap for BK, BE, VI, VO, HCCA, TXCMD,
MGNT, HIGH, BEACON:
[ 996.595965] 3 2 1 0 4 4 4 4 4
[ 996.635059] Dot11d_Init()
[ 996.635063] rtl819xU:unknown rf chip, can't set channel map in
function:rtl819x_set_channel_map()
[ 996.635065]
[ 996.705600] udev: renamed network interface wlan0 to wlan11

lsusb:
0bda:8192 Realtek Semiconductor Corp.

-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'),
(500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.34-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--
42

On Mon, 2010-06-07 at 21:01 +0300, Guy Sheffer wrote:
> Package: linux-2.6
> Version: 2.6.34-1~experemental.2
> Severity: normal
>
> This device should be supported (at least it says that on the cover, and
> supplied driver, which does not compile anymore).

The hardware vendor seems to have lied to you.

Please send the supplied driver and I can try to puzzle out what the
important change is.

> It is detected, but then returns: unknown rf chip, can't set channel map
> in function:rtl819x_set_channel_map() in dmesg
>
> Seems to be a related problem to the recently fixed #580740
> The device gets an interface, but no rf signals seem to be detected
> (compared to a wifi card next to it, right next to the AP).
[...]

That's an entirely different problem - the driver did not claim the
device ID for a device that it could handle. Here we have a device that
it can't handle.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.