From: Christian Lamparter <chunkeey@googlemail.com>
To: Scott S <scotta1265@gmail.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: will rtl8192su driver work for 64-bit kernel 3.2.0-23-generic?
Date: Wed, 25 Dec 2013 00:31:42 +0100 [thread overview]
Message-ID: <106771444.37oG374YIb@debian64> (raw)
In-Reply-To: <CAGqmZoTrBnxcemEjc67o==K_TZCm8D+yr3BjqiaTKfXsRugaPA@mail.gmail.com>
On Tuesday, December 24, 2013 03:59:19 PM Scott S wrote:
> >>> I'm looking for a better driver for a Rosewill RNX-N180UBE USB wifi on
> >>> 64-bit Linux Mint 13 (Ubuntu 12LTS Kernel 3.2.0-23) the Ubuntu driver
> >>> is junk+10.
>
> -------------------------------------
>
> >in what way is it junk? Is it crashing/misbehaving, does it lack important
> >features, is the wifi connection unstable, or is something else bothering
> >you?
>
> Well, let's see, this is a new USB antenna, but this is what I've
> noticed so far:
>
> Sometimes I get a "black screen of death" crash when watching hi-speed
> streaming videos on Amazon or NFL.com, or during shut-down , but not
> sure, because sometimes the message is Kernel BUG: xxxxxxx whatever
> and ---cut here------ and other messages... but I only get those
> messages when this one is plugged in. (I have 2 other USB antennas
> that I can't get to work well either, but of the 3, this one works the
> best) hahaha :)
>
> Here's some of the other problems I've noticed:
>
> It doesn't turn-off from the applet (the signal strength indicator
> always stays on, then it's locked up. Won't do jack on/off)
> Suspend wake-up problems.
> Crashes when uplugged, but not all the time...
>
> System won't completely shutdown when plugged in or after unplugged,
> and more error messages.
>
> (I've had some success using using CTRL+ALT+PrnScr REISUB sometimes
> for a complete shutdown.)
>
> Other than that, it works great! No, really. Better than my other 2.
> When it works, it's fast.
This is great data (do you think you could capture a few of those error
messages?). Since all this sounds like "just" driver problems... and they
can be fixed (or are already fixed, after all 3.2 was releases almost two
years ago). Do you know the module name of the driver you are currently
using? ("lsmod" can tell you that, it should be something like r8712u,
rtl8190n or rtl8192su). Maybe there is already an intermediate solution.
> > Oh, you can help with the rtl8192su-mac80211 driver rewrite. This would
> > certainly make a difference :-D
>
> I really wish I could. I love Linux.
>
> But wait a minute, if it's doomed anyway. :/
Wait a minute ;-). r92su is "doomed" since it doesn't provide any major
improvements over r8712u (apart from the cfg80211 interface). However,
the rtl8192su-mac80211 driver is not doomed, but it needs "free hands".
> Thanks for the response and Merry Christmas Happy New Year
Thank you, the same to you.
Christian
prev parent reply other threads:[~2013-12-24 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 22:58 will rtl8192su driver work for 64-bit kernel 3.2.0-23-generic? Scott S
2013-12-22 23:50 ` Christian Lamparter
[not found] ` <CAGqmZoTrBnxcemEjc67o==K_TZCm8D+yr3BjqiaTKfXsRugaPA@mail.gmail.com>
2013-12-24 23:31 ` Christian Lamparter [this message]
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=106771444.37oG374YIb@debian64 \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=scotta1265@gmail.com \
/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).