From: wwguy <wey-yi.w.guy@intel.com>
To: Erik Hardesty <ehardesty@gmail.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: Problems with Intel Wifi Link 1000 on newer kernels
Date: Thu, 30 Jun 2011 16:12:49 -0700 [thread overview]
Message-ID: <1309475569.26211.3.camel@wwguy-ubuntu> (raw)
In-Reply-To: <BANLkTinEJ_XZcrV-SwRRJ=r1Heo0-YBhfA@mail.gmail.com>
On Thu, 2011-06-30 at 16:12 -0700, Erik Hardesty wrote:
> Forcing iwlwifi-1000-3.ucode results in the same issues. No change in
> linux 3.0-rc5.
>
> On Thu, Jun 30, 2011 at 9:19 AM, wwguy <wey-yi.w.guy@intel.com> wrote:
> > On Thu, 2011-06-30 at 02:51 -0700, Stanislaw Gruszka wrote:
> >> On Fri, Jun 17, 2011 at 01:14:11AM -0500, Erik Hardesty wrote:
> >> > Having trouble with iwlagn in kernels newer than 2.6.38.
> >> > I've tried 2.6.39 and 3.0rc3 and both give me the same problem.
> >> > I have the latest intel firmware installed on the system. Both
> >> > iwlwifi-1000-3.ucode
> >> > and iwlwifi-1000-5.ucode are in /lib/firmware
> >> >
> >> > Note: 2.6.38 does not exhibit the same issue and works fine.
> >>
> >> If there is no other proposition to fix the issue from Intel,
> >> perhaps you could bisect the problem.
> >
> > what if you remove iwlwifi-1000-5.ucode and force to use -3 version of
> > uCode; are you still seeing the problem with new kernel?
> >
then no idea :-(, maybe has to bisect it.
what exactally the problem you facing, do you have a bugzilla# ?
Thanks
Wey
> >
> >
> >
prev parent reply other threads:[~2011-06-30 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 6:14 iwlagn: Problems with Intel Wifi Link 1000 on newer kernels Erik Hardesty
2011-06-18 11:12 ` wwguy
2011-06-22 4:59 ` Erik Hardesty
2011-06-30 9:51 ` Stanislaw Gruszka
2011-06-30 14:19 ` wwguy
2011-06-30 23:12 ` Erik Hardesty
2011-06-30 23:12 ` wwguy [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=1309475569.26211.3.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=ehardesty@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--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).