From: Lars Zastrow <Lars.Zastrow@gmx.de>
To: backports@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: bug-report: Ralink corp. Device [1814:539a] - Kernel 3.8 +
Date: Mon, 17 Jun 2013 05:18:32 +0200 [thread overview]
Message-ID: <51BE8008.20302@gmx.de> (raw)
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.
Best regards
Lars Zastrow
next reply other threads:[~2013-06-17 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 3:18 Lars Zastrow [this message]
2013-06-19 13:12 ` bug-report: Ralink corp. Device [1814:539a] - Kernel 3.8 + Stanislaw Gruszka
2013-06-19 17:59 ` Lars Zastrow
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=51BE8008.20302@gmx.de \
--to=lars.zastrow@gmx.de \
--cc=backports@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.