mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stefanik Gábor" <netrolller.3d@gmail.com>
To: "Larry Finger" <Larry.Finger@lwfinger.net>
Cc: free_beer_for_all@yahoo.com, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org
Subject: Re: WLAN regression before this morning
Date: Fri, 25 Jul 2008 18:01:16 +0200	[thread overview]
Message-ID: <69e28c910807250901q1f5924ambeb30a15e785b05a@mail.gmail.com> (raw)
In-Reply-To: <4889F7D6.4010706@lwfinger.net>

On Fri, Jul 25, 2008 at 5:57 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> I too have a problem with wireless in the current 2.6.26-gitX kernels. If
> you have done the git pull, you can try bisecting to find the problem. Use
> 'git bisect good v2.6.26' to mark a known good point. If you don't wish to
> take the time bisecting, then issue a 'git checkout v2.6.26'. That should
> give you a kernel that works.
>
> Larry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

I am also seeing problems - although I can connect to networks (with
zd1211rw, ath5k & sometimes with b43), it disconnects after about 2
minutes with a sudden "Removed STA"/"Destroyed STA" pair (no "assume
out of range" or anything). However, if I use wpa_supplicant to
connect to wepped networks (rather than just "iwconfig wlan0 essid
<ESSID> key s:<ASCII key>"), the problem goes away, and the connection
is stable for hours.

-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

      reply	other threads:[~2008-07-25 16:01 UTC|newest]

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

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=69e28c910807250901q1f5924ambeb30a15e785b05a@mail.gmail.com \
    --to=netrolller.3d@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=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

all inboxes | Powered by JetHome®