Logitech elite duo wireless troubles
 

Hi,

I got a really annoyinqg problem with my keyboard, its the logitech elite duo wireless model.q I know that logitech doesqn't support linux but qi need to know if anyone else has haqd this problem or knows a fix. When i'm typing it randomly qputs the letter Q in every now and then and sometimes worse then others. q

Example: (you can really just read the above and see all the Q's everwhere.)q qI will just type and it will qtype Qq's everywhere, no matter what key i'm using. Sometimes every key i strike it thqrows a Q up onto the screen!

I can go back and delete them (the Q's), but it gets really annoying qand it seems to make the problem worse.

Please help!! TIA

I have the same Logitech cordless Elite Duo setup (mouse and keyboard) and they work fine (notice no strange q's inserted). :P

Maybe check your XF86Config file to see if there is something strange going on in there and you can also check your keymaps directory to see if it recognizes the proper keyboard setup.

Without knowing what distro, wm or any other info its hard to give any answer other than just guesses.

rberry88

I'm running redhat 9

Could someone with a working Elite duo setup paste up a copy of their XF86Config file, it would be greatly appreciated.

Thank you.

The keyboard section:
The mouse section:

Pretty basic setup but it all works, the only strange thing is that the wheel on the keyboard also works to scroll and I'm not sure how to adjust the settings for it. The mouse side button works as "back" in Mozilla and in Opera it acts as "rewind" and I don't see any settings for this anywhere.

But since it all works I'm not ready to break it and start over.

rberry88

Thank you, hopefully i can use that and get it working. Thanks again!

I am also running RH 9.0 with the Cordless MX Duo (Cordless Elite Keyboard / MX700 Mouse) and experienced a similar problem when running the keyboard / mouse receiver through a KVM Switch (iogear MiniView Micro). I have just now plugged the keyboard directly into my Linux box and have not seen any q's so far!

FWIW, I don't think it is an X-config issue as I also tried the keyboard (through the switch) running in console mode only and experienced error messages regarding invalid escape sequences.

Note that I have not had any problems (so far) with the keyboard through the KVM switch when running WinXP (Dual boot with Linux) or my Win2K Laptop.

My thinking is that the KVM switch has some problems with the wireless link (iogear does not support wireless through their switch), but where Windows ignores these characters, Linux tries to use them???

If it's wireless, make sure there's no interference. This may not be an OS problem.

your manual should have some info on interference.

I can't use my new wireless mouse on my wacom tablet, because the tablet interferes with the mouse.

:(

Thanks dittohead, the RF interference makes more sense to me, but I've tried moving the receiver to several locations with no change in the quirky performance -- or course it's hard to find a spot on my desk without some kind of EM radiating device nearby!

What doesn't make sense is that I see no spurious characters on either of my windows machines -- one of which _is_ my Linux box as well, when running through the KVM switch. But I do get them in Linux, both at the console and under X (through the KVM).

So far, no problems under Linux with the Keyboard plugged directly into the PC.

However the other variable is that the KVM switch is strictly PS/2 connectors but currently I have the receiver plugged in via it's USB port. A bit more runtime under Linux - direct - USB and I'll switch to the PS/2 connectors.

John

Hmm, quite strange.

Sorry I couldn't help more, it seems that the kvm switch maybe what's doing it.

I don't know KVM switches much, but The Screen Savers (a show on techtv cable station) use them quite a lot. Their problem with them most of the time is they don't last a very long time like most other peripherals.

You can try psoting in their forums: www.thescreensavers.com

But if you aren't getting any problems in windows, but you are in a linux, it makes me wonder if maybe the keyboard sends out special keycodes that alert the windows drivers of battery low, rf interference etc, that show up in linux as "q". Because they only showup in linux when the KVM switch is on, maybe the kvm switch doesn't translate well?

I'm out of ideas, I hope you find something.

spurrious q's with logitech elite duo wireless keyboard and linux
 

well misery loves company. I have the exact same problem with my wireless elite duo connected to a kvm switch. the q's never appear on either xp system but always appear on all linux versions on both boxes. RH9, RH8 and Java Desktop Services all exibit same problem. I also noted that the backspace key will almost always (99% of the time) generate the q but that a control-h or control-8 will not generate the q and will do the destructive backspace. further, there is an accumulation of q's if you do not type anything and then start to type. it's clear to me the keyboard and kvm are operating the same irrespective of the os. my guess is the logitech elite duo driver on windows is chucking the erroneous q's when then come in. wish i had a solution other than plugging the keyboard into the machine. i also noticed my wireless mouse gets stuck, true on all os's, and i need to pick it up and put it down to get it to move. weirdness.

any answers?
 

Hi.
I've got the same problem.
logitech cordless desktop pro/ KVM switch.
The letter "q" appearing for long stretches, but not all the time.
Funny thing is it only happens sometimes and only on the main Debian box(shuttle).
My second computer is Debian as well but no "escape sequences" there as far as i can tell.
And it only started to happen recently.
So I am going to change the batteries on the keyboard and see what happens.
Will report back for posperity.
Love to hear any feadback from the previous posters.
regards.
g

spurrious q's with linux
 

I removed the kvm switch and everything works peachy. Changing batteries on the wireless keyboard had no effect.

Logitech Mouse and Keyboard
 

I know this is an old post but hey.....

I have the exact some problem on my Logitech Wireless Elite Duo. But herein I think lies your answer. I started sucking batteries like crazy with this keyboard and mouse, so I called logitech and they replaced the keyboard and mouse without question. They let me keep the old one and I setup the new one for home use, using the old one at work. Now I run fedora at work and home, but I get the Q problem at work only. So there is a problem with these early keyboards, not all of them mind you, just some of them. I also have very odd channel problems on the old keyboard and mouse where they will randomly flip channels then neither works and they both lock up. Solution recycle them and bought two new ones....you might want to try logitech for a replacement.

Cheers,

DH

i am using the wireless elite duo through a kvm a well... on fedora, & i had this problem, except it was the letter w.

the only solution i could find was to unplug & re-plugin the keyboard.

I have the same setup, wMX700 DwUO, and a KVM :D

Yet my problem is different, I don't get q's, instead I get a w after I use the backspace, everytime I use the backspace.

Also the mouse fritz's when I switch sometimes. Kind of annoying, Prolly just going to buy a regular wkeyboar an mouse for my linux box, and screw the KVM.

I also have the same problem, not the letter q, but as others have stated, I get the letter w. The problem is a little more intricate but the same nonetheless:

K/M: Cordless MX Duo
KVM - Belkin 4 Port
OS': Windows XP + Red Hat 8.0

I have found that when only the Windows box is connected, it all works fine. The MX Duo works fine, even if plugged through the KVM. The second I boot up linux, and switch over to the Linux box I start to get the random w's. What's even stranger is, if I then change back to Windows, the previously fully functioning mouse, completely locks up. I have to logout and back in for it to 'reinitialise' and work again.

Now, i'm currently booted into RH 8.0 with the MX Duo connected through Port 2 on the KVM and the Windows box is shut down. It all works fine. It's only once I start to flick between the 2 boxes that it causes problems.

I'd be interested to know, if anybody at all has been able to successfully use the Cordless MX Duo, through a KVM with Linux.

----

On a slighltly different, yet related problem. Has anyone managed to get the side buttons and scroll bar to work in RH 8.0 or any Linux for that matter? It's odd that the keyboard scroll works, but the mouse doesn't - I currently have it configured as a Generic 3 Button Mouse - any suggestions? I might give the posted XF86Config a go. Cheers.

http://www.linuxquestions.org/questi...94#post1073594

Yea! I got one working great under Redhat 9 with a KVM switch. I just re-wrote the keyboard event generator to eat the garbage scancodes. After reading this thread I think I know what the problem is......

The battery status indicator. Under XP the Logitech software displays a battery status my guess is that the keyboard periodically sends status messages/scancodes (perhaps triggered by BackSpace) and this is the problem.

Belkin KVM
 

I have been having the same problem that all of you have been having with the eratic behavior of the mouse and keyboard. At first my problem was that i would switch to another port and my keyboard would not work, but my mouse would work great. Now i have switched and am using a microsoft keyboard and mouse combo. After the switch to the different keyboard/mouse combo my mouse is now acting crazy when i switch between computers, however, the only thig that i see has changed (other than the obvious) is the fact that now the USB--->PS/2 converter has switched to the mouse end of he cable. So i am thinking that the problem is the converter. I have also read this on the SuSe forum board. I am going to bestbuy after class tonight to get a new combo which does not have the converter and i will post back and let you know my findings.

also, my previous keyboad was logitech MX Duo.

Well i have come to the conclusion that this KVM is just a POS.

Well it's definately a case of MS Windows activating something funky in the keyboard which is causeing the 'w' s after I press the back space. It also changes the scancodes for the little scrollwheel & the Go & Back buttons.

I wonder if when the battery levels get lower I'll get a 'q' ;-)

The good news is the patches I wrote & posted in another thread solved all my problems & it now works perfectly. So if any one wants either the patches or Redhat 9 XFree86 rpm's let me know.

Hi jadx, I would love a copy of the patches you've got mate. That would be awesome!
I have Email, ICQ, AIM or MSN - let me know which is your favoured method and your details. Thanks heaps.

OK Rayxen

See the message thread http://www.linuxquestions.org/questi...13#post1118813

Thanks mate, I shall check it out. I'm actually having more problems than before now. When I switch to the Linux box (RH) it all works fine at the moment (haven't tried your patch yet). Then when I switch back to Windows, I lose the mouse completely and can't get it back without a restart. If I then switch back to RH again the mouse is gone for good.

I'm about to give up on this whole KVM w/ the Logitech, it's simply not going to work. I think my best bet may be to buy another monitor, k/b + mouse. Hook up the 2 linux boxes with those and just leave the Logitech on the Windows box. Thanks, I'll try your patch as well.

I had similar problems but after downloading the latest drivers from Logitech and patching XFree86 it's all worked faultlessly for nearly a month now. I remember once I had to turn everything (all my computers & the KVM switch) off at the power points (not just at the computer) for things to start working properly. Thankfully that only happend once.

Hm... perhaps it will be worthwhile trying that. It will save me having to put another monitor on the desk. Well I've got the latest drivers that came on the CD, I'll check the website to see if their are new ones. I've actually got a new keyboard since my last problems. The copper contacts on the mouse wore out and the mouse would no longer charge in the base station. They sent me a whole new package.

I'll give it a go and hopefully it will all work. *Fingers Crossed* - thanks for the help and the patch.

Generally you can count on drivers shipped with products as being out of date. By the time the CD is cut, the product manufactured and shipped through wharehouses & the retail chain the drivers are most often superceeded.

Re: spurrious q's with linux
 

https://bugzilla.redhat.com/bugzilla....cgi?id=120937

I just got the wireless keyboard and I can't use it at all on anything but the login screen. No "q" issue. I have a KVM switch, but even when I haven't switched I have this problem. The cursor just blinks when I type. The mouse, otoh, works fine.

Fedora Core 2