On 18-05-2004 10:05, "Brad Knowles" <brad.knowles@xxxxxxxxx> wrote: >> sometimes the driver fails to unload after a session, which currently >> requires a reboot to fix. i posted a question about that a while back, >> to which someone suggested using kextunload to remove the driver. i >> haven't actually messed with this yet, because i have another question >> about it. is the kismac driver tool move than just a gui for kextload >> and kextunload? because if not, then the shell commands would not be >> successful anyway and i'd be wasting my time learning about them. > > The KisMac driver tool is a complete wireless card driver, with > extra hooks to allow KisMac to do things it normally could not with > the standard drivers. When it starts, KisMac calls kextunload on the > existing OS driver and then kextload on the KisMac driver tool, and > does the process in reverse when shutting down. i have a very similar problem: quitting kismac, the macjack kernel extension won't unload if you first ejected the card or if the machine went to sleep with kismac running and the only solution i found is to reboot the machine.