From: Andrew Morton <akpm@linux-foundation.org>
To: jmerkey@wolfmountaingroup.com
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: 2.6.27-rc3-git6 busted-ass iwl3945 driver drops packets with WEP enabled
Date: Wed, 20 Aug 2008 17:50:54 -0700 [thread overview]
Message-ID: <20080820175054.0795eecb.akpm@linux-foundation.org> (raw)
In-Reply-To: <1749.69.2.248.210.1219253222.squirrel@webmail.wolfmountaingroup.com>
On Wed, 20 Aug 2008 11:27:02 -0600 (MDT)
jmerkey@wolfmountaingroup.com wrote:
>
> On an Acer 9410 laptop with dual core processors, the iwl3945 driver has
> intermittment receiver lockup problems (stops receiving packets) using the
> Linux iwl3945 drivers with WEP encryption enbaled. The adapter works fine
> without WEP or WPA. If the same system is booted to Windows Vista (which
> takes about 15 minutes to boot because Vista is a fat slow pig) the
> wireless drivers work fine with WEP under Vista on the same system.
>
> If the system copies the ndis .sys drivers and I build ndiswrapper (which
> has to be really hacked up to build on 2.6.27) and use the ndis drivers on
> 2.6.27-rc3 with a modified ndiswrapper, they work fine.
>
> I suspect the firmware or an interaction with the firmware settings since
> when the system is booted to Vista after running 2.6.27-rc3 with the
> iwl3945 drivers, I have to power cycle the system periodically after
> running the iwl3945 driver to get the drivers under Vista to work again,
> but not always.
>
(cc linux-wireless)
Was 2.6.26 OK?
next parent reply other threads:[~2008-08-21 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1749.69.2.248.210.1219253222.squirrel@webmail.wolfmountaingroup.com>
2008-08-21 0:50 ` Andrew Morton [this message]
2008-08-21 4:27 ` 2.6.27-rc3-git6 iwl3945 driver drops packets with WEP enabled jmerkey
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=20080820175054.0795eecb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jmerkey@wolfmountaingroup.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;
as well as URLs for NNTP newsgroup(s).