From: "Michael Büsch" <m@bues.ch>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtlwifi: Fix EFUSE_ANA8M map value
Date: Sat, 23 May 2015 12:40:38 +0200 [thread overview]
Message-ID: <20150523124038.17417873@wiggum> (raw)
In-Reply-To: <55600CEB.5080703@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On Sat, 23 May 2015 00:15:23 -0500
Larry Finger <Larry.Finger@lwfinger.net> wrote:
> No, it is able to scan and connect with the vanilla kernel, but it is not
> terribly reliable with about 25% ping loss. I just got a report of a regression.
> Kernel 4.0 fails whereas 3.19 works. I have been seeing a lot of patches from
> various sources. I thought they were OK, but I will need to bisect.
I tried with 3.16 and 4.0 based Debian kernels. Neither worked.
I use the firmware provided by Debian's firmware-realtek package.
I have two of these devices, so I think the hardware should be ok, unless they are broken both.
When I first tried to use it, I forgot to install firmware. It tried to load it, then some 'alternative firmware' and then froze the system partially. I guess there's some unreleased lock or such in an error path somewhere. I didn't check this, because it didn't seem too terribly important for now.
I will also try your driver from your github repo soon and see if that makes it work.
> Some days I am sorry that I ever heard of Linux. :)
Retired, but still out of time. :)
--
Michael
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-23 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 19:44 [PATCH] rtlwifi: Fix EFUSE_ANA8M map value Michael Büsch
2015-05-21 21:54 ` Larry Finger
2015-05-22 5:00 ` Michael Büsch
2015-05-22 20:21 ` Larry Finger
2015-05-22 21:13 ` Michael Büsch
2015-05-23 5:15 ` Larry Finger
2015-05-23 10:40 ` Michael Büsch [this message]
2015-05-23 18:01 ` Michael Büsch
2015-05-25 16:10 ` Larry Finger
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=20150523124038.17417873@wiggum \
--to=m@bues.ch \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/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).