I'm hoping this is the right place to put this, since other people were talking about mice.
So, I'm a gamer and recently started using Razer's Naga Epic mouse (no official drivers exist for it yet, but in a few weeks they'll be out). It was working just fine until last night.
Usually, when I connect the mouse, my MBP tells me that it's detected a new keyboard, since the thumb panel functions as a number pad. This would happen in wired or wireless mode. (Wireless mode works by plugging into a base which then communicates with the mouse.)
This is where things get weird. All of a sudden, the base just isn't being recognized. It's still getting power via the USB port, but it's not actually connecting for whatever reason. Wired mode works fine for the mouse -- except for the part where plugging it in causes a kernel panic.
I'm thinking this may have been caused by using CleanMyMac - which probably wasn't a good idea. It just seems a little more than coincidental.
What I'm wondering is if there is a way to just completely reinstall all of my USB drivers. Is all of that stuff on my install discs? Will that even fix what I've got going on? Everything works fine on my husband's Windows PC - I updated the mouse's firmware last night to see if that would help, and whereas before, it would lose any special settings that I set up on Windows (specific color configurations and sensitivity, mostly), this time, when I moved from one computer back to the other, these settings appear to have stuck, in both wired and wireless modes.
I'm mostly confused, and so far Razer Support is as well.
I have gotten this escalated to Razer engineers, at least. Here's a copy of the latest kernel panic report (caused by UNPLUGGING the mouse, this time - I should note that I installed the prefpane for the regular Naga just to see if it would help with the Naga Epic, that's the razernaga.kext you see):
Interval Since Last Panic Report: 155875 sec
Panics Since Last Report: 3
Anonymous UUID: 9CBC2B72-35B5-4B7B-9F83-C9CEB0258890
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10J567
Kernel version:
Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)
Kernel panics can be caused by only two things: faulty hardware, and buggy or conflicting kernel extensions. NOTHING ELSE can cause this problem.
You have so many third-party kernel extensions installed, you're lucky you can boot at all. In the panic log you submitted, the DoubleCommand extension is directly implicated. Delete it and reboot.
Right, so I figure that plugging in causes some extensions to conflict. My current setup is pretty old, so I'm not surprised that there's a large number of third-party stuff. I'm very in to the idea of not starting completely fresh with each new system.
shrug
Re: DoubleCommand - nothing in the Extensions folder so I just canned the prefpane. Hopefully that takes it out with it, because I sure couldn't find that .kext. Which may be the problem.
That might fix the kernel panics, but the issue with the wireless dock not being recognized is another one entirely, I suppose.
Kernel extensions can be installed anywhere, but unless they're in /System/Library/Extensions, they don't load automatically by default. Make sure DoubleCommand didn't install anything in /Library/LaunchAgents or /Library/StartupItems that might have loaded its extension.
Ah, ding-ding. Kext was in StartUpItems. What I'm betting was going on was that because the side thumb panel functions as an additional keyboard, DoubleCommand (which I haven't used since 2007, so it needed to go anyway) didn't know what to do with it and freaked out. At least this makes sense to me. Thanks for your help.
Now, to figure out the wireless. Which probably doesn't have a single thing to do with kexts...
The mac drivers for the Razer Naga Epic just came out, but when I run the installer, I don't get a new item in the system preferences. Has anyone else run into this?
