linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming-Ching Tiew <mctiew@yahoo.com>
To: linux-wireless@vger.kernel.org
Subject: Re: Tp-link wn7200nd - cannot associate
Date: Mon, 3 Jan 2011 17:45:25 -0800 (PST)	[thread overview]
Message-ID: <75410.15386.qm@web31507.mail.mud.yahoo.com> (raw)
In-Reply-To: <AANLkTinBGj6Q1DoGogerhFDMD0ZR1OVYqjSucc-a4oPu@mail.gmail.com>



--- On Mon, 1/3/11, Rafał Miłecki <zajec5@gmail.com> wrote:

> >
> > I have a TP-LINK WN7200ND, I am tested it with Kernel
> 2.6.36.1 and 2.6.35.10, basically after inserting the USB,
> the interface is up and it can never associate with any
> access point.
> >
> > #lsmod |grep rt2
> >
> > rt2800usb               7632  0
> > rt2800lib              20328  1 rt2800usb
> > rt2x00usb               4628  2
> rt2800usb,rt2800lib
> > rt2x00lib              15408  2
> rt2800lib,rt2x00usb
> > mac80211              122068  2
> rt2x00usb,rt2x00lib
> > cfg80211               92252  2
> rt2x00lib,mac80211
> >
> > There are a lot of similar complaints on the net, this
> is one example :-
> >
> > http://ubuntuforums.org/showthread.php?t=1530095
> >
> > There don't seem to be any issue with 'iwlist wlanX
> scan'. But just can't associate.
> >
> > Any recommendation ? Any debug information I should
> provide ?
> 
> Are your networks encrypted? How? What is output of
> wpa_supplicant? Did you try
> nohwcrypt=1
> ?
> 

Thanks for the reply. Now I am suspecting that it's the power supply to the usb device. The device is supposed to be 500mW, what do I have to do to check indeed the notebook usb power supply is not enough ?

Regards.


      

  reply	other threads:[~2011-01-04  1:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03  2:38 Tp-link wn7200nd - cannot associate Ming-Ching Tiew
2011-01-03 10:48 ` Rafał Miłecki
2011-01-04  1:45   ` Ming-Ching Tiew [this message]
2011-01-03 15:04 ` Chin Shi Hong
2011-01-04 16:42   ` Helmut Schaa
2011-01-05  1:28     ` Ming-Ching Tiew

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=75410.15386.qm@web31507.mail.mud.yahoo.com \
    --to=mctiew@yahoo.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).