From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Pending ath9k bugs
Date: Mon, 1 Jun 2009 11:41:34 -0700 [thread overview]
Message-ID: <20090601184134.GC5516@tesla> (raw)
Here is a list of pending ath9k bugs, if I've missed
anything please reply to this e-mail and let us know. If you
have any insights into specific AP issues (one with Airport
Express N, another with DAP-1353) please let us know.
kernel.org:
1) "Very low signal strenghts with ath9k in 2.6.29"
http://bugzilla.kernel.org/show_bug.cgi?id=12930
Patch available but user still reports issues with both Windows and Linux
with an AR5416 PCI-E card. Patch has not yet been pushed upstream.
2) "AR5008/DWA-552 - Very slow" on 2.6.30-rc2
http://bugzilla.kernel.org/show_bug.cgi?id=13141
Card is an AR5416 card (PCI-E), AP is "Airport Express N" in 11 mode
with WPA. Claims under windows performance is better. User is testing
with kerenl 2.6.30-rc2.
ath9k-devel:
1) Cannot associate with AP DAP-1353 in 11n mode, no encryption.
First message:
https://lists.ath9k.org/pipermail/ath9k-devel/2009-May/001566.html
Thread:
https://lists.ath9k.org/pipermail/ath9k-devel/2009-May/thread.html#1566
Red Hat Bugzilla:
1) " [ath9k] not able to use WLAN on channel 13 with AR5008 [168c:0024] [NEEDINFO]"
https://bugzilla.redhat.com/show_bug.cgi?id=503285
2) "ath9k - bit rate is always reported as 1 Mb/s [NEEDINFO]"
https://bugzilla.redhat.com/show_bug.cgi?id=481259
3) " ath9k can not connect to hidden networks [NEEDINFO]"
https://bugzilla.redhat.com/show_bug.cgi?id=496505
This is against a "linksys wpa54g" with WPA2
4) "NetworkManager requires ath9k reload to work. [NEEDINFO]"
https://bugzilla.redhat.com/show_bug.cgi?id=489216
OpenSuse:
1) "wi-fi card Atheros AR928X returns "no scan results""
https://bugzilla.novell.com/show_bug.cgi?id=462673
Not sure what to make of this. Jiri might know better.
I reviewed most ath9k Ubuntu bug reports but unfortunately all are
on old stable kernel releases or old kernels, most need more info,
and I was unable to find any useful bug report which reflects the
current ath9k as is upstream or any critical fix for older stable
kernel releases. If I missed anything please do let us know.
Luis
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: <linux-wireless@vger.kernel.org>
Cc: <linville@tuxdriver.com>, <Gaurav.Jauhar@atheros.com>,
<senthilkumar@atheros.com>, <ath9k-devel@lists.ath9k.org>,
<leann.ogasawara@canonical.com>, <tim.gardner@canonical.com>,
<parag.warudkar@gmail.com>, <drago01@gmail.com>,
<drjoms@gmail.com>, <jirislaby@gmail.com>, <debaditya@gmail.com>,
<arxs@fedoraproject.org>, <michal@harddata.com>,
<fabian.deutsch@gmx.de>
Subject: Pending ath9k bugs
Date: Mon, 1 Jun 2009 11:41:34 -0700 [thread overview]
Message-ID: <20090601184134.GC5516@tesla> (raw)
Here is a list of pending ath9k bugs, if I've missed
anything please reply to this e-mail and let us know. If you
have any insights into specific AP issues (one with Airport
Express N, another with DAP-1353) please let us know.
kernel.org:
1) "Very low signal strenghts with ath9k in 2.6.29"
http://bugzilla.kernel.org/show_bug.cgi?id=12930
Patch available but user still reports issues with both Windows and Linux
with an AR5416 PCI-E card. Patch has not yet been pushed upstream.
2) "AR5008/DWA-552 - Very slow" on 2.6.30-rc2
http://bugzilla.kernel.org/show_bug.cgi?id=13141
Card is an AR5416 card (PCI-E), AP is "Airport Express N" in 11 mode
with WPA. Claims under windows performance is better. User is testing
with kerenl 2.6.30-rc2.
ath9k-devel:
1) Cannot associate with AP DAP-1353 in 11n mode, no encryption.
First message:
https://lists.ath9k.org/pipermail/ath9k-devel/2009-May/001566.html
Thread:
https://lists.ath9k.org/pipermail/ath9k-devel/2009-May/thread.html#1566
Red Hat Bugzilla:
1) " [ath9k] not able to use WLAN on channel 13 with AR5008 [168c:0024] [NEEDINFO]"
https://bugzilla.redhat.com/show_bug.cgi?id=503285
2) "ath9k - bit rate is always reported as 1 Mb/s [NEEDINFO]"
https://bugzilla.redhat.com/show_bug.cgi?id=481259
3) " ath9k can not connect to hidden networks [NEEDINFO]"
https://bugzilla.redhat.com/show_bug.cgi?id=496505
This is against a "linksys wpa54g" with WPA2
4) "NetworkManager requires ath9k reload to work. [NEEDINFO]"
https://bugzilla.redhat.com/show_bug.cgi?id=489216
OpenSuse:
1) "wi-fi card Atheros AR928X returns "no scan results""
https://bugzilla.novell.com/show_bug.cgi?id=462673
Not sure what to make of this. Jiri might know better.
I reviewed most ath9k Ubuntu bug reports but unfortunately all are
on old stable kernel releases or old kernels, most need more info,
and I was unable to find any useful bug report which reflects the
current ath9k as is upstream or any critical fix for older stable
kernel releases. If I missed anything please do let us know.
Luis
next reply other threads:[~2009-06-01 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 18:41 Luis R. Rodriguez [this message]
2009-06-01 18:41 ` Pending ath9k bugs Luis R. Rodriguez
2009-06-01 18:48 ` [ath9k-devel] " Luis R. Rodriguez
2009-06-01 18:48 ` Luis R. Rodriguez
2009-06-01 19:30 ` Jiri Slaby
2009-06-01 19:30 ` Jiri Slaby
2009-06-01 19:52 ` [ath9k-devel] " Luis R. Rodriguez
2009-06-01 19:52 ` Luis R. Rodriguez
2009-06-02 5:09 ` Vasanthakumar Thiagarajan
2009-06-02 5:09 ` Vasanthakumar Thiagarajan
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=20090601184134.GC5516@tesla \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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.