-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
after upgrading from 2.6.34 to either 2.6.35 or 2.6.35.1, wpasupplicant will
no longer associate to my WPA2 access point. The log is full of "Failed to
initiate AP scan" messages.
Is this a known issue? I couldn't quite find out by sifting through the
archives... The system is a Thinkpad T61, x86_64, Debian sid, network-
manager and wpasupplicant 0.6.10-2.
Cheers,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxnmlcACgkQXjXn6TzcAQnMGACfWGBirSDBKoTpgC0wbvVprU3W
U3wAmgKGiivAZdln14CdkBWIF2hJd+BS
=84Cy
-----END PGP SIGNATURE-----
On Sun, Aug 15, 2010 at 09:42:15AM +0200, Marcus Better wrote:
> Hi,
>
> after upgrading from 2.6.34 to either 2.6.35 or 2.6.35.1, wpasupplicant will
> no longer associate to my WPA2 access point. The log is full of "Failed to
> initiate AP scan" messages.
>
> Is this a known issue? I couldn't quite find out by sifting through the
> archives... The system is a Thinkpad T61, x86_64, Debian sid, network-
> manager and wpasupplicant 0.6.10-2.
>
> Cheers,
>
> Marcus
I'm not aware of this issue. Please open a bug at bugzilla.kernel.org.
Please include dmesg output for starters.
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John W. Linville wrote:
> I'm not aware of this issue. Please open a bug at bugzilla.kernel.org.
https://bugzilla.kernel.org/show_bug.cgi?id=16610
Cheers,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxqNcwACgkQXjXn6TzcAQknwQCgk+c05IofA8KG6J+OP9nGD4m1
E6MAoLQSThgPu0+8io9HUuBNISNIs5zX
=+wgZ
-----END PGP SIGNATURE-----