logitech elite duo keyboard prints a 'q' when hitting backspace
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
One person said they called Logitech and got a replacement set which did not have any problems ( such as inserting characters ), while the old set continued to have them ( logitech did not require him to send in the faulty gear ). Unplugging and replugging the keyboard connector seems to be the fix du jour.
I do use a USB KVM switch, so I will be on the lookout for any problems after switching between Linux and Windows boxen.
I have noticed that when I have my KVM switched to my windows machine throughout the boot process, then switch to the linux machine and watch the full boot process it will switch back and forth with no problems of the 'w' occuring, when I started both machines at the same time, it screwed up.
I've just purchased 3 Logitech Cordless MX Duo keyboard/mouse sets and was having similar problems to what is described in this thread.
Basically you can see the problem by starting in run level 3 (Non gui) and running showkey
[root@posidon root] showkey -s
0xe1 0x5c 0xe1 0x39 0xe5 0x91
Every time I pressed the backspace. Which resulted in a 'w' appearing in X. This was VERY annoying. I have a suspicion that windows may be tinkering/programming the keyboard controller chip because after putting up with this problem for a week and writing a patch for XFree86 to eat the crap scancodes generated after the backspace. It's now entirely dissapeared and the only reason I can think of is I restarted one of my Linux systems last & the KVM switch was set to it. Unfortunately I cannot reboot my XP computer for the next few hours. (I'm rebuilding the Redhat 9 XFree86 rpms in a terminal window and it takes about 3 hours on the 333mhz that I use for that stuff)
Anyway the following patches solved my problems
---------------------------- cut here-----------------------------------------
Well I still do not know if XP is reprogramming the Keyboard controller but the Logitech software certianly does!. When I booted through Linux the little scroll wheel on the left of the keyboard was returning 0xe0 0x48 the same as the up arrow. I switched my KVM to XP and changed the scroll wheels function from scroll to switch apps and it now has a new scancode of 0xe2 0x81. The funny part is no matter what I do it keeps the new scancode. The good news (for me) is this will make it easier to use in X
Rebuild X to fix a Winbloze issue. Why didn't I guess that?? (smirk)
None-the-less, many, many bows and thanks to jadx for the patch. Until I know enough karate to rebuild X, the keyboard upluggaroo routine appears to work just dandy. Haven't tried the "boot to the linux box" trick ... yet! (wide grin) That would certainly simplify things.
FYI, here's the setup:
IOGear MiniView 4 port KVM (not a micro, *no* keyboard shortcuts, just one little ol' button on front to cycle the ports):
- (shiny new) Firewall running RH 9 on port A ... this post is its first foray into being a functional part of the LAN.
- Personal computer running XP Pro on port B
- Development system (ultimately ... old Notes server & CD farm) running RH 9 on port C
- Old Firewall (future undecided) running RH 7.2 on port D ... old reliable has been booting from a floppy forever and just refuses to quit, but it's too slow for content filtering and traffic shaping, plus whatever else I may decide to toss in there. (snicker)
Logitech Cordless Optical Trackman on a separate receiver
Logitech Cordless Access (early multimedia keys version) Keyboard on a separate receiver
As soon as I got the Cordless Access (no duo, single band receiver) and plugged it into the KVM ... POOF ... broken Linux all over the place. I was in the process of setting up the new firewall (using it now thanks to the replugaroo workaround), so the spurrious "w" characters were, shall we say, problematic. Fortunately (knocks on head) the TrackMan has been exemplary in its performance.
FYI, this IOGear KVM has been a trooper. Maybe it's the fact that it's just a button, but I've had it for years and years, and (knock on head) it's never even hiccoughed, except that time I shorted out the keyboard that was hooked to it. Port A wasn't the same for a while, but then it got better. (wipes forehead) (bemused grin)
Now to set up that development platform so I can figure out how to build things. (wrings hands expectantly)