Hello, I am trying to configure my linksys usb wireless n card. But I am having trouble getting it to work. Running gentoo I am able to get the card working with the in kernel module rt2800usb and the firmware rt2870.bin from http://www.ralinktech.com/support.php?s=2. However I can not see all the networks (i can see 2 that are on channel 11 and 1) I have tried moving my ap (access point) to that channel and I am still unable to find my own ap. What is strange is if I move to my arch machine and used the 2800sta kernel module(i just plugged in the device and it ran with that) i am able to see my ap but not able to set the ssid on that interface(or do much else to change the interface at all). I have followed the instructions from http://wiki.archlinux.org/index.php/...860_and_rt2870 and still have had little luck getting the card to work. Any suggestions would be greatly appreciated. My dmesg from the gentoo setup gives some clue but i dont understand what to do about i : [107332.704170] ehci_hcd 0000:00:1a.7: detected XactErr len 0/3860 retry 1

Are you sure that your linksys usb wireless n card uses Ralink chip?

What is output for lsusb?

Bus 001 Device 020: ID 1737:0071 Linksys
-and no i am not sure its the ralink chip, is there a way to check beyond lsusb ?

Every thing is right. I found interesting thread, but for Opensuse, may be it helps you though.

http://forums.opensuse.org/network-i...ml#post1987916

I have seen something alot like that in my troubles. I have also heard in irc, that the .dat file is mostly for config. It still dose not work on the arch box which has that setup. What dosnt make sense though is why the in tree kernel module dose not work?

is it usb 2.0, and you have ehci_hcd loaded?

if everything yes, connect it and do from root, "hwinfo --usb", if you have this utility on arch.

Sorry for the delay had to patch hwinfo to run with the latest kernel headers....:
there are several usb devices listed but the one for this component is-
09: USB 00.0: 0000 Unclassified device
[Created at usb.122]
UDI: /org/freedesktop/Hal/devices/usb_device_1737_71_noserial_if0
Unique ID: cLrx.TM1j25nzVR2
Parent ID: k4bc.cO89g+iefn1
SysFS ID: /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0
SysFS BusID: 1-2:1.0
Hardware Class: unknown
Model: "Cisco-Linksys LLC Dual-Band Wireless-N USB Network Adapter"
Hotplug: USB
Vendor: usb 0x1737 "Cisco-Linksys LLC"
Device: usb 0x0071 "Dual-Band Wireless-N USB Network Adapter"
Revision: "1.01"
Driver: "rt2800usb"
Driver Modules: "rt2800usb"
Device File: wlan0
Speed: 480 Mbps
HW Address: 00:1e:e5:XX:XX:XX(removed)
Module Alias: "usb:v1737p0071d0101dc00dsc00dp00icFFiscFFipFF"
Driver Info #0:
Driver Status: rt2800usb is active
Driver Activation Cmd: "modprobe rt2800usb"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #18 (Hub)
__as an added note____
using a vm i was able to test the card to make sure it worked in windows and the card works fine in windows

VM is using the same driver and the same kernel.
Do you have any NetworkManager running? May be other tools, witch prevents communicates with driver, so you can't get full netscan?

There is no network manager running. The vm is not using the same driver. I have the closed source virtual box, so i was able to send the usb device into the vm, and install the windows driver from the cd.

Try to use ndiswrapper in linux with the same driver.

And about ehci_hcd error, you can try unload ehci at all with modprobe -r or blacklist it.
May be uhci will do job better.

Another possibility - it is just combination kernel+driver

According to the EHCI spec, XactErr is "Set to a one by the Host Controller during status update in the case where the host did not receive a valid response from the device (Timeout, CRC, Bad PID, etc.)"

Do you have any other messages about ehci in boot log?

cat /var/log/dmesg | grep eh
[ 2.001494] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.001549] ehci_hcd: block sizes: qh 128 qtd 96 itd 160 sitd 96
[ 2.001630] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[ 2.001713] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[ 2.001716] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[ 2.002281] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[ 2.002376] ehci_hcd 0000:00:1a.7: reset hcs_params 0x103206 dbg=1 cc=3 pcc=2 ordered !ppc ports=6
[ 2.002379] ehci_hcd 0000:00:1a.7: reset hcc_params 16871 thresh 7 uframes 1024 64 bit addr
[ 2.002427] ehci_hcd 0000:00:1a.7: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT
[ 2.006325] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[ 2.006327] ehci_hcd 0000:00:1a.7: supports USB remote wakeup
[ 2.006392] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xe8405000
[ 2.006448] ehci_hcd 0000:00:1a.7: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT
[ 2.010317] ehci_hcd 0000:00:1a.7: init command 010001 (park)=0 ithresh=1 period=1024 RUN
[ 2.016135] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 2.016653] usb usb1: Manufacturer: Linux 2.6.31-gentoo-r2-bostwick-server ehci_hcd
[ 2.018432] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[ 2.018514] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 2.018517] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 2.018967] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 2.019064] ehci_hcd 0000:00:1d.7: reset hcs_params 0x103206 dbg=1 cc=3 pcc=2 ordered !ppc ports=6
[ 2.019067] ehci_hcd 0000:00:1d.7: reset hcc_params 16871 thresh 7 uframes 1024 64 bit addr
[ 2.019115] ehci_hcd 0000:00:1d.7: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT
[ 2.022987] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 2.022989] ehci_hcd 0000:00:1d.7: supports USB remote wakeup
[ 2.023055] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xe8404000
[ 2.023111] ehci_hcd 0000:00:1d.7: reset command 080002 (park)=0 ithresh=8 period=1024 Reset HALT
[ 2.026978] ehci_hcd 0000:00:1d.7: init command 010001 (park)=0 ithresh=1 period=1024 RUN
[ 2.032134] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 2.032635] usb usb2: Manufacturer: Linux 2.6.31-gentoo-r2-bostwick-server ehci_hcd
[ 2.118030] ehci_hcd 0000:00:1a.7: GetStatus port 1 status 001803 POWER sig=j CSC CONNECT
[ 2.118068] ehci_hcd 0000:00:1a.7: GetStatus port 2 status 001803 POWER sig=j CSC CONNECT
[ 2.118105] ehci_hcd 0000:00:1a.7: GetStatus port 3 status 001403 POWER sig=k CSC CONNECT
[ 2.118162] ehci_hcd 0000:00:1a.7: GetStatus port 5 status 001403 POWER sig=k CSC CONNECT
[ 2.118194] ehci_hcd 0000:00:1a.7: GetStatus port 6 status 001403 POWER sig=k CSC CONNECT
[ 2.134100] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 001803 POWER sig=j CSC CONNECT
[ 2.269218] ehci_hcd 0000:00:1a.7: port 1 high speed
[ 2.269220] ehci_hcd 0000:00:1a.7: GetStatus port 1 status 001005 POWER sig=se0 PE CONNECT
[ 2.327152] usb 1-1: new high speed USB device using ehci_hcd and address 2
[ 2.378343] ehci_hcd 0000:00:1a.7: port 1 high speed
[ 2.378347] ehci_hcd 0000:00:1a.7: GetStatus port 1 status 001005 POWER sig=se0 PE CONNECT
[ 2.496217] ehci_hcd 0000:00:1a.7: port 2 high speed
[ 2.496220] ehci_hcd 0000:00:1a.7: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
[ 2.547036] usb 1-2: new high speed USB device using ehci_hcd and address 3
[ 2.600218] ehci_hcd 0000:00:1a.7: port 2 high speed
[ 2.600223] ehci_hcd 0000:00:1a.7: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
[ 2.694340] ehci_hcd 0000:00:1a.7: port 3 low speed --> companion
[ 2.745028] ehci_hcd 0000:00:1a.7: GetStatus port 3 status 003002 POWER OWNER sig=se0 CSC
[ 2.745134] ehci_hcd 0000:00:1a.7: port 5 low speed --> companion
[ 2.797025] ehci_hcd 0000:00:1a.7: GetStatus port 5 status 003002 POWER OWNER sig=se0 CSC
[ 2.797132] ehci_hcd 0000:00:1a.7: port 6 low speed --> companion
[ 2.849027] ehci_hcd 0000:00:1a.7: GetStatus port 6 status 003002 POWER OWNER sig=se0 CSC
[ 2.901256] ehci_hcd 0000:00:1d.7: port 6 full speed --> companion
[ 2.901261] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 003801 POWER OWNER sig=j CONNECT
[ 2.953027] ehci_hcd 0000:00:1d.7: GetStatus port 6 status 003002 POWER OWNER sig=se0 CSC
[ 6.701025] ehci_hcd 0000:00:1d.7: suspend root hub

hmmm something really strange is going on with my ap and card. because when I was moving my card around(i was thinking emi interference) i was able to see more ap then before. Im going to move my ap up away from the tower and other things now to see what happens.

So now i have turned up something really interesting .The problem I was having was with the ap and the 2800usb driver together. I had my ap in multi-wireless mode(so it could send out b,g, and n) when i changed the mode to n only I could not find the ap, then when I changed the mode to g only(it still allows N to connect, just in G mode)I was able to see my ap and connect to it.

My hopes are dashed yet again . I though i had fixed the issue but I am still having issues with 2800usb module. In theory I could move to ndis and I should but I want to know why this isnt working. The problem I am having is when I connect to the ap i am not able to do anything, my transfer rate is set to 1mps but i cant get dhcp, i cant change anything. I have read more about the error that was occuring in my dmesg.:
"The software retries were introduced to solve one particular problem:
Many EHCI controllers will generate a transaction error if a data
transfer is occurring on one port at the same time as a device is being
unplugged on another port. This is clearly a hardware bug, and the
software retries were intended to work around it. In practice only a
couple of software retries are needed; if the transfer hasn't succeeded
by that point then it's never going to succeed. I set the upper limit
to 32 retries just to be conservative.

Delaying longer in order to allow the device to shape itself up is
generally hopeless. I've haven't seen more than one or two cases where
that would work -- and it's quite possible that those cases would have
worked out okay if the software retry mechanism had existed back when
they occurred. If transaction errors aren't caused by noise in the
cable then they are almost always caused by bugs or failures in the
device. Once a device's firmware has crashed, it doesn't magically fix
itself."