linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Paul Bolle <pebolle@tiscali.nl>, linux-wireless@vger.kernel.org
Subject: Re: [iwl4965] Microcode SW error detected
Date: Thu, 26 May 2011 12:26:48 -0500	[thread overview]
Message-ID: <1306430810.3151.4.camel@dcbw.foobar.com> (raw)
In-Reply-To: <20110525131130.GA3260@redhat.com>

On Wed, 2011-05-25 at 15:11 +0200, Stanislaw Gruszka wrote:
> On Tue, May 24, 2011 at 06:50:53PM +0200, Paul Bolle wrote:
> > On Tue, 2011-05-24 at 09:09 +0200, Stanislaw Gruszka wrote:
> > > What is your configuration (mode,
> > > encryption, do you use wpa_supplicant or NetworkManager, which version,
> > > etc ...)?
> > 
> > 0) Mode as is displayed in iwconfig output? That is "Managed".
> > 
> > 1) Encryption is wep (so, no wpa_supplicant).
> > 
> > 2) Currently using NetworkManager-0.8.4-1.fc14.x86_64.
> 
> I try to use WEP with one AP, no microcode errors. However with different
> NetworkManager version, not sure if it is important. I'll try lately on F-14. 
> What channel do you use? Is network 11n or 11g or mixed ? WEP is 40 bits or
> other?

If it makes a difference, NM 0.8.x uses only the 'wext' supplicant
driver and uses wpa_supplicant 0.6.x.  NM still requests periodic scans
about every 2 minutes as usual.

(F15+, ie NM 0.9, uses "nl80211,wext" and supplicant 0.7.3+git)

Dan

> > > I will try to reproduce locally. If I'll be not able to reproduce,
> > > I'll ask you for debug logs on broken, and working (i.e. 2.6.38) version
> > > for compare.
> > 
> > 3) Sure, no problem. But isn't 2.6.38 from before the iwlegacy split?
> Yes, it is. If the problem was introduced during driver split (that
> happen in 2.6.39), one way to find a fix would be compare driver
> behaviour before the split and after.
> 
> Stanislaw
> --
> 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



  parent reply	other threads:[~2011-05-26 17:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 11:45 [iwl4965] Microcode SW error detected Paul Bolle
2011-05-24  7:09 ` Stanislaw Gruszka
2011-05-24 15:54   ` Paul Bolle
2011-05-24 16:03     ` Stanislaw Gruszka
2011-05-24 16:50   ` Paul Bolle
2011-05-25 13:11     ` Stanislaw Gruszka
2011-05-25 13:31       ` Paul Bolle
2011-05-31 13:37         ` Stanislaw Gruszka
2011-06-06  8:58           ` Paul Bolle
2011-06-06 11:36             ` Stanislaw Gruszka
2011-06-06 18:29               ` Paul Bolle
2011-05-26 17:26       ` Dan Williams [this message]
2011-06-07  6:32 ` Bernhard Schmidt
2011-06-07 14:54   ` Stanislaw Gruszka
2011-06-07 19:23     ` Paul Bolle
2011-06-08 13:47       ` Stanislaw Gruszka
2011-08-15 10:51         ` Paul Bolle
2011-09-04  8:28     ` Paul Bolle
2011-09-05  9:33       ` Stanislaw Gruszka
2011-09-05 10:32         ` Paul Bolle
2012-09-14 12:17         ` Paul Bolle
2012-10-15 14:51           ` Paul Bolle
2012-10-15 15:17             ` Stanislaw Gruszka

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=1306430810.3151.4.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=sgruszka@redhat.com \
    /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).