Do you have more than around 10 wireless networks in your vicinity? I have noticed that if I have more than 10 (more than can be displayed by nsGUI), I get KP. If you change the mode to mode 2 and then turn on, do you still get KP? Or if you go to a deserted place where there are fewer wireless networks do you still get KP?
I am using iwi2200 for Intel 2200 but your issue sounds very familiar. Mine only works if there are few wireless networks around.
One more thing I notice is that whenever I boot and start nsGUI, it will hang (not responding in activity monitor and I cannot kill the process either in activity monitor OR in shell mode. I log off and log back in again, then it works. This pretty consistent.
I am using iwi2200 for Intel 2200 but your issue sounds very familiar. Mine only works if there are few wireless networks around.
One more thing I notice is that whenever I boot and start nsGUI, it will hang (not responding in activity monitor and I cannot kill the process either in activity monitor OR in shell mode. I log off and log back in again, then it works. This pretty consistent.
Hey, yes i think i do, and no i havent tested it on a deserted place (could try but its pretty difficult around the city to find a deserted place). Can you explain to me the changing the modes you mention please?
I've been testing the new release (iwi3945 rev 660) and I'm get this messages on the console i cant understand. I posted this messages in the file called LOOP2.rtf. I'm not able to turn the card on as I was before, and about 15 mins after the kext is loaded got a KP.
I dont know if a m doing anythig wrong but just in case these are the steps am following:
1. get the files from the svn trunk with SyncroSVNClient.
2. compiling both The network Selector project and the iwi3945 project (ignoring the 22 warnings and 21 errors. is this right???)
3. loading the kext with Terminal and copying the compiled NetworkSelector in to the extensions directory
4 Execute the network selector and start debuging
I'm still getting KP at reboot when the driver is loaded. Here are my logs


