On my system this is clearly a Network Manger bug, not a kernel/driver bug.
I have two kernels installed, 2.6.24-21-generic and 2.6.27-4-generic. When I boot the older 2.6.24 kernel I cannot connect using Network Manger, but I connect right away using wpa_supplicant from the command line. When I boot the newer 2.6.27 kernel, I am also unable to connect using Network Manger, but once again wpa_supplicant connects right away from the command line.
I am attaching four files showing syslog during attempts to connect using NM and wpa_supplicant on the 2.6.24 kernel, and attempts to connect using NM and wpa_supplicant on the 2.6.27 kernel.
On my system this is clearly a Network Manger bug, not a kernel/driver bug.
I have two kernels installed, 2.6.24-21-generic and 2.6.27-4-generic. When I boot the older 2.6.24 kernel I cannot connect using Network Manger, but I connect right away using wpa_supplicant from the command line. When I boot the newer 2.6.27 kernel, I am also unable to connect using Network Manger, but once again wpa_supplicant connects right away from the command line.
I am attaching four files showing syslog during attempts to connect using NM and wpa_supplicant on the 2.6.24 kernel, and attempts to connect using NM and wpa_supplicant on the 2.6.27 kernel.