logitech elite duo keyboard prints a 'q' when hitting backspace
This is my first time posting here. I have a RH linux 8.0 box, running stock kernel ( 2.4.18-19.8.0mppe).
I recently purchased a Logitech Elite Duo wireless keyboard/mouse. It worked fine the first time I used it. After reboot it has starting doing something very annoying. Every time I hit the backspace key, it does the backspace but then it prints a 'q'. I have no idea why it is doing this or how to fix it.
If I hit the 'connect' button on the back of the keyboard it will stop doing that for maybe 5 minutes and then, just when I think it's safe to hit the backspace key, whammo, another 'q'. Also, besides the backspace, it will *sometimes* print a 'q' for no apparent reason.
I have a switch box that the keyboard/mouse/monitor are connected to so that I can switch between my linux box and windows box. I'm connected to the PS/2 port for these devices.
I've searched this site and google.com/linux with no luck.
Has anyone seen this before?
Any and all help is appreciated.
Logitech Cordless Mouse Prints 'q' in X11
I have a similar setup, with a Logitech cordless keyboard and an IO Gear 2-port KVM switch. The keyboard works fine in windoze and in linux console mode, but when I switch to X-Windows, the letter 'q' gets inserted in the X terminal, in Mozilla urls, etc - basically anywhere I type. This starts to happen as soon as the first backspace or up-arrow (to recall a previous command) is pressed. From then on, the q's start appearing at random times (inserting about one every 5 or 10 characters typed). I'm running RedHat 9.
I, too, would appreciate any help!
I have not yet figured out a way to keep this from happening altogether. The one thing that I have found to work when I start getting the 'q' problem is to unplug and replug the cord for the keyboard in the switchbox. Once I do that I get no more 'q' problems. However, the next time I reboot or log out of X, I get the 'q' problem and have to unplug/replug the keyboard cord again. I hope this helps!
I'm running SuSE 8.2, and I have a Cordless Desktop Optical with an aten CS12 KVM switch.
I can't solve this problem but I tried everything I found on the web.
The unplug/replug trick not working here.
Is there any new development on this?
qI have the same problem! I have a kvm switch too and the only time i get this problem is in linux.. works fine with windows. I run red hat 9q qand am clueless about this very very annoqying problem.
This works for me
I have not been able to find a permanent solution. The thing that works best for me is to make sure the switch box is switched to the linux box when you boot the linux box. Other than that, plugging/unplugging the mouse connection (input) to the switchbox is the only other thing that works (when I forget to switch the switchbox when booting) for me.
It is very annoying. Good luck. Please let me know if you ever find a solution.
Just adding another name to the list of people with this problem.
In this case a Logitech Duo MX (Cordless Elite Keyboard / MX 700 cordless mouse combo) through an ioGear MiniView Micro KVM switch; RH 9.0, Kernel 2.4.20-28.9, XFree86-4.3.0-2.90.43. Using XkbRules='xfree86', XkbModel='pc105', etc. in my XF86Config file.
What seems to be common to all of us is:
1. Logitech cordless Keyboard / Mouse combination (1 receiver for both, correct?)
2. Running the receiver using the PS/2 connectors through a 'smart' KVM switch (e.g. a switch which intercepts a keyboard combination to switch between computers, not a physical knob to accomplish this task).
3. No spurious characters under Windows (note that through the KVM & PS/2 neither of my Windows installs -- XP or 2K -- correctly detect the mouse).
4. Random insertions of q when working in Linux under X.
If we can narrow this down to a repeatable and identifiable set of circumstances, it may be we can get the attention of somebody who really knows how to fix this.
My only additional information is that I get errors in the console as well ('invalid escape code sequence') when I have the keyboard running through the PS/2 connectors to the KVM switch. Currently I have the keyboard plugged into the USB port of my PC (dual boot Linux / WinXP) and have no problems under Linux. Next step is to use the PS/2 connectors direct into the PC and see if I have problems.
qi have this too PLEASE help someone
SuSE Linux 9.0
Logitech Elite Duo wireless keyboard
I have a KVM switch and use the same Elite Duo on a Win2K system (it works fine there)
But on Linux, I get the random q problem - usually when I have had a slight delay in typing, or when I start a newline.
Anyone found a solution to this?
Anyone found a solution to this?
I too have the same (read similar :) problem
I have a Logitech Elite Duo Pro and a Laser (cheapo) brand KVM switch.
My setup works flawlessly in XP/ME/98 but under linux (two machines and 1 RH9 other Fedora Core 1) and I get spurious 'w' s appearing after I hit backspace..
The unplug the keyboard trick works here too, but thats DAMMN annoying..
Anyone got any ideas yet?
saqme problem here
I have the same problem with:q
Logitech Cordless Desktop MX (Elite Duo in US)
ATEN 4-port Switch (from what I heard qqit's a high quality brand)
Mandrake 9.2q, I have also tried with Mandrake 10beta (linux 2.6.2)q qwith same result
On Windows it works fine, my other 2 machine qon XP and one is on old 98SE.
That's very annoying especially when it comes to type passwords... you never sure of what you're typing.q
qI get the same problem also after hitting 'qDelete'.
or when I didn't type for some time I get like a row of qqqqqqqqqqqqqqqqqq
btw, how qcan I confugure the other qbuttons+scroqll on the mouse?
Based on what everyone has written, it does not sound like this keyboard is compatible with Linux -- have you considered adding this information to the HCL? -- J.W.
I am also experienceing the same problem and have logged a bug with Red Hat, bug id: 120937. As and when I get information I will post it into the forum.
Having played around with a similar problem, perhaps I can help with this:
Firstly, my setup:
-Box1 is a notebook running winXP
-Box2 is a VIA motherboard running Mandrake 9.2
-Keyboard and mouse are a Logitech Cordless Desktop (The older version, without all the multimedia buttons.)
-Switch-box is a cheap mechanical one; two pc's, each channel with two ps/2 and one vga connection.
The problem I experienced:
-When booting up, I always make sure that the pc currently booting has the keyboard and mouse.
-Works fine in Windows, I switch to Linux, works fine.
-But then, as soon as I switch back to Linux, no more keyboard. (I dont know about the mouse as I use different mice for each pc.)
-When I unplug the keyboard cable going into the windows box and plug it back in again, it works fine again.
I took the mechanical switchbox apart and found that the 5volt supply pin of both computers is connected to the keyboard input at all times, regardless of the switch position, by means of two diodes. So, whichever pc outputs a higher supply voltage supplies power to the keyboards.
I suspect the logitech wireless receiver does not like being switched around between two clock signals without being reset (ie re-powered up).
The fix I am planning is the following: If I place a little push button next to the switching unit's switch I could "reset" the keyboard by pushing this button and thereby disconnecting the power to the logitech wireless receiver for a second or so.
ie. every time the mouse/kboard/monitor is switched I would afterwards press this button and "simulate" the keyboard being plugged out and back in again....
Will let you know if it works (Once I find the time to actually try it out :) , meanwhile its back to plugging everything around manually...)
keyboard hardware reset
As promised in my previous message:
The keyboard hardware reset works great. I put a little switch next to the KVM switch's main buttons. Holding it disrupts the +5V supply to the keyboard.
Having done all of this I came accross the following: If the keyboard becomes "stuck" after switching (see my prev post) I can either push the new "hardware reset" button or -here_it_comes- the space key on the keyboard! I came accross this totally by coincidence, but it does work. The keyboard becomes un-stuck.
If I would have only known before taking my KVM switch box apart...
Weird... weird... :scratch:
|All times are GMT -5. The time now is 12:52 PM.|