From: Eric Valette <Eric.Valette@Free.fr>
To: linux-wireless@vger.kernel.org
Subject: ralink 3290: still lots of misc errors reported by Iwconfig with 3.10 + HD streaming on WiFi fails
Date: Tue, 09 Jul 2013 12:50:52 +0200 [thread overview]
Message-ID: <51DBEB0C.6040704@Free.fr> (raw)
I just bought a HP netbook for my son equipped with this chipset. I
first tried linux 3.9.7, got WiFi working badly but working. Saw fix for
TX power in 3.9.9. WiFi became more reliable but still had a lot of TX,
and MISC errors reported by iwconfig. While laptop is now usable for
internet browsing, trying to play HD tv via XBMC + tvheadend fails
miserably due to WiFi data rate and WiFi errors while other PC at home
do play without problems.
Saw the fix in 3.10 for TX errors and indeed the TX errors dropped to 0.
However, the MISC error count in turn rose (Downloading
linux-3.10.tar.xz on 3.10 reports 550 misc errors). So there is still
some problem with this chipset. I know support is experimental but I
would be glad to test any patchif possible on 3.9.x as on 3.10 I have no
ATI driver available at the moment and thus HD decoding is out of reach
anyway.
Using ralink proprietary driver on linux recent kernel and amd64 is a no
go(does not compile due to API change + lots of INT32/pointers
conversion)but may be the driver code could shed some light for people
with adequate knowledge...
Please CC me I'm not subscribed
-- eric
next reply other threads:[~2013-07-09 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 10:50 Eric Valette [this message]
2013-07-09 14:22 ` ralink 3290: still lots of misc errors reported by Iwconfig with 3.10 + HD streaming on WiFi fails Stanislaw Gruszka
2013-07-09 14:35 ` Eric Valette
2013-07-09 15:00 ` Eric Valette
2013-07-10 11:31 ` Stanislaw Gruszka
2013-07-11 6:31 ` Eric Valette
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=51DBEB0C.6040704@Free.fr \
--to=eric.valette@free.fr \
--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).