Greetingage:

I've googled this 'til my eyes glazed over. I have a problem with the
Debian kernel (2.4x, 2.6x, doesn't matter) throwing error messages related
to keyboard scancodes.

Kernel 2.4x
keyboard: unknown e1 escape sequence
keyboard: unrecognized scancode (65) - ignored

the message is slightly different with a 2.6x kernel. In addition to
these console messages, there are issues within X -- using a 2.4x kernel,
the letter "q" will appear at random while typing. In a 2.6x kernel, the
problem is extra (or missing) " " (spaces).

This prob has been dismissed repeatedly from what I've been able to find
as being imaginary, or a non-issue -- it is an issue, in that it makes the
system virtually unusable when logged into the console.

So. Before someone pipes up and tells me it's a hardware issue, let me
educate the masses further.

1) errors don't get thrown in DOS (6.x, or FreeDOS 9.x) 2) errors don't
get thrown in WinBlows (2K or XP) 3) errors don't get thrown with Fedora
(FC4) 4) errors don't get thrown with RedHat 5) mucking around with
xmodmap

(Note, this *is* my first go around with Deb -- been at this since '94
however, so it's not a newbie "lack of education" thing, and I administer
Linux for a living.)

The fact that the keyboard has no issues with other OSes led me to look at
the keyboard driver that's used with the Debian dist. I'm confused by
something.

Is there a reason that error handling is done the way that it is (ie: does
something depend on it)? If not, would someone let me know if there's
been discussion regarding *why* on earth the keyb handler doesn't just pop
garbage off the stack/buffer and discard it instead of doing what it does?
(the error handling in the driver seems overly complex to me).

Someone's solution for the problem was to comment out the error message in
the code and recompile. That's dandy in regards to not seeing the
problem, but the invalid code is still buffered and needs to go someplace,
so it's not a solution (just hides a symptom).

I'm willing to try fixing the issue and submit the patch for future
releases, but (and I say this with all sincerity) you probably don't want
any code I've written cluttering things up. I mentioned I administer
Linux for a living -- I didn't mention that my coding has been relegated
mostly to scripting for over 10 years (any C I write is going to be ugly
and covered in rust).

Or, is this moot? Has it been fixed already and I'm just looking in the
wrong spot? Gotta tell ya, after 4 days of screwing around, I'm ready to
drop Debian entirely and just stick with the others.

S.

On Wed, 25 Jan 2006 17:37:56 +0000, retyaH evetS wrote:


> Or, is this moot? Has it been fixed already and I'm just looking in the
> wrong spot? Gotta tell ya, after 4 days of screwing around, I'm ready to
> drop Debian entirely and just stick with the others.

Depends on where you have looked. Which Logitech cordless is it? It is
possible that it already has been defined. If not, I found these links
helpful when setting up a Logitech Media Elite. The only key I wasn't
able to get recognized was the Function Lock. I believe it's hardwired.

http://gentoo-wiki.com/HOWTO_Use_Multimedia_Keys

http://linux.seindal.dk/item65.html

http://www.linuxquestions.org/questi...d.php?t=125333

Thanksforthe feedback. I think the point of my prev iouspostwas missed
(the posted links wer ecompletely unrelated). I'm writing this messag
efrom the Debiansystem I'm tryingto configure. The typ osaren't typos --
they're a result of the key boarddriver not working properly.

Frankly,I don't really care about the hotkeys(Media ,Mute, Vo
lume,etc...) I just w antto be able to use the keyboard without having to
hit the spacebar twice at times, and without having tobackspaceover and
over a gain. *This* is what I've been fig htingfor 4 (oop .. 5) days now.
This only occurs with Debian. X/console works fine under RedHat and
Fedora. Console works fine under variousDOSes, and it works fine with MS
platforms.

FWIW, I ran 'xev' tonight to see if I could gatherany insight into the
problem. X sees the keyboard events that are responsible for the spaces
(or under 2.4.x,the letter 'q' ) as a "key release" event without a
corresponding "key press" event. At the lowest levels, a keyrelease
event , without a corresponding keypress event, should be discarded (which
was the point I was trying to make in my earlierpost).

Thoughts? I'm now oneday closer to torching myDebian installationand
throwingFC4 on this box -- something I'm intimately familar with , a
ndsomething that I know works without any screwing around.

S.

PS: Aren't all the friggin' spaces frustrating? It's 1000% worse when
you're trying to actually get work done. You can read "now oneday closer
to torching myDebian installationand" -- for some reason, the kernel
doesn't understand things like: "ls-al h" ... or: "psauxw |more"

Go figure. :-P

On Wed, 25 Jan 2006 14:22:57 -0500, thunder wrote:

> On Wed, 25 Jan 2006 17:37:56 +0000, retyaH evetS wrote:
>
>
>> Or, is this moot? Has it been fixed already and I'm just looking in
>> the wrong spot? Gotta tell ya, after 4 days of screwing around, I'm
>> ready to drop Debian entirely and just stick with the others.
>
> Depends on where you have looked. Which Logitech cordless is it? It is
> possible that it already has been defined. If not, I found these links
> helpful when setting up a Logitech Media Elite. The only key I wasn't
> able to get recognized was the Function Lock. I believe it's hardwired.
>
> http://gentoo-wiki.com/HOWTO_Use_Multimedia_Keys
>
> http://linux.seindal.dk/item65.html
>
> http://www.linuxquestions.org/questi...d.php?t=125333

I just got a LX710 myself and had problems in Ubuntu(Debian based),
looked around and could only find this thread and didnt get answer
from the Ubuntu community, heres what i did to somewhat fix the issue

*To Fix the Multiple Space Problem
Open keyboard prefrence
Increase delay for multiple keystroke
Decrease speed of repeated ke

--
spyke0
-----------------------------------------------------------------------
spyke01's Profile: http://unixadmintalk.com/67
View this thread: http://unixadmintalk.com/showthread.php?t=14191 (KDE/QT on Solaris)