From: Larry Finger <Larry.Finger@lwfinger.net>
To: Norbert Preining <preining@logic.at>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: dire state of rtl driver in 3.7
Date: Sat, 22 Dec 2012 10:36:36 -0600 [thread overview]
Message-ID: <50D5E194.3050503@lwfinger.net> (raw)
In-Reply-To: <20121222150909.GA3979@gamma.logic.tuwien.ac.at>
On 12/22/2012 09:09 AM, Norbert Preining wrote:
> Dear all,
>
> I have no idea who is responsible or how to continue, but the rtl driver
> is in such a dire state and it seems nobody cares. I have no reported
> several times about it, without the slightest reactions. How can it be
> that after so many years we still not be able to do wireless.
>
> Ok, here are some facts to make people happy:
> kernel 3.7.0
> rtl8192se
> AP infos:distance: 3m
> NEC Aterm WR8600N ATERM-B45459
> firmware 1.0.11
It is not that no one cares; however, your attitude does nothing to induce me to
work on this problem. The facts are not needed "to make people happy", they are
necessary to try to reproduce the problem. If I cannot make it happen here, then
I cannot fix it. Also, remember that I am a volunteer. I get nothing from
Realtek but starting code of varying quality and some sample chips. At least my
versions do not crash your computer.
Your subject for the E-mails certainly defeats any attempt to search. There is
no driver named "rtl".
As I told you in a previous mailing, my system shows none of the symptoms that
you see. I have tested all 3 varieties of chips that use driver rtl8192se and I
never get the long ping times that you reported earlier.
I have never tested forcing a reset on the chip the way you did. I am not
surprised that bad things happen.
From some of the material that you report, it appears that you have an 802.11n
connection using WPA1 encryption. (More of those pesky details!) That particular
configuration is one that I have not been using as my 802.11n router is shared
with my spouse, and I cannot change it that easily, but I will give it a try.
Larry
next prev parent reply other threads:[~2012-12-22 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 15:09 dire state of rtl driver in 3.7 Norbert Preining
2012-12-22 16:36 ` Larry Finger [this message]
2012-12-22 22:55 ` dire state of rtl8192se " Norbert Preining
2012-12-23 1:49 ` Larry Finger
2013-01-19 3:06 ` Norbert Preining
2012-12-23 5:49 ` dire state of rtl " Mike Galbraith
2012-12-23 13:21 ` Borislav Petkov
2012-12-23 19:13 ` Larry Finger
2012-12-23 19:18 ` Borislav Petkov
2012-12-23 19:10 ` Larry Finger
2012-12-24 4:27 ` Mike Galbraith
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=50D5E194.3050503@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=preining@logic.at \
/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).