From: "John W. Linville" <linville@tuxdriver.com>
To: Hubert Tonneau <hubert.tonneau@fullpliant.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: 32 bits executables with 64 bits kernel wifi issue
Date: Wed, 2 Mar 2011 08:38:49 -0500 [thread overview]
Message-ID: <20110302133848.GA2536@tuxdriver.com> (raw)
In-Reply-To: <0B3412811@briare1.fullpliant.org>
On Wed, Mar 02, 2011 at 11:54:07AM +0000, Hubert Tonneau wrote:
> Hi,
>
> If I use a 32 bits kernel, then I can connect to any Wifi box,
> but if I use a 64 bits kernel with 32 bits executables,
> it will connect on some Wifi boxes (french Freebox), but fail to connect to others (french Livebox).
>
> The wifi driver used is iwl3945.
> When connection fails, WPA supplicant will report successfull association,
> but udhcpc will fail to get a lease.
> It does not seem to be related to a peticular kernel release: I tested with 2.6.36.4,
> but get the same problem with 2.6.32.28 64 bits.
>
> Regards,
> Hubert Tonneau
We have had a number of 32/64 compatibility problems with the wireless
extensions API in the past. I wonder if this is another one?
Does your version of wpa_supplicant support the "-Dnl80211" option
(instead of "-Dwext")? It might be worth trying that to see if it
works better?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-03-02 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 11:54 32 bits executables with 64 bits kernel wifi issue Hubert Tonneau
2011-03-02 13:38 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 18:03 Hubert Tonneau
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=20110302133848.GA2536@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=hubert.tonneau@fullpliant.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 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.