2.6.1: atkbd.c errors + mouse errors with a belkin KVM
I'm seeing some strange behavior using kernel 2.6.1 and a Belkin KVM. I have talked to two others who have seen the same problem. This did not happen in 2.6.0 or any 2.4 kernel.
When switching ports using the keyboard, that is hitting scroll lock twice and then the port # I want ( 1 - 16), then coming back the same way, I often get the following error:
kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
I have also seen this same error while switching from X11 to console, but only once. In that one case, I lost mouse control, and keyboard control, and was unable to regain either. I had to reboot to rectify the situation.
I'm not sure if this happens when pushing the buttons on the front of the kvm.
KVM Information:
Belkin Omniview Matrix2 , Model F1DM216T
Maufacturer URL: http://catalog.belkin.com/IWCatProductPage.process?Merchant_Id=1&Product_Id=122933
Is there any further information I can submit to help solve this?
Quoted 5 lines · fire-eyes
I'm seeing some strange behavior using kernel 2.6.1 and a Belkin KVM. ... I often get the following error:
kernel:
atkbd.c: Unknown key released (translated set 2, code0x7aon isa0060/serio0).
It is not really an error - the kernel is just being a bit noisy. The 0x7a was really 0xfa, the ACK that a keyboard command succeeded.
Sooner or later the noise will go away. For now it is more interesting to fix bugs in behaviour.
Quoted 5 lines · Andries Brouwer
Quoted 3 lines · fire-eyes
I'm seeing some strange behavior using kernel 2.6.1 and a Belkin KVM. ... I often get the following error:
Quoted 8 lines
Quoted 2 lines
kernel:
atkbd.c: Unknown key released (translated set 2, code0x7aon isa0060/serio0).It is not really an error - the kernel is just being a bit noisy. The
0x7awas really0xfa, the ACK that a keyboard command succeeded.Sooner or later the noise will go away. For now it is more interesting to fix bugs in behaviour.
Well, the kernel is quite rightfully noisy at this point - getting unexpected ACKs is rather suspicious.
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Quoted 11 lines · Vojtech Pavlik
Quoted 8 lines
Quoted 2 lines
kernel:
atkbd.c: Unknown key released (translated set 2, code0x7aon isa0060/serio0).It is not really an error - the kernel is just being a bit noisy. The
0x7awas really0xfa, the ACK that a keyboard command succeeded.Sooner or later the noise will go away. For now it is more interesting to fix bugs in behaviour.
Well, the kernel is quite rightfully noisy at this point - getting unexpected ACKs is rather suspicious.
Yes, I do not propose that you remove the noise today. But nothing is wrong.
Several utilities access the keyboard directly. (For example X and kbdrate.) Since setting keyboard rate and starting X are rather common actions, most people will see these messages a few times in their syslog.
A few months from now, when we are satisfied that the keyboard code is in perfect shape, these messages can be silenced by default.
Andries
Quoted 14 lines · Andries Brouwer
Quoted 11 lines · Vojtech Pavlik
Quoted 8 lines
Quoted 2 lines
kernel:
atkbd.c: Unknown key released (translated set 2, code0x7aon isa0060/serio0).It is not really an error - the kernel is just being a bit noisy. The
0x7awas really0xfa, the ACK that a keyboard command succeeded.Sooner or later the noise will go away. For now it is more interesting to fix bugs in behaviour.
Well, the kernel is quite rightfully noisy at this point - getting unexpected ACKs is rather suspicious.
Quoted 6 lines
Yes, I do not propose that you remove the noise today. But nothing is wrong.
Several utilities access the keyboard directly. (For example X and kbdrate.) Since setting keyboard rate and starting X are rather common actions, most people will see these messages a few times in their syslog.
kbdrate is supposed to use the ioctls, as is X. Actually kbdrate does use the ioctls on my systems.
Quoted 2 lines
A few months from now, when we are satisfied that the keyboard code is in perfect shape, these messages can be silenced by default.
Actually, I think they could stay, because they'll not happen under normal circumstances by then.
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR