[kismac] Re: [OpenSVN] r84 committed.
- From: jesse@xxxxxxxxxxxxx
- To: kismac@xxxxxxxxxxxxx
- Date: Wed, 15 Feb 2006 17:48:28 +0200 (EET)
It has always worked for me, often without even turning it off. On
occasion it has taken a couple of tries. When I run into situations where
the airport hardware is disabled, or whatever is happening, I've just
opened up the terminal, cd'd to /system/library/extensions/ and typin in a
sudo kextunload and then a sudo kextload for the appleairport2.kext
driver, and it's back to normal.
Jesse
>>On Feb 14, 2006, at 10:07 PM, Robin L Darroch wrote:
>>
>>>Hi Seth,
>>>
>>>I think you've probably overestimated the reliability of passive
>>>mode airport extreme support, based on your sample of one. :) I
>>>rather doubt that you're the only one on the list who has tried to
>>>use KisMAC/airport-extreme-passive by first turning off the airport
>>>using the menu bar icon. I know that was the second thing I tried
>>>(after trying it *without* turning it off there, and having to
>>>reboot my computer to get the airport back online). Unfortunately,
>>>for many of us even turning the airport off first is not enough for
>>>KisMAC to be successful at passive scanning with Airport Extreme.
>>>I think perhaps other system processes are laying claim to the
>>>Airport and not relinquish that claim even when the airport is
>>>turned off... therefore, when KisMAC tries to load its passive mode
>>>driver, it clashes with one of those processes and dies,
>>>subsequently rendering the airport inoperative until the next
>>>reboot. This is why most people are successful following a safe
>>>mode reboot, but not after booting their computers normally even
>>>accompanied by switching the airport off prior to firing up KisMAC.
>>>
>>>I guess you can count yourself lucky that you're not running
>>>anything that causes a conflict!
>>>
>>>Cheers,
>>>Robin
Other related posts:
