From: Alden Page <pagea@allegheny.edu>
To: linux-wireless@vger.kernel.org
Subject: Re: bugreport Connectivity problems with rtl8192cu
Date: Fri, 28 Dec 2012 02:18:53 +0000 (UTC) [thread overview]
Message-ID: <loom.20121228T030252-692@post.gmane.org> (raw)
In-Reply-To: 50DCE1F3.806@lwfinger.net
Larry Finger <Larry.Finger@...> writes:
> What is this doing here? You need to have either the in-kernel
driver available, or the vendor driver. This bit shows you
> have both.
Since I was having a lot of trouble with the in-kernel driver,
I tried the vendor driver. I went to some lengths to get it to
compile and install in thenew kernel. Unfortunately, this was
before I referred to the documentation and read that it supports
x86 only.
Apparently I didn't uninstall the broken vendor driver entirely
as I thought I did. I will try to clean it out. Still, the
problems that I described were present before I installed it.
next prev parent reply other threads:[~2012-12-28 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 23:43 bugreport Connectivity problems with rtl8192cu Alden Page
2012-12-28 0:04 ` Larry Finger
2012-12-28 2:18 ` Alden Page [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-21 21:01 Alden Page
2012-12-21 21:53 ` Larry Finger
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=loom.20121228T030252-692@post.gmane.org \
--to=pagea@allegheny.edu \
--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).