Bug 9126 (Keyboard_first_key) - When push several keys on a POS keyboard model TA61100001 of WincorNixdorf, the first is not recognized
Summary: When push several keys on a POS keyboard model TA61100001 of WincorNixdorf, t...
Status: REJECTED UNREPRODUCIBLE
Alias: Keyboard_first_key
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 low
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-05 02:46 UTC by Roberto Muñoz
Modified: 2008-09-24 07:09 UTC (History)
3 users (show)

See Also:
Kernel Version: all 2.6
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Roberto Muñoz 2007-10-05 02:46:46 UTC
Most recent kernel where this bug did not occur: occur since kernel 2.6
Distribution: RedHat
Hardware Environment: POS (Point of Sell), all from WincorNixdorf, with keyboard TA61100001
Software Environment: Does not matter
Problem Description:
In drivers/input/keyboard/atkbd.c about line 535, there is this part of code:

/*
 * If the get ID command failed, we check if we can at least set the LEDs on
 * the keyboard. This should work on every keyboard out there. It also turns
 * the LEDs off, which we want anyway.
 */
                param[0] = 0;
                if (atkbd_command(atkbd, param, ATKBD_CMD_SETLEDS))
                        return -1;
                atkbd->id = 0xabba;
                return 0;
        }


That 'if' with the keyboard model TA61100001 of WincorNixdorf fail, so returns -1 and the driver is not set. In this case, when you push a key, it is not recognized, you must push it at least two times quickly to get one key.

Our temporary solution is comment that 'if'.

Steps to reproduce:

Boot the machine with a 2.6 kernel and the problematic keyboard connected. At the moment you change the keyboard with other wich works, and then returns to the problematic, its works
Comment 1 Dmitry Torokhov 2007-10-06 07:35:16 UTC
Does it help if you boot with i8042.dumbkbd parameter?
Comment 2 Björn Gerhart 2008-01-07 02:52:41 UTC
We can not reproduce the error in our office of Wincor Nixdorf with kernel 2.6.17. 

For further investigation, please give deeper information upon the issue. Kernel version and keyboard firmware version are important to know, as well as a more detailed description on how to reproduce the error and anything which may be of importance.
Comment 3 Roberto Muñoz 2008-01-09 08:21:13 UTC
We tried several 2.6 kernels up to 2.6.13. The above code is from version 2.6.13.

I don't know the firmware version. I guess, with the labels down the keyboard, is TA61100001 6d00109951 Siemens-Nixdorf. If it is not the version, tellme how to know it.

To reproduce, is very important to boot with the problematic keyboard connected and do not change it, because when a newer keyboard is plugged, the kernel loads the rigth driver and all works fine altough unplug and plug the problematic keyboard.
Comment 4 Niels de Vos 2008-09-24 07:10:47 UTC
I am currently out of the office and will be back on Monday the 29th of September.

Please contact the WNLPOS Team <wnlpos@wincor-nixdorf.com> for WNLPOS and general Linux issues.

Questions about JavaPOS should be redirected to <javapos@wincor-nixdorf.com>.

For other urgent issues Peter D

Note You need to log in before you can comment on or make changes to this bug.