On Sun, 8 Feb 2004, [iso-8859-2] Martin MOKREJ© wrote:
I tried latest kernel and I see some error logged by the system, Should I
worry?
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
This happens on 4.3.0 also, and is due to the X server directly
bit banging the keyboard controller to set the repeat rate. If
you look at the code, it first tries to use the new kernel ioctl,
then a fallback, then finally it does bitbanging if the previous
methods fail.
The kernel people believe that it should not ever directly access
the hardware, and that it should only use the ioctl, and if the
ioctl isn't available in your kernel (perhaps your kernel is very
very ancient), then X should not set the repeat rate at all.
The question then is: Why is the ioctl not working?
I am currently investigating this matter myself, and there are a
few possibilities that could be happening:
1) Compile time problem: The kernel headers on the machine that
X is being compiled on, do not have the KDKBDRATE ioctl
present, and so the code to use that ioctl does not get
compiled in.
or
2) The KDKBDRATE ioctl stuff gets built in, but at runtime the
ioctl is failing for some reason or another, thus the ioport
bitbanging occurs, and can totally hang the machine according
to kernel folk.
If anyone has any other possibilities, feel free to share. I've
written a small debugging patch to put into a future build in
order to peek into what's going on, but haven't gotten it into
test builds yet. Not an uber-high priority item however, so
it'll take a week or two probably for a test build to get out
there and get some feedback from people seeing this problem.
--
Mike A. Harris
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
