From: Larry Finger <Larry.Finger@lwfinger.net>
To: Alden Page <pagea@allegheny.edu>
Cc: linux-wireless@vger.kernel.org
Subject: Re: bugreport Connectivity problems with rtl8192cu
Date: Fri, 21 Dec 2012 15:53:21 -0600 [thread overview]
Message-ID: <50D4DA51.6040903@lwfinger.net> (raw)
In-Reply-To: <CABLZTyB1Dr9z_XeHmE0ES6fZ6AqQekqmXxGo_nfRuWgxLgLXSg@mail.gmail.com>
On 12/21/2012 03:01 PM, Alden Page wrote:
> I apologize for sending this to both maintainers listed on the rtl819x
> privately. I've never had to file a bug before and did not mean to
> give the impression of malice or selfishness, I'm simply unfamiliar
> with the way open source developers go about things.
>
> In any case, I am having some problems with the rtl8192cu driver.
> After a period of five minutes to an hour, I will lose connectivity to
> my wireless router. In the 3.2 kernel, I would be unable to connect
> until I restarted my computer. My wireless SSID would be visible
> through nm-applet, but connecting would just result in network-manager
> prompting me for the password again, attempting to connect for a
> while, and then timing out before repeating the cycle. I compiled and
> installed the 3.7.1 kernel to see if it would solve this problem but
> had no such luck. The only difference is that unplugging the wireless
> adapter and plugging it back in restores connectivity for a period of
> time before the problem occurs again. I also get stuck at "Waiting for
> headers" a lot while waiting for package upgrades. The device is an
> Encore N150, which uses this particular Realtek chipset. The
> proprietary driver does not support my architecture. While I
> appreciate the invitation to "look for the problem myself", I have no
> experience working with the kernel or writing drivers. I'll do my best
> anyway, of course.
>
> Some information about my system:
> Crunchbang 11 on kernel 3.7.1 amd64
> Encore N150 Wireless USB adapter, using network-manager and nm-applet
> Connecting to a Linksys E3000. Works fine with all other devices in the house
>
> The adapter does not lose its connection in Windows, so I think
> hardware failure is unlikely.
>
> Relevant modules:
> rtl8192cu 75225 0
> rtlwifi 81359 1 rtl8192cu
> rtl8192c_common 48515 1 rtl8192cu
One point. GregKH is the maintainer of drivers/staging/*. Some of the Realtek
drivers are in that tree because they do not meet all the requirements for
inclusion in the main drivers/net/wireless tree. The driver in question,
rtl8192cu, is found in drivers/net/wireless.
> The output of dmesg is attached in plaintext.
>
> Thanks for your time (and the warm welcome)
Your attached dmesg output did not even show a disconnection. Why was that?
Larry
next prev parent reply other threads:[~2012-12-21 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 21:01 bugreport Connectivity problems with rtl8192cu Alden Page
2012-12-21 21:53 ` Larry Finger [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-27 23:43 Alden Page
2012-12-28 0:04 ` Larry Finger
2012-12-28 2:18 ` Alden Page
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=50D4DA51.6040903@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pagea@allegheny.edu \
/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).