From: Lars Zastrow <Lars.Zastrow@gmx.de>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: backports@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Re: bug-report: Ralink corp. Device [1814:539a] - Kernel 3.8 +
Date: Wed, 19 Jun 2013 19:59:25 +0200 [thread overview]
Message-ID: <51C1F17D.5050604@gmx.de> (raw)
In-Reply-To: <20130619131234.GB2580@redhat.com>
Am 19.06.2013 15:12, schrieb Stanislaw Gruszka:
> On Mon, Jun 17, 2013 at 05:18:32AM +0200, Lars Zastrow wrote:
>> Dear Team,
>>
>> I'am using the following wireless-network-device:
>>
>> Network controller [0280]: Ralink corp. Device [1814:539a]
>> Subsystem: Hewlett-Packard Company Device [103c:1839]
>> Kernel driver in use: rt2800pci
>>
>> I had problems with it since I bought my laptop... The driver was
>> unstable with the kernel I used back in autumn 2012. Howeverer, one
>> kernel-update fixed it. Must be something about 3.4x?
>>
>> It was defenetly working with the Kernels from 3.5 till 3.7 on
>> multible distros. 3.8 was bringing back the old Problems:
>>
>> - extremly low signal
>> - hard to establish a connection to any acess-point.
>>
>> The last "problematic" kernel I have testet was 3.9.5-1 on
>> Arch-Linux. Compiling the compat-drivers manually did not bring any
>> fix.
>>
>> I am currently using 3.7.4-1 wich is working.
> This most likely is a RT5390 TX power problem I made on 3.8.
>
> This patch should help:
> https://git.kernel.org/cgit/linux/kernel/git/linville/wireless.git/commit/?id=8c8d2017ba25c510ddf093419048460db1109bc4
>
> Stanislaw
Yes, indeed! It helps.
Now it was possible to upgrade my kernel, without losing my
wireless-device to be usable. Thank you very much.
I'm afraid it is not a "flawless" experience.
On the git-page you mentioned:
> Once we implement proper TSSI tuning on 5390/3290 we can restore back
setting TX power by BBP_R1 register for those chips.
Is there any hope, that the driver will increase its performance one day?
...there are better chips on the market, that is for sure.
Regards
Lars Zastrow
prev parent reply other threads:[~2013-06-19 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 3:18 bug-report: Ralink corp. Device [1814:539a] - Kernel 3.8 + Lars Zastrow
2013-06-19 13:12 ` Stanislaw Gruszka
2013-06-19 17:59 ` Lars Zastrow [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=51C1F17D.5050604@gmx.de \
--to=lars.zastrow@gmx.de \
--cc=backports@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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).