From: Mike Galbraith <bitbucket@online.de>
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: Sun, 23 Dec 2012 06:49:55 +0100 [thread overview]
Message-ID: <1356241795.5620.47.camel@marge.simpson.net> (raw)
In-Reply-To: <20121222150909.GA3979@gamma.logic.tuwien.ac.at>
On Sun, 2012-12-23 at 00:09 +0900, Norbert Preining wrote:
> Network card is built in into a Lenovo Thinkpad Edge
Toshiba Satellite.
> # lspci -nnv -s 03:00.0
> 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8191SEvB
> Wireless LAN Controller [10ec:8172] (rev 10)
> Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:e020]
[10ec:8181] here.
> Effects:
> - either does not associate at all with the AP
> - or the kernel believes it is associated and packages ping to the router
> get stuck for up to 50+ seconds!!!
> - the kernel believes everything is fine but actually nothing gets out
> (Destination unreachable)
> - wild ping time up-down:
> 64 bytes from 192.168.0.1: icmp_req=73 ttl=255 time=3.05 ms
> 64 bytes from 192.168.0.1: icmp_req=74 ttl=255 time=6.42 ms
> 64 bytes from 192.168.0.1: icmp_req=75 ttl=255 time=1.21 ms
> 64 bytes from 192.168.0.1: icmp_req=76 ttl=255 time=6808 ms
> 64 bytes from 192.168.0.1: icmp_req=77 ttl=255 time=5800 ms
> 64 bytes from 192.168.0.1: icmp_req=78 ttl=255 time=4792 ms
...
Looks a lot like my driver experience with older kernels, I had to use
the external driver in the rare event that I needed wireless to work.
The in tree driver works peachy these days (needed it recently, was
pleasantly surprised when it _just worked_, not even a hiccup), so
somebody cared, gave at least the 10ec:8181 bits some serious love.
-Mike
next prev parent reply other threads:[~2012-12-23 5:50 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
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 ` Mike Galbraith [this message]
2012-12-23 13:21 ` dire state of rtl " 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=1356241795.5620.47.camel@marge.simpson.net \
--to=bitbucket@online.de \
--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).