From: reinette chatre <reinette.chatre@intel.com>
To: John Ranson <ranson@analager.net>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] iwlwifi 4965 uCode available
Date: Mon, 13 Jul 2009 14:42:14 -0700 [thread overview]
Message-ID: <1247521334.17896.1683.camel@rc-desk> (raw)
In-Reply-To: <bcd1ba70907131252x3d9e21bbx80241aba1edff5ba@mail.gmail.com>
Hi John,
On Mon, 2009-07-13 at 12:52 -0700, John Ranson wrote:
> Reinette,
>
> On Mon, Jul 13, 2009 at 11:56 AM, reinette
> chatre<reinette.chatre@intel.com> wrote:
> > John,
> >
> > On Mon, 2009-07-13 at 11:43 -0700, John Ranson wrote:
> >> I am also seeing frequent loss of association and firmware restarts
> >> with the new firmware. On occasion, I can't recover even when I
> >> reload the driver. Admittedly, I am using an old driver right now
> >> (2.6.29, I think).
> >
> > The better restart work was added in 2.6.31 I think, so it is only in
> > the recent driver that you will have a smooth recovery after a failure.
> > You may thus be seeing the same problem as Helmut, with him running the
> > recent restart code.
>
> Can I also get this with the latest compat wireless release and
> 2.6.30.1? I don't usually switch to a new kernel until it's been
> stable for a while.
yes - compat wireless contains all the latest code, which includes this
restart work.
>
> >
> >>
> >> I'm going to upgrade to 2.6.30.1 with the latest compat-wireless. I'll
> >> file a bug if things continue as they are.
> >
> > Even if the restart code gets you up and running smoothly after a
> > failure, please do submit a bug report so that we can look into this.
>
> I'll be sure to file a bug.
Thank you very much
Reinette
prev parent reply other threads:[~2009-07-13 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 21:21 iwlwifi 4965 uCode available reinette chatre
2009-07-09 23:13 ` [ipw3945-devel] " Rafał Miłecki
2009-07-09 23:26 ` reinette chatre
2009-07-13 20:30 ` Rafał Miłecki
2009-07-13 20:32 ` Rafał Miłecki
2009-07-13 20:38 ` reinette chatre
2009-07-13 20:43 ` Rafał Miłecki
2009-07-13 20:48 ` reinette chatre
2009-07-13 21:12 ` Rafał Miłecki
2009-07-12 12:45 ` Helmut Schaa
2009-07-13 15:46 ` reinette chatre
2009-07-13 18:29 ` Helmut Schaa
2009-07-13 18:43 ` [ipw3945-devel] " John Ranson
2009-07-13 18:56 ` reinette chatre
2009-07-13 19:52 ` John Ranson
2009-07-13 21:42 ` reinette chatre [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=1247521334.17896.1683.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=helmut.schaa@googlemail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ranson@analager.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