From: Jeremi Thebeau <jeremi.thebeau@googlemail.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Intel Corporation PRO/Wireless 4965 AG or AGN randomly shuts off
Date: Thu, 1 Apr 2010 09:26:48 +0200 [thread overview]
Message-ID: <g2s4c251d3f1004010026rbb8030e0pc820fa75c96df52e@mail.gmail.com> (raw)
In-Reply-To: <1270056176.2446.3494.camel@rchatre-DESK>
Thanks Reinette,
I haven't played around much with ucode, linux modules, dirver and
applying patches. Do you have a suggestion for a good primer. I will
try to make sense of that ridiculously long bug when i get a chance.
Assuming I am able to install and patch, if the device drops off
again, are there any specific logs I should keep an eye on to help
test this patch?
Jeremi
On Wed, Mar 31, 2010 at 7:22 PM, reinette chatre
<reinette.chatre@intel.com> wrote:
> Hi Jeremi,
>
> On Tue, 2010-03-30 at 22:43 -0700, Jeremi Thebeau wrote:
>
>> jeremi@linux64:~$ uname -a
>> Linux linux64 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC
>> 2010 x86_64 GNU/Linux
>>
>> with Ubuntu Karmic 64 bit.
>
> Is it possible to give the latest driver code a try to ensure we are
> dealing with the latest features? compat-wireless may be an easy way for
> you to do this.
>
> We have seen some devices that essentially get disconnected from the
> platform, which seems to be happening here. We prepared a patch for this
> a while ago, but nobody with this issue has yet been able to test it.
> Perhaps you could? Please try
> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2037#c112 ...
> hopefully it will still be straight forward to apply.
>
> Reinette
>
>
>
next prev parent reply other threads:[~2010-04-01 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 5:43 Intel Corporation PRO/Wireless 4965 AG or AGN randomly shuts off Jeremi Thebeau
2010-03-31 17:22 ` reinette chatre
2010-04-01 7:26 ` Jeremi Thebeau [this message]
2010-04-01 15:45 ` reinette chatre
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=g2s4c251d3f1004010026rbb8030e0pc820fa75c96df52e@mail.gmail.com \
--to=jeremi.thebeau@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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