Kernel errors with Logitech keyboard

Question

Level 1

0 points

Kernel errors with Logitech keyboard

Hello,

I have a core2duo iMac running 10.5 like a breeze. I have one problem though: my console log prints 4 lines of errors for each key i press. As you can understand, this is filling up the logs quite a bit. For every key i press, i get this:

5/21/08 7:39:03 PM kernel final dcConfig = 0
5/21/08 7:39:03 PM kernel returning 0
5/21/08 7:39:04 PM kernel final dcConfig = 0
5/21/08 7:39:04 PM kernel returning 0

This site and Google both dont give me any result, there isn't even a mention of something called dcConfig associated with OSX. I'm open to any suggestion at this point: maybe some keylogger running and being broken? Several scanning apps couldn't find anything, but I cant be sure my system is 'clean'.

The keyboard is a simple Logitech UltraX USB keyboard connected through a cheap noname usb hub. Bypassing the hub, the problem remains, so that isn't the problem.

Anyone have a clue?

iMac C2D, Mac OS X (10.5.2)

Posted on May 21, 2008 10:44 AM

Reply

Answer 1

dechamp

Level 4

3,495 points

May 21, 2008 2:29 PM in response to MichielH

The easy answer is that you probably don't have the proper drivers for your keyboard installed. The problem is that Logitech seems to have left Mac's out of their driver list for that model.

Logitech has many mice and other products that do not work well with Mac's. The more complicated or custom the device, the less of a chance for satisfaction.

Connect an Apple or a generic keyboard to your mac and see if the problem continues after a restarting with the Ultra keyboard disconnected. If the problem goes away then you'll probably have to work with Logitech for support.

The good news is that due to recent popularity changes, more software and hardware companies are taking a new look at their Mac product lines 🙂

Reply

Answer 2

MichielH Author

Level 1

0 points

Jun 13, 2008 11:33 AM in response to MichielH

Well, an unsupported keyboard is one thing (everything works fine with the keyboard, so I dont really see the need for additional drivers), but kernel errors is another thing. I dont think they should be happening. And if other people using the same keyboard are having the same problems, I think my Google search should be turning up a lot more results. I don't have another keyboard lying around, so I'm not able to test. I don't think Logitech can help with OSX giving kernel errors as well.

Reply

Answer 3

orangekay

Level 5

4,085 points

Jun 13, 2008 11:45 AM in response to MichielH

That's a Windows keyboard with keys whose functionality is specific to Windows, and even then they probably require a Logitech driver be installed to post meaningful key down events in the queue. Apple's keyboard driver likely has no idea what to do with the data these extra keys throw on the bus, so the fact that it logs errors is not surprising.

Reply

Answer 4

MichielH Author

Level 1

0 points

Jun 13, 2008 1:41 PM in response to orangekay

It logs an error with every key, it should know what to do with an 'a', and it does. It even knows what to do with the windows key.

Reply

Answer 5

orangekay

Level 5

4,085 points

Jun 13, 2008 2:21 PM in response to MichielH

So the keyboard is probably sending extraneous metadata with every keystroke; possibly indicating the state of a proprietary modifier, or just some random identifier garbage only their driver knows how to handle. Unless you can reproduce the problem with a Mac keyboard the fault lies entirely with Logitech engineers.

Reply

Answer 6

MichielH Author

Level 1

0 points

Jun 27, 2008 11:43 AM in response to orangekay

Well, the problem remains with an official Apple keyboard, so there goes the Logitech theory out of the window..

Reply

Answer 7

orangekay

Level 5

4,085 points

Jun 27, 2008 12:06 PM in response to MichielH

Then there may be a kernel extension to blame somewhere. Run this script:

http://www.khiltd.com/Downloads/ConsultantsCanary.tar.gz

It's going to spew out a list of all the third party background software it can find installed under your account into a Terminal window. Copy that list and paste it in here, editing out any personal information such as serial numbers and names you might not want floating around the internet.

Reply

Answer 8

MichielH Author

Level 1

0 points

Jun 28, 2008 2:15 PM in response to orangekay

Meh, that's kinda what i'm afraid of: some piece of software thats secretly logging my keystrokes causing this...

I've put up a log on http://www.mhil.net/cclog.txt

Your help is much appreciated 🙂

Reply

Answer 9

orangekay

Level 5

4,085 points

Jun 28, 2008 4:11 PM in response to MichielH

Looks like you've got Parallels Desktop and VMWare Fusion running at the same time. The only other mention of this specific error message I can find linked it to Parallels Desktop installation, so if you've got both products handy I'd try getting rid of Parallels and see if that helps.

Clearly there are a ton of files there so hopefully they give you an uninstaller. If not you'll have to weed them out manually.

Reply

Answer 10

MichielH Author

Level 1

0 points

Feb 18, 2009 6:49 AM in response to MichielH

Turns out, it wasn't Paralls causing the problems. It was Double Command, which I uninstalled at the same time.

Reply

Answer 11

MichielH Author

Level 1

0 points

Feb 18, 2009 6:50 AM in response to MichielH

See previous comment.

Reply