Linux wireless drivers development
 help / color / mirror / Atom feed
From: barry bouwsma <free_beer_for_all@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: WLAN regression before this morning
Date: Fri, 25 Jul 2008 08:20:09 -0700 (PDT)	[thread overview]
Message-ID: <761713.15647.qm@web46115.mail.sp1.yahoo.com> (raw)

Servus,

Last successfully built and used kernel was 2.6.26-rc8, about
the start of 29.Jun UTC or so.

Present build of GIT 2.6.26 during the merge window, updated
just before 06h UTC, today, 25.Jul.

With today's kernel, I am not even able to associate with a
WLAN less than two metres away from my ZD1211rw type USB
adapter, to say nothing of more distant WLANs with which I
could authenticate with the earlier code without problems --
I don't even come near the associate stage.

The networks all show up as expected in `iwlist wlan1 scan'
with decent strengths; while all I get from dmesg is
[ 1016.829827] wlan1: authenticate with AP 00:1X:YZ:AB:23:45
[ 1017.032769] wlan1: authenticate with AP 00:1X:YZ:AB:23:45
[ 1017.234213] wlan1: authenticate with AP 00:1X:YZ:AB:23:45
[ 1017.435402] wlan1: authentication with AP 00:1X:YZ:AB:23:45 timed out


If I've hosed myself with a new .config option, I'll be kicking
meself where it hurts most.  Else, back to -rc8 to both send
this message and to regain 'net access to do other needed so-
called `work', so sorry I haven't narrowed this down further...

And I'll feel me a fool if the failure is because I went from
a different (BSD) OS into 2.6.26-merge, while going from that
into -rc8 I promptly associate as desired.


thanks
barry bouwsma


      


             reply	other threads:[~2008-07-25 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 15:20 barry bouwsma [this message]
2008-07-25 15:57 ` WLAN regression before this morning Larry Finger
2008-07-25 16:01   ` Stefanik Gábor

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=761713.15647.qm@web46115.mail.sp1.yahoo.com \
    --to=free_beer_for_all@yahoo.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox