From: Pavel Roskin <proski@gnu.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Luca Venturini <lucventurini@gmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: New IWL4935 driver for Intel Wireless Cards does not support WPA2 wireless network with PEAP - MSCHAPV2
Date: Wed, 02 Apr 2008 15:48:05 -0400 [thread overview]
Message-ID: <1207165685.7840.5.camel@dv> (raw)
In-Reply-To: <20080402122440.GA24239@csclub.uwaterloo.ca>
On Wed, 2008-04-02 at 08:24 -0400, Lennart Sorensen wrote:
> Strangely I find with the 2.6.24 kernel currently in Debian, the intel
> wireless seemed to work great with WPA2 (at least on a 4965). Maybe
> that was 2.6.24.2 or 2.6.24.3 or something. It was a couple of weeks
> ago now. I haven't heard of the 4935 before.
Since nobody has mentioned that, it's possible to compile the latest
wireless drivers for the current kernel (starting with 2.6.18) thanks to
the compat-wireless package:
http://linuxwireless.org/en/users/Download
That should be of great help for those looking to use the latest
wireless drivers without having to recompile the currently used kernel.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-04-02 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 8:40 New IWL4935 driver for Intel Wireless Cards does not support WPA2 wireless network with PEAP - MSCHAPV2 Luca Venturini
2008-04-01 16:44 ` John W. Linville
2008-04-01 20:06 ` BuraphaLinux Server
2008-04-01 21:02 ` Luca Venturini
2008-04-02 0:54 ` Pavel Roskin
2008-04-02 12:24 ` Lennart Sorensen
2008-04-02 19:48 ` Pavel Roskin [this message]
[not found] <adKlV-3WV-5@gated-at.bofh.it>
[not found] ` <adS9O-4u9-1@gated-at.bofh.it>
[not found] ` <adUY2-379-7@gated-at.bofh.it>
[not found] ` <adVUj-5bx-81@gated-at.bofh.it>
[not found] ` <47F38267.2040301@fenrir.org.uk>
2008-04-02 15:30 ` Luca Venturini
2008-04-02 15:57 ` Filippo Zangheri
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=1207165685.7840.5.camel@dv \
--to=proski@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=lucventurini@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.