From: "John W. Linville" <linville@tuxdriver.com>
To: Azhar <Azhar.iq@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: TL-WN721N
Date: Mon, 26 Oct 2009 15:51:58 -0400 [thread overview]
Message-ID: <20091026195158.GK2792@tuxdriver.com> (raw)
In-Reply-To: <loom.20091018T103209-571@post.gmane.org>
On Sun, Oct 18, 2009 at 08:33:46AM +0000, Azhar wrote:
> John W. Linville <linville@...> writes:
>
> >
> > On Thu, Oct 15, 2009 at 02:20:52PM +0000, Azhar wrote:
> > > Hi all,
> > >
> > > I am looking for drivers of TL-WN721N (for linux)...i have been going through
> > > pages aand pages of documentation....but every other link seems to route
> > > here...i would really appreciate if you could guide me
> > >
> > > Thanks
> > >
> > > Azhar
> >
> > Is it PCI? USB? The output of lspci or lsusb would be helpful
> > to know. Of course, in most cases you distribution would have the
> > driver auto-loaded for you if it was supported at all...
> >
> > John
>
> ndiswrapper -l
>
> WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be
> ignored in a future release.
> WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be
> ignored in a future release.
> netathur : driver installed
> device (0CF3:9271) present
>
>
> lsusb
>
> Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc.
I suspect you should try a wireless-testing kernel or a bleeding-edge
wireless-compat package.
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-10-26 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 14:20 TL-WN721N Azhar
2009-10-15 15:10 ` TL-WN721N John W. Linville
2009-10-18 8:33 ` TL-WN721N Azhar
2009-10-21 20:23 ` TL-WN721N Pavel Roskin
2009-10-26 19:51 ` John W. Linville [this message]
2009-10-15 15:15 ` TL-WN721N Stefan Lippers-Hollmann
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=20091026195158.GK2792@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Azhar.iq@gmail.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).