mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Mike Galbraith <bitbucket@online.de>
Cc: Norbert Preining <preining@logic.at>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: dire state of rtl driver in 3.7
Date: Sun, 23 Dec 2012 14:21:34 +0100	[thread overview]
Message-ID: <20121223132134.GA8190@liondog.tnic> (raw)
In-Reply-To: <1356241795.5620.47.camel@marge.simpson.net>

On Sun, Dec 23, 2012 at 06:49:55AM +0100, Mike Galbraith wrote:
> 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.

Good for you.

I have a [10ec:8176] in my laptop and while I don't have the issues
Norbert is reporting, I can't say the thing just worked.

I had to use the wireless recently in a bunch of networks and what it
would do, is associate properly, connection gets established and traffic
is fine for a minute or so. Then, after a minute traffic would cease and
I'd need to re-associate. And it worked sporadically, sometimes fine,
sometimes with constant connection interruptions. And this observation
was the case with almost all wireless networks I'd use.

FWIW, the wifi adapter is:

01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
        Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8195]
        Flags: fast devsel, IRQ 17
        I/O ports at 3000 [size=256]
        Memory at f0200000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 01-91-81-fe-ff-4c-e0-00

using rtl8192ce.

Hmm.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2012-12-23 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-22 15:09 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 ` dire state of rtl " Mike Galbraith
2012-12-23 13:21   ` Borislav Petkov [this message]
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=20121223132134.GA8190@liondog.tnic \
    --to=bp@alien8.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=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

all inboxes | Powered by JetHome®