This I find puzzling, as I have trolled the various forums and wikis for days without finding a single instance of an MBP 4,1 user succeeding in getting a connection to a WPA/WPA2 wireless AP. Yes, it will connect to an open AP, so the problem lies in the current version of wpasupplicant, not ndiswrapper or any of the network-managers.
Originally Posted by cyberdork33
This is confirmed by using wpasupplicant directly, with config file /etc/wpa_supplicant/wpa_supplicant.conf
(No need for a more elaborate config file, as wpa_supplicant correctly picks up all necessary settings of the wireless AP. That directory in /var/run must be made first.) Then do
and stop it with Ctrl-C after some time. Then study the output in tmp: it appears that everything associates fine until the 4-way handshaking phase, when it somehow proceeds to reassociate, etc, until things time out.
$ sudo ifconfig wlan0 up
$ sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf -d > tmp
I've also tried Debian unstable with the 2.6.25 kernel... same problem.
P.S. The 2.6.25 kernel has solved the problem with usbhid, so the special fn-key works without the quirks work-around. The applesmc module still gives those never-ending error messages.
PP.SS. I'm abandoning my attempts at installing GNU/Linux directly to the hardware of the MBP 4,1 until I see reports of wpasupplicant having been fixed. I'll try and see whether a bug report (in Ubuntu Launchpad or Debian BTS) is indicated.