From: nanok <rnanok@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: nanokk@gmx.net, linux-wireless@vger.kernel.org
Subject: Re: Bug: 2.6.32 ath5k, associating with WEP128 AP is unreliable
Date: Fri, 26 Mar 2010 00:04:45 +0100 [thread overview]
Message-ID: <20100325230445.GB7547@spartakus> (raw)
In-Reply-To: <b6c5339f1003251544r35b59c8fqf6a9beeaa3264b82@mail.gmail.com>
On Thu, Mar 25, 2010 at 06:44:01PM -0400, Bob Copeland wrote:
> On Thu, Mar 25, 2010 at 6:24 PM, nanok <rnanok@gmail.com> wrote:
> > On Thu, Mar 25, 2010 at 05:04:02PM -0400, Bob Copeland wrote:
> >> On Thu, Mar 25, 2010 at 5:02 PM, Bob Copeland <me@bobcopeland.com> wrote:
> >>
> >> > As you are using debian I have to ask: have you installed
> >> > crda? ?Since 2.6.30 ath5k gained regulatory support which
> >> > may cause certain channels to be disabled.
> >>
> >> By "since 2.6.30" I meant post-2.6.30, sorry for any
> >> confusion.
> >>
> >> --
> >> Bob Copeland %% www.bobcopeland.com
> >>
> >
> > hi Bob,
> >
> > no confusion, it's perfectly clear either way you state it.
> > unfortunately, it's 2.6.3
> > 0 that "works" (not pre-2.6.30), or did you mean since 2.6.30, excluding
> > 2.6.30?
>
> Right, that is what I tried to correct. _After_ 2.6.30,
> ath5k began reporting the regdomain from the EEPROM which
> means some channels (13 is a common case) are no longer
> accessible whereas they were before with static reg domains
> and no EEPROM support. That was the major change in the
> driver. Most other changes since 2.6.30 were in the
> upper-layers. I don't recall any changes to crypto in that
> timeframe.
>
> WRT to the original report, is only WEP causing problems
> (i.e. does WPA work?)
>
> --
> Bob Copeland %% www.bobcopeland.com
>
wpa works with wpa_supplicant, i haven't tested in a while, but i can as
soon as i get home. plain also works (no encryption). iirc, the original
"plaintif" experienced the same.
to keep things accurate, i have experienced again a lock up (kernel
panick) while i was trying to get the wlan0 up (ath5k), and getting
errors, so now i have switched back to ath-pci (madwifi). there might be
something wrong with my hardware (additionally).
--
nanok
next prev parent reply other threads:[~2010-03-25 23:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 23:04 Bug: 2.6.32 ath5k, associating with WEP128 AP is unreliable Don Darling
2010-01-25 17:39 ` Bob Copeland
2010-01-25 17:44 ` Gábor Stefanik
2010-01-25 18:52 ` Larry Finger
2010-01-25 19:21 ` Gábor Stefanik
2010-01-25 21:13 ` Bob Copeland
2010-01-26 2:36 ` Don Darling
2010-03-21 20:49 ` nanok
2010-03-25 21:02 ` Bob Copeland
2010-03-25 21:04 ` Bob Copeland
2010-03-25 22:24 ` nanok
2010-03-25 22:44 ` Bob Copeland
2010-03-25 23:04 ` nanok [this message]
2010-03-26 3:52 ` Bob Copeland
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=20100325230445.GB7547@spartakus \
--to=rnanok@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=nanokk@gmx.net \
/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).